Articles de revues : « Software development companies »

1

AXINTE, Sabina-Daniela. « Security Challenges for Software Development Companies ». International Journal of Information Security and Cybercrime 5, n^o 2 (29 décembre 2016) : 9–16. http://dx.doi.org/10.19107/ijisc.2016.02.01.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

2

Aramo-Immonen, Heli, Hannu Jaakkola et Harri Keto. « Multicultural Software Development ». International Journal of Information Technology Project Management 2, n^o 1 (janvier 2011) : 19–36. http://dx.doi.org/10.4018/jitpm.2011010102.

Texte intégral

Résumé :

Productivity management is a challenge for software engineering companies and, in this regard, there is a current trend toward globalization. Via acquisitions and mergers, business has become international and employs different national cultures. Therefore, the focus of this article is on the understanding of cultural differences affecting productivity in globalized software production. The relation between productivity and non coding activities in software development projects has not been proven. Software development is expert work, typically made in closely collaborating local teams and global distribution of expert work increases the degree of difficulty. In this paper, the authors analyze multicultural ICT companies from their productivity perspective through the lens of cultural differences. The purpose of this study is to report findings based on general cultural studies and reported experiences that seem to affect productivity in the software industry. Some company cases are also described and analyzed.

Styles APA, Harvard, Vancouver, ISO, etc.

3

Sambhanthan, Arunasalam, et Vidyasagar Potdar. « Green Business Practices for Software Development Companies ». International Journal of Enterprise Information Systems 11, n^o 3 (juillet 2015) : 13–26. http://dx.doi.org/10.4018/ijeis.2015070102.

Texte intégral

Résumé :

This paper reports the findings of a text analysis of the corporate sustainability reports of eleven large scale Indian Software Development Businesses for the period of 2012 to 2014. The results shows that there are twenty two reported components of software development sustainability namely green buildings, green energy, green factory, green data centres, green infrastructure, green initiatives, green innovation, green packaging, green portfolio, green power, green practices, green procurement, green products, green program, green rating, green solutions, green space, green team, green tech and green supply chain which are addressed in the published reports of Indian software development businesses. The reports were further analysed to infer some knowledge on how the software development companies could contribute to green environment and the possible environmental impacts of these contributions. Finally a number of generalised conclusions were derived and followed by a set of implications for best practices in green software development as the outcome of the research reported in this paper.

Styles APA, Harvard, Vancouver, ISO, etc.

4

Nunes, Nuno J., et Joao F. Cunha. « Wisdom : A Software Engineering Method for Small Software Development Companies ». IEEE Software 17, n^o 5 (septembre 2000) : 113–19. http://dx.doi.org/10.1109/52.877877.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

5

Eito-Brun, Ricardo, et Miguel-Angel Sicilia. « Innovation-Driven Software Development : Leveraging Small Companies' Product-Development Capabilities ». IEEE Software 33, n^o 5 (septembre 2016) : 38–46. http://dx.doi.org/10.1109/ms.2016.63.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

6

Jankovic, Marko, Slavko Zitnik et Marko Bajec. « Reconstructing de facto software development methods ». Computer Science and Information Systems 16, n^o 1 (2019) : 75–104. http://dx.doi.org/10.2298/csis180226038j.

Texte intégral

Résumé :

Software development is a complex process that requires disciplined engineering approaches. Empirical studies show that companies still don?t document their development practice, or if they do, these are not up-to-date and do not reflect how they really develop software. The main objective of this paper is to propose an approach that can help companies in documenting their real development practice. Comparing to existing approaches that require substantial effort on the side of project members, our approach extracts information on development practice directly from software repositories. Five companies have been studied to identify information that can be retrieved from software repositories. Based on this, an approach to reconstruct development practice has been developed. The approach has been evaluated on a real software repository shared by an additional company. The results confirm that software repository information suffice for the reconstruction of various aspects of development process, i.e. disciplines, activities, roles, and artifacts.

Styles APA, Harvard, Vancouver, ISO, etc.

7

Herala, Antti, Jussi Kasurinen et Erno Vanhala. « Views on Open Data Business from Software Development Companies ». Journal of theoretical and applied electronic commerce research 13, n^o 1 (janvier 2018) : 91–105. http://dx.doi.org/10.4067/s0718-18762018000100106.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

8

Giardino, Carmine, Nicolo Paternoster, Michael Unterkalmsteiner, Tony Gorschek et Pekka Abrahamsson. « Software Development in Startup Companies : The Greenfield Startup Model ». IEEE Transactions on Software Engineering 42, n^o 6 (1 juin 2016) : 585–604. http://dx.doi.org/10.1109/tse.2015.2509970.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

9

Colenci, Alfredo, et Edson Walmir. « A referencial model for small companies of development software ». IEEE Latin America Transactions 9, n^o 1 (mars 2011) : 823–29. http://dx.doi.org/10.1109/tla.2011.5876426.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

10

Paternoster, Nicolò, Carmine Giardino, Michael Unterkalmsteiner, Tony Gorschek et Pekka Abrahamsson. « Software development in startup companies : A systematic mapping study ». Information and Software Technology 56, n^o 10 (octobre 2014) : 1200–1218. http://dx.doi.org/10.1016/j.infsof.2014.04.014.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

11

Goldoni, Vanessa, et Mírian Oliveira. « Knowledge management metrics in software development companies in Brazil ». Journal of Knowledge Management 14, n^o 2 (6 avril 2010) : 301–13. http://dx.doi.org/10.1108/13673271011032427.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

12

