Journal articles: '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

11

Jiménez, Rafael C., Mateusz Kuzak, Monther Alhamdoosh, Michelle Barker, Bérénice Batut, Mikael Borg, Salvador Capella-Gutierrez, et al. "Four simple recommendations to encourage best practices in research software." F1000Research 6 (June 13, 2017): 876. http://dx.doi.org/10.12688/f1000research.11407.1.

Full text

Abstract:

Scientific research relies on computer software, yet software is not always developed following practices that ensure its quality and sustainability. This manuscript does not aim to propose new software development best practices, but rather to provide simple recommendations that encourage the adoption of existing best practices. Software development best practices promote better quality software, and better quality software improves the reproducibility and reusability of research. These recommendations are designed around Open Source values, and provide practical suggestions that contribute to making research software and its source code more discoverable, reusable and transparent. This manuscript is aimed at developers, but also at organisations, projects, journals and funders that can increase the quality and sustainability of research software by encouraging the adoption of these recommendations.

APA, Harvard, Vancouver, ISO, and other styles

12

Garijo, Daniel, Hervé Ménager, Lorraine Hwang, Ana Trisovic, Michael Hucka, Thomas Morrell, and Alice Allen. "Nine best practices for research software registries and repositories." PeerJ Computer Science 8 (August 8, 2022): e1023. http://dx.doi.org/10.7717/peerj-cs.1023.

Full text

Abstract:

Scientific software registries and repositories improve software findability and research transparency, provide information for software citations, and foster preservation of computational methods in a wide range of disciplines. Registries and repositories play a critical role by supporting research reproducibility and replicability, but developing them takes effort and few guidelines are available to help prospective creators of these resources. To address this need, the FORCE11 Software Citation Implementation Working Group convened a Task Force to distill the experiences of the managers of existing resources in setting expectations for all stakeholders. In this article, we describe the resultant best practices which include defining the scope, policies, and rules that govern individual registries and repositories, along with the background, examples, and collaborative work that went into their development. We believe that establishing specific policies such as those presented here will help other scientific software registries and repositories better serve their users and their disciplines.

APA, Harvard, Vancouver, ISO, and other styles

13

Park, Soojin, Mansoo Hwang, Sangeun Lee, and Young Park. "A Generic Software Development Process Refined from Best Practices for Cloud Computing." Sustainability 7, no. 5 (April 30, 2015): 5321–44. http://dx.doi.org/10.3390/su7055321.

Full text

APA, Harvard, Vancouver, ISO, and other styles

14

Balijepally, VenuGopal, Gerald DeHondt, Vijayan Sugumaran, and Sridhar Nerur. "Agility in Software Development and Project Value." Journal of Database Management 28, no. 4 (October 2017): 40–59. http://dx.doi.org/10.4018/jdm.2017100103.

Full text

Abstract:

Agile Development Methods, considered as an alternative to the traditional plan-based methods, have received much attention since their inception. These practices have evolved and developed over time, culminating in 2001 with the Agile Manifesto. Since that time, preferred methodologies, implementations, and best practices have continued to evolve with a focus on doing what works best for the individual company or project. However, the concept of agility in software development has remained quite nebulous, lacking in clarity particularly about its underlying dimensions. In this research the authors conceive agility in terms of four distinct dimensions. Drawing from the theoretical perspective of holographic organization, they develop a model explaining how each of these underlying dimensions of agility contributes to project value in software teams. The authors test the model using survey data collected from industry practitioners and discuss findings.

APA, Harvard, Vancouver, ISO, and other styles

15

Bozza, C., and T. Chiarusi. "KM3NeT Acquisition Control: advanced techniques and best practices in data acquisition software development." Journal of Instrumentation 16, no. 08 (August 1, 2021): C08002. http://dx.doi.org/10.1088/1748-0221/16/08/c08002.

Full text

APA, Harvard, Vancouver, ISO, and other styles

16

Torres-Ricaurte, Diana María, and Carlos Mario Zapata-Jaramillo. "Best practices of interoperability among heterogeneous software systems: a Semat-based representation." Revista Facultad de Ingeniería 26, no. 44 (December 31, 2016): 155. http://dx.doi.org/10.19053/01211129.v26.n44.2017.5790.

Full text

Abstract:

Interoperability among heterogeneous software systems is a software quality sub-characteristic. Some methods for dealing with interoperability exhibit differences in aspects like generality, development method, and work products, among others. However, some authors understand interoperability as a non-functional requirement with general-purpose practices for identifying and specifying such requirement. Other authors assess and achieve interoperability by using work products falling beyond defined practices. Consequently, in this paper we propose four best practices in order to accomplish interoperability among heterogeneous software systems. Our best practices are represented with the Semat (Software Engineering Method and Theory) kernel, since it includes a language with simple and precise elements. Definition of interoperability best practices enables unification of the effort focused on software systems interoperability.

APA, Harvard, Vancouver, ISO, and other styles

17

Huang, Qing. "Research on the Key Points of Best Practice of Software Architecture Design." Advanced Materials Research 225-226 (April 2011): 992–95. http://dx.doi.org/10.4028/www.scientific.net/amr.225-226.992.

Full text

Abstract:

