Requirements Maturation Analysis by Accessibility and Stability

Abstract

Abstract-The success of any projects can be affected by requirements changes. We define requirements elicitation as the activity of adding, deleting, and modifying requirements. We here refer to the completion of requirements elicitation of a software component as requirements maturation. The requirements of the component will never be changed after 100% maturation. We introduce the requirements maturation efficiency (RME) in order to estimate the requirements maturation period for the component. The RME of the requirements represents how quickly the requirements of a component reach 100% maturation. The goal of this paper is to define a method of estimating the RME of each component. Since requirements analysts (RAs) elicit requirements by accessing requirement sources and stability is one of the characteristics of requirements, we can assume that the RME of a component must be derived from the accessibility of the requirements source and the stability of the requirements. We model accessibility as the number of information flows from the source of the requirements to the RA and model stability with the requirements maturation index (RMI). The results from multiple regression analysis for two cases indicate that RME can be derived by these two factors with a significant level of 5%. We also discuss a method by which to estimate the period for requirements maturation.

JeB: Safe Simulation of Event-B Models in JavaScript

“…Stated another way: we must have complete requirements before developing. Unfortunately, we know that we do not for most actual projects [12].…”

Validation Obligations: A Novel Approach to Check Compliance between Requirements and their Formal Specification

“…Software engineers have fewer tools at their disposal though. In a typical software development, the requirements in the beginning phase differ from the ones in the ending phase [10]. Two reasons account for this:…”

Proving the Fidelity of Simulations of Event-B Models

“…Works on requirements elicitation with formal goal models [3], on transforming goal models into specifications [4], or on formal domain modeling in [5] for instance, show that the formalization question can be answered. The major reason lies in the fact that requirements evolve during many projects [6]. Therefore, it is unlikely that the very first formal model will contain the complete and final specification.…”