Xu, Peng, et Yurong Yao. « Methodology Fit in Offshoring Software Development Projects ». Information Resources Management Journal 27, n^o 4 (octobre 2014) : 66–81. http://dx.doi.org/10.4018/irmj.2014100104.

Texte intégral

Résumé :

Offshoring has become a viable alternative for companies to lower software development costs and leverage labor resources worldwide. To achieve success in offshoring software development projects, a vendor must choose appropriate development methodologies. This study aims to examine how methodology fit affects offshoring project performance. It proposes that methodology fit affects project performance through interfirm knowledge sharing between vendors and clients. In addition, the impact of methodology fit on knowledge sharing is dependent on relational capital between vendors and clients. A survey was conducted among software companies in China that provide offshoring services. 108 completed questionnaires were collected. The results confirm this article's hypotheses.

Styles APA, Harvard, Vancouver, ISO, etc.

13

Xu, Peng, et Yurong Yao. « Methodology Fit in Offshoring Software Development Projects ». Information Resources Management Journal 28, n^o 3 (juillet 2015) : 42–58. http://dx.doi.org/10.4018/irmj.2015070104.

Texte intégral

Résumé :

Offshoring has become a viable alternative for companies to lower software development costs and leverage labor resources worldwide. To achieve success in offshoring software development projects, a vendor must choose appropriate development methodologies. This study aims to examine how methodology fit affects offshoring project performance. The authors propose that methodology fit affects project performance through interfirm knowledge sharing between vendors and clients. In addition, the impact of methodology fit on knowledge sharing is dependent on relational capital between vendors and clients. A survey was conducted among software companies in China that provide offshoring services. 108 completed questionnaires were collected. The results confirm the authors' hypotheses.

Styles APA, Harvard, Vancouver, ISO, etc.

14

Al-Refai, Mohammed, Basem Zughoul, Yousef Al-Raba’nah, Mohammad Alauthman et Ahmad Muraish. « Software Development by Merging Prototyping and Agile Approaches ». International Journal of Advanced Research in Computer Science and Software Engineering 7, n^o 9 (31 octobre 2017) : 47. http://dx.doi.org/10.23956/ijarcsse.v7i9.410.

Texte intégral

Résumé :

during the past four decades, new software development approaches were presented to going with new trends of the software development companies and developers. Nowadays most software companies search to customise short period and minimal costs to produce valuable software products. These productions are within unstable, changing environments. Agile Methodologies were thus introduced to achieve the new requirements of the software development companies. Agile development invented for handling change. The key benefit of agile methodology is used to simplify the change-oriented software engineering process, but agile methodology needs to take more consideration to user point of view. Although the weaknesses of prototyping approach have, it can be used effectively by end users to describe requirements that developers may not have considered. This paper presents a proposed framework based on merge prototyping and agile approaches not only to cure the weaknesses of agile development and prototype methodology but to enrol the user in every single step, which will lead to faster and much accepted overall results.

Styles APA, Harvard, Vancouver, ISO, etc.

15

Özcan-Top, Özden, et Fergal McCaffery. « A hybrid assessment approach for medical device software development companies ». Journal of Software : Evolution and Process 30, n^o 7 (28 décembre 2017) : e1929. http://dx.doi.org/10.1002/smr.1929.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

16

Fehér, Péter, et András Gábor. « The role of Knowledge Management Supporters in software development companies ». Software Process : Improvement and Practice 11, n^o 3 (2006) : 251–60. http://dx.doi.org/10.1002/spip.269.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

17

Sharma, Ankita, et Manav Bali. « Comparative Study on Software Development Methods : Agile vs Scrum ». International Journal of Emerging Research in Management and Technology 6, n^o 6 (29 juin 2018) : 165. http://dx.doi.org/10.23956/ijermt.v6i6.263.

Texte intégral

Résumé :

Now a days most of the software companies are able to produce valuable software in a very short span of time with minimum costs and with adjustable environments. For this purpose Agile Methodologies were thus introduced to meet all the requirements of a software development company. In this paper we will discuss the agile technique and SCRUM there advantages and disadvantages. Also we discuss about the dissimilarities and similarities between the new requirements of the software development companies.

Styles APA, Harvard, Vancouver, ISO, etc.

18

H. Kulkarni, Rajesh, P. Padmanabham, Manasi Harshe, K. K. Baseer et Pallavi Patil. « Investigating Agile Adaptation for Project Development ». International Journal of Electrical and Computer Engineering (IJECE) 7, n^o 3 (1 juin 2017) : 1278. http://dx.doi.org/10.11591/ijece.v7i3.pp1278-1285.

Texte intégral

Résumé :

Agile methodologies adaptation in software companies is an accepted norm.Rapid application development and efficient deliverables being the premise. The changing business needs, cost effectiveness and timely delivery are catered to by agile methods. Different software development models are in the literature and also are being used by the industry. Few companies have adopted agile, few are gearing up for and few are in transition. We investigated agile presence in a software company.Project management is an evolving art with innovative methods being added up.The aim of this paper is to tease about project management challenges, agile, agile transition in companies and a comparison of conventional software engineering practices with agile process model.This paper takes stock of the current status of quality in software projects and to add on quality process improvement strategies. The results presented here are after a qualitative interview study with one cross function team using streamline development framework in agile development.

Styles APA, Harvard, Vancouver, ISO, etc.

19

Ogunyemi, Abiodun, David Lamas et Emmanuel Eze. « Exploring the State of Human-centred Design Practice in Software Development Companies : A Cross-Case Analysis of Three Nigerian Software Companies ». Interacting with Computers 30, n^o 5 (1 septembre 2018) : 444–67. http://dx.doi.org/10.1093/iwc/iwy020.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