Software architecture design is one decision-making process for a series of major issues from software development and the best practices had been summed up. Nevertheless, the strict observance of the best practices still cannot raise the design line from the class development to framework development. The reason was that most imitators are unable to understand accurately the essence of two key words of "iteration" and "divide and rule". Therefore, this paper made further study of the "iteration" and "divide and rule". First, the meaning of "iteration" would be redefined. It is that each cycle should have a respective emphasis and end with the time deadline so as to make a clear distinction among them and improve iterative efficiency. Second, the meaning of "divide and rule" would also be redefined. It is that the passive decomposition based on Test First is better than active decomposition. Because it is the most suitable to have no alternative but to decompose according to current concrete conditions. By this way, best practices of architectural design can be implemented in real project, so as to improve the level of architecture design in essence.

APA, Harvard, Vancouver, ISO, and other styles

18

De Almeida, Jonathas Arestides, Helder Jerônimo Leite Rangel, Matheus Augusto Coutinho Costa, Maurício Barbosa De Lira Filho, Francisco Petrônio Alencar De Medeiros, and Heremita Brasileiro Lira. "Guia interativo de boas práticas em Engenharia de Software." Revista Principia - Divulgação Científica e Tecnológica do IFPB 1, no. 44 (March 7, 2019): 23. http://dx.doi.org/10.18265/1517-03062015v1n44p23-30.

Full text

Abstract:

Analyzing the diversity of best practices in Software Engineering present in industry, the Software Engineering Research Group of the Federal Institute of Paraíba realized the need to organize them together in a web repository so that the access, identification and proper application in various software project scenarios is easier. The objective of work is to present the first functional version of this web environment, in order to enable the best practices in Software Engineering as researched by the group. This project has been developed using agile methodologies and is the result of a trio of complementary and collaborative projects from the research group: Repository of Practices in Management of Software Project, Repository of Practices in the Software Development Process, together with the project Reconfigurable Best Practices Environment in Software Engineering.

APA, Harvard, Vancouver, ISO, and other styles

19

Tharian, Manoj. "Rational Unified Process Part-1." Mapana - Journal of Sciences 1, no. 1 (August 22, 2002): 81–94. http://dx.doi.org/10.12723/mjs.1.8.

Full text

Abstract:

This paper presents an overview of the Rational Unified Process. The Rational unified Process is a software engineering process, delivered through a web-enabled, searchable knowledge base. The process enhances team productivity and delivers software best practices via guidelines, templates and tool mentors for all critical software lifecycle activities. The knowledge base allows development teams to gain the full benefits of the industry-standard Unified Modeling Language(UML). The rational Unified Process is a software Engineering Process. It provides a disciplined approach to assigning tasks and responsibilities within development organization. Its goal is to ensure the production of high-quality software that meets the needs of its end-users, within a predictable schedule and budget.[11,13] The rational Unified Process is a process product , developed and maintained by Rational Software. The development team for the Rational Unified Process are working closely with customers, partners, Rational's that the process is continuously updated and improved upon to reflect recent experiences and evolving and proven best practices. The Rational Unified Process is a guide for how to effectively use the Unified modeling Language(UML). The UML is a industry-standard language that allows us to clearly communicate requirements, architectures and designs. The UML is a industry-standard language that allows us to clearly communicate requirements architectures and designs. the UML originally created by Rational Software, and is now maintained by the standards organization Object Management Group(OMG).[4] the Rational Unified Process captures many of the best practices in modern software development in a form that is suitable for a wide range of projects and organizations. Deploying these best practices 3/4 using the Rational Unified Process as your guide 3/4 offers development teams a number of key advantages. In next section, we describe the six fundamental best practices of the Rational Unified Process. The Rational Unified Process describes how to effectively deploy commercially proven approaches to software development for software development teams. These are called "best practices" not so much because you can precisely quantify their value, but rather, because they are observed to be commonly used in industry by successful organizations.

APA, Harvard, Vancouver, ISO, and other styles

20

Almeida, Samyra Lara Ferreira, Nadja Da Nóbrega Rodrigues, Heremita Brasileiro Lira, Carlos Diego Quirino Lima, Ana Karina De Melo Pedrosa Dunning, and Rayssa Mª S. de Freitas. "Aplicação e análise de processo de desenvolvimento de software: um estudo de caso no GPES-IFPB." Revista Principia - Divulgação Científica e Tecnológica do IFPB 1, no. 43 (December 13, 2018): 152. http://dx.doi.org/10.18265/1517-03062015v1n43p152-165.

Full text

Abstract:

The Software Engineering Research Group from the Federal Institute of Paraiba is developing a research to identify and publicize on the web the best practices in software development processes, seeking to propagate their use among professionals and undergraduates. As one of the stages to completion of this work, the team is working on the conformation and refinement of its software development process, based on the best practices identified in research activities, aiming to systematise their technical activities for software production. This article aims to present the software development scenario in a research environment and the proposed software development software for the focal research group . As this is an exploring and applied research, the main methodological procedures used were: bibliographical research, definition, application and evaluation of the software development process. Results indicate: the proposition of software development process, application and result analysis of its use, and improvement suggestions in its recommendations.

APA, Harvard, Vancouver, ISO, and other styles

21

Preuveneers, Davy, and Paulo Novais. "A survey of software engineering best practices for the development of smart applications in Ambient Intelligence." Journal of Ambient Intelligence and Smart Environments 4, no. 3 (2012): 149–62. http://dx.doi.org/10.3233/ais-2012-0150.

Full text

APA, Harvard, Vancouver, ISO, and other styles

22

Kramer, Jeremy, and Torrey Wagner. "Developmental Test and Requirements: Best Practices of Successful Information Systems Using Agile Methods." Delivering Performance at the Speed of Relevance: Agile Aquisition Approaches 26, no. 88 (April 1, 2019): 128–50. http://dx.doi.org/10.22594/dau.19-819.26.02.

Full text

Abstract:

