Abstract
It is unlikely that the system will be better than the requirements identified in the design phase. So it is obvious that the quality of the software is closely related to the quality of the development process - from design to programming. The software requirements are a decisive factor for the software quality. The development of a computer system is not a task for a layman. Software development is a complex process composed of activities and steps that follow patterns and models developed by Software Engineering - SE. A requirements engineering - RE, a subfield there SE seeks a translation of customer needs through requirements elicitation. To have a greater chance of success for a successful software project, the activities da RE must not be neglected. This search aims to develop guidelines for building a strategy in the process of transforming requirements elicited using the MindMaps technique into iStar models. For the development of this search, a Systematic Literature Review - SLR was conducted to analyze the frequency of the use of MindMaps in the elicitation process and their transformation into more complex models. As a result of this research, templates and guidelines for the necessary routing for the process of transforming the requirements identified through the MindMaps into iStar models were created. The main contribution of this paper is to propose this routing in the process of converting the elicited requirements (MindMaps) into iStar models.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.