Relevant bibliographies by topics / Software Development Best Practices

Academic literature on the topic 'Software Development Best Practices'

Author: Grafiati
Published: 10 December 2022
Last updated: 28 January 2023

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Contents

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Software Development Best Practices.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Software Development Best Practices"

1

Soraluz Soraluz, Aldo Emanuel, Miguel Ángel Valles Coral, and Danny Lévano Rodríguez. "Behavior Driven Development: Best Practices for Software Quality." Ingeniería y Desarrollo 39, no. 1 (October 21, 2021): 190–204. http://dx.doi.org/10.14482/inde.39.1.005.3.

Full text
Abstract:
Asegurar la calidad y funcionalidad de un producto de software es garantizar su correcta estructura, composición, ejecución e integridad, pero en algunos casos estas características se ven afectadas debido a la ineficiente gestión y desarrollo del software. El objetivo de la revisión fue identificar buenas prácticas al usar el desarrollo guiado por comportamientos. Para su desarrollo, se indagó en artículos de investigación categorizados en revistas indexadas en bases de datos como IEEE, ScienceDirect, Scielo, Scopus y Redalyc elaboradas entre los años 2016 y 2020. El análisis y revisión permitió identificar buenas prácticas, como el uso de los escenarios solo para pruebas de funcionalidad, organizar las características en carpetas de acuerdo a los escenarios del sistema, contextualizar el funcionamiento al mismo idioma de los clientes para facilitar la comunicación, el uso de etiquetas para agrupar escenarios, organizar características según necesidades y generar escenarios sin dependencia. Se concluyó que estas buenas prácticas permiten una correcta comunicación, diseño estructurado del software, calidad funcional de cada componente de código y sobre todo un producto eficiente con riesgo mínimo de pérdida de recursos y alto margen de éxito.
APA, Harvard, Vancouver, ISO, and other styles
2

Vogel, David A., and Jill E. Connelly. "Best practices for dealing with offshore software development." Handbook of Business Strategy 6, no. 1 (December 2005): 281–86. http://dx.doi.org/10.1108/08944310510557855.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Mohapatra, Sanjay. "Best Practices in Software Maintenance Projects." International Journal of IT/Business Alignment and Governance 4, no. 1 (January 2013): 11–26. http://dx.doi.org/10.4018/jitbag.2013010102.

Full text
Abstract:
Maintenance of software projects is an important phase in software engineering. However, there are many challenges associated during this maintenance phase, including technical and managerial. In order to reduce the cost of maintaining software project, many such projects are being outsourced to low cost development countries like India, Philippines, Russia or China. This paper talks about decision parameters for outsourcing maintenance projects. However, outsourced maintenance projects have their own issues and challenges such as poor domain knowledge, lack of understanding of application & technological knowledge and managerial issues such as lack of motivation, attrition. To find solution to these issues, the research conducted study in CMM level 5 organizations and based on case studies, developed an approach for addressing these issues and challenges successfully. The best practices so identified (such as training the trainer, process oriented systematic approach, developing a test strategy and involving end users during execution) can be adopted in other organizations as well. It was observed that the best practices improved productivity while reducing defects in the deliverables.
APA, Harvard, Vancouver, ISO, and other styles
4

Meso, Peter, and Radhika Jain. "Agile Software Development: Adaptive Systems Principles and Best Practices." Information Systems Management 23, no. 3 (June 2006): 19–30. http://dx.doi.org/10.1201/1078.10580530/46108.23.3.20060601/93704.3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

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

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
6

Akbar, Muhammad Azeem, Sajjad Mahmood, Hussain Alsalman, Abdul Razzaq, Abdu Gumaei, and Muhammad Tanveer Riaz. "Identification and Prioritization of Cloud Based Global Software Development Best Practices." IEEE Access 8 (2020): 191242–62. http://dx.doi.org/10.1109/access.2020.3031365.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Haq, Sami ul, and Muhammad Tariq . "The Context of Global Software Development: Challenges, Best Practices and Benefits." Information Management and Business Review 3, no. 4 (October 15, 2011): 193–97. http://dx.doi.org/10.22610/imbr.v3i4.933.