20

Trauzettel, Franziska, et Michael Minge. « Usability in the lifecycle of medical software development ». Current Directions in Biomedical Engineering 2, n^o 1 (1 septembre 2016) : 583–86. http://dx.doi.org/10.1515/cdbme-2016-0129.

Texte intégral

Résumé :

AbstractA close cooperation with users is necessary to ensure that interactive systems are robust, easy to use and accepted. Therefore, in medical technology, standards for usability are of fundamental importance. We investigated with the presented study how the concept of usability is currently understood and implemented in medical software companies. Interviews were conducted with 21 employees of German enterprises. Furthermore we extended an already existing quantitative online survey where 53 companies (including 24 from the health industry sector) participated in. Results show that the importance of usability is recognized by most of the respondents. Moreover, a wide variety of methods and approaches is known and implemented for exploring user needs and evaluating system prototypes. However, it was observed that human-centered design activities mainly focus on functionality, risk prevention and accessibility. Hedonic user needs and subjective perceptions (“user experience”) still play a minor role. Based on the results, practical requirements are derived and a “best case” for methodological approach is introduced.

Styles APA, Harvard, Vancouver, ISO, etc.

21

Pashchenko, Denis. « Fully Remote Software Development Due to COVID Factor ». International Journal of Software Science and Computational Intelligence 13, n^o 3 (juillet 2021) : 64–70. http://dx.doi.org/10.4018/ijssci.2021070105.

Texte intégral

Résumé :

The internal transformation and using the fully remote software development under the influence of the pandemic has not only changed the industry, but heralded the construction of a new reality. This article presents the results of a study that covered the experience of transformation of 26 project teams from the world's leading IT corporations, software vendors, and high-tech companies with strong internal development practices: Alphabet, Amazon, BSC Group, Custis, Deutsche Bank, Evernote, Exness, Positive Technologies, PromSvyazBank, Sberbank, VTB, Yandex. Experts determined the results of rapid adaptation to changes, considered the medium-term impact of the pandemic factor on work processes, and made forecasts for 2021. The results of the study are accompanied by brief comments and recommendations of the author, the main idea of which is the need to quickly understand a new trend in software development, hiring specialists, and organizing teams associated with the refusal of high-tech IT companies to return to teamwork in shared offices.

Styles APA, Harvard, Vancouver, ISO, etc.

22

Pedroso, Sandra Laís, et Leonardo Rocha de Oliveira. « Measurement process of software development projects for supporting strategic business objectives in software developing companies ». Journal of Information Systems and Technology Management 10, n^o 2 (30 août 2013) : 357–76. http://dx.doi.org/10.4301/s1807-17752013000200010.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

23

L, Balu, et Leena James. « Facilitating Protégé Career Development through Roles of Mentors in Software Companies ». Ushus - Journal of Business Management 16, n^o 2 (1 avril 2017) : 53–69. http://dx.doi.org/10.12725/ujbm.39.5.

Texte intégral

Résumé :

The success of protégé contribution in any organizationtoday depends more on the type of relationship that an organization establishes with the support of mentors. Research indicates that individuals who are mentoredhave an increased likelihood of career success as a result of the targeted developmental support they receive. Mentors serve as trusted and significant advisors,providing a sounding board for day-to-day issues encountered on the job and alternative perspectives on issues regarding both problem identification and problem-solving. Mentoring can take on different forms. There are many ways through which mentors can improve the effectiveness of the mentoring process. Qualities of mentors, skills of mentors and mentoring methods have already contributed toward protégé career development. In this paper, the author is making an effort to assist the human resource department on how protégé career development can be achieved through the new roles of the Mentors, in the near future. By practising new roles, mentors in organizations can facilitate healthy relationships between the levels of management and in turn, try to achieve individual goals and organizationalgoals.

Styles APA, Harvard, Vancouver, ISO, etc.

24

РУДНИЧЕНКО, Н. Д. « FLEXIBLE METHODOLOGIES EFFICIENCY RESEARCH IN PRACTICE OF MODERN SOFTWARE DEVELOPMENT COMPANIES ». Transport development, n^o 1(1) (27 septembre 2017) : 171–77. http://dx.doi.org/10.33082/td.2017.1-1.20.

Texte intégral

Résumé :

The results of research on the effectiveness of the use of flexible software development methodologies in the practice of modern companies are presented. The results of the survey on the use of project management methodologies, as well as the results of the cost analysis of 9 different projects are presented. The peculiarities of various agile development methodologies are revealed at their practical application.

Styles APA, Harvard, Vancouver, ISO, etc.

25

Kakkar, Gurleen. « Empirical Analysis by Examining Critical Success Factors for Project Success during Software Development : Case of Indian Software Development Companies ». International Journal of Management 07, n^o 04 (2019) : 290–300. http://dx.doi.org/10.35620/ijm.2019.7407.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

26

Bramorski, Tom. « Best Practices In Operations Executive Information Systems Software Development And Implementation ». Review of Business Information Systems (RBIS) 9, n^o 2 (1 avril 2005) : 13–22. http://dx.doi.org/10.19030/rbis.v9i2.4458.

Texte intégral

Résumé :

In this paper we identify best industry practices and current trends in the development and management of software products. We discuss the strategic importance of developing appropriate operational capabilities that are prerequisites for achieving marketing success. We illustrate these concepts with examples from software companies to highlight how they achieved the desired balance between market demands and operational resources. Finally, we highlight the benefits these companies had derived from such an alignment.

