Bibliographies thématiques / Software development companies

Sommaire

  1. Articles de revues
  2. Thèses
  3. Livres
  4. Chapitres de livres
  5. Actes de conférences

Littérature scientifique sur le sujet « Software development companies »

Auteur : Grafiati
Publié le 4 juin 2021
Mis à jour le 16 février 2022

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

Choisissez une source :

Consultez les listes thématiques d’articles de revues, de livres, de thèses, de rapports de conférences et d’autres sources académiques sur le sujet « Software development companies ».

À côté de chaque source dans la liste de références il y a un bouton « Ajouter à la bibliographie ». Cliquez sur ce bouton, et nous générerons automatiquement la référence bibliographique pour la source choisie selon votre style de citation préféré : APA, MLA, Harvard, Vancouver, Chicago, etc.

Vous pouvez aussi télécharger le texte intégral de la publication scolaire au format pdf et consulter son résumé en ligne lorsque ces informations sont inclues dans les métadonnées.

Articles de revues sur le sujet "Software development companies"

1

AXINTE, Sabina-Daniela. « Security Challenges for Software Development Companies ». International Journal of Information Security and Cybercrime 5, no 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, no 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, no 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, no 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, no 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, no 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, no 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, no 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, no 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, no 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.
Plus de sources

Thèses sur le sujet "Software development companies"

1

Giardino, Carmine, et Nicolò Paternoster. « Software Development in Startup Companies ». Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3652.

Texte intégral
Résumé :
Context: Software startups are newly created companies with no operating history and are extremely fast in producing cutting-edge technologies. These companies develop software un- der highly uncertain conditions, tackling fast growing markets with severe lack of resources. Startups present an unique combination of characteristics which pose several challenges to the software development activities, creating interesting problems for software engineers. However, despite the increasing economical importance and the high failure rate, there are only a few sci- entific studies attempting to address software engineering (SE) issues, especially for early-stages startups. In a context where a wrong decision can easily lead the entire business to failure, the support of SE can contribute to foster performances of startups and making a big impact on a large number of companies. Objective: In view of a lack of primary studies, the first step to attending the software development strategies with scientific and engineering approaches is by an understanding of the startups’ behavior. For this reason this research aims to understand how software development strategies are engineered by practitioners, in the period of time that goes from idea conception to the first open beta release of the software product. Methods: This research combines a systematic review of the state-of-the-art with a cross- sectional case study conducted in 13 web startups recently founded and distributed in di↵erent geographic areas and market sectors. A grounded theory approach guided the execution of a sys- tematic mapping study, integrated with semi-structured interviews and follow-up questionnaires to explore the state-of-practice. Results: We selected, classified and evaluated 37 relevant studies. The systematic review revealed that the studies which constitute the body of knowledge are generally not rigorously designed and executed, make use of inconsistent terminology, and cover only small samples of startups. Moreover, we extrapolated concepts from the case study to form a theoretical model, explaining the underlying phenomenon of software development in early-stage startups. The model is grounded in the empirical data and its explanatory power was further validated through a systematic procedure. Finally we proposed a multi-faceted evolutionary model to describe the dynamics of the software development after the first product release. Conclusions: The research provided a wide set of evidences fostering the understanding of how software development is structured and executed, from idea conception to the first release. The results revealed the urgent priority of startups of releasing the product as quickly as possi- ble to verify the product/market fit and to adjust the business and product trajectory according to the early collected user feedbacks. Nevertheless, the initial gain obtained in speeding-up the development by low-precision and product-centric engineering activities is counterbalanced by the need of restructuring the product and the workflows before setting o↵ for further grow. In fact, when user requests and company’s size start to increase startups face an initial and temporary drop-down in productivity, creating the need of mitigation strategies to find a sweet spot between being fast enough to enter the market early while controlling the amount of accu- mulated technical debt. The conclusions can be generalized with a good degree of confidence to the majority of early-stage software startups involved in the production of innovative products, especially for web and mobile applications.
Styles APA, Harvard, Vancouver, ISO, etc.
2