Full text
Abstract:
Global Software Development (GSD) environment is based on a contractual relationship between client and vendor organizations in which a client outsources all or some part of its software development activities to a vendor. The vendor in return provides the agreed services in lieu of certain amount of remuneration. The main reasons to select the GSD technique include reduced cost, faster development and access to skilled manpower available across the world. Though GSD is emerging as an effective technique, but it suffers from many challenges like poor communication, lack of trust and coordination. These challenges pose serious risk to the smooth execution of the GSD projects. In the past decade, GSD has become an area of active research and a number of the researchers have worked on different aspects of it. In this paper, we present a critical review of the research studies conducted on GSD to highlight the challenges, best practices and benefits of GSD. Our findings reveal that much of the research in this area has been focused on addressing issues faced by client organizations, however, vendor side in the GSD relationship is much ignored due to which this field of study is still immature; hence, further research work is required to be undertaken to address the issues faced by the vendor organizations.
APA, Harvard, Vancouver, ISO, and other styles
8

Procaccianti, Giuseppe, Héctor Fernández, and Patricia Lago. "Empirical evaluation of two best practices for energy-efficient software development." Journal of Systems and Software 117 (July 2016): 185–98. http://dx.doi.org/10.1016/j.jss.2016.02.035.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Tharian, Manoj. "Rational United Process Part - II Best Practices for Software Development Team." Mapana - Journal of Sciences 1, no. 2 (July 24, 2003): 69–81. http://dx.doi.org/10.12723/mjs.2.7.

Full text
Abstract:
One Of the major problems with most business engineering efforts, is frat the software engineering and the business engineering community do not communicate properly With each other. This leads to that the Output from business engineering is not used properly as input to the software development effort, and viceversc. The Rational Unified Process addresses this by providing a common language and process for both communities, cs we" os showing how to create and maintain direct traceability between and soft-wore rnodels. In Business Modeling we document business processes using so called business use cases. This assures a common understanding among a" stakeholders Of What business process needs to be supported in the organization. The business use cases cre analyzed to understand how the business should support the I O business processes. This is documented in a business object-model. Many projects may choose not do modéing. Requirements The goal Of the Requirements workaow is 'o describe What the system should do and allows the agree on that description. TO achieve
APA, Harvard, Vancouver, ISO, and other styles
10

Sambhanthan, Arunasalam, and Vidyasagar Potdar. "Green Business Practices for Software Development Companies." International Journal of Enterprise Information Systems 11, no. 3 (July 2015): 13–26. http://dx.doi.org/10.4018/ijeis.2015070102.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Software Development Best Practices"

1

Bronson, Darren (Darren Frazier) 1970. "Best practices for evolutionary software development." Thesis, Massachusetts Institute of Technology, 1999. http://hdl.handle.net/1721.1/80490.

