Software Development Processes and Process Improvement

2017 ◽  
pp. 23-49
Author(s):  
Neil Walkinshaw
Keyword(s):  
Software Development ◽  
Process Improvement ◽  
Development Processes

scholarly journals CMMI and Ideal in Software Process Improvement

2020 ◽  
Vol 17 ◽  
Keyword(s):  
Customer Satisfaction ◽  
Best Practices ◽  
Software Development ◽  
Process Improvement ◽  
Software Process ◽  
Software Process Improvement ◽  
Critical Factors ◽  
Development Processes ◽  
The Ideal

Different models and standards have been developed with the purpose of improving software development processes and obtaining quality products and achieving customer satisfaction. Despite the efforts that organizations make, they do not always achieve these results. In this article we present the results of the implementation of best practices established by the CMMI model using the IDEAL and SCAMPI B methodology. The results show that applying best practices helps organizations to improve their processes, minimize the number of defects and increase customer satisfaction. Likewise, the critical factors that were considered and aspects to be considered in the deployment of processes are presented.

A New Framework for Improving Software Development Process on Small Computer Systems

1997 ◽  
Vol 07 (02) ◽  
pp. 171-184
Author(s):  
Makoto Sakai ◽  
Ken-Ichi Matsumoto ◽  
Koji Torii
Keyword(s):  
Software Development ◽  
Process Improvement ◽  
Development Process ◽  
Computer Systems ◽  
Project Manager ◽  
Small Computer ◽  
Software Development Process ◽  
Development Processes ◽  
Development Risks ◽  
New Framework

While small computer systems have provided us with a wide array of development and operational environments, implementation methods, and domains of the software to be developed, it has also made the software development more risky. This paper proposes a new framework for improving the software development process on small computer systems to reduce software development risks. The key idea of the proposed framework is that the solutions to the software development problems can be extracted by the project manager, with relatively low overload, from the development processes that were actually executed in order to reduce the development risks, and then be formalized and stored in a database. The formalized solutions can be used not only for process improvement, but also for devising new solutions if new problems should occur in the future. We believe that the proposed framework is capable of making up for the difficulties in implementing CMM on small computer systems, and it encourages us to apply CMM to such risky software development.

scholarly journals An Objective Compliance Analysis of Project Management Process in Main Agile Methodologies with the ISO/IEC 29110 Entry Profile

2017 ◽  
Vol 10 (1) ◽  
pp. 75-106 ◽  
Author(s):  
Sergio Galvan-Cruz ◽  
Manuel Mora ◽  
Rory V. O'Connor ◽  
Francisco Acosta ◽  
Francisco Álvarez
Keyword(s):  
Software Development ◽  
Process Improvement ◽  
Software Process ◽  
Software Process Improvement ◽  
Agile Methodologies ◽  
Development Processes ◽  
Software Development Methodologies ◽  
Agile Software ◽  
Initial Results

Software Process Improvement efforts (SPI) are pursued by organizations for improving the overall quality of their software development processes. However, very small entities (VSEs) avoid them by the lack of required financial and other organizational resources. In contrast, VSEs use agile software development methodologies (ASDMs), but these ASDMs do not foster adherence to best scholastic practices promoted by SPI. Furthermore, while a new ISO/IEC standard (29110) has been recently released for VSEs, it was not designed taking account the ASDM approaches. Thus, we investigate the extent of adherence of main ASDMs (two industrial and one academic type) with this new standard. Initial results provide evidence on the strong need to enhance the two industrial ASDMs (XP and SCRUM). In contrast, the academic ASDM (UPEDU) fits the standard very well but it is scarcely used by VSEs. Hence, it is concluded that there is a knowledge gap between the praxis with ASDMs and the recommended scholastic software processes like the ISO/IEC 29110 standard for VSEs.

Agile SPI

2011 ◽  
pp. 177-192 ◽  
Author(s):  
Julio A. Hurtado ◽  
Francisco J. Pino ◽  
Juan C. Vidal ◽  
César Pardo ◽  
Luís Eduardo Fernández
Keyword(s):  
Software Development ◽  
Process Improvement ◽  
Software Industry ◽  
Software Process ◽  
Software Process Improvement ◽  
Medium Size ◽  
Development Processes ◽  
Main Components

This chapter presents Agile SPI, a framework in which the main goal is to motivate small and medium size enterprises (SMEs) towards improving and certifying their software development processes. This framework was born in the SIMEP-SW project where a software process improvement model for supporting process improvement in the Colombian software industry context was built. We present Agile SPI, its origin, development, principles, architecture, main components, and the initial experiences.

Agile SPI

2009 ◽  
pp. 3308-3324
Author(s):  
Julio A. Hurtado ◽  
Francisco J. Pino ◽  
Juan C. Vidal ◽  
César Pardo ◽  
Luís Eduardo Fernández
Keyword(s):  
Software Development ◽  
Process Improvement ◽  
Software Industry ◽  
Software Process ◽  
Software Process Improvement ◽  
Medium Size ◽  
Development Processes ◽  
Main Components

This chapter presents Agile SPI, a framework in which the main goal is to motivate small and medium size enterprises (SMEs) towards improving and certifying their software development processes. This framework was born in the SIMEPSW project where a software process improvement model for supporting process improvement in the Colombian software industry context was built. We present Agile SPI, its origin, development, principles, architecture, main components, and the initial experiences.

A Systematic Review and Catalog of Security Metric during the Secure Software Development Life Cycle

2020 ◽  
Vol 13 ◽  
Author(s):  
Sampada G.C ◽  
Tende Ivo Sake ◽  
Amrita
Keyword(s):  
Systematic Review ◽  
Life Cycle ◽  
Software Development ◽  
Software Security ◽  
Security Assessment ◽  
Security Metrics ◽  
Development Life Cycle ◽  
Development Processes ◽  
Secure Software Development ◽  
Software Development Life Cycle

Background: With the advancement in the field of software development, software poses threats and risks to customers’ data and privacy. Most of these threats are persistent because security is mostly considered as a feature or a non-functional requirement, not taken into account during the software development life cycle (SDLC). Introduction: In order to evaluate the security performance of a software system, it is necessary to integrate the security metrics during the SDLC. The appropriate security metrics adopted for each phase of SDLC aids in defining the security goals and objectives of the software as well as quantify the security in the software. Methods: This paper presents systematic review and catalog of security metrics that can be adopted during the distinguishable phases of SDLC, security metrics for vulnerability and risk assessment reported in the literature for secure development of software. The practices of these metrics enable software security experts to improve the security characteristics of the software being developed. The critical analysis of security metrics of each phase and their comparison are also discussed. Results: Security metrics obtained during the development processes help to improve the confidentiality, integrity, and availability of software. Hence, it is imperative to consider security during the development of the software, which can be done with the use of software security metrics. Conclusion: This paper reviews the various security metrics that are meditated in the copious phases during the progression of the SDLC in order to provide researchers and practitioners with substantial knowledge for adaptation and further security assessment.

scholarly journals Assumptions Underlying Agile Software-Development Processes

2005 ◽  
Vol 16 (4) ◽  
pp. 62-87 ◽  
Author(s):  
Daniel Turk ◽  
France. Robert ◽  
Bernhard Rumpe
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Development Processes ◽  
Agile Software
Sign in / Sign up

Export Citation Format

Share Document