scholarly journals Estimation of software quality parameters for hybrid agile process model

2021 ◽  
Vol 3 (3) ◽  
Author(s):  
Lalband Neelu ◽  
D. Kavitha
Keyword(s):  
Software Quality ◽  
Process Model ◽  
Quality Attributes ◽  
Parameter Analysis ◽  
Agile Development ◽  
Software Project ◽  
Quality Attribute ◽  
Functional Features ◽  
Agile Process ◽  
Agile Model

AbstractThis study aims to motivate a new hybrid agile methodology is a combination of agile models from Scrum, Extreme Programming, and Lean Software Development. The main aim of the hybrid agile model is the timely delivery of projects to clients with high quality at a reduced rate. But the main difficulty in hybrid agile model to effectively reflect the software quality attributes. Basically, the failure of a software project is mainly not because of inefficiency of functional features but due to inefficiency of quality attributes, like performance, reliability and effective usability. The work presents the introduction of Hybrid Agile Quality Parameter Analysis (HAQPE) that is a quality attribute driven agile development method. The outcome of developed quality attribute HAQPE was evaluated through hybrid agile process assessment by applying it to a commercial project of software industry. The results demonstrated that the developed quality attribute model is more efficient than the legacy agile development process.

Assessment of Software Quality

2010 ◽  
pp. 200-219 ◽  
Author(s):  
Praveen Ranjan Srivastava ◽  
Ajit Pratap Singh ◽  
Vageesh K. V.
Keyword(s):  
Quality Assurance ◽  
Software Engineering ◽  
Software Quality ◽  
Quality Attributes ◽  
Decision Makers ◽  
Software Quality Assurance ◽  
Quality Attribute ◽  
Software Products ◽  
Multiple Contexts ◽  
Software Product

Software Quality Assurance consists of monitoring the software engineering processes and ensuring the highest quality. But, the software quality attributes that we deal with are not explicit in the outset and cannot be easily measured. The same attribute has multiple significance and importance in multiple contexts. The user, the developer and the manager of a software product may have different stands regarding the significance of a quality attribute. A software quality engineer, while measuring the total software quality should provide appropriate weight to each of the decision makers. This chapter proposes a fuzzy multi-criteria approach to measure the total software quality and to identify the best alternative from a set of software products.

Agile RUP

2011 ◽  
pp. 231-246
Author(s):  
Gary K. Evans
Keyword(s):  
Development Process ◽  
The Body ◽  
Agile Development ◽  
Software Project ◽  
Software Projects ◽  
Distinctive Features ◽  
Major Stakeholder ◽  
Small Set ◽  
Agile Process ◽  
Iterative Software

The Rational Unified Processâ (RUP) is the de facto iterative software development process in use today. But it is huge (over 3,200 files), prescriptive, and generic rather than concise, agile, and specific. Organizations moving to RUP are often confused about how to apply it to their culture, unsure how much of it to adopt, and wary of how they can adapt it to their specific software projects. This chapter starts with a brief summary of the traditional waterfall development process, then offers an overview of RUP, its philosophy and distinctive features. Then the general philosophy of agile development is discussed. The body of the chapter defines a small set of activities that have been successfully applied in commercial “Agile” RUP projects by the author. The chapter then discusses how some of the major stakeholder groups on a software project are affected by moving to an agile process.

A QUALITY-DRIVEN DECISION-SUPPORT METHOD FOR IDENTIFYING SOFTWARE ARCHITECTURE CANDIDATES

2003 ◽  
Vol 13 (05) ◽  
pp. 547-573 ◽  
Author(s):  
MIKAEL SVAHNBERG ◽  
CLAES WOHLIN ◽  
LARS LUNDBERG ◽  
MICHAEL MATTSSON
Keyword(s):  
Decision Support ◽  
Software Architecture ◽  
Software Quality ◽  
Quality Attributes ◽  
Software System ◽  
Quality Attribute ◽  
Quality Requirements ◽  
Decision Method ◽  
Decision Support Method