Full text
Abstract:
Thesis (M.B.A.)--Massachusetts Institute of Technology, Sloan School of Management; and, (S.M.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 1999.
Includes bibliographical references (p. 41-42).
by Darren Bronson.
S.M.
M.B.A.
APA, Harvard, Vancouver, ISO, and other styles
2

patney, vikas. "Software Engineering Best Practices for Parallel Computing Development." Thesis, Tekniska Högskolan, Högskolan i Jönköping, JTH. Forskningsmiljö Informationsteknik, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-23803.

Full text
Abstract:
In today’s computer age, the numerical simulations are replacing the traditional laboratory experiments. Researchers around the world are using advanced computer software and multiprocessor computer technology to perform experiments, and analyse these simulation results to advance in their respective endeavours. With a wide variety of tools and technologies available, it could be a tedious and time taking task for a non-computer science researcher to choose appropriate methodologies for developing simulation software The research of this thesis addresses the use of Message Passing Interface (MPI) using object-oriented programming techniques and discusses the methodologies suitable to scientific computing, also, propose a customized software engineering development model.
APA, Harvard, Vancouver, ISO, and other styles
3

Iqbal, Ajmal, and Syed Shahid Abbas. "Communication Risks and Best practices in Global Software Development." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5090.

Full text
Abstract:
Context. Global Software Development (GSD) or Global Software Engineering (GSE) is defined as the plan of action in which the software development is performed under various boundaries, such as temporal, political, organizational and cultural [1,2] . The projects developed in globally distributed environment are containing more risks than projects developed in collocated environment because of different challenges such as temporal, geographical and socio-cultural distances [67]. In this thesis communication risks have been discussed along with their causes and effects that hinder the effectiveness of GSD projects. Moreover mitigation practices to resolve communication risks and their negative impacts are also discussed. Objectives. The study describes the identification of communication risks, their causes, effects and the practices to mitigate the risks from both literature and industrial perspectives. Some recommendations has also been discussed on the basis of these resulted communication risks and their mitigation practices. Methods. Detailed systematic literature review in order to collect the data from relevant empirical studies with respect to our scope has been conducted in the first phase. Studies were selected from various Electronic Data Sources (EDS) such as IEEE Xplore (IEEE), ACM Digital Library (ACM), Inspec (IS), Compendex (CD), ISI Web of Science (WoS), Cite Seer (CS), Google Scholar (GS), Science Direct (SD), Springer Link (SL), Wiley Inter Science (WIS), and Business Source Premier (BSP). In second phase 22 industrial interviews were conducted from 13 different multinational organizations. In third phase data analysis has been made based on the analysis of ground theory. On the basis of the codes of grounded theory, comparative analysis has been performed between literature and industrial settings. At the end of the thesis some recommendations has been provided in order to resolve communication risks in GSD. Results. As a result of systematic literature review 44 risks, 44 causes, 38 effects and 63 practices have been identified in GSD with respect to communication. 27 risks, 22 causes, 19 effects and 39 mitigation practices were identified from the industrial interviews. These risks, causes, effects and practices are not only described in this thesis but also mapped in relation to each other. At the end in comparative analysis the combined risks, causes, effects and practices were identified in tabular form. In total 47 risks, 45 causes, 39 effects and 65 mitigation practices were identified through this work. Conclusions. Communication plays a fundamental role in achieving the best practices in Global Software Engineering. This study points out the salient risks and limitations that hamper the process of smooth communication in geographically dispersed teams. The causes and effects of the mentioned risks are discussed in detail and a set of recommendations is provided to cope with those risks and to minimize their effect. The resultant set of recommendations is based on the best suitable practices which shall be followed by globally distributed organizations to achieve a fully communicated environment just like an in-house development setting.
0046760622684
APA, Harvard, Vancouver, ISO, and other styles
4

Kumar, Kshitij. "Dilemma of speed vs. scale in software system development best practices from industry leaders." Thesis, Massachusetts Institute of Technology, 2017. http://hdl.handle.net/1721.1/110137.

Full text
Abstract:
Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, School of Engineering, System Design and Management Program, 2017.
Cataloged from PDF version of thesis.
Includes bibliographical references (pages 90-93).
Many startup organizations face a dilemma as they scale up and their systems grow more complex. This dilemma is between the speed of releases i.e. agility and the scalability of their systems, reflected in the performance, stability and maintainability of their systems as they become larger. A startup is typically very nimble and releases new features and updates to its product very quickly. However, as a startup grows bigger the frequency of releases typically tends to go down. A similar phenomenon is observed in case of incumbent organizations, those that are old, large and complex, and that already have systems at scale; they have systems that perform at scale, and are stable and maintainable, but the pace of development is slow, and it find it hard to speed up their release cycles. Through the study of organizations that have successfully reconciled the required and coveted scalability along with speed as these organizations moved from being small startups to become larger, this study demonstrates that speed vs scale is a dilemma for startups that can be reconciled as they scale up, because there are a set of practices such as modular architecture choices, minimizing work in progress by adopting frequent deployments, automation in testing and utilizing innovative management techniques, which can enable startup organizations to scale up their system and maintain high speed. Although the study of incumbents as they try to speed up while maintaining their scalability is outside the scope of this work, this study also presents a hypothesis for further investigation that it may also be possible for incumbent organizations to speed up at large scale, by embracing these practices.
by Kshitij Kumar.
S.M. in Engineering and Management
APA, Harvard, Vancouver, ISO, and other styles
5

Shearer, James D. "Development of a Digital Game-Based Learning Best Practices Checklist." Bowling Green State University / OhioLINK, 2011. http://rave.ohiolink.edu/etdc/view?acc_num=bgsu1303865257.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Servadei, Giacomo. "The Scrum approach to software development." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2015. http://amslaurea.unibo.it/8255/.

Full text
Abstract:
Agile methodologies have become the standard approach to software development. The most popular and used one is Scrum. Scrum is a very simple and flexible framework that respond to unpredictability in a really effective way. However, his implementation must be correct, and since Scrum tells you what to do but not how to do it, this is not trivial. In this thesis I will describe the Scrum Framework, how to implement it and a tool that can help to do this. The thesis is divided into three parts. The first part is called Scrum. Here I will introduce the framework itself, its key concepts and its components. In Scrum there are three components: roles, meetings and artifacts. Each of these is meant to accomplish a series of specific tasks. After describing the “what to do”, in the second part, Best Practices, I will focus on the “how to do it”. For example, how to decide which items should be included in the next sprint, how to estimate tasks, and how should the team workspace be. Finally, in the third part called Tools, I will introduce Visual Studio Online, a cloud service from Microsoft that offers Git and TFVC repositories and the opportunity to manage projects with Scrum. == Versione italiana: I metodi Agile sono diventati l’approccio standard per lo sviluppo di software. Il più famoso ed utilizzato è Scrum. Scrum è un framework molto semplice e flessibile che risponde ai cambiamenti in una maniera molto efficace. La sua implementazione deve però essere corretta, e visto che Scrum ci dice cosa fare ma non come farlo, questo non risulta essere immediato. In questa tesi descriverò Scrum, come implementarlo ed uno strumento che ci può aiutare a farlo. La tesi è divisa in tre parti. La prima parte è chiamata Scrum. Qui introdurrò il framework, i suoi concetti base e le sue componenti. In Scrum ci sono tre componenti: i ruoli, i meeting e gli artifact. Ognuno di questi è studiato per svolgere una serie di compiti specifici. Dopo aver descritto il “cosa fare”, nella seconda parte, Best Practices, mi concentrerò sul “come farlo”. Ad esempio, come decidere quali oggetti includere nella prossima sprint, come stimare ogni task e come dovrebbe essere il luogo di lavoro del team. Infine, nella terza parte chiamata Tools, introdurrò Visual Studio Online, un servizio cloud della Microsoft che offre repository Git e TFVC e l’opportunità di gestire un progetto con Scrum.
APA, Harvard, Vancouver, ISO, and other styles
7

Bergström, Jonas, and Andreas Dahlqvist. "BESMART : a framework for shifting from BESpoke to MARkeT-driven requirements engineering." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2007. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-1308.

Full text
Abstract:
Requirements Engineering has two main directions, Bespoke (product developed for one customer) and Market-Driven (several potential customers for the same product). These two are in some ways very much alike but in some aspects very different. Over the last couple of years the software development industry has tended to shift more and more to Market-Driven Requirements Engineering. This has brought attention to the challenges facing a Market-Driven development organization, without focusing on the actual shift from Bespoke development. Based on the differences and similarities between Bespoke and Market-Driven Requirements Engineering, this thesis presents a framework for shifting from the former to the latter. The framework (BESMART) involves three steps. Firstly, the organization assesses their potential to become more Market-Driven. Secondly they assess their current way of working to identify which areas that may need to be improved. Finally, BESMART provides multiple suggestions that address the identified improvement areas. The organization is then able to choose the one that best suits their needs. This also lets the organization choose a solution that they find feasible. The framework was used at a case organization during its development. This way it was ensured that the theoretical framework could actually be used in a real world setting. The practical use of BESMART resulted in some refinements aimed at making it more applicable in industry. Once the framework had been applied, it was evaluated by representatives from the case organization. The industry evaluation resulted in some improvement suggestions but showed that the framework was both useful and usable and provided an improvement plan that seemed promising enough to pilot in the organization.
APA, Harvard, Vancouver, ISO, and other styles
8

Chidyiwa, Octavia. "An investigation of the best-practices for implementing an Ecommerce software engineering project comparing two common methodologies, viz. Agile and Traditional." University of the Western Cape, 2020. http://hdl.handle.net/11394/7925.

Full text
Abstract:
Masters of Science
In a world where technology is advancing at a very rapid pace, global competition has significantly increased, and this is putting pressure on software companies to produce quality software. It has therefore become critically important to manage well the implementation of software engineering projects by employing effective methods that ensure the best product is produced. The most popular software project implementation methodologies are the Traditional methods and Agile methods. This research explored these two methodologies by comparing the strength and weakness of both approaches. The research was conducted using a constructionist epistemology with a critical inquiry using the grounded theory methodology, applying both quantitative and qualitative methods to the case studies. Findings were collected through participant observation using a designed questionnaire targeting a selected sample of the study population. This sample of the population consisted of Ecommerce organizations in the Western Cape province of South Africa to establish which of the Traditional or Agile methods would best lead to the successful implementation of Ecommerce software engineering projects. The research results showed that the Agile methodology was the preferred and recommended approach. Very few participants of the research supported the Traditional approach to still be considered and used for projects with well-known end goals. An Ecommerce website prototype for a local Cape Town business was constructed as following the Agile approach to measure and validate the findings of the research. The prototype was built successfully from conception to the final delivery product and on time confirming the Agile approach as best for Ecommerce software development. In conclusion, the Agile methodology is the choice approach based on reviewed literature, the research results, and the prototype construction. These results will help in critical decision making regarding an appropriate development methodology to follow for the Ecommerce industry in the Western Cape.
APA, Harvard, Vancouver, ISO, and other styles
9

Petrillo, Fábio dos Santos. "Práticas ágeis no processo de desenvolvimento de jogos eletrônicos." reponame:Biblioteca Digital de Teses e Dissertações da UFRGS, 2008. http://hdl.handle.net/10183/22809.

Full text
Abstract:
A indústria de jogos eletrônicos está entrando em uma nova era, na qual a tecnologia e a criatividade fundem-se, produzindo alguns dos mais estonteantes entretenimentos do Séc. XXI. Essa indústria, que já em 2003 ultrapassou o faturamento do cinema, tendo um rendimento anual de bilhões de dólares, emerge como uma das mais poderosas, excitantes e influentes no mundo das artes. Mesmo com toda essa pujança e rentabilidade, muitos dos relatos sobre projetos de jogos (doravante denominados postmortems) mostram que a produção desses softwares não é uma tarefa simples, estando ainda distante de um processo de trabalho saudável e sinergético. Entretanto, ao analisarmos mais atentamente os postmortems disponíveis nos sites especializados em jogos eletrônicos, pode-se constatar a adoção de várias práticas de engenharia de software, em especial, práticas ágeis de desenvolvimento. Assim, é possível melhorar o processo de desenvolvimento de jogos eletrônicos através da aplicação dessas práticas? Que práticas são mais adequadas para este domínio? Que impacto sua adoção tem sobre propriedades subjetivas como a criatividade e a diversão? O objetivo deste trabalho é avaliar o impacto da aplicação de práticas ágeis no processo de desenvolvimento de jogos eletrônicos, analisando os principais problemas da indústria de jogos, levantando as boas práticas já adotadas e propondo um conjunto de práticas ágeis que contemplem as características do processo de desenvolvimento de jogos. Finalmente, com o intuito de obter resultados experimentais da aplicação dessas práticas, será realizado um estudo de caso, possibilitando avaliar seus efeitos sobre o processo de trabalho.
The industry of electronic games is entering a new age, in which technology and creativity are fused, producing some of the most stunning entertainment of the 21st Century. This industry, which already in 2003 exceeded the cinema invoice, having an annual yield of billions of dollars, emerges nowadays as one of the most powerful, exciting and influential in the world of arts. Despite of all this exuberance and profitability, many reports about games projects show that the production of these softwares is not a simple task, surrounded by common problems and being still distant of having a healthy and synergetic work process. However, despite of problems found, game postmortems claims to use software engineering best practices in the game development process, specially, agile practices. Thus, is possible to improve the electronic game development process using agile practices? What practices are most appropriate for game development? What is the impact of such practices on subjective properties as creativity and fun? The aim of this work is to study the effects of agile practices on electronic game development process, analysing the most important problems in the game industry, surveying best practices and proposing a set of agile practices focused on the game development issues. Finally, a case study will be presented.
APA, Harvard, Vancouver, ISO, and other styles
10

Trueheart, Stacie Lee. "Health Literacy Best Practices in Policy Development." ScholarWorks, 2018. https://scholarworks.waldenu.edu/dissertations/4989.

Full text
Abstract:
Low health literacy is a problem the U.S. faces and, like health care itself, is a complex issue stemming from patient demographics and the healthcare providers being very diverse. Tools have been developed to mitigate the risks of low health literacy, however, without formal policy. The purpose of this qualitative case study was to explore and compare commonalities in health literacy best practices of organizations that are recognized as leaders in health literacy and are addressing low health literacy in their communities. By comparing the organizations' abilities to implement standards of plain language and health literacy tools/guidelines, best practice and policy recommendations could be made to various organizations regardless of level (local, state, federal, or nonprofit). The theoretical framework was based on the Evans and Stoddart framework of determinants of health and the health behavioral theories. The conceptual framework was based on health literacy best practices and policy. The research questions focused on how organizations implement health literacy tools/guidelines, the impact of health literacy best practices on policy development and addressing health literacy through formal policy. The qualitative multiple case study used open-ended interview questions via telephone conferencing, with 13 participants from health literacy organizations. The analysis was done by coding and bracketing the responses manually and with NVivo software. Results indicate that health literacy policy development and involvement exists but it is not derived from the health literacy best practices. The implications for positive social change for this study impacts the patient (individual), community, organization, and society through best practices and recommendations for policy development.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Software Development Best Practices"

1

1970-, Hansmann Uwe, ed. Agile software development: Best practices for large software development projects. Heidelberg [Germany]: Springer, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

United States. General Accounting Office. Accounting and Information Management Division. Defense software: Review of Defense report on software development best practices. Washington, D.C. (P.O. Box 37050, Washington 20013): The Division, 2000.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

1956-, Cagley Thomas M., ed. Mastering software project management: Best practices, tools and techniques. Ft. Lauderdale, FL: J. Ross Pub., 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

1951-, Haug Michael, ed. Software best practice. Berlin: Springer, 2001.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

A, Beasley Reyna, ed. Software project cost and schedule estimating: Best practices. Upper Saddle River, NJ: Prentice Hall, 1998.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

A, Halpin T., Krogstie John, and Proper Erik, eds. Innovations in information systems modeling: Methods and best practices. Hershey, PA: Information Science Reference, 2009.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Associates, Culpepper and. On-time software development: Best practices for building quality products. Alpharetta, Ga: Culpepper and Associates, 1999.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

1958-, Stanwick Victor R., ed. Web application design handbook: Best practices for web-based software. Amsterdam: Morgan Kaufmann Publishers, 2004.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

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

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Chemuturi, Murali. Mastering software quality assurance: Best practices, tools and techniques for software developers. Fort Lauderdale, Fla: J. Ross Pub., 2011.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Software Development Best Practices"

1

Kurtz, Jamie, and Thomas Besluau. "Software Development Best Practices with Drupal." In Pro Drupal as an Enterprise Development Platform, 217–39. Berkeley, CA: Apress, 2013. http://dx.doi.org/10.1007/978-1-4302-6005-9_10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Rost, Dominik, Balthasar Weitzel, Matthias Naab, Torsten Lenhart, and Hartmut Schmitt. "Distilling Best Practices for Agile Development from Architecture Methodology." In Software Architecture, 259–67. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-23727-5_21.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Schatten, Alexander, Markus Demolsky, Dietmar Winkler, Stefan Biffl, Erik Gostischa-Franta, and Thomas Östreicher. "Qualitätssicherung und Test-Driven Development." In Best Practice Software-Engineering, 113–62. Heidelberg: Spektrum Akademischer Verlag, 2010. http://dx.doi.org/10.1007/978-3-8274-2487-7_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Ransome, James F., Anmol, and Mark S. Merkow. "Design and Development (A4): SDL Activities and Best Practices." In Practical Core Software Security, 123–49. Boca Raton: Auerbach Publications, 2022. http://dx.doi.org/10.1201/9781003319078-6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Ransome, James F., Anmol, and Mark S. Merkow. "Design and Development (A3): SDL Activities and Best Practices." In Practical Core Software Security, 103–22. Boca Raton: Auerbach Publications, 2022. http://dx.doi.org/10.1201/9781003319078-5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Kuzniarz, Ludwik, and Miroslaw Staron. "Best Practices for Teaching UML Based Software Development." In Satellite Events at the MoDELS 2005 Conference, 320–32. Berlin, Heidelberg: Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11663430_33.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Ordoñez-Pacheco, Rodrigo, Karen Cortes-Verdin, and Jorge Octavio Ocharán-Hernández. "Best Practices for Software Development: A Systematic Literature Review." In Advances in Intelligent Systems and Computing, 38–55. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-63329-5_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Chemuturi, Murali. "Pitfalls and Best Practices in Requirements Engineering and Management." In Requirements Engineering and Management for Software Development Projects, 203–15. New York, NY: Springer New York, 2012. http://dx.doi.org/10.1007/978-1-4614-5377-2_14.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Gasca-Hurtado, Gloria Piedad, Vianca Vega-Zepeda, Mirna Muñoz, and Jezreel Mejía. "Protocol to Design Techniques for Implementing Software Development Best Practices." In Communications in Computer and Information Science, 115–26. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-24647-5_10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Hölzl, Matthias, Nora Koch, Mariachiara Puviani, Martin Wirsing, and Franco Zambonelli. "The Ensemble Development Life Cycle and Best Practices for Collective Autonomic Systems." In Software Engineering for Collective Autonomic Systems, 325–54. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-16310-9_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software Development Best Practices"

1

Zeid, Amir. "Best practices for teaching object-oriented framework development." In Proceedings. 18th Conference on Software Engineering Education & Training. IEEE, 2005. http://dx.doi.org/10.1109/cseet.2005.10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Kuzak, Mateusz, Jen Harrow, Rafael C. Jimenez, Paula Andrea Martinez, Fotis E. Psomopoulos, Radka Svobodova Varekova, and Allegra Via. "Lesson Development for Open Source Software Best Practices Adoption." In 2018 IEEE 14th International Conference on e-Science (e-Science). IEEE, 2018. http://dx.doi.org/10.1109/escience.2018.00011.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Dautovic, Andreas, Reinhold Plosch, and Matthias Saft. "Automatic Checking of Quality Best Practices in Software Development Documents." In 2011 11th International Conference on Quality Software (QSIC). IEEE, 2011. http://dx.doi.org/10.1109/qsic.2011.23.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Ahmed, Faheem, and Luiz Fernando Capretz. "Best practices of RUP ® in software product line development." In 2008 International Conference on Computer and Communication Engineering (ICCCE). IEEE, 2008. http://dx.doi.org/10.1109/iccce.2008.4580828.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Ibarra-Florencio, Nivardo, Jorge Buenabad-Chavez, and José Rangel-Garcia. "BP4ED: Best Practices Online for eLearning Content Development - Development Based on Learning Objects." In 9th International Conference on Software Engineering and Applications. SCITEPRESS - Science and and Technology Publications, 2014. http://dx.doi.org/10.5220/0005106101760182.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Est'cio, Bernardo Jose da Silva. "Development of a Set of Best Practices for Distributed Pair Programming." In 2012 Seventh IEEE International Conference on Global Software Engineering Workshop (ICGSEW). IEEE, 2012. http://dx.doi.org/10.1109/icgsew.2012.8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Vieira, Ricardo Godoi, Breno Lisi Romano, Gláucia Braga e Silva, Henrique Fernandes de Campos, and Adilson Marques da Cunha. "Using Best Practices of Software Engineering into a Real Time System Development." In 2009 Sixth International Conference on Information Technology: New Generations. IEEE, 2009. http://dx.doi.org/10.1109/itng.2009.208.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Kennedy, David N., Christian Haselgrove, Robert Buccigrossi, and Jeffrey Grethe. "Software development for neuroimaging: Promoting community access and best practices through NITRC." In 2009 IEEE International Symposium on Biomedical Imaging: From Nano to Macro (ISBI). IEEE, 2009. http://dx.doi.org/10.1109/isbi.2009.5193260.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Berger, Christian, Bjornborg Nguyen, and Ola Benderius. "Containerized Development and Microservices for Self-Driving Vehicles: Experiences & Best Practices." In 2017 IEEE International Conference on Software Architecture Workshops (ICSAW). IEEE, 2017. http://dx.doi.org/10.1109/icsaw.2017.56.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Mohan, Vaishnavi, Lotfi ben Othmane, and Andre Kres. "BP: Security Concerns and Best Practices for Automation of Software Deployment Processes: An Industrial Case Study." In 2018 IEEE Cybersecurity Development (SecDev). IEEE, 2018. http://dx.doi.org/10.1109/secdev.2018.00011.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Software Development Best Practices"

1

Eslinger, S. Software Acquisition and Software Engineering Best Practices. Fort Belvoir, VA: Defense Technical Information Center, November 1999. http://dx.doi.org/10.21236/ada371477.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Fisher, Maryl. EISA 432 Energy Audits Best Practices: Software Tools. Office of Scientific and Technical Information (OSTI), November 2014. http://dx.doi.org/10.2172/1166056.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Mead, Nancy, Lawrence Tobin, and Suzanne Couturiaux. Best Training Practices Within the Software Engineering Industry. Fort Belvoir, VA: Defense Technical Information Center, November 1996. http://dx.doi.org/10.21236/ada324517.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Arhin, Stephen, Babin Manandhar, Kevin Obike, and Melissa Anderson. Impact of Dedicated Bus Lanes on Intersection Operations and Travel Time Model Development. Mineta Transportation Institute, June 2022. http://dx.doi.org/10.31979/mti.2022.2040.

Full text
Abstract:
Over the years, public transit agencies have been trying to improve their operations by continuously evaluating best practices to better serve patrons. Washington Metropolitan Area Transit Authority (WMATA) oversees the transit bus operations in the Washington Metropolitan Area (District of Columbia, some parts of Maryland and Virginia). One practice attempted by WMATA to improve bus travel time and transit reliability has been the implementation of designated bus lanes (DBLs). The District Department of Transportation (DDOT) implemented a bus priority program on selected corridors in the District of Columbia leading to the installation of red-painted DBLs on corridors of H Street, NW, and I Street, NW. This study evaluates the impacts on the performance of transit buses along with the general traffic performance at intersections on corridors with DBLs installed in Washington, DC by using a “before” and “after” approach. The team utilized non-intrusive video data to perform vehicular turning movement counts to assess the traffic flow and delays (measures of effectiveness) with a traffic simulation software. Furthermore, the team analyzed the Automatic Vehicle Locator (AVL) data provided by WMATA for buses operating on the study segments to evaluate bus travel time. The statistical analysis showed that the vehicles traveling on H Street and I Street (NW) experienced significantly lower delays during both AM (7:00–9:30 AM) and PM (4:00–6:30 PM) peak hours after the installation of bus lanes. The approximation error metrics (normalized squared errors) for the testing dataset was 0.97, indicating that the model was predicting bus travel times based on unknown data with great accuracy. WMATA can apply this research to other segments with busy bus schedules and multiple routes to evaluate the need for DBLs. Neural network models can also be used to approximate bus travel times on segments by simulating scenarios with DBLs to obtain accurate bus travel times. Such implementation could not only improve WMATA’s bus service and reliability but also alleviate general traffic delays.
APA, Harvard, Vancouver, ISO, and other styles
5

Adams, R. J., S. Eslinger, K. L. Owens, and M. A. Rich. Software Acquisition Best Practices: Experiences From the Space Systems Domain. Fort Belvoir, VA: Defense Technical Information Center, September 2004. http://dx.doi.org/10.21236/ada427935.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Roth, Christian. Design of the In-vehicle Experience. SAE International, June 2022. http://dx.doi.org/10.4271/epr2022012.

Full text
Abstract:
The in-vehicle experience, both physical and digital, is increasingly the differentiating factor between vehicles. Since touch displays, smart surfaces, and internet connectivity are present in most vehicle segments, the growing resemblance of in-vehicle experiences with mobile experiences leads to user expectations on par with smartphones. While manufacturers are faced with providing suitable service offerings that are safe to use, they must also identify services to exclude or limit, without encouraging drivers to resort back to their mobile devices. This increasingly complex in-vehicle experience design process is being shaped by new stakeholders, including operating system providers and application developers. Design of the In-vehicle Experience examines the challenging and changing relationships between manufacturers (that lack in software development and mobile experience design skills) and new stakeholders (that lack the decades of experience designing for the driving context). The report also discusses augmenting and expanding existing guidelines and best practices to address the challenges of modern in-vehicle experience design.
APA, Harvard, Vancouver, ISO, and other styles
7

Montgomery, Brian T. Defense, Diplomacy and Development - Status, Challenges, and Best Practices. Fort Belvoir, VA: Defense Technical Information Center, February 2012. http://dx.doi.org/10.21236/ada561488.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Andrews, Russel D. Development of a Cetacean Tagging Best Practices Guidelines Document. Fort Belvoir, VA: Defense Technical Information Center, September 2011. http://dx.doi.org/10.21236/ada597823.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Spangler, Stephen, Roger Fujan, Carl Broyles, Brian Baker, Justin Jameson, Gerald Piotrowski, John Groboski, and Steve Hutsell. Record Package guidance : best practices. Engineer Research and Development Center (U.S.), August 2021. http://dx.doi.org/10.21079/11681/41460.

Full text
Abstract:
The CAD/BIM Technology Center receives numerous questions throughout the year regarding the development of a Record Package that shows as-built conditions. While the Center does produce Standards on the look and organization of CAD drawings that are used to show as-built conditions, users wanted guidance on the Record Package development. The Chicago District had undertaken the development of such guidance, but a formal document was never officially released. The CAD/BIM Community of Practice (CoP) Work Structure Committee finished this guidance and their efforts are reflected in this document.
APA, Harvard, Vancouver, ISO, and other styles
10

El-Rayes, Khaled, and Ernest-John Ignacio. Evaluating the Benefits of Implementing Mobile Road Weather Information Sensors. Illinois Center for Transportation, February 2022. http://dx.doi.org/10.36501/0197-9191/22-004.

Full text
Abstract:
State departments of transportation (DOTs) have traditionally utilized fixed road weather information sensors (RWIS) to improve road safety during inclement weather; enhance the management of labor, equipment, and materials for winter road maintenance; and reduce adverse environmental impacts from road maintenance activities. Despite the benefits of these fixed RWIS sites, their coverage and effectiveness are limited because of their stationary locations. To overcome these limitations, recent advances in mobile road weather information sensing technology and cellular communications have enabled the development of mobile RWIS that can be deployed on vehicles to expand the limited coverage of fixed RWIS networks. Combining mobile RWIS, fixed RWIS networks, automatic vehicle location, and maintenance decision support systems (MDSS) provide DOTs with accurate georeferenced road and weather information that can be used by DOTs to optimize winter road maintenance operations and deicer applications. This report presents the findings of a research project funded by the Illinois Department of Transportation to investigate the effectiveness of mobile RWIS and MDSS in improving winter maintenance operations. This project had the following three objectives. First, conduct a literature review to gather and analyze current practices and latest research studies on mobile RWIS and their use for collecting real-time winter roadway conditions to optimize winter maintenance operations. Second, perform interviews with other state DOTs to gather and analyze their experiences and best management practices for the deployment and use of mobile RWIS and MDSS. Third, develop recommendations for a pilot study to evaluate the deployment and performance of mobile RWIS and MDSS in order to determine their effectiveness, implementation requirements, software/technology needs, operational challenges, and life-cycle costs.
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Software Development Best Practices' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography