Abstract
Throughout the development of software, during Requirements Engineering activities, software requirements dynamically and constantly evolve and mature from an “identified” stage to an “approved” stage. This evolution takes place individually for each requirement, in a very particular way, because it depends on the level of understanding that the requirements engineer reaches in relation to it. How, then, to monitor the evolution of each software requirement? How to know the quality of each software requirement? How to measure the level of understanding and difficulty that the requirements engineer has in relation to each software requirement? This paper aims to present a proposal to answer these questions through the use of an instrument developed specifically to assess and reveal the quality grades of each software requirement and also to assess and reveal that the levels of understanding and of difficulty of the requirements engineer is in relation to each software requirement. This instrument was called the Hermeneutical Theodolite of Requirements, which also can be applied to evaluate that the levels of understanding and of difficulty of the requirements engineer is in relation to the domain of application, essential input artifact and primordial to the specification of the requirements of software.
Highlights
To monitor the evolution of each software requirement? How to know the quality of each software requirement? How to measure the level of understanding and difficulty that the requirements engineer has in relation to each software requirement? This paper aims to present a proposal to answer these questions through the use of an instrument developed to assess and reveal the quality grades of each software requirement and to assess and reveal that the levels of understanding and of difficulty of the requirements engineer is in relation to each software requirement
To evaluate and reveal the different levels of understanding and difficulty that the requirements engineer has in relation to the application domain and to evaluate and reveal the different degrees of quality in which each software requirement is found, it is proposed the utilization of the Hermeneutical Theodolite of Requirements, an instrument composed of two mechanisms: one that acts on the application domain and another that acts on the software requirements
Individualized dynamics, as its evolution depends on the understanding and interpretation of the requirements engineer on this requirement, and about the application domain for which the software will be developed
Summary
S. Vega stand the business needs to be met by this software, for your requirements to be specified in such a way that your behavior is defined correctly and in accordance with the fundamental needs to be met, with the problems to be solved, with the functionalities to be made available, with the information to be processed, with the performances to be achieved, with the restrictions to be considered and with the interfaces to be created [1]. While some progress faster and more others need more time and attention to reach the appropriate maturity level All of these factors, depend on the ability of the requirements engineer to understand and interpret the application domain for which the software will be developed. This means that it can be applied regardless of the techniques, processes, and paradigms used for software development
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
