The Influence of the Application of Agile Practices in Software Quality Based on ISO/IEC 25010 Standard

2022 ◽  
pp. 1416-1443
Author(s):  
Gloria Arcos-Medina ◽  
David Mauricio

Agile practices are activities or procedures that are applied during the software development process in order to improve its quality and productivity. The objective of this study is to determine the influence of agile practices on software quality. For this purpose, a model composed of 4 groups of agile practices and 8 quality characteristics according to the ISO/IEC 25010 standard has here been proposed. The results of 146 questionnaires addressed to people involved in the software development process show that the application of agile engineering and project management practices have a significant positive influence on the quality attribute functionality. On the other hand, project management practices have a low impact on the quality characteristics of compatibility, portability, security, and usability.

Author(s):  
Gloria Arcos-Medina ◽  
David Mauricio

Agile practices are activities or procedures that are applied during the software development process in order to improve its quality and productivity. The objective of this study is to determine the influence of agile practices on software quality. For this purpose, a model composed of 4 groups of agile practices and 8 quality characteristics according to the ISO/IEC 25010 standard has here been proposed. The results of 146 questionnaires addressed to people involved in the software development process show that the application of agile engineering and project management practices have a significant positive influence on the quality attribute functionality. On the other hand, project management practices have a low impact on the quality characteristics of compatibility, portability, security, and usability.


2014 ◽  
pp. 1608-1638
Author(s):  
Iwona Dubielewicz ◽  
Bogumila Hnatkowska ◽  
Zbigniew Huzar ◽  
Lech Tuzinkiewicz

Software maintenance is sometimes considered as a special kind of activity that is separated from a software development process. Meanwhile, the opposite is true; maintenance should be taken into account from the beginning of the software development process. Because a model-based software development is the prevailing software development paradigm, the maintainability should be considered within models that arise in software development process. We claim that the quality of the models arising in the software development process has a positive influence on their maintainability: the higher quality of the models, the more effective maintainability activity. The background for our consideration is MDA approach, and the scope of the consideration is limited to perfective maintenance only. The set of so called 6C quality characteristics is assumed to define a quality of MDA-models. Our selection of 6C quality characteristics is justified by the fact that they are related to activities performed on models within the maintenance. To assess MDA-models in the context of the maintainability, we define checklists for the 6C characteristics. These checklists are used for derivation of some measures which are useful in checking to what scope a given characteristics is satisfied. The main advantage of the approach is its independence of the knowledge of future changes of user requirements that trigger perfective maintenance. In the chapter, we demonstrate a simple example of how to assess the quality of PIM-models that are the realization of the CIM-model. Additionally, we discuss how to select, for further development, the best PIM-model from the set of possible solution.


Author(s):  
Mirna Muñoz

Software has become the core of organizations in different domains because the capacity of their products, systems, and services have an increasing dependence on software. This fact highlights the research challenges to be covered by computer science, especially in the software engineering (SE) area. On the one way, SE is in charge of covering all the aspects related to the software development process from the early stages of software development until its maintenance and therefore is closely related to the software quality. On the other hand, SE is in charge of providing engineers able to provide technological-base solutions to solve industrial problems. This chapter provides a research work path focused on helping software development organizations to change to a continuous software improvement culture impacting both their software development process highlighting the human factor training needs. Results show that the implementation of best practices could be easily implemented if adequate support is provided.


Author(s):  
Rory V. O'Connor ◽  
Shuib Basri

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


Software architecture involves the structure and organization by which modern system components and subsystems interact to form system and the properties of systems that can best be designed and analyzed at the system level. This paper provides a review of the principles of architecture first approach in software project management and its effect on cost of software development process. This paper reviews the literature and practitioners’ experiences relating to architecture first approach, and advantages of architecture first approach in cost of software development process. This paper also reviews related works about factors that may reduce the cost of software development process. Weobserved parameters related to software architecture that may affect the cost of software development process.The parameters are software (product) delivery time, defect prevention, risk mitigation, and change management. After this, the parameters show that they have their own effect on the software development process. Finally, the paper concludes by describing how those parameters affect the cost of software development process.


2009 ◽  
pp. 2665-2679
Author(s):  
Sameer Verma

This chapter introduces the open source software development process from a software quality perspective. It uses the attributes of software quality in a formal model and attempts to map them onto the principles of the open source process. Many stages of the open source process appear to have an ad-hoc approach. Although open source is not considered to be a formal methodology for software development, it has resulted in the development of very high quality software, both in the consumer and in the enterprise space. In this chapter, we hope to understand the open source process itself, and apply it to other methodologies in order to achieve better software quality. Additionally, this chapter will help in understanding the “Wild West” nature of open source and what it may hold for us in the future.


Author(s):  
Sameer Verma

This chapter introduces the open source software development process from a software quality perspective. It uses the attributes of software quality in a formal model and attempts to map them onto the principles of the open source process. Many stages of the open source process appear to have an ad-hoc approach. Although open source is not considered to be a formal methodology for software development, it has resulted in the development of very high quality software, both in the consumer and in the enterprise space. In this chapter, we hope to understand the open source process itself, and apply it to other methodologies in order to achieve better software quality. Additionally, this chapter will help in understanding the “Wild West” nature of open source and what it may hold for us in the future.


2020 ◽  
Vol 44 (1) ◽  
pp. 1-31
Author(s):  
Gloria Arcos-Medina ◽  
David Mauricio

Agile practices are activities or actions that are utilized during software development to improve the quality and productivity of the resulting software. Those practices are influenced by a set of factors that affect the realization of their objectives. The purpose of this study is to determine the influence of organizational factors and the personnel working on the software development project to the agile practices. To this end, a model has been proposed that is composed of six critical success factors derived from the theories of administrative and human behavior and four groups of agile practices, and resulted in identifying 13 factor-practice relationships. The results from 146 questionnaires addressed to individuals involved in the software development process show that the factors of Confidence, Perception of Self-efficacy, Integrity and Availability of the Information and Experiences Learned, and Media Used all have a noteworthy positive influence on teamwork agile practices.


Sign in / Sign up

Export Citation Format

Share Document