This article provides insights into the current state of developmental testing (DT) and requirements management in Department of Defense information systems employing Agile development. The authors describe the study methodology and provide an overview of Agile development and testing. Insights are described for requirements, detailed planning, test execution, and reporting. This work articulates best practices related to DT and requirements management strategies for programs employing modernized Software Development Life Cycle practices.

APA, Harvard, Vancouver, ISO, and other styles

23

Murphy, Thomas, and Kathryn Cormican. "Towards holistic goal centered performance management in software development: lessons from a best practice analysis." International Journal of Information Systems and Project Management 3, no. 4 (February 8, 2022): 23–36. http://dx.doi.org/10.12821/ijispm030402.

Full text

Abstract:

There are strong motivating factors for more effective performance measurement practices in software development. Astute practices in this domain are lauded to improve efficiency and effectiveness. However previous studies have shown that measurement in software is intricate, complex and fraught with challenges. Consequently it is poorly managed in practice. Our research seeks to better understand performance management in a real world software development setting in order to identify the challenges and generate a roadmap for improvement. This paper presents findings from an inductive analysis of a radical measurement program in a global software organization. Our study investigates the level at which non-compliance with best practice can explain the company’s disappointing results. We found that a narrow focus on projects, rather than on organizational goals, has seriously hindered its success. We also found that the rate of change in the organization as a whole was impinging on the effective implementation of its measurement program. An analysis of the results demonstrates just how challenging software measurement is. The findings provide an evaluation of best practice relative to the literature that is informed by real industry experience.

APA, Harvard, Vancouver, ISO, and other styles

24

Ahmad Ibrahim, Siti Rohana, Jamaiah Yahaya, and Hasimi Sallehudin. "Green Software Process Factors: A Qualitative Study." Sustainability 14, no. 18 (September 7, 2022): 11180. http://dx.doi.org/10.3390/su141811180.

Full text

Abstract:

In the twenty-first century, the use of software is growing due to many applications requiring large and complex software. Many people do not realise that the use of software has influenced the operation of computer hardware to move indirectly as it affects the hardware’s energy consumption and carbon emissions. Previous studies focused more on models and tools to measure the impact of power consumption and energy efficiency from hardware than on software development studies. Energy consumption can be optimised by the greening software process throughout all phases of development activity. Besides, the current green software process models are more focused on environmental and economic elements and do not integrate with the waste elements in the development phase. Integrating sustainability and waste elements is essential to ensure that the development process complies with green process standards. A qualitative method is used through interviews involving eight informants from Malaysia’s public and private sectors. The objectives of the empirical study are to reveal the current practices of the green software process in industry, identify software process waste and determine green factors associated with the software process. The analysis is guided by a thematic approach using Atlas.ti 8 software. This paper describes the results from the qualitative study that consists of three main themes: best practices of a software process, nine software wastes (building the wrong feature, rework, unnecessarily complex solutions, extraneous cognitive load, psychological distress, waiting, knowledge loss, ineffective communication, delay), and six green factors (resources, people, organisational, technical, environmental, technology). The analysis findings indicate that the software industry needs elements of best practices, green practices, and software technologies in each development phase to produce a green and sustainable software process. The advancement of computing today presents technology as an essential factor in green elements to ensure that the software process is constantly updated and always green.

APA, Harvard, Vancouver, ISO, and other styles

25

Misra, Subhas C., and Virender Singh. "Conceptualizing open agile software development life cycle (OASDLC) model." International Journal of Quality & Reliability Management 32, no. 3 (March 2, 2015): 214–35. http://dx.doi.org/10.1108/ijqrm-08-2013-0127.

Full text

Abstract:

Purpose – Software development life cycle (SDLC) has always been the core methodology for any software engineer that depicts the entire development process which an organization is bound to utilize to achieve successful software. The purpose of this paper is to bring forth a conceptual model after analysing the best practices in SDLC, and extracting the best out of agile methodologies and the open source software, thereby bringing forward an optimised structure. Design/methodology/approach – The OASDLC is hypothesized specifically for “Brihaspati” project and is formulated keeping in mind the gaps and limitations posed by existing SDLC models. OASDLC is further put to test for achieving lower costs and efforts involved. The tests are further substantiated by means of hypothesis validation through execution of a survey based research. Findings – It has been observed that the present conceptual model further optimizes the efforts involved while adopting such a practice. Originality/value – This paper proposes a novel SDLC model so as to achieve a best practice for a software project. On analysing the issues involved such as tight budget and timelines, it led the authors to formulate a newer concept “Open Agile Software Development Life Cycle model” (OASDLC).

APA, Harvard, Vancouver, ISO, and other styles

26

Park, Bo Kyung, Chae Yun Seo, Ki Du Kim, Jong Hoon Lee, and R. Young Chul Kim. "Best Practices on Software Development and Management Process for the Republic of Korea Army Information System." Journal of KIISE 47, no. 10 (October 31, 2020): 911–25. http://dx.doi.org/10.5626/jok.2020.47.10.911.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

Garg, Adarsh, D. P. Goyal, and Anu Singh Lather. "The influence of the best practices of information system development on software SMEs: a research scope." International Journal of Business Information Systems 5, no. 3 (2010): 268. http://dx.doi.org/10.1504/ijbis.2010.031930.

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

Inkinen, Tommi. "Best practices of the Finnish Government Information Society Policy Programme." Transforming Government: People, Process and Policy 6, no. 2 (May 25, 2012): 167–87. http://dx.doi.org/10.1108/17506161211246917.

Full text

Abstract:

