The Impact of Software Development Process on Software Quality: A Review

2016 ◽  
Author(s):  
Brijendra Singh ◽  
Shikha Gautam
Keyword(s):  
Software Development ◽  
Software Quality ◽  
Development Process ◽  
Software Development Process ◽  
The Impact

scholarly journals Are UX Evaluation Methods Providing the Same Big Picture?

Sensors ◽  
2021 ◽  
Vol 21 (10) ◽  
pp. 3480
Author(s):  
Walter Takashi Nakamura ◽  
Iftekhar Ahmed ◽  
David Redmiles ◽  
Edson Oliveira ◽  
David Fernandes ◽  
...  
Keyword(s):  
Software Development ◽  
Decision Process ◽  
Development Process ◽  
Evaluation Methods ◽  
Sentence Completion ◽  
Software Development Process ◽  
Software Application ◽  
Software Products ◽  
Big Picture ◽  
The Impact

The success of a software application is related to users’ willingness to keep using it. In this sense, evaluating User eXperience (UX) became an important part of the software development process. Researchers have been carrying out studies by employing various methods to evaluate the UX of software products. Some studies reported varied and even contradictory results when applying different UX evaluation methods, making it difficult for practitioners to identify which results to rely upon. However, these works did not evaluate the developers’ perspectives and their impacts on the decision process. Moreover, such studies focused on one-shot evaluations, which cannot assess whether the methods provide the same big picture of the experience (i.e., deteriorating, improving, or stable). This paper presents a longitudinal study in which 68 students evaluated the UX of an online judge system by employing AttrakDiff, UEQ, and Sentence Completion methods at three moments along a semester. This study reveals contrasting results between the methods, which affected developers’ decisions and interpretations. With this work, we intend to draw the HCI community’s attention to the contrast between different UX evaluation methods and the impact of their outcomes in the software development process.

Boosting the Competitiveness of Organizations With the Use of Software Engineering

2021 ◽  
pp. 198-216
Author(s):  
Mirna Muñoz
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Software Quality ◽  
Development Process ◽  
Research Work ◽  
Software Development Process ◽  
The Core ◽  
Development Organizations ◽  
Technological Base ◽  
The One

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.

The Impact of Conflict Judgments between Developers and Testers in Software Development

2013 ◽  
Vol 24 (4) ◽  
pp. 26-50 ◽  
Author(s):  
Xihui Zhang ◽  
Jasbir S. Dhaliwal ◽  
Mark L. Gillenson ◽  
Thomas F. Stafford
Keyword(s):  
Job Satisfaction ◽  
Software Development ◽  
Software Quality ◽  
Theory And Practice ◽  
Primary Role ◽  
Software Development Process ◽  
Research Model ◽  
Quality Testing ◽  
The Impact

The primary role of testers is to verify and validate the software produced by developers to ensure its quality. Testing is designed to catch problems in the software and report them for correction, so it is a conflict-laden, confrontational, and judgmental process. This “audit” role of testing is inherently adversarial, ensuring the development of components of interpersonal conflict judgments between developers and testers. Prior research indicates that such conflict is likely to be negatively associated with software quality and job satisfaction, producing negative judgments about the artifact production process and about the job itself. This study addresses the question: How do judgments of conflict between developers and testers impact the software development process? The authors develop and empirically test a research model which proposes that the conflict judgment targets of both the tasks and the persons who perform them will have direct impact on both software quality and job satisfaction judgments. Results of testing this model indicate that interpersonal judgments arising from conflict, as well as judgments made by testers and developers about the conflict targets of tasks and persons negatively influence subsequent software quality and job satisfaction judgments. Implications for theory and practice are discussed.

Towards Measuring the Change Impact in ATL Model Transformations

2016 ◽  
Vol 26 (02) ◽  
pp. 153-181 ◽  
Author(s):  
Andreza Vieira ◽  
Franklin Ramalho
Keyword(s):  
Software Development ◽  
Static Analysis ◽  
Development Time ◽  
Development Process ◽  
Model Transformations ◽  
Software Development Process ◽  
Model Driven ◽  
Change Impact ◽  
The Impact

The Model-Driven Development (MDD) approach shifts the focus on code to models in the software development process. In MDD, model transformations are elements that play an important role. MDD-based projects evolve along their lifecycle in a way that changes in their transformations are frequent. Before applying changes it is important to measure their impacts within the transformation. However, currently no technique helps practitioners in this direction. We propose an approach to measure the change impact in ATL model transformations. Based on static analysis, it detects the elements impacted by a change and calculates the change impact value through three metrics we defined. By using our approach, practitioners can (i) save effort and development time since the elements impacted with the change are automatically detected and (ii) better schedule and prioritize changes according to the impact value. To empirically evaluate our approach we conducted a case study.

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
Keyword(s):  
Project Management ◽  
Software Development ◽  
Software Quality ◽  
Development Process ◽  
Management Practices ◽  
Positive Influence ◽  
Quality Characteristics ◽  
Software Development Process ◽  
Agile Practices ◽  
Significant Positive Influence

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.

scholarly journals The Effect of Team Dynamics on Software Development Process Improvement

2012 ◽  
Vol 3 (3) ◽  
pp. 13-26 ◽  
Author(s):  
Rory O’Connor ◽  
Shuib Basri
Keyword(s):  
Software Development ◽  
Process Improvement ◽  
Development Process ◽  
Software Process ◽  
Software Process Improvement ◽  
Working Environment ◽  
Team Dynamics ◽  
Software Development Process ◽  
Software Development Teams ◽  
The Impact

This article identifies the effect of team dynamics in the context of software development teams and its impact on software process improvement (SPI) activities in very small companies, in order to understand the relationship between these two variables. Most software development work is done by teams of software engineers working together in a collaborative manner to execute a software development process. Although there is much literature examining software process and how to improve it, less attention has been paid to the issues of team-working and specifically the impact of team dynamics on the software development process. Team dynamics is the term used to define how people work and interact together in teams. Teamwork is more effective with the existence of positive team dynamic, as it encourages a better working environment with satisfied, fulfilled employees who will in turn be more productive. This paper presents the results of a research study of team dynamics in very small software development companies and its impact on the software development process and software process improvement activities.

Software Quality and the Open Source Process

2009 ◽  
pp. 2665-2679
Author(s):  
Sameer Verma
Keyword(s):  
Software Development ◽  
Open Source ◽  
Software Quality ◽  
Development Process ◽  
Ad Hoc ◽  
Formal Model ◽  
Source Process ◽  
Software Development Process ◽  
High Quality ◽  
Very High

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.

Software Quality and Open Source Process

2011 ◽  
pp. 291-310
Author(s):  
Sameer Verma
Keyword(s):  
Software Development ◽  
Open Source ◽  
Software Quality ◽  
Development Process ◽  
Ad Hoc ◽  
Formal Model ◽  
Source Process ◽  
Software Development Process ◽  
High Quality ◽  
Very High

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.

Sign in / Sign up

Export Citation Format

Share Document