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 evolut...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.展开更多
In order to develop quality software that meets the originals needs of its users, it is necessary to perform the Requirements Engineering, so that the software context to be developed is identified, examined and speci...In order to develop quality software that meets the originals needs of its users, it is necessary to perform the Requirements Engineering, so that the software context to be developed is identified, examined and specified properly. However, there is a problem that is increasingly in debate: the difficulty in understanding and establishing the purpose of the software to be developed, as pointed out by important researches in the area, such as the Chaos Report, which indicates that only 29% of software projects are successful, and the Software Engineering Institute, which points out software requirements as a critical factor for the success of software engineering and that deficiencies in this dimension are the main causes of software project failures. This article presents a proposal to address this problem through the use of the Hermeneutical Elicitation of Requirements, which is the conceptual adequacy of some hermeneutical methods in a technical approach that assists the requirements engineer to conceive better of the software requirements. In this way, the software engineer will be better able to develop the software to better meet the needs of its end users and sponsors.展开更多
The Software Engineering aims to develop, within the deadlines and costs established, quality software and that meets the needs of its users. To be made the definition of what the software should do (to establish its ...The Software Engineering aims to develop, within the deadlines and costs established, quality software and that meets the needs of its users. To be made the definition of what the software should do (to establish its purpose), it included the execution of activity the Requirements Engineering, where the context of software to be developed is identified, examined and specified. All other activities of software development depend primarily on this activity. However, there is a problem increasingly in evidence: understand the context of software to be developed. This article aims to present a proposal to face this problem through the use of specific hermeneutical methods for the Requirements Engineering, which will help the software development team understand the original needs of the business to be attended. The basic idea is to produce a hermeneutic specification acceptable, which will be used for the extraction and the specification of the software requirements to be developed. In essence, the hermeneutics focuses on the true interpretation and understanding in contextualized of what is intended to know. The Hermeneutical Engineering of Requirements comes to be the result of the adequacy of methods hermeneutical to assist, specifically the activity of Engineering of Requirements.展开更多
文摘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.
文摘In order to develop quality software that meets the originals needs of its users, it is necessary to perform the Requirements Engineering, so that the software context to be developed is identified, examined and specified properly. However, there is a problem that is increasingly in debate: the difficulty in understanding and establishing the purpose of the software to be developed, as pointed out by important researches in the area, such as the Chaos Report, which indicates that only 29% of software projects are successful, and the Software Engineering Institute, which points out software requirements as a critical factor for the success of software engineering and that deficiencies in this dimension are the main causes of software project failures. This article presents a proposal to address this problem through the use of the Hermeneutical Elicitation of Requirements, which is the conceptual adequacy of some hermeneutical methods in a technical approach that assists the requirements engineer to conceive better of the software requirements. In this way, the software engineer will be better able to develop the software to better meet the needs of its end users and sponsors.
文摘The Software Engineering aims to develop, within the deadlines and costs established, quality software and that meets the needs of its users. To be made the definition of what the software should do (to establish its purpose), it included the execution of activity the Requirements Engineering, where the context of software to be developed is identified, examined and specified. All other activities of software development depend primarily on this activity. However, there is a problem increasingly in evidence: understand the context of software to be developed. This article aims to present a proposal to face this problem through the use of specific hermeneutical methods for the Requirements Engineering, which will help the software development team understand the original needs of the business to be attended. The basic idea is to produce a hermeneutic specification acceptable, which will be used for the extraction and the specification of the software requirements to be developed. In essence, the hermeneutics focuses on the true interpretation and understanding in contextualized of what is intended to know. The Hermeneutical Engineering of Requirements comes to be the result of the adequacy of methods hermeneutical to assist, specifically the activity of Engineering of Requirements.