PurposeThe purpose of this paper is to classify the best practices selected by the “Finnish Government Information Society Policy Programme” with a framework that includes four segments: technology, supply, demand, and spatial impact scale. These segments are elemental parts of service development processes, the best of which are classified into seven distinct categories: Telecommunications; Citizen Readiness; Education and Research; Working Life; Public Sector Electronic Services; Social and Health Care; and Electronic Commerce.Design/methodology/approachThe empirical material includes the best practices as defined by the Finnish Government Information Society Policy Programme 2003‐2007. The best practices were analyzed through their project descriptions. The data were classified with textual content analysis into categories that were further analyzed numerically. The tools of statistical analysis included cross‐tabulations and chi‐square tests.FindingsThe results reveal differentiation among the best practices. The majority of service development concerns applications and software. However, physical infrastructure development was also present in the largest cities. Public sector organizations produced more than half of all of the best practices selected. Public‐private partnerships were also common, and the majority of service development was targeted to the national level.Research limitations/implicationsThe best practices analyzed illustrate the view of the Finnish Government Information Society Policy Programme. Consequently, the analysis highlights the values of the policy program. The data include only a small segment of on‐going development activity and represents a case study and therefore it is limited to the Finnish and Nordic context.Originality/valueThis paper uses a unique primary data set. The results obtained reflect the originality of the study and clearly provide sufficient grounds to consider electronic service development. The results are also transferable to public sector decision makers dealing with regional policies and development.

APA, Harvard, Vancouver, ISO, and other styles

29

Muñoz, Mirna, Pérez Negrón, Jezreel Mejia, and Lara López. "Actual state of the coverage of Mexican software industry requested knowledge regarding the project management best practices." Computer Science and Information Systems 13, no. 3 (2016): 849–73. http://dx.doi.org/10.2298/csis160808040m.

Full text

Abstract:

In Mexico, the small and medium size enterprises (SMEs) are key for the software development industry. For them, having highly qualified personal for the development of high quality software products is a fundamental piece to guarantee their permanency in the market. Therefore, matching the software industry requirements with the academy training represents a significant problem that must be addressed for both sectors benefit. This paper presents an analysis of the coverage between the Moprosoft norm, standard developed to be used for software industry to ensure quality in Software Engineering practices, and ten academic curricular programs of higher education related to Computer Science and Informatics; to get an overview of the knowledge and skills that Computer Science students acquire at universities, regarding knowledge required in organizations that work under process models. In addition, a survey to 32 SMEs was conducted to contrast the coverage results with their hired, recently graduated, personal.

APA, Harvard, Vancouver, ISO, and other styles

30

Althar, Raghavendra Rao, Abdulrahman Alahmadi, Debabrata Samanta, Mohammad Zubair Khan, and Ahmed H. Alahmadi. "Mathematical foundations based statistical modeling of software source code for software system evolution." Mathematical Biosciences and Engineering 19, no. 4 (2022): 3701–19. http://dx.doi.org/10.3934/mbe.2022170.

Full text

Abstract:

<abstract><p>Source code is the heart of the software systems; it holds a wealth of knowledge that can be tapped for intelligent software systems and leverage the possibilities of reuse of the software. In this work, exploration revolves around making use of the pattern hidden in various software development processes and artifacts. This module is part of the smart requirements management system that is intended to be built. This system will have multiple modules to make the software requirements management phase more secure from vulnerabilities. Some of the critical challenges bothering the software development community are discussed. The background of Machine Learning approaches and their application in software development practices are explored. Some of the work done around modeling the source code and approaches used for vulnerabilities understanding in software systems are reviewed. Program representation is explored to understand some of the principles that would help in understanding the subject well. Further deeper dive into source code modeling possibilities are explored. Machine learning best practices are explored inline with the software source code modeling.</p></abstract>

APA, Harvard, Vancouver, ISO, and other styles

31

Humayun, Mamoona, Mahmood Niazi, Maram Fahhad Almufareh, N. Z. Jhanjhi, Sajjad Mahmood, and Mohammad Alshayeb. "Software-as-a-Service Security Challenges and Best Practices: A Multivocal Literature Review." Applied Sciences 12, no. 8 (April 14, 2022): 3953. http://dx.doi.org/10.3390/app12083953.

Full text

Abstract:

Cloud computing (CC) is the delivery of computing services on demand and is charged using a “pay per you use” policy. Of the multiple services offered by CC, SaaS is the most popular and widely adapted service platform and is used by billions of organizations due to its wide range of benefits. However, security is a key challenge and obstacle in cloud adoption and therefore needs to be addressed. Researchers and practitioners (R&P) have discussed various security challenges for SaaS along with possible solutions. However, no research study exists that systematically accumulates and analyzes the security challenges and solutions. To fill this gap and provide the state-of-the-art (SOTA) picture of SaaS security, this study provides a comprehensive multivocal literature review (MVLR), including SaaS security issues/challenges and best practices for mitigating these security issues. We identified SaaS security issues/challenges and best practices from the formal literature (FL) as well as the grey literature (GL) to evaluate whether R&P is on the same page or if controversies exist. A total of 93 primary studies were identified, of which 58 are from the FL and 35 belong to the GL. The studies are from the last ten years, from 2010 to 2021. The selected studies were evaluated and analyzed to identify the key security issues faced by SaaS computing and to be aware of the best practices suggested by R&P to improve SaaS security. This MVLR will assist SaaS users to identify the many areas in which additional research and development in SaaS security is required. According to our study findings, data breaches/leakage, identity and access management, governance and regulatory compliance/SLA compliance, and malicious insiders are the key security challenges with the maximum frequency of occurrence in both FL and GL. On the other hand, R&P agree that up-to-date security controls/standards, the use of strong encryption techniques, regulatory compliance/SLA compliance, and multifactor authentication are the most important solutions.