To sustain the qualities of a software system during evolution, and to adapt the quality attributes as the requirements evolve, it is necessary to have a clear software architecture that is understood by all developers and to which all changes to the system adheres. This software architecture can be created beforehand, but must also be updated as the domain of the software, and hence the requirements on the software system evolve. Creating a software architecture for a system or part of a system so that the architecture fulfils the desired quality requirements is often hard. In this paper we propose a decision-support method to aid in the understanding of different architecture candidates for a software system. We propose a method that is adaptable with respect to both the set of potential architecture candidates and quality attributes relevant for the system's domain to help in this task. The method creates a support framework, using a multi-criteria decision method, supporting comparison of different software architecture candidates for a specific software quality attribute and vice versa, and then uses this support framework to reach a consensus on the benefits and liabilities of the different software architecture candidates and to increase the confidence in the resulting architecture decision.

Impact of Clone Refactoring on External Quality Attributes of Open Source Softwares

2018 ◽  
pp. 86-94
Author(s):  
Himanshi Vashisht ◽  
Sanjay Bharadwaj ◽  
Sushma Sharma
Keyword(s):  
Open Source ◽  
Internal Structure ◽  
Software Quality ◽  
Source Code ◽  
Quality Attributes ◽  
Software Component ◽  
External Quality ◽  
Code Refactoring ◽  
Observable Behaviour

Code refactoring is a “Process of restructuring an existing source code.”. It also helps in improving the internal structure of the code without really affecting its external behaviour”. It changes a source code in such a way that it does not alter the external behaviour yet still it improves its internal structure. It is a way to clean up code that minimizes the chances of introducing bugs. Refactoring is a change made to the internal structure of a software component to make it easier to understand and cheaper to modify, without changing the observable behaviour of that software component. Bad smells indicate that there is something wrong in the code that have to refactor. There are different tools that are available to identify and emove these bad smells. A software has two types of quality attributes- Internal and external. In this paper we will study the effect of clone refactoring on software quality attributes.

scholarly journals Cubing Fabrication/Costing and Machine Performance on African Fermented Condiment Quality Attributes Compared with Commercial Bouillon Types

Processes ◽  
2021 ◽  
Vol 9 (3) ◽  
pp. 481
Author(s):  
Eunice O. Uzodinma ◽  
Chigozie F. Okoyeuzu ◽  
Nneka N. Uchegbu ◽  
Charles Odilichukwu R. Okpala ◽  
Waheed A. Rasaq ◽  
...  
Keyword(s):  
Vitamin E ◽  
Food Processing ◽  
Quality Attributes ◽  
The Other ◽  
Throughput Capacity ◽  
Quality Attribute ◽  
Crude Fibre ◽  
Machine Performance ◽  
Calcium Iron ◽  
Carbohydrate Contents

Cubing machines in food processing have evolved over the years, which have made products like Star®, Knorr®, and Chicken® bouillon cubes become commercially available today, even in many parts of Africa. On the other hand, the fermented mesquite seed “okpeye” food condiment, traditionally produced by well-trained artisans and widely utilised in Nigeria, requires further product development in order to compete with bouillon cubes. Quality comparisons between the cubed “okpeye” condiment and commercially available bouillon cube products have not yet been reported. Therefore, cubing fabrication/costing and machine performance on African fermented “okpeye” condiment quality attributes, compared with commercial bouillon types, were done. The processing of mesquite seeds into the “okpeye” condiment resembled those of artisans. Bouillon cube products involved the Star®, Knorr®, and Chicken® types. Quality attributes involved proximate, micronutrient, phytochemical, and microbial aspects. Results showed that the throughput capacity of a cubing machine increased with an efficiency of 48 condiment cubes/min, forming properly without separation. Across all studied samples, the protein, ash, moisture, crude fat, crude fibre, and carbohydrate contents were in the range of 1.45–42.50%, 5.29–6.75%, 8.50–12.29%, 2.56–18.54%, 2.45–3.19%, and 18.16–25.56%, respectively. The protein, fat, moisture, calcium, iron, magnesium, and manganese contents of “okpeye” condiment were significantly higher (p < 0.05) than those of bouillon cubes. Fair amounts of vitamins B1, B2, B3, and E were found, with the “okpeye” condiment higher in vitamin E. Besides the flavonoids (0.12–0.18%), alkaloids (0.08–0.15%), saponins (0.19–0.55%), and tannins (0.69–0.93%) present, the microbial loads were similar (p > 0.05) across all samples. Indeed, the “okpeye” condiment can be cubed, and by quality attribute, it competes favourably, and very promising substitute to commercial bouillon cubes.

