Abstract
The attributes of quality are that it is complex taxonomy, it cannot be weighted or measured but can be felt, discussed and judged. Early assessment and verification of functional attributes (requirements) are supported well by renowned standards while the nonfunctional attributes (requirements) are not. Agile software development methodologies are of high repute as the most popular and effective approaches to the development of software systems. Early requirements verification methodologies in Agile Software Engineering are well focused in this way and hence mainly researched have achieved in functional requirements. For early quality aspects (attributes) in order to bring quality in our design and hence development process, it is very important to consider nonfunctional requirements quality metrics (attributes). A comprehensive work is also being done to propose and validate (using iThink) different quality models which could make sure the quality of agile software products being developed, which will be though available in detail in the literature review (section II). Yet a generic and standard quality metrics model is missing in this for the agile software practices in all, which off course is further needed to make sure that the agile product being developed, will surely accomplish quality characteristics as decided by the stakeholders as well as the mentioned quality standard they are addressing. In this work we have proposed a quality metrics model that fulfills the desired quality attributes exist in ISO/IEC (Quality standards, ISO 9126, ISO 25000) in early requirements, we validated this by performing simulations in iThink technology that also ensures that the quality of item being produced to meet the described criteria.
Highlights
Extreme Programming is one of a software engineering practice, articulated in 90s by Ward Cunningham, Kent Beck, and Ron Jeffries [17], the most important and noticeable among several methodologies
Taking this comprehensive research literature into account and research work done into the quality metrics in agile software engineering (XP etc.) it has been observed that the quality aspect is the most important aspect in every methodology that is used for the development of software products
As we know that extreme programming is different from other previous methodologies [17], there must be a standard quality metric model that fulfills the criteria for the activities and quality attributes of agile methods especially extreme programming
Summary
Extreme Programming is one of a software engineering practice, articulated in 90s by Ward Cunningham, Kent Beck, and Ron Jeffries [17], the most important and noticeable among several methodologies. XP is different from traditional methodologies in a way that it emphasizes on adaptation than on prediction. In XP programming it is believed that it is more realistic to adapt different changes that appear during the whole software development process rather than specifying all the requirements at the beginning. Though in the software development process, requirement management and requirement engineering practices are very important & very critical [18]. Different quality models have been proposed that try to cover all the important and critical quality attributes [9] [4].
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