APA, Harvard, Vancouver, ISO, and other styles

32

Bhatti, Muhammad Wasim, and Ali Ahsan. "Effective Communication among Globally Distributed Software Development Teams." Journal of Global Information Management 25, no. 3 (July 2017): 40–62. http://dx.doi.org/10.4018/jgim.2017070103.

Full text

Abstract:

Global software development, an emerging software development methodology within a technology-enabled environment has recently received increased attention from scholars and practitioners. Despite the fact that the lack of effective communication is a major challenge of globally distributed teams, communication research related to the scale development is still very limited in existing literature. Considering the communication challenges and increasing need to measure the effectiveness of communication, this research is focused to develop a scale for “Effective Communication” for globally distributed software development teams. Systematic literature review is performed to identify the best practices of effective communication for the development of “Effective Communication” scale. A questionnaire survey consisting of 29 items is administered in globally distributed software development teams. Confirmatory factor analysis and statistical results depicted that the four-factor model (e.g. stakeholders' involvement, acculturation, usage of appropriate tools and technology, and information availability) is more parsimonious and an optimal model fit.

APA, Harvard, Vancouver, ISO, and other styles

33

Hassan, Ali, Soayba Younas, and Amiya Bhaumik. "Agile Methodology in an SaaS Deployment Project." International Journal of Information Technology Project Management 12, no. 2 (April 2021): 1–29. http://dx.doi.org/10.4018/ijitpm.2021040101.

Full text

Abstract:

Agile manifesto has proven its ability in managing and execution of projects in multiple industry sectors. Many researches have been conducted on the advantages and applicability of agile practices in software development and information technology industry. In this paper, empirical research has been conducted to identify the differences in agile management practices between software development and software as a service (SaaS) deployment projects. Case studies of a payment card industry (PCI) organization have been presented to identify key characteristics, tools, and methods of agile project management practices practically followed while implementing and managing of SaaS-based projects. Moreover, best suited agile management practices for pre- and post-deployment projects have also been discussed.

APA, Harvard, Vancouver, ISO, and other styles

34

Tubaishat, Abdallah. "IT Systems Development: An IS Curricula Course that Combines Best Practices of Project Management and Software Engineering." Issues in Informing Science and Information Technology 6 (2009): 257–68. http://dx.doi.org/10.28945/1057.

Full text

APA, Harvard, Vancouver, ISO, and other styles

35

Obrenovic, Zeljko, and Dusan Starcevic. "Adapting the unified software development process for user interface development." Computer Science and Information Systems 3, no. 1 (2006): 33–52. http://dx.doi.org/10.2298/csis0601033o.

Full text

Abstract:

In this paper we describe how existing software developing processes, such as Rational Unified Process, can be adapted in order to allow disciplined and more efficient development of user interfaces. The main objective of this paper is to demonstrate that standard modeling environments, based on the UML, can be adapted and efficiently used for user interfaces development. We have integrated the HCI knowledge into developing processes by semantically enriching the models created in each of the process activities of the process. By using UML, we can make easier use of HCI knowledge for ordinary software engineers who, usually, are not familiar with results of HCI researches, so these results can have broader and more practical effects. By providing a standard means for representing human computer interaction, we can seamlessly transfer UML models of multimodal interfaces between design and specialized analysis tools. Standardization provides a significant driving force for further progress because it codifies best practices enables and encourages reuse, and facilitates inter working between complementary tools. Proposed solutions can be valuable for software developers, who can improve quality of user interfaces and their communication with user interface designers, as well as for human computer interaction researchers, who can use standard methods to include their results into software developing processes.

APA, Harvard, Vancouver, ISO, and other styles

36

Et.al, Naveen N. Kulkarni. "Tailoring effective requirement's specification for ingenuity in Software Development Life Cycle." Turkish Journal of Computer and Mathematics Education (TURCOMAT) 12, no. 3 (April 11, 2021): 3338–44. http://dx.doi.org/10.17762/turcomat.v12i3.1590.

Full text

Abstract:

Software Requirements Engineering (SRE) process define software manuscripts with sustaining Software Requirement Specification (SRS) and its activities. SRE comprises many tasks requirement analysis, elicitation, documentation, conciliation and validation. Natural language is most popular and commonly used to form the SRS document. However, natural language has its own limitations wrt quality approach for SRS. The constraints include incomplete, incorrect, ambiguous, and inconsistency. In software engineering, most applications are object-oriented. So requirements are unlike problem domain need to be developed. So software documentation is completed in such a way that, all authorized users like clients, analysts, managers, and developers can understand it. These are the basis for success of any planned project. Most of the work is still dependent on intensive human (domain expert) work. consequences of the project success still depend on timeliness with tending errors. The fundamental quality intended for each activity is specified during the software development process. This paper concludes critically with best practices in writing SRS. This approach helps to mitigate SRS limitation up to some extent. An initial review highlights capable results for the proposed practices

APA, Harvard, Vancouver, ISO, and other styles

37

Domander, Richard, Alessandro A. Felder, and Michael Doube. "BoneJ2 - refactoring established research software." Wellcome Open Research 6 (February 22, 2021): 37. http://dx.doi.org/10.12688/wellcomeopenres.16619.1.

Full text

Abstract:

Research software is often developed with expedience as a core development objective because experimental results, but not the software, are specified and resourced as a project output. While such code can help find answers to specific research questions, it may lack longevity and flexibility to make it reusable. We reimplemented BoneJ, our software for skeletal biology image analysis, to address design limitations that put it at risk of becoming unusable. We improved the quality of BoneJ code by following contemporary best programming practices. These include separation of concerns, dependency management, thorough testing, continuous integration and deployment, source code management, code reviews, issue and task ticketing, and user and developer documentation. The resulting BoneJ2 represents a generational shift in development technology and integrates with the ImageJ2 plugin ecosystem.

APA, Harvard, Vancouver, ISO, and other styles

38

Domander, Richard, Alessandro A. Felder, and Michael Doube. "BoneJ2 - refactoring established research software." Wellcome Open Research 6 (April 28, 2021): 37. http://dx.doi.org/10.12688/wellcomeopenres.16619.2.

Full text

Abstract:

Research software is often developed with expedience as a core development objective because experimental results, but not the software, are specified and resourced as a project output. While such code can help find answers to specific research questions, it may lack longevity and flexibility to make it reusable. We reimplemented BoneJ, our software for skeletal biology image analysis, to address design limitations that put it at risk of becoming unusable. We improved the quality of BoneJ code by following contemporary best programming practices. These include separation of concerns, dependency management, thorough testing, continuous integration and deployment, source code management, code reviews, issue and task ticketing, and user and developer documentation. The resulting BoneJ2 represents a generational shift in development technology and integrates with the ImageJ2 plugin ecosystem.

APA, Harvard, Vancouver, ISO, and other styles

39

Griffin, Daniel, Silvia Gallagher, Vanessa Vigano, Dimitra Mousa, Sanne Van Vugt, Alex Lodder, and Jake Rowan Byrne. "Best Practices for Sustainable Inter-Institutional Hybrid Learning at CHARM European University." Education Sciences 12, no. 11 (November 10, 2022): 797. http://dx.doi.org/10.3390/educsci12110797.

Full text

Abstract:

CHARM European University offers an inter-institutional Master’s (MSc) in Global Challenges for Sustainability across five European university campuses using innovative, challenge-based, transdisciplinary, and student-centered pedagogies. However, delivering modules across multiple locations at the same time poses a major challenge. Multiple hybrid classrooms solve this challenge by offering spaces for students and staff to teach and learn locally and remotely. This study describes the first Participatory Action Research (PAR) cycle iteration of the design, implementation, testing, and delivery of hybrid classrooms within a European university alliance. Hybrid classroom collaboration was facilitated through videoconference software, and this research describes a collaborative space design for transdisciplinary teamwork within this environment. Perspectives from a technical expert on virtual learning environments, an educationalist who supports teaching staff, and a classroom-based teaching assistant are presented. Integrating educational principles and module learning outcomes, aligning physical build specifications, testing hardware and software, identifying pedagogical needs, facilitating professional development, and ensuring adequate time for testing is crucial for successful hybrid classroom delivery. This research contributes practical use cases and recommendations for educational and support staff delivering digital transformation through hybrid classrooms across inter-institutional co-operations.

APA, Harvard, Vancouver, ISO, and other styles

40

Miller, Andrew, Ronald Giachetti, and Douglas Van Bossuyt. "Challenges of Adopting DevOps for Combat Systems Development Environment." Defense Acquisition Research Journal 29, no. 99 (January 1, 2022): 22–48. http://dx.doi.org/10.22594/dau.21-870.29.01.

Full text

Abstract:

The Department of Defense (DoD) is often exhorted to adopt best practices from industry, and more recently, innovation in software development as exemplified by Silicon Valley. Yet, the DoD is vastly different from industry in multiple aspects, and adoption of such practices is not as straightforward as in industry. This article investigates the challenges of adopting Development and Operations (DevOps) in the U.S. Navy for combat systems. The authors conducted interviews of multiple subject matter experts in the Navy and DoD familiar with software development, DevOps, and the DoD’s acquisition processes. The observations collected from the interviews were organized and classified into either organizational, process, regulatory challenges, and technical challenges. The majority of the challenges cited were nontechnical challenges dealing with regulations, organization culture, and process. Knowledge of the challenges could help acquisition leaders in planning for, and adapting DevOps to, the Navy’s acquisition process to improve DoD’s software development and maintenance processes.

APA, Harvard, Vancouver, ISO, and other styles

41

Khan, Arif Ali, Shuib Basri, P. D. D. Dominic, and Fazal E. Amin. "Communication Risks and Best Practices in Global Software Development during Requirements Change Management: A Systematic Literature Review Protocol." Research Journal of Applied Sciences, Engineering and Technology 6, no. 19 (October 20, 2013): 3514–19. http://dx.doi.org/10.19026/rjaset.6.3554.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Núñez-Sánchez, Yeison, and Antonio González-Torres. "Third-party management in software development: proposal of a methodology." Enfoque UTE 11, no. 2 (April 1, 2020): 71–84. http://dx.doi.org/10.29019/enfoque.v11n2.621.

Full text

Abstract:

Outsourcing allows organizations to reduce costs, optimize the use of resources, provide added value in services and goods, and concentrate on achieving the strategic objectives of the business. However, many software projects have failed due to the lack of knowledge of the factors involved in its planning. Some of these elements are poor communication with the supplier, weak monitoring of the status of tasks, lack of active participation of users and stakeholders at all stages of the process, and software quality assurance. Consequently, this research aims to aid the management of the outsourcing process and proposes a methodology for its management during system development. The methodology comprises 7 phases, each one with its inputs, tasks, and outputs, which are used by the following stages. In summary, it synthesizes the best practices for the management of third parties.

APA, Harvard, Vancouver, ISO, and other styles

43

Vinayak, Kalluri, and Rambabu Kodali. "Reliability and validity of new product development practices in Indian manufacturing industries." Journal of Advances in Management Research 11, no. 1 (April 29, 2014): 82–101. http://dx.doi.org/10.1108/jamr-09-2012-0043.

Full text

Abstract:

Purpose – The purpose of this paper is to conduct an empirical investigation on the new product development (NPD) practices in Indian manufacturing industries. The NPD best practices constructs are identified from the literature and then an effort have been made to statistically establish the underlying principal components of NPD practices by checking their reliability and validity for the case of Indian manufacturing industry. Design/methodology/approach – In all, 96 NPD best practices constructs are identified from literature articles published between 1998 and 2009. Principal component analysis (PCA) is conducted to establish the seven components of NPD practices. Cronbach's α values are computed to measure internal consistency or reliability of the established components of NPD practices. Further, confirmatory factor analysis is conducted on the established measurement model to test a hypothesized factor structure through construct validity, convergent validity and divergent validity. Findings – The PCA of NPD best practices identified the seven underlying components (latent variables) namely “NPD strategy,” “NPD support system,” “product portfolio management,” “NPD team,” “NPD tools,” “product launch” and “concept generation.” In NPD strategy, Indian manufacturing companies are highly inclined toward cost reduction, cycle time reduction, competitive advantage and fast follower strategies. All NPD support system constructs are information technology dependent tools which require hardware, software and databases to support it. Indian manufacturing organizations are fundamentally concentrating on right balance of portfolio through improvements in the current products, cost reduction and additions to existing lines by using modular architectures and the reliable and valid NPD tools are FMEA, six sigma/quality management, DFMA/DF’X and QFD. Originality/value – To the best of the author's knowledge, this research represents the first attempt to investigate empirically the NPD practices in Indian manufacturing industry.

APA, Harvard, Vancouver, ISO, and other styles

44

Horton, Randy, Bob Moll, and Ke Li Yew. "The Best of Both Worlds: Using Qualitative and Quantitative Feedback to Improve the Design of Connected Medical Devices." Proceedings of the International Symposium on Human Factors and Ergonomics in Health Care 11, no. 1 (October 2022): 95–97. http://dx.doi.org/10.1177/2327857922111019.

Full text

Abstract:

The medical device industry has a long legacy of product development processes that are heavily influenced by the design of the device hardware. As devices have become connected, often to smartphones via connections such as Bluetooth, software is playing an increasing role in the overall system and in particular the user interface. As a result, iterative agile design practices that are prevalent in software are starting to influence the connected device development process. These modern agile practices put the user at the center of the design problem. But what is the best way in this new world to get feedback from users such that the overall product can be improved? In this paper, we share two techniques, one qualitative and one quantitative, that can answer this question. We’ll also explore the synergy of using both techniques together.

APA, Harvard, Vancouver, ISO, and other styles

45

Annarelli, Alessandro, Cinzia Battistella, and Fabio Nonino. "Web-application development projects by online communities." Industrial Management & Data Systems 117, no. 1 (February 6, 2017): 166–97. http://dx.doi.org/10.1108/imds-10-2015-0440.

Full text

Abstract:

Purpose The purpose of this paper is to propose an in-depth analysis of online communities of practice that support the innovative development of web applications. The analysis is aimed at understanding the preeminent characteristics of communities of practice that can favour the process of innovation (conceptualisation and realization of a web application) and if these characteristics differ in the diverse phases of a software development project (requirement specification, design, implementation and verification). Design/methodology/approach The authors adopted a multiple case study research design, selected 29 communities of practice related to the development of web applications and classified them recognizing the different practices that refer to the different phases of the innovation process of web-applications software development. Finally, the authors focussed on seven communities comparing five important dimensions for each one. Findings The results of the empirical analysis show that the best practices are different, considering the different phases of the project, and that these practices can be strategies directed at members to attract them and also, strategies directed at the community to permit collaboration. Originality/value The paper proposes an important and new insight into the management of virtual communities of practice (VCoP). The authors supposed that the ways to manage a VCoP could depend on project phases. In particular, the management practices of community should differ according to the different project phases, i.e. requirements specification, design, implementation and verification of the software. Literature in this sense presented only research focussed on the different effects of virtualness on teams depending on the length of team duration and on communication efforts.

APA, Harvard, Vancouver, ISO, and other styles

46

Kashfi, Pariya, Agneta Nilsson, and Robert Feldt. "Integrating User eXperience practices into software development processes: implications of the UX characteristics." PeerJ Computer Science 3 (October 16, 2017): e130. http://dx.doi.org/10.7717/peerj-cs.130.

Full text

Abstract:

User eXperience (UX) is a key factor in the success of software systems. Many software companies face challenges in their work with UX. Existing research does not analyze UX practices and challenges in relation to other software quality characteristics or, in particular, in relation to usability. A better understanding of these challenges can help researchers and practitioners better address them in the future. In this empirical study, we have interviewed 17 practitioners with different backgrounds and occupations from eight software development companies. Their responses are coded, and analyzed with thematic analysis. We report eight themes of challenges that practitioners face in their work with UX. While some of these challenges partly overlap with those reported in existing literature about usability or other software quality characteristics, the participants of our study either view many of the challenges as unique to UX, or more severe in the case of UX. Although at a superficial level challenges of UX and other quality characteristics overlap, we differentiate these challenges at a deeper level through the five main characteristics of UX:subjective,holistic,dynamic,context-dependentandworthwhile. In particular, we identified that these characteristics have at least 20 implications (i.e. additional difficulties) for day-to-day work of practitioners. We found that 11 of these implications have been previously reported in literature. However, to the best of our knowledge, the remaining nine implications are unique to our study. These implications can explain why practitioners perceive the challenges to be more severe than for other quality characteristics. Most importantly, they can explain the industry’s lopsided focus on the pragmatic aspect of UX. Our findings can be useful for researchers in identifying new and industry-relevant research areas and for practitioners to learn from empirically investigated challenges in UX work, and base their improvement efforts on such knowledge. Identifying and investigating the overlaps underlines the importance of these challenges, and can also help finding research areas not only for enhancing UX work but also software quality in general. It also makes it easier for practitioners to spot, better understand as well as find mitigation strategies for UX, through learning from past experiences and developments in the area of software quality.

APA, Harvard, Vancouver, ISO, and other styles

47

Ozoliņš, Pēteris. "Preparation and Facilitation of Retrospective Meeting in Scrum process." Information Technology and Management Science 21 (December 14, 2018): 60–63. http://dx.doi.org/10.7250/itms-2018-0009.

Full text

Abstract:

Agile methods have become very popular in software development. They emphasise importance of collaboration and communication in successful product development. Scrum is one of the most popular agile methods and it involves a number of artefacts and practices. The retrospective is one of the practices. It is an activity that serves a purpose as a team meeting to improve development processes. It is a time-boxed event, which should be planned and facilitated in order to obtain the best outcome. The paper aims at identifying appropriate practices for organising and running successful retrospectives. The practices are identified in the paper along with their attributes and usage suggestions.

APA, Harvard, Vancouver, ISO, and other styles

48

López Herrera, Gloria Yolanda, and Juan Carlos Jiménez Sanz. "Best practices for requirements identification, specification, and validation to guide software implementation and maintenance processes for applications in an electricity supply company." Sistemas y Telemática 13, no. 35 (December 3, 2015): 53–76. http://dx.doi.org/10.18046/syt.v13i35.2152.

Full text

Abstract:

The objective of this project is to identify and adapt the best practices for the identification, specification, and validation of requirements that guide the software implementation and maintenance processes in applications of an electric company. We performed this identification through the study and analysis of the actual state of the topic in Colombia, particularly within electric companies and supported by the theoretical examples of requirements engineering. Both the examples and the methodological models identified as best practices —such as RUP, agile development (focused on Scrum), CMMI, use cases and use cases 2.0, PMI —focused on the management of the scope and stakeholders—, and BABOK support the understanding of this topic. The result is a process that collects models to improve the requirements for new developments and for the handling of change requests and incidents/emergencies, obtaining positive evaluations by expert judgement in a pilot experiment.

APA, Harvard, Vancouver, ISO, and other styles

49

Turaga, Nitesh, Mallory A. Freeberg, Dannon Baker, John Chilton, Anton Nekrutenko, and James Taylor. "A guide and best practices for R/Bioconductor tool integration in Galaxy." F1000Research 5 (November 24, 2016): 2757. http://dx.doi.org/10.12688/f1000research.9821.1.

Full text

Abstract:

Galaxy provides a web-based platform for interactive, large-scale data analyses, which integrates bioinformatics tools written in a variety of languages. A substantial number of these tools are written in the R programming language, which enables powerful analysis and visualization of complex data. The Bioconductor Project provides access to these open source R tools and currently contains over 1200 R packages. While some R/Bioconductor tools are currently available in Galaxy, scientific research communities would benefit greatly if they were integrated on a larger scale. Tool development in Galaxy is an early entry point for Galaxy developers, biologists, and bioinformaticians, who want to make their work more accessible to a larger community of scientists. Here, we present a guide and best practices for R/Bioconductor tool integration into Galaxy. In addition, we introduce new functionalities to existing software that resolve dependency issues and semi-automate generation of tool integration components. With these improvements, novice and experienced developers can easily integrate R/Bioconductor tools into Galaxy to make their work more accessible to the scientific community.

APA, Harvard, Vancouver, ISO, and other styles

50

Devyanin, Petr Nikolaevich, Vladimir Iurevich Telezhnikov, and Alexey Vladimirovich Khoroshilov. "Building a methodology for secure system software development on the example of operating systems." Proceedings of the Institute for System Programming of the RAS 33, no. 5 (2021): 25–40. http://dx.doi.org/10.15514/ispras-2021-33(5)-2.

Full text

Abstract:

System software is a cornerstone of any software system, so building secure system software in accordance with requirements of certification authorities and state-of-the-art practices is an important scientific and technical problem. One of possible approaches to cope with the problem is to build a methodology for secure system software development including advanced scientific technologies and industry best practices. The paper presents current results achieved in building such methodology in the following directions. The first one is regulatory framework improvement including development of GOST R specifications defining requirements to formal models of access control policies and their formal verification. The second direction is design and verification of formal models of corresponding security functional requirements. The third direction is application of new and well established technologies of static and run-time analysis of systems software. The considered technologies include static analysis, fuzzing, functional and unit testing as well as testing the system software against formal models of its functional security requirements. The forth direction is development of methods for acquisition of results of all kinds of the analysis and for its analytical processing. All the directions are illustrated by practical examples of application of the methodology to development of Astra Linux operating system distribution that is certified according to the highest evaluation assurance levels.

APA, Harvard, Vancouver, ISO, and other styles

Journal articles on the topic 'Software Development Best Practices'

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