Styles APA, Harvard, Vancouver, ISO, etc.

27

Song, Kwang Yoon, In Hong Chang et Hoang Pham. « Analysis of Environmental Factors for Mobile Software Development Focused on Korean Companies ». Mobile Information Systems 2021 (3 mai 2021) : 1–18. http://dx.doi.org/10.1155/2021/6689905.

Texte intégral

Résumé :

Software should be a product that can be used easily and accurately by the user and should be improved quickly and accurately when problems arise. In many software development projects, software requirements are frequently modified during the design or development phase, which tests the development of specific designers’ or developers’ capabilities. Software development environmental factors (SDEFs), such as differences in mutual work recognition among users, developers, and testers or knowledge differences, can hinder communication, which may lead to faulty development owing to erroneous job definition. Because the exact size and scope of the software cannot be calculated, the risk of excessive requirements, such as schedule, cost, and manpower, may increase. This study aims to investigate 32 SDEFs to examine the influence of factors affecting the reliability of software developed by Korean companies to identify factors with high influence and compare differences with previous studies. Moreover, we found whether any new SDEFs from the top 10 rankings only affected Korean companies, and also US companies included in previous studies. A factor analysis revealed several potential factors to identify the mutually independent characteristics of the factors. Through statistical analysis methods, the difference between the group means and the impact on improving the software reliability were found in Korean companies. These findings can provide useful benefits to software developers and managers working in countries with different or similar cultures and help increase working efficiency, i.e., work versus time investment and software reliability improvement.

Styles APA, Harvard, Vancouver, ISO, etc.

28

Lesser, Eric, et Linda Ban. « How leading companies practice software development and delivery to achieve a competitive edge ». Strategy & ; Leadership 44, n^o 1 (18 janvier 2016) : 41–47. http://dx.doi.org/10.1108/sl-11-2015-0083.

Texte intégral

Résumé :

Purpose – Increasingly companies recognize that effective and rapid software development – from ideation to delivery – is crucial to achieving competitiveness. This article looks at how leading companies are establishing an enterprise capability for accelerated software delivery to differentiate themselves in the market. Design/methodology/approach – This research looks at how leading software organizations focus on software investments that efficiently and speedily deliver marketplace results. Findings – Successful companies build comprehensive skills in Agile and lean software development methods and for fostering extensive collaboration among business users, IT professionals and customers throughout the software development and delivery lifecycle. Practical implications – Advanced organizations are more likely to apply more mature development practices, such as service-oriented architecture (SOA) and Agile iterative development methods. Originality/value – Advanced organizations collaborate much more with customers and business partners to improve software development outcomes.

Styles APA, Harvard, Vancouver, ISO, etc.

29

Et.al, Javed Iqbal. « The Effects of Agile Methodologies on Software Project Management in Pakistani Software Companies ». Turkish Journal of Computer and Mathematics Education (TURCOMAT) 12, n^o 3 (11 avril 2021) : 1717–27. http://dx.doi.org/10.17762/turcomat.v12i3.996.

Texte intégral

Résumé :

Agile methodologies are always tends to increase the quality of software and also handling the complex software projects. However, the software companies in Pakistan have recently felt the disparity of producing successful software. In this context, an extensive survey has been conducted in 52 prominent software development companies of Pakistan to identify this remedy and the motivation behind this production discrepancy. It is revealed from the survey that there is a lack of empirical evidence in the relationship of agile methodologies with the effective and progressive management of software project management factors including, schedule, scope, risk, budget, quality and resources. Therefore, the proposed study delivers an extensive statistical comparison to determine the effectiveness of agile methodologies in terms of their effects on the project management factors. The results suggest that in general all agile methodologies play a significant role towards the successful software development in the software company. However, Extreme Programming, Scrum, Kanban and Agile modeling are the main determinants of production disparity among software companies. Furthermore, it is determined that the quality factor has a positive correlation with the rest of the factors. It is also found that the budget factor has significantly correlated with other five factors, while rest of the factors has insignificant correlation. We have also compared agile methodologies in terms of project management factors, which specify that each agile methodology has its own importance and effect with respect to managing different factors of project management.

Styles APA, Harvard, Vancouver, ISO, etc.

30

Nidagundi, Padmaraj, et Leonids Novickis. « TOWARDS UTILIZATION OF LEAN CANVAS IN THE DEVOPS SOFTWARE ». Environment. Technology. Resources. Proceedings of the International Scientific and Practical Conference 2 (15 juin 2017) : 107. http://dx.doi.org/10.17770/etr2017vol2.2522.

Texte intégral

Résumé :

The growth of technology made human to depend more on the software applications in his daily life and nowadays software companies focused more on building robust error free software to end customers in very short time. Software development companies facing one side growth of technological complexity and another side build the products fast to win a competition in business. In recent years growth of a DevOps given lot of new growth opportunity for the software companies. DevOps basic principles focused on the collaboration and communication as a key in between software development information technology professional. It is concentrated on the automating the most of the routine tasks such as development, delivery, infrastructure, support, software testing in software development process. DevOps also emphasize on the building, testing and releasing the software more quickly and in a reliable way.

Styles APA, Harvard, Vancouver, ISO, etc.

31

Alhroub, Abdalla, et Ayham A. M. Jaaron. « Assessing agile project management practices : the case of Palestinian software development companies ». Middle East J. of Management 6, n^o 1 (2019) : 95. http://dx.doi.org/10.1504/mejm.2019.097370.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

32

Alhroub, Abdalla, et Ayham A. M. Jaaron. « Assessing agile project management practices : the case of Palestinian software development companies ». Middle East J. of Management 6, n^o 1 (2019) : 95. http://dx.doi.org/10.1504/mejm.2019.10018536.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

33

García-Berna, José, Juan Carrillo de Gea, Begoña Moros, José Fernández-Alemán, Joaquín Nicolás et Ambrosio Toval. « Surveying the Environmental and Technical Dimensions of Sustainability in Software Development Companies ». Applied Sciences 8, n^o 11 (20 novembre 2018) : 2312. http://dx.doi.org/10.3390/app8112312.

Texte intégral

Résumé :

The growing concern over the state of degradation of the environment has led to a consideration of aspects relating to sustainability in software. Bearing this in mind, we have carried out a survey of practitioners, aiming to gather information about their awareness of sustainable software, not only during the development process, but also throughout the period in which the software is used. Using the data gathered, we studied professionals’ perspectives on sustainability in software development, and were able to get a picture of the current situation of the application of sustainability practices in this sector. We focused on the environmental and technical dimensions of sustainability aimed at extending the longevity of information systems and making them more energy efficient. From the results, we observed that there is a widespread desire to pursue sustainable behavior at work, even though there are not always clear guidelines on how to proceed in this endeavor.

Styles APA, Harvard, Vancouver, ISO, etc.

34

Arnold, Bob, et M. Reza Shadnam. « Innovation Goals in Software Development for Business Applications ». Evolving Trends in Engineering and Technology 1 (août 2014) : 53–62. http://dx.doi.org/10.18052/www.scipress.com/etet.1.53.

Texte intégral

Résumé :

Having been in touch with technical side of many companies in various sectors, we know industry is facing a period of unprecedented change. We have compiled a list of common technological challenges in the sector that companies are facing in adapting to the change. The purpose of this contribution is to discuss and communicate areas where technological challenges in the Software Development Sector lie. We see this kind of inventory beneficial to the academic community as it provides an account of industry challenges. The analysis would be necessary to really assist players in the sector in being better prepared for formalizing and documenting their learning and know-how development. Beside knowledge management benefits, the analysis also would help in taking advantage of research and development funding and attracting investors; both academic and industrial organizations can take advantage of this aspect. We are calling this type of analysis “capabilities analysis”. A single company might not solve the world’s technical problems, but just being aware of them and measuring steps taken to advance, even slightly, in the direction of solving the problems presented in this analysis would make the company stand out. When data is formulated this way, strong evidence is created that the project goes beyond standard engineering by distinguishing risk that can be eliminated through experiment from standard engineering risk. The main contribution of this work is classification of problems and approaches to solve them in this field.

Styles APA, Harvard, Vancouver, ISO, etc.

35

Li, Bingzhi. « Performance Evaluation Study on Software and Information Technology Service Listed Companies ». International Journal of Economics and Finance 11, n^o 1 (15 décembre 2018) : 76. http://dx.doi.org/10.5539/ijef.v11n1p76.

Texte intégral

Résumé :

The development of software and information technology service is not only related to the promotion of information industry competitiveness, but also closely related to the adjustment and optimization of industrial structure and even the development of national economy. In recent years, software and information technology services have developed well. However, there are still some problems such as weak international competitiveness, weak innovation ability and unbalanced talent structure, etc. This paper builds the performance evaluation index system of software and information technology service enterprises from five perspectives of profitability, operation ability, debt paying ability, development ability and innovation ability. To evaluate the performance of listed companies in software and information technology services by combining TOPSIS and grey relational degree method to balance the performance of the enterprise and discover the problems in the development of the enterprise in time.

Styles APA, Harvard, Vancouver, ISO, etc.

36

Pobyvaev, Sergey A. « Appraisal : Business Development Trends After COVID-19 ». Economic Strategies 144, n^o 3 (25 juin 2021) : 90–98. http://dx.doi.org/10.33917/es-3.177.2021.90-98.

Texte intégral

Résumé :

Research methodology for studying the strategic potential of Russian appraisal companies is based on "Strategic Matrix of a Company" software package, whose algorithm implies analysis of qualitative and quantitative indicators that allow to create a complete profile of the company and to prepare a scenario forecast of its development. The main qualitative parameters under analysis include such criteria as the degree of innovation and services differentiation, the level of competition and the company's position in the market, priority of certain strategic goals in the company's activities, effectiveness of motivation, corporate culture, the ability to quickly gain access to necessary resources.

Styles APA, Harvard, Vancouver, ISO, etc.

37

O'Connor, Rory V., et Shuib Basri. « Understanding the Role of Knowledge Management in Software Development ». International Journal of Systems and Service-Oriented Engineering 4, n^o 1 (janvier 2014) : 39–52. http://dx.doi.org/10.4018/ijssoe.2014010103.

Texte intégral

Résumé :

Software and systems engineering is distinct from other forms of engineering as it deals with an intangible product, where the progress in construction is not explicitly visible and team members often rely on the documentation of others to follow and review progress. Furthermore unlike traditional engineering disciplines, there is no single standardized unified process. The role of knowledge management in the software engineering literature is becoming more evident, as the software development activity is essentially a human knowledge intensive activity and is seen by many as a key factor. This paper discusses the role of software development knowledge management within software development process and specifically how software development knowledge is managed in software development in order to support software process improvement and the role of knowledge management in this. The authors present the results of a study of knowledge management process practices in very small software companies and discusses these under the major identified issues of: Communication; Learning and sharing; Documentation and Knowledge management process and commitment. The findings in this study give an insight towards knowledge management practices as they relate to software development process practices in very small companies and the important factors that must be considered to preserve knowledge and quality software.