Lindmark, Fanny, et Hanna Kvist. « Security in software : How software companies work with security during a software development process ». Thesis, Linköpings universitet, Institutionen för datavetenskap, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-130964.

Texte intégral
Résumé :
This study is conducted, due to recent interest in privacy and software security, on how a number of software development companies work during a development process to develop secure software to the possible extent. The study is based on four interviews with four software companies located in Linköping, Sweden. The interviews followed a semi-structured format to ensure the possibility to compare the given answers from the companies to each other. This structure was chosen to give each company the liberty to express what they valued and thought were important during a software development process. The aim was to analyze how and if these companies work with security when developing software, and to see what differences and similarities that could be established. We found differences between the companies' perspective of security and on their methods of working. Some valued secure software more than others and performed more measures to ensure it. We also found some similarities on their view on importance of secure software and ways to work with it. The differences and similarities were related to the size of the companies, their resources, the types of products they develop, and the types of clients they have.
Styles APA, Harvard, Vancouver, ISO, etc.
3

Smith, Stanley A. (Stanley Alan). « Software development in establised and new entrant companies : case studies of leading software producers ». Thesis, Massachusetts Institute of Technology, 1993. http://hdl.handle.net/1721.1/12725.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
4

Rodríguez, P. (Pilar). « Combining lean thinking and agile software development:how do software-intensive companies use them in practice ? » Doctoral thesis, Oulun yliopisto, 2013. http://urn.fi/urn:isbn:9789526203324.

Texte intégral
Résumé :
Abstract Software engineering is advancing according to market needs. Consequently, software development methods that initially caused controversies such as Agile, and more recently Lean, are increasingly being adopted by the software industry. Particularly, Lean Software Development, which was initially regarded as one of the Agile methods, is acquiring an identity of its own as a means to scale Agile. However, Lean thinking is still open to interpretation in the domain of software development, which differs fundamentally from the manufacturing domain where Lean originally emerged. Specific issues such as the essence of Lean Software Development, the compatibility of Lean and Agile and the best combination of them are not properly understood. This dissertation addresses Lean thinking and its combination with Agile in the field of software development, by providing empirical evidence on how software-intensive organisations use them in practice. The research was performed in four phases. First, the relevant literature was analysed to identify research opportunities. Second, a survey strategy was used to investigate status and trends in the adoption of Agile and Lean. The third phase explored in detail how Agile and Lean are combined in practice, by conducting case studies on two large-scale, industry-leading companies that were transforming their processes from Agile Software Development into Lean Software Development. Finally, in the fourth phase, the results of the previous research phases were synthetized to draw conclusions and outline implications. The results of the study confirmed the interest of practitioners in using a combination of Agile and Lean. Unlike in manufacturing, the borders of Agile and Lean are not clearly defined in the software domain. The results provided evidence of numerous compatibilities between Agile and Lean in software development. Generally, the use of Agile methods at a prescriptive level is guided by Lean principles. However, Lean thinking also brings new practical elements to software development processes, such as Kanban, work-in-progress limits, a ‘pull’ and ‘less waste’-oriented culture and an extended emphasis on transparency and collaborative development. The results showed the fundamental importance of practices that enable quick feedback, fast learning and adaptation
Tiivistelmä Ohjelmistotuotanto kehittyy markkinoiden tarpeiden mukaisesti. Aiemmin kiisteltyjä ketteriä menetelmiä, ja nykyään myös Lean-menetelmiä sovelletaan yhä useammin ohjelmistoteollisuudessa. Lean-menetelmiin perustuva Lean-ohjelmistokehitys erottuu selkeämmin välineenä laajentaa ketterien menetelmien käyttöä. Lean on yhä monitulkintainen ohjelmistotuotannossa, joka poikkeaa teollisuustuotannosta, josta Lean on peräisin. Lean-ohjelmistokehitystä, Lean- ja ketterien menetelmien yhteensopivuutta ja niiden parasta yhdistelmää ei vielä ymmärretä riittävän hyvin. Tämä väitöskirja käsittelee Lean-menetelmien yhdistämistä ketteriin menetelmiin ohjelmistotuotannossa. Tutkimus esittää kokemusperäistä tietoa, kuinka näitä menetelmiä käytetään ohjelmisto-alan organisaatioissa. Tutkimus oli nelivaiheinen. Aluksi tutkimusmahdollisuudet kartoitettiin tutkimalla aiheeseen liittyvää kirjallisuutta. Seuraavaksi tutkittiin kyselytutkimuksen avulla Lean- ja ketterien menetelmien käyttämisen nykytilaa ja kehitystä. Kolmannessa vaiheessa tapaustutkimuksilla selvitettiin Lean- ja ketterien menetelmien yhdistämistä käytännössä. Tapaustutkimuksia tehtiin kahdessa suuressa yrityksessä, jotka olivat muuttamassa prosessejaan ketteristä menetelmistä kohti Lean-ohjelmistokehitystä. Lopuksi aiemmat tutkimusvaiheet yhdistettiin johtopäätöksiä ja vaikutusten hahmottamista varten. Tutkimuksen tulokset vahvistavat Lean- ja ketterien menetelmien yhdistämisen kiinnostavan ohjelmistotuotannonharjoittajia. Lean- ja ketterien menetelmien rajat eivät ole selkeästi määriteltyjä ohjelmistotuotannossa. Tulokset tukevat käsitystä Lean- ja ketterien menetelmien yhteensopivuudesta. Lean ohjaa yleisellä tasolla ketterien menetelmien käyttöä. Lean tuo kuitenkin myös uusia elementtejä ohjelmistotuotantoon, kuten Kanban-menetelmän, keskeneräisen työn rajoittamisen, kysyntään perustuvan ’pull’-menetelmän ja turhan työn vähentämistä tavoittelevan ’less-waste’-työkulttuurin. Lean-ajattelu myös lisää painotusta läpinäkyvyyteen ja yhteistyöhön
Styles APA, Harvard, Vancouver, ISO, etc.
5

