scholarly journals Proposed Metrics for Process Capability Analysis in Improving Software Quality: An Empirical Study

2016 ◽  
Vol 1 (3) ◽  
pp. 152
Author(s):  
K Sridhar Patnaik ◽  
Pooja Jha
Keyword(s):  
Empirical Study ◽  
Software Development ◽  
Software Quality ◽  
Research Work ◽  
Software Project ◽  
High Quality ◽  
Cost Constraints ◽  
Capability Analysis ◽  
Increasing Demand ◽  
The Impact

A software project faces its top expense on defect removal; thereby delaying the schedules. There has been increasing demand for high quality software. Here, high quality software means, delivering defect free software and meeting the predictable results within time and cost constraints. Software defect prediction strives to improve software quality and testing efficiency. The research work presented here is an empirical study and analyzes importance of different metrics used in the organization. The paper examines the impact of LSL and USL, known as organization baselines, on various projects and proposes four metrics for capability analysis metrics. These can prove beneficial for categorizing the process of software development. These metrics aim to improve the ongoing software development process and are helpful in determining the quality of these processes in terms of their specification limits. Also, the paper attempts to justify the probability of the values related to the data provided by normal distribution or Gaussian distribution.

scholarly journals AGILE SOFTWARE DEVELOPMENT

2021 ◽  
Vol 5 (12) ◽  
Author(s):  
Gopalkrishna Waja ◽  
Jill Shah ◽  
Pankti Nanavati
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Extreme Programming ◽  
Software Project ◽  
Research Papers ◽  
Agile Methodology ◽  
Development Methodology ◽  
Software Development Methodology ◽  
Agile Software ◽  
The Impact

Agile Software Development plays a quintessential part in modern day software development. The term Agile refers to frequent reassessment and adaptation of plans and techniques and dividing tasks into shorter tasks for efficiency. Agile Software Development differs considerably from Traditional Software Development Methodology. Agile methodology aims to deliver features of a software project in small steps within a short duration of time (i.e., iterations). Hence, it becomes necessary to use agile software development methodology in todays’ fast-paced revolutionizing software industry. This paper discusses the important subtopics of Agile Software Development which gathered by reviewing/surveying of research papers. First, is the Agile Planning Life Cycle which consists of various stages such as pre-planning, planning, release planning and product backlog management. In the next section, principles such as Scrum, Extreme Programming, Kanban and Lean are discussed. The last section comprises the impact of Agile principles on software quality.

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.

Evaluation of Project Architecture in Software Development Mixing Waterfall and Agile by Using Process Simulation

2017 ◽  
Vol 02 (02) ◽  
pp. 1750007
Author(s):  
Taiga Mitsuyuki ◽  
Kazuo Hiekata ◽  
Takuya Goto ◽  
Bryan Moser
Keyword(s):  
Software Development ◽  
Process Simulation ◽  
System Development ◽  
Development Project ◽  
Development Projects ◽  
Software Project ◽  
Conditional Response ◽  
Agile Process ◽  
Requirement Changes ◽  
The Impact

For software development, especially massive software systems, a waterfall process is used traditionally. A waterfall process can be highly effective on the condition that a master plan is fixed and the possibility of changes and uncertain rework is low. However, in software development projects, many kinds of reworks occur corresponding to uncertain requirement changes and program bugs. In addition, with the advent of cloud-based software platforms and continuous development operations, it is possible to develop a software system while operating the system. To respond to this situation, software development projects often adopt an agile process. Agility may allow conditional response to uncertain rework, yet at the same time it may be difficult to control the achievement of known project targets. Recently, many cases of adopting mixed processes including waterfall and agile have been reported in the massive software development projects. In this paper, we argue that the mixed process architecture should be designed, considering the scale of the targeted software project, the culture of organization, the probability of uncertain requirement changes, and so on. This paper proposes a methodology of evaluating the impact of waterfall, agile, and mixed project architectures by using process simulation. A project architectural approach is evaluated with a simulator which includes a software reliability growth model and uncertain rework driven by requirement change and error propagation. The proposed methodology was applied to a development project for a simple shopping website. The results showed that the proposed methodology allows exploration of partial agile adoption depending on the nature of the system development project, including its scale and chances of change. For example, in this paper, if the scale of the project is small, the positive effect of increasing agility by adopting agile processes is low. On the other hand, if the scale of the project is large, the effect of increasing agility by adopting agile process can increase. Furthermore, it became clear that it is important to not apply an agile process blindly, but instead to design a mixed project architecture considering the number of errors and development schedule targets across the project scope.