Styles APA, Harvard, Vancouver, ISO, etc.

38

Thorwart, K. « The AMETIST process improvement experiment : towards efficient team development in small companies ». Software Process : Improvement and Practice 4, n^o 1 (mars 1998) : 11–18. http://dx.doi.org/10.1002/(sici)1099-1670(199803)4:1<11 ::aid-spip89>3.0.co;2-7.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

39

Ravaglia, Claudia Carrijo, Mirian Picinini Mexas, Ana Claudia Dias, Haydée Maria Correia da Silveira Batista et Kleber da Silva Nunes. « Management of software development projects in Brazil using agile methods ». Independent Journal of Management & ; Production 12, n^o 5 (1 août 2021) : 1357–74. http://dx.doi.org/10.14807/ijmp.v12i5.1353.

Texte intégral

Résumé :

The aim of the paper is to analyze how agile management practices are being adopted by specialists from software development technology companies in Brazil, identifying actions that contribute to the success of software implementation, aiming to ensure the survival of organizations in the market. The study counted with a literature review to support the field research with software development specialists who use the agile methodology and work in Brazil in the states of Rio de Janeiro and São Paulo. The results were analyzed through a descriptive statistics and content analysis. The research identified that the companies that adopt agile software management methodology in Brazil prefer the Scrum method and the development teams may be geographically distributed. The main positive points identified when adopting agile methods were the process speed, team involvement, maximization of results, involvement with the client, and simplicity. Most experts identified problems in the implementation of the agile methodology and as points of attention: management of distributed teams, scope estimation and communication. It was possible to identify the existence of a positive financial result by adopting the agile method for software development projects, as well as actions that contribute to the success of these projects, such as controlling quality using different testing techniques, project management, time, stakeholders, scope, and have agile communication, with feedback and good leadership. On the other hand, it was observed in the statistics that, although efficient, this method is still not being widely used. This research can contribute to the managers of software development companies in the use of agile methods as well as improving management decision-making.

Styles APA, Harvard, Vancouver, ISO, etc.

40

O'Connor, Rory V., et Claude Y. Laporte. « An Innovative Approach to the Development of an International Software Process Lifecycle Standard for Very Small Entities ». International Journal of Information Technologies and Systems Approach 7, n^o 1 (janvier 2014) : 1–22. http://dx.doi.org/10.4018/ijitsa.2014010101.

Texte intégral

Résumé :

For very small software development companies, the quality of their software products is a key to competitive advantage. However, the usage of Software Engineering standards is extremely low amongst such very small software companies. A primary reason cited by many such companies for this lack of quality standards adoption is the perception that they have been developed for large multi-national software companies and not with small and very small organizations in mind and are therefore not suitable for their specific needs. This paper describes an innovative systematic approach to the development of the software process lifecycle standard for very small entities ISO/IEC 29110, following the Rogers model of the Innovation-Development process. The ISO/IEC 29110 standard is unique amongst software and systems engineering standards, in that the working group mandated to develop a new standard approached industry to conduct a needs assessment and gather actual requirements for a new standard as part of the standards development process. This paper presents a unique insight from the perspective of some of the standards authors on the development of the ISO/IEC 29110 standard, including the rationale behind its development and the innovative design of implementation guides to assist very small companies in adopting the standards, as well outlining a pilot project scheme for usage in early trials of this standard.

Styles APA, Harvard, Vancouver, ISO, etc.

41

Gupta, Varun, Jose Maria Fernandez-Crehuet et Thomas Hanne. « Freelancers in the Software Development Process : A Systematic Mapping Study ». Processes 8, n^o 10 (27 septembre 2020) : 1215. http://dx.doi.org/10.3390/pr8101215.

Texte intégral

Résumé :

[Context] Freelancers could catalyze the software development process by providing their niche skills to generate high quality outputs. They could help companies (including startups) to foster innovations by suggesting creative ideas and providing their expertise in implementing them (for instance, designing solutions, coding solutions etc.). Freelancers could effectively and efficiently work as a virtual member of the software development team. The company must make informed decisions about which task to allot to the freelancer, which freelancer to select, pricing the task, and evaluating the submitted work. On the other hand, the freelancer should make an informed decision about evaluating the monetary value of the task to be charged, trusting the requester, analyzing the skills requirement of the task (finding matches between skill requirement and skills processed), selecting the best task, and maintaining the highest level of reputation. However, the literature does not provide freelancers and the companies the guidelines that support their decision making. However, if freelancers are selected carefully for the most suitable task, the companies will benefit a lot in terms of improved software development metrics. [Objectives] The objective of this paper is to provide the research community the research trends in freelancer-supported software development. This helps to understand that which software development areas have higher concentrations of research efforts, which area has the support of empirical evidence to support management decision makings, and which area requires the research attention. [Method] The systematic study is conducted by planning the mapping protocol, executing the protocol, and reporting the findings using various visualization tools like bar charts and pie charts. The search process was planned to be executed using set of inclusion and exclusion conditions on four bibliographic databases (IEEExplore, Springerlink, Sciencedirect, and ACM digital library). The relevant papers are selected by applying inclusion and exclusion conditions. The google citations of the relevant papers are subject to the inclusion and exclusion conditions again to include the more relevant papers. Finally, the systematic schema was created and populated after analyzing the studies abstracts. [Results] The results indicate the following (a) The research focus is on generic software development (78%) rather on individual life cycle activities. (b) The number of empirical studies is limited (25%). (c) A number of studies proposing solutions and evaluating on live cases in industrial settings are missing from the literature. This is in comparison to the validation approaches (72%) i.e., solutions tested in laboratory settings. (d) At present, the literature has limited ability to provide the software companies (including startups) with the guidelines (in the form of opinions and experience reports) for involving freelancers in the software development process. (e) The reported challenges include Collaboration and Coordination (33%), Developer Recommendation (or selection) (19%), Team Formulation (14%), Task Recommendation (allocation) (14%), Task Decomposition (11%), Privacy and Security (Confidentiality) (11%), Budget Estimation (8%), Recognition (8%), Trust Issues (8%), Market Dynamism (6%), Intellectual Property Issues (6%), Participation of Crowd Worker (6%), and Capacity Utilization (3%). These challenges are highly interactive, and each challenge impacts all other challenges. (e) Recent focus of the researchers (total 7 studies in 2019) is on generic software development handling the collaboration and coordination (3 studies out of 7), Developer recommendation (2 studies out of 7), and task recommendation (2 studies out of 7). [Conclusion] The freelancer-driven software engineering research area has got the attraction of the researchers, but it will take a long time to gain maturity. This puts an urgent call for more empirical studies and evaluation-based solution research that could help companies (including startups) to foster innovations. Further, the research focus should be well distributed among the various development phases to address the unique challenges associated with individual activities. The accurate management of the freelancer in the software development could help companies and startups to foster innovations and remain competitive in the marketplace.