Saarnak, Stefan, et Björn Gustafsson. « A comparison of lifecycles : Agile software processes vs. projects in non-Agile software companies ». Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3251.

Texte intégral
Résumé :
In the software industry a number of different software processes has been used throughout the years to address known problems with software development, despite their intention complains has been raised that some of these are too bureaucratic. The Agile Alliance was formed in 2001 and aimed to solve this problem, they developed a manifesto and twelve principles which are supported by all Agile software processes. The purpose with the manifesto and its principles is to uncover better ways of developing software and these are by many intercessors of Agile seen as common sense and not completely new ideas. The aim with this master thesis is to answer the question if companies that explicitly claim that they do not use any Agile software process are already applying some of these ideas since they are thought of as obvious and common sense. The comparison in this thesis is performed between the project lifecycles used in specific projects by five non-Agile software companies and four identified lifecycle characteristics and two more general characteristics of the Agile software processes Extreme Programming (XP) and Dynamic Systems Development Method (DSDM). The result from the analysis of these interviews has shown that it is very difficult to decide if a software company really is working as described by XP or DSDM, this is due to that many different factors affect the final outcome. For example type of project and is the software company using different software processes for different kinds of projects. Since we just covered specific projects we were only able to conclude with absolute certainty actions that really were performed in just these projects. The project lifecycles of these software companies had some similarities with the above mentioned Agile software processes, but as a whole the analysis showed that they are quite different due to that two very important characteristics according to us, namely iterative development and frequent releases, were not applied by any of the software companies and that their project phases differed tremendously compared to XP and DSDM. Our common sense hypothesis for Agile software development was shown in this investigation to be incorrect since important activities were not performed by any of the software companies. Instead of using an iterative approach with frequent releases they all followed sequential waterfall like software processes.
Styles APA, Harvard, Vancouver, ISO, etc.
6

Soliński, Adam. « Analysis of the application and integration of methodologies by software development companies ». Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2924.

