No abstract

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.

Abstract-One of most common aspect with traditional software development is managing requirements. As requirements emerge throughout the software development process and thus are needed to be addressed through proper communication and integration between stakeholders, developers and documentation. Agile methodology is an innovative and iterative process that supports changing requirements and helps in addressing changes throughout the development process.Requirements are elicited at the beginning of every software development process and project (product) and latter are prioritized according to their importance to the market and to the product itself. One of the most important and influencing steps while making a software product is requirements prioritization. Prioritizing requirements helps the software team to understand the existence and importance of a particular requirement, its importance of use and its urgency to time to market. There are many requirements prioritization techniques with their relative strength and weaknesses. Otherwise many of them fail to take account all the factors that must be considered while prioritizing requirements such as cost, value, risk, time to market, number of requirements and effect of non-functional requirements on functional requirements.There are several requirements prioritization methodologies that aid in decision making but importantly many lacks to account the important factors that have significant influence in prioritizing requirements. A requirement prioritization methodology based on several factors such as time to market, cost, risk etc has been proposed. The proposed model is expected to overcome this lack. In sprints, requirements will be prioritized both on the basis of influencing factors such as cost, value, risk, time to market etc. and through the effect of non-functional requirements over functional requirements. This will improve the overall quality of software product when it is included in the development process of scrum. Requirements will not only be prioritized based on sprints, human decision but by critically analyzing the factors (sub characteristics) that can cause the product to success/ fail repeatedly thus ensuring the consistency in right requirements and hence the right prioritized requirements will be selected for a particular sprint at a time.

Abstract-Requirements prioritization is one of the important parts of managing requirements in software development process which plays its role in the success or failure of a software product. A software product can go wrong or fail if right requirements are not prioritized at right time. Thus, there is a need of a vast or complete requirements prioritization technique or model that spans all the factors that must be considered while prioritizing requirements whether it's for a traditional software development or agile software development. There are several requirements prioritization methodologies that aid in decision making and in prioritizing requirements but importantly many lacks to account the important factors that have significant influence in prioritizing requirements. A requirement prioritization methodology that takes account of important factors such as time and human behavioral factors that has an influence in prioritizing requirements is required. This new model/ technique expected to overcome the lack that is in existing prioritization techniques because of not considering time gap factor and human behavioral factor. Extensive study on literature of agile methodology, requirements elicitation and prioritization has been done to find out factors that influence the decision making process of requirement prioritization. It is found that as agile methodologies such as XP, SCRUM deliver products in increments, there is a time gap between each increment of approximate 4 weeks or more, this time lapse could cause human behavioral to change either because of market demand or any other personal reason and, thus, influences the prioritization decision. These factors could be termed as time factor and human behavioral factors. Thus, a requirement prioritization technique or model is needed that takes account of all such factors while prioritizing requirements whether it's for a traditional software development or agile software development.