Special Issue: Trade-off Analysis of Software Quality Attributes

2005 ◽  
Vol 13 (4) ◽  
pp. 327-328 ◽  
Author(s):  
Claes Wohlin ◽  
Lars Lundberg ◽  
Michael Mattsson
Keyword(s):  
Software Quality ◽  
Quality Attributes ◽  
Special Issue ◽  
Trade Off

scholarly journals NON FUNCTIONAL REQUIREMENTS (NFRS) TRACEABILITY METAMODEL FOR AGILE DEVELOPMENT

2015 ◽  
Vol 77 (9) ◽  
Author(s):  
Adila Firdaus ◽  
Imran Ghani ◽  
Dayang Norhayati Abg Jawawi ◽  
Wan Mohd Nasir Wan Kadir
Keyword(s):  
Process Model ◽  
Full Scale ◽  
Agile Development ◽  
Functional Requirement ◽  
Functional Requirements ◽  
Agile Methodologies ◽  
And Performance ◽  
Requirement Changes ◽  
Recall Methods

Agile methodologies are well known for early and frequent releases. Besides, these methodologies also handle requirement changes well without causing delays. However, it has been noticed that the functional requirements changes can affect the non-functional requirements (NFRs) such as security and performance. It is also possible that the agile team is not even aware of these effects causing dysfunctional system. This issue could be addressed by offering traceability mechanism that helps to trace the effect of functional requirement changes on the non-functional requirements. Unfortunately, a few researchers have conducted studies regarding this issue. Thus, this study attempts to present a Traceability Process Model (TPM) to tackle the issue of tracing NFR especially security and performance. However, to materialize a full scale TPM, a metamodel is necessary. Therefore in this paper, we present a metamodel by integrating two existing metamodels. Then we validate the newly built metamodel with precision and recall methods. Lastly, we also develop a traceability tool that is based on the proposed metamodel.

AN EMPIRICAL STUDY OF SOFTWARE METRICS FOR ASSESSING THE PHASES OF AN AGILE PROJECT

2012 ◽  
Vol 22 (04) ◽  
pp. 525-548 ◽  
Author(s):  
GIULIO CONCAS ◽  
MICHELE MARCHESI ◽  
GIUSEPPE DESTEFANIS ◽  
ROBERTO TONELLI
Keyword(s):  
Software Quality ◽  
Web Application ◽  
Software Metrics ◽  
Pair Programming ◽  
Application Development ◽  
Agile Practices ◽  
Code Metrics ◽  
Agile Process ◽  
Adoption Level

We present an analysis of the evolution of a Web application project developed with object-oriented technology and an agile process. During the development we systematically performed measurements on the source code, using software metrics that have been proved to be correlated with software quality, such as the Chidamber and Kemerer suite and Lines of Code metrics. We also computed metrics derived from the class dependency graph, including metrics derived from Social Network Analysis. The application development evolved through phases, characterized by a different level of adoption of some key agile practices — namely pair programming, test-based development and refactoring. The evolution of the metrics of the system, and their behavior related to the agile practices adoption level, is presented and discussed. We show that, in the reported case study, a few metrics are enough to characterize with high significance the various phases of the project. Consequently, software quality, as measured using these metrics, seems directly related to agile practices adoption.

Sign in / Sign up

Export Citation Format

Share Document