Texte intégral
Résumé :
Context. In recent years there has been observed a significant shift from plan-driven development towards agile, which is considered as a vast improvement to processes. However, it has also been spotted that agile methodologies are hardly ever applied in their pure form. Moreover, hybrid processes as combinations of plan-driven and agile practices emerge. In addition, agile adoption has been reported to result in both: benefits and limitations. Objectives. In this study the following matters are investigated: 1) the commonness of plan driven and agile practices usage, 2) common practices combinations, 3) patterns for agile adoption over time, 4) hybrid development models and 5) the actual effects of agile adoption in terms of benefits and limitations as perceived by practitioners. Methods. The thesis presents an empirical investigation of software development organizations. The objectives are achieved through a targeted survey based on existing evidence and a multidimensional data analysis. The mean for obtaining data is a web-based questionnaire with an interactive board with practices and time indication sliders (to capture applied development models and practices adoption strategies) and hierarchical cumulative voting (to measure the relative significance of benefits and limitations). The data analysis is supported by hierarchical cluster analysis and an extended hierarchical voting analysis framework (EHV-F). Results. In total, 45 practitioners have been successfully surveyed. The commonness of 7 plan-driven and 14 agile practices usage was investigated. The relative significance of agile adoption benefits (32 factors in 10 categories) and limitations (23 factors in 7 categories) was measured with respect to global view (all respondents and perspectives), different agile adoption strategies as well as distinguished development models. Conclusions. It is concluded that agile practices dominate over plan-driven, however, hybrid approaches, being combinations of plan-driven and agile practices, are frequently applied. It is also concluded that some practices are commonly used together since they facilitate each other (e.g. continuous integration with testing which facilitate short iterations and releases). Some agile practices are still unsuccessfully applied and eventually abandoned (e.g. pair programming), what should be further investigated by researchers. Incremental agile adoption strategy was found to be the most beneficial approach. It is also concluded that agile adoption leads first of all to improved quality of working life, increased knowledge transfer and improved verification and validation processes. On the other hand, agile adoption is very demanding since it requires high professional skills from development teams as well as managers. Hence, more resources should be devoted to training on agile for all the parties involved in development. Agile is still commonly considered to be poorly scalable. Moreover, the quality of design with agile methods is not considered as a benefit at all. These areas should be further investigated by researchers.
Styles APA, Harvard, Vancouver, ISO, etc.
7

Wiener, Martin Amberg Michael. « Critical success factors of offshore software development projects the perspective of German-speaking companies / ». Wiesbaden : Deutscher Universitäts-Verlag, 2006. http://site.ebrary.com/id/10231882.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
8

Loughnane, David, et Henrik Oskarsson. « The Contract Winning Process A guide for small development companies ». Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2004. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3717.

Texte intégral
Résumé :
In order to survive in today’s business world it is necessary to win contracts. If companies fail to do this then their existence is threatened. Therefore, the manner in which companies conduct their contract winning activities become of paramount importance. Much focus in software engineering research and academic literature centres around the post-contract winning activities, such as project planning, costing and scheduling. The emphasis on the contract winning process, though not neglected, is quite small in comparison. There exists a need for more research in this interesting area and this thesis aims to partly address this need. Consequently, the main focus of this research is the contract winning process. The approach used to investigate this area consisted of a theoretical study followed by an empirical study, where eight small development companies were interviewed. The findings show that a uniform formal process does not exist for winning and negotiating contracts. As a result of these findings, from both the theoretical and empirical studies, a contract winning process model for small development companies was formulated. The proposed model consists of five sequential stages with recommended activities for each stage. The model is intended for small software engineering development companies but because the model is generic it could also be used by non-software companies.
Styles APA, Harvard, Vancouver, ISO, etc.
9

Wang, Anjia. « Apparel Companies' Management System (APLAN) ». CSUSB ScholarWorks, 2004. https://scholarworks.lib.csusb.edu/etd-project/2524.

Texte intégral
Résumé :
APLAN is a computer software system developed to aid in an apparel company's management system. APLAN is designed to improve the efficiency of production management by combining the companies' main production activities in one system. This project was designed to use MYSQL as the database system. JSP (Java Server Pages) is an interface between MySQL and the web browser and the database access scheme is JDBC (JAVA Database Connectivity).
Styles APA, Harvard, Vancouver, ISO, etc.
10