Styles APA, Harvard, Vancouver, ISO, etc.

42

CHEVERS, DELROY. « SOFTWARE PROCESS IMPROVEMENT : AWARENESS, USE, AND BENEFITS IN CANADIAN SOFTWARE DEVELOPMENT FIRMS ». Revista de Administração de Empresas 57, n^o 2 (avril 2017) : 170–77. http://dx.doi.org/10.1590/s0034-759020170206.

Texte intégral

Résumé :

ABSTRACT Since 1982, the software development community has been concerned with the delivery of quality systems. Software process improvement (SPI) is an initiative to avoid the delivery of low quality systems. However, the awareness and adoption of SPI is low. Thus, this study examines the rate of awareness, use, and benefits of SPI initiatives in Canadian software development firms. Using SPSS as the analytical tool, this study found that 59% of Canadian software development firms are aware of SPI programs and 43% of employees use a form of SPI programs to develop software products. Although the sample size is small and the results cannot be generalized, the sample firms that use SPI programs reported an improvement in software product quality as the greatest benefit. These findings confirm the importance of SPI programs as a means of producing higher-quality software products, which can increase the likelihood of software companies winning global contracts.

Styles APA, Harvard, Vancouver, ISO, etc.

43

KARLSSON, CHRISTER, et EVA LOVÉN. « MANAGING NEW TECHNOLOGY INTEGRATION : INTEGRATING SOFTWARE IN MANUFACTURED PRODUCTS ». International Journal of Innovation Management 09, n^o 03 (septembre 2005) : 343–70. http://dx.doi.org/10.1142/s1363919605001290.

Texte intégral

Résumé :

Development processes in which software is integrated in hardware products are explored with the aim of finding obstacles to the development process and hypothesising how they can be dealt with. Empirical data are based on case studies in nine manufacturing companies chosen to have a varied amount of software in their products and experience of technology integration. Results indicate that obstacles in experienced companies concern processes, structures and resources but few culture-related issues. In companies with short experience of software integration in hardware development, cultural aspects were important. Where new technology played a strategic role in the product function, organisational issues such as structures, processes and cultural differences formed obstacles. Where technology only had a supporting role, resource-related obstacles such as lack of competencies were more important. Managerial measures tended to be partly related to the different types of obstacles, partly to the strategic situation of the company.

Styles APA, Harvard, Vancouver, ISO, etc.

44

O’Connor, Rory, et Shuib Basri. « The Effect of Team Dynamics on Software Development Process Improvement ». International Journal of Human Capital and Information Technology Professionals 3, n^o 3 (juillet 2012) : 13–26. http://dx.doi.org/10.4018/jhcitp.2012070102.

Texte intégral

Résumé :

This article identifies the effect of team dynamics in the context of software development teams and its impact on software process improvement (SPI) activities in very small companies, in order to understand the relationship between these two variables. Most software development work is done by teams of software engineers working together in a collaborative manner to execute a software development process. Although there is much literature examining software process and how to improve it, less attention has been paid to the issues of team-working and specifically the impact of team dynamics on the software development process. Team dynamics is the term used to define how people work and interact together in teams. Teamwork is more effective with the existence of positive team dynamic, as it encourages a better working environment with satisfied, fulfilled employees who will in turn be more productive. This paper presents the results of a research study of team dynamics in very small software development companies and its impact on the software development process and software process improvement activities.

Styles APA, Harvard, Vancouver, ISO, etc.

45

Zhang, Ying, Farhad Ali, Kunhao Wang, Shah Nazir et Zeqi Leng. « Utilizing Virtual Crowd for Global Software Development ». Scientific Programming 2021 (15 juillet 2021) : 1–9. http://dx.doi.org/10.1155/2021/2259594.

Texte intégral

Résumé :