Effect of knowledge management on software product experience with mediating effect of perceived software process improvement: An empirical study for Indian software industry

2019 ◽  
Vol 46 (2) ◽  
pp. 258-272
Author(s):  
Mitali Chugh ◽  
Nitin Chanderwal ◽  
Rajesh Upadhyay ◽  
Devendra Kumar Punia
Keyword(s):  
Knowledge Management ◽  
Empirical Study ◽  
Software Development ◽  
Process Improvement ◽  
Software Process ◽  
Empirical Studies ◽  
Software Process Improvement ◽  
Mediating Effect ◽  
Software Product ◽  
The Impact

The software development industry is characterised by swift innovation and competition. To survive, software engineering (SE) organisations need to develop high-quality software products in a timely fashion and at low cost. Knowledge-based approaches to software development are extremely supportive to acquiring new knowledge and leveraging existing knowledge from software projects; this enables constant improvement of software development practices. In this empirical study of Indian SE organisations, we study the impact of managing knowledge for perceived software process improvement (PSPI) and its effect on software product quality. Information technology (IT) in knowledge management (KM) is an important facilitator for any SE organisation desiring to exploit evolving technologies for management of their knowledge assets and for carrying out various KM processes of knowledge capture, storage, retrieval and sharing. Surveys collected from Indian SE organisations were analysed to propose a model using a structured equation modelling (SEM) technique. Our findings reveal that the relation between KM and quality of software product is positively mediated by PSPI. These findings reinforce an arena that is of growing importance to researchers and practitioners and which has seen only a limited number of empirical studies to date in the context of Indian SE organisations.

Usability evaluation of component based software system using software metrics

2020 ◽  
Vol 14 (3) ◽  
pp. 281-289
Author(s):  
Jyoti Agarwal ◽  
Sanjay Kumar Dubey ◽  
Rajdev Tiwari
Keyword(s):  
Software Development ◽  
Software Metrics ◽  
Research Work ◽  
Fuzzy Model ◽  
Software Project ◽  
Software System ◽  
Quality Factors ◽  
Quality Product ◽  
Software Product ◽  
Component Based Software Engineering

Component Based Software Engineering (CBSE) provides a way to create a new Component Based Software System (CBSS) by utilizing the existing components. The primary reason for that is to minimize the software development time, cost and effort. CBSS also increases the component reusability. Due to these advantages, software industries are working on CBSS and continuously trying to provide quality product. Usability is one of the major quality factors for CBSS. It should be measured before delivering the software product to the customer, so that if there are any usability flaws, it can be removed by software development team. In this paper, work has been done to evaluate the usability of CBSS based on major usability sub-factors (learnability, operability, understandability and configurability). For this purpose, firstly software metrics are identified for each usability sub-factor and the value of each sub-factor is evaluated for a component based software project. Secondly, overall usability of the software project is evaluated by using the calculated value of each usability sub-factor. Usability for the same project was also evaluated using Fuzzy approach in MATLAB to validate the experimental work of this research paper. It was identified that the value of usability obtained from software metrics and fuzzy model was very similar. This research work will be useful for the software developer to evaluate the usability of any CBSS and will also help them to compare different version of any CBSS in term of their usability.

A Review of Software Quality Methodologies

2012 ◽  
pp. 129-150 ◽  
Author(s):  
Saqib Saeed ◽  
Farrukh Masood Khawaja ◽  
Zaigham Mahmood
Keyword(s):  
Software Development ◽  
Software Quality ◽  
Software Systems ◽  
High Quality ◽  
Software Applications ◽  
Pervasive Systems ◽  
Development Lifecycle ◽  
Development Cycle ◽  
Software Development Lifecycle ◽  
Reliable Software

Pervasive systems and increased reliance on embedded systems require that the underlying software is properly tested and has in-built high quality. The approaches often adopted to realize software systems have inherent weaknesses that have resulted in less robust software applications. The requirement of reliable software suggests that quality needs to be instilled at all stages of a software development paradigms, especially at the testing stages of the development cycle ensuring that quality attributes and parameters are taken into account when designing and developing software. In this respect, numerous tools, techniques, and methodologies have also been proposed. In this chapter, the authors present and review different methodologies employed to improve the software quality during the software development lifecycle.

Sign in / Sign up

Export Citation Format

Share Document