Wiener, Martin. « Critical success factors of offshore software development projects : the perspective of german-speaking companies / ». Wiesbaden : Dt. Univ.-Verl, 2006. http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&doc_number=014952985&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
Plus de sources

Livres sur le sujet "Software development companies"

1

Growing software : Big strategies for small software companies. San Francisco : No Starch Press, 2009.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
2

Aramand, Majid. Developing dynamic design capabilities in software product development companies. Tampere : Tampere University of Technology, 2006.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
3

Sanders, Marty. Looking at the broad picture : Smarter software development for Irish companies. Newcastle upon Tyne : Cambridge Scholars Pub., 2011.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
4

Jones, Capers. Software engineering best practices : Lessons from successful projects in the top companies. New York : McGraw-Hill, 2010.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
5

Stack, Catherine Patricia. The implementation of ISO 9000 in Irish software development companies : A case study approach. Dublin : University College Dublin, 1995.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
6

Dybå, Tore. Process improvement in practice : A handbook for IT companies. Boston : Kluwer Academic, 2004.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
7

Owen, Edwards, dir. Netscape time : The making of the billion-dollar start-up that took on Microsoft. New York : St. Martin's Press, 1999.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
8

Windows Phone 7 companion. Indianapolis : Wiley Publishing, 2011.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
9

Glenn, Walter J. Microsoft Exchange server 2003 administrator's companion. Redmond, Wash : Microsoft Press, 2004.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
10

Nanda, Vivek. Iso 9001:2000 Achieving Compliance and Continuous Improvement in Software Development Companies. ASQ Quality Press, 2003.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
Plus de sources

Chapitres de livres sur le sujet "Software development companies"

1

Akbar, Rehan, Asif Riaz Khan et Kiran Adnan. « Software Development Process Evolution in Malaysian Companies ». Dans Data Management, Analytics and Innovation, 139–50. Singapore : Springer Singapore, 2019. http://dx.doi.org/10.1007/978-981-32-9949-8_10.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
2

Solemon, Badariah, Shamsul Sahibuddin et Abdul Azim Abd Ghani. « Adoption of Requirements Engineering Practices in Malaysian Software Development Companies ». Dans Advances in Software Engineering, 141–50. Berlin, Heidelberg : Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-17578-7_15.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
3

Mittner, Jan, et Alena Buchalcevova. « Company Process Support by Software Systems : Research in Small Software Companies in the Czech Republic ». Dans Information System Development, 219–29. Cham : Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-07215-9_18.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
4

Richardson, Ita. « SPI Models : What Characteristics Are Required for Small Software Development Companies ? » Dans Software Quality — ECSQ 2002, 100–113. Berlin, Heidelberg : Springer Berlin Heidelberg, 2002. http://dx.doi.org/10.1007/3-540-47984-8_14.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
5

Fraser, Steven, Barry Boehm, Jack Järkvik, Erik Lundh et Kati Vilkki. « How Do Agile/XP Development Methods Affect Companies ? » Dans Extreme Programming and Agile Processes in Software Engineering, 225–28. Berlin, Heidelberg : Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11774129_34.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
6

Buchalcevova, Alena. « Software Process Improvement in Small Companies as a Path to Enterprise Architecture ». Dans Information Systems Development, 243–53. New York, NY : Springer New York, 2013. http://dx.doi.org/10.1007/978-1-4614-4951-5_20.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
7

Staron, Miroslaw, et Wilhelm Meding. « Measurement-as-a-Service – A New Way of Organizing Measurement Programs in Large Software Development Companies ». Dans Software Measurement, 144–59. Cham : Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-24285-9_10.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
8

Cursino, Rodrigo, João Farias, Maria Lancastre et Wylliams Santos. « Agile Requirements Validation in Brazilian Software Development Companies : A Survey ». Dans Agile Methods, 3–18. Cham : Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-14310-7_1.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
9

Marcus, Aaron, Jeremy Ashley, Clause Knapheide, Arnie Lund, Dan Rosenberg et Karel Vredenburg. « A Survey of User-Experience Development at Enterprise Software Companies ». Dans Human Centered Design, 601–10. Berlin, Heidelberg : Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-02806-9_70.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
10

Rodríguez, Pilar, Jouni Markkula, Markku Oivo et Juan Garbajosa. « Analyzing the Drivers of the Combination of Lean and Agile in Software Development Companies ». Dans Product-Focused Software Process Improvement, 145–59. Berlin, Heidelberg : Springer Berlin Heidelberg, 2012. http://dx.doi.org/10.1007/978-3-642-31063-8_12.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.

Actes de conférences sur le sujet "Software development companies"

1

Zhang, Yuxia, Xin Tan, Minghui Zhou et Zhi Jin. « Companies' domination in FLOSS development ». Dans ICSE '18 : 40th International Conference on Software Engineering. New York, NY, USA : ACM, 2018. http://dx.doi.org/10.1145/3183440.3195047.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
2

Meding, Wilhelm. « Sustainable measurement programs for software development companies ». Dans IWSM/Mensura '17 : 27th International Workshop on Software Measurement and 12th International Conference on Software Process and Product Measurement. New York, NY, USA : ACM, 2017. http://dx.doi.org/10.1145/3143434.3143438.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
3

Kivihalme, M., et A. Valsta. « Improving Software Development Processes in Small Companies : A Case Study ». Dans Software Engineering. Calgary,AB,Canada : ACTAPRESS, 2010. http://dx.doi.org/10.2316/p.2010.677-022.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
4

Mendoza, Alejandra Herrera, Jose Luis Solleiro Rebolledo et Rosario Castanon Ibarra. « A Competitiveness Model for Mexican Software Development Companies ». Dans PICMET '07 - 2007 Portland International Conference on Management of Engineering & Technology. IEEE, 2007. http://dx.doi.org/10.1109/picmet.2007.4349344.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
5

Tuape, Micheal, et Yirsaw Ayalew. « Factors Affecting Development Process in Small Software Companies ». Dans 2019 IEEE/ACM Symposium on Software Engineering in Africa (SEiA). IEEE, 2019. http://dx.doi.org/10.1109/seia.2019.00011.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
6

Cheng, Tjan-Hien, Slinger Jansen et Marc Remmers. « Controlling and monitoring agile software development in three dutch product software companies ». Dans 2009 ICSE Workshop on Software Development Governance (SDG). IEEE, 2009. http://dx.doi.org/10.1109/sdg.2009.5071334.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
7

Šmite, Darja. « What Happens, When Software Product Development Companies Go Global ? » Dans 2010 5th IEEE International Conference Global Software Engineering (ICGSE). IEEE, 2010. http://dx.doi.org/10.1109/icgse.2010.57.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
8

Meding, Wilhelm. « Effective monitoring of progress of agile software development teams in modern software companies ». Dans IWSM/Mensura '17 : 27th International Workshop on Software Measurement and 12th International Conference on Software Process and Product Measurement. New York, NY, USA : ACM, 2017. http://dx.doi.org/10.1145/3143434.3143449.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
9

Akbar, Rehan, Sohail Safdar, Mohd Fadzil Hassan et Azrai Abdullah. « Software development process tailoring for small and medium sized companies ». Dans 2014 International Conference on Computer and Information Sciences (ICCOINS). IEEE, 2014. http://dx.doi.org/10.1109/iccoins.2014.6868453.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
10

Sharif, Abdullahi Mohamud, et Shuib Basri. « Risk assessment factors for SME software development companies in Malaysia ». Dans 2014 International Conference on Computer and Information Sciences (ICCOINS). IEEE, 2014. http://dx.doi.org/10.1109/iccoins.2014.6868827.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
Vous pouvez également être intéressé par les bibliographies sur le sujet « Software development companies » pour d’autres types de sources :
Articles de revues Thèses Livres
Nous offrons des réductions sur tous les plans premium pour les auteurs dont les œuvres sont incluses dans des sélections littéraires thématiques. Contactez-nous pour obtenir un code promo unique!

Vers la bibliographie