Software firms are interested in outsourcing and developing of software globally to the virtual crowd for minimizing the product cost and for increasing the software quality. Developments in information technology (IT) have changed the organizational working environment from centralized to disperse development working practices. As a result, companies have recognized the value of virtual world networks that offer benefits such as efficient time management, lower cost of growth, reduced travel costs, and access to larger competent team members to select the right skilled individual. With the wide spread of Web 3.0 applications and improvements in cloud computation technologies, multinational, multiskilled, and diverse crowds carry out the software developmental process. The aim of this research is to select the effective virtual crowd for the development of quality software. The proposed “characteristic-based virtual crowd selection (CBVCS)” method will select the crowd according to their unique characteristics such as their skills, experiences, expertise, and knowledge.

Styles APA, Harvard, Vancouver, ISO, etc.

46

Pušara, Dejan. « THE IMPACT OF TECHNOLOGICAL DEVELOPMENT ON INSURANCE COMPANIES ». ЗБОРНИК РАДОВА ЕКОНОМСКОГ ФАКУЛТЕТА У ИСТОЧНОМ САРАЈЕВУ 1, n^o 18 (8 octobre 2019) : 73. http://dx.doi.org/10.7251/zrefis1918073p.

Texte intégral

Résumé :

In the contemporary business environment, the fundamental parameter for the successful subsistence of the competitive advantages is keeping pace with the contemporary trends. This also applies to the insurance industry, regardless of how conservative it is considered to be. Information and Communication Technologies influence all business sectors of the insurance companies. The users are increasingly reaching for the Internet as tools of research of insurance prices and products, and possibilities are opening up for the insurers through the new distribution channels. Innovations of the existing products and the development of the new ones represent the driving force behind the evolution of the entire insurance sector. Investing in the modern technology through information systems and risk modeling software makes administrative work easier, and has a significant role in the strategic-business decision-making process.

Styles APA, Harvard, Vancouver, ISO, etc.

47

Ņikiforova, Oksana, Kristaps Babris et Jānis Kristapsons. « Survey on Risk Classification in Agile Software Development Projects in Latvia ». Applied Computer Systems 25, n^o 2 (1 décembre 2020) : 105–16. http://dx.doi.org/10.2478/acss-2020-0012.

Texte intégral

Résumé :

Abstract Software development method, which does not have any faults or gaps in project implementation, has not been elaborated so far. Due to this reason, the authors have decided to perform this study to make it easier for the companies, which use one of the agile development methods, to better foresee potential risks and to deal with their consequences. The aim of the research is to identify and classify risks in agile software development methods and the related projects based on the obtained survey data. To achieve the goal, the authors have developed evaluation criteria, as well as implemented practical questionnaire in various software development companies. From the obtained survey data, the risks are classified according to various factors, i.e., the changing highest and lowest priorities and needs in various projects. Thus, the obtained research results can be applied in various areas of project development, changing the order of priority factors.

Styles APA, Harvard, Vancouver, ISO, etc.

48

Moreno, Valter, José Ricardo Monteiro Pinheiro et Luiz Antonio Joia. « Resource-Based View, Knowledge-Based View and the Performance of Software Development Companies ». Journal of Global Information Management 20, n^o 4 (octobre 2012) : 27–53. http://dx.doi.org/10.4018/jgim.2012100102.

Texte intégral

Résumé :

Software development companies face a globalized, highly competitive and turbulent environment, where efficiency, efficacy and innovation capacity are critical for survival. In this context, small and medium enterprises (SMEs) tend to suffer the most due to the scarcity of resources to which they are usually subjected and their dependence on a few more powerful customers. This paper describes the elaboration and test of a model that draws on the resource-based view and knowledge-based view to explain the differences in performance of software SMEs. The analysis of data collected from 265 Brazilian companies suggests that: absorptive capacity contributes significantly to the development of a company’s stock of technological knowledge; the flexibility of the IT infrastructure, managerial capacity, and IT technological knowledge are strong predictors of software development performance; and organizational performance is positively influenced by software development performance and managerial capacity. The implications of these findings are then discussed.

Styles APA, Harvard, Vancouver, ISO, etc.

49

Huda, Kazi Nazmul, Rashedul Hassan et Mohammad Imran. « Job Stress among the information technology professionals of software development companies of Bangladesh ». IIMS JOURNAL OF MANAGEMENT SCIENCE 11, n^o 3 (2020) : 203–16. http://dx.doi.org/10.5958/0976-173x.2020.00012.00015.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

50

Kukreja, Vinay, Sachin Ahuja et Amitoj Singh. « Measurement and structural model of agile software development critical success factors ». International Journal of Engineering & ; Technology 7, n^o 3 (30 juin 2018) : 1236. http://dx.doi.org/10.14419/ijet.v7i3.12776.

Texte intégral

Résumé :

Purpose: Agile methodologies have emerged as an innovative and successful business changing way for software development companies since the success rate for completing the software projects on time and budget is better than conventional methodologies. This study proposes a theoretical framework of success factors for agile software development and validates the proposed framework using structural equation modeling.Design Methodology: A survey based random sampling was performed for data collection from 201 respondents identified from the pool of agile practitioners in software companies. Structural Equation Modeling performed on the collected data to validate measurement model as well as the structural model.Findings: The theoretical model was confirmed with modifications and the results showed that required level of fitness indexes have been achieved for the measurement model and structural model. The validation of the factors has also been done.Originality/Value: This study will guide the agile practitioners, academicians and project managers to focus more on the particular success factors which have high weight towards project success.

Styles APA, Harvard, Vancouver, ISO, etc.

Articles de revues sur le sujet « Software development companies »

Créez une référence correcte selon les styles APA, MLA, Chicago, Harvard et plusieurs autres