Abstract
Requirements of a system keep on changing based on the need of stakeholders or the system developers, making requirement engineering an important aspect in software development. This develops a need for appropriate requirement change management. The importance of requirements traceability is defining relationships between the requirements and artefacts extracted by the stakeholder during the software development life-cycle and gives vital information to encourage software understanding. In this paper, we have concentrated on developing a tool for requirement traceability that can be used to extend the requirement elicitation and identification of system-wide qualities using the notion of quality attribute scenarios to capture the non-functional requirements. It allows us to link the functional and non-functional requirements of the system based on the quality attribute scenarios template proposed by the Carnegie Mellon Software Engineering Institute (SEI). Apart from this, the paper focuses on tracing the functional and non-functional requirements of the system using the concept of requirement traceability matrix.
Highlights
The essential proportion of accomplishment of a software system is how much it meets the goal for which it was developed [1]
We have concentrated on developing a tool for requirement traceability that can be used to extend the requirement elicitation and identification of system-wide qualities using the notion of quality attribute scenarios to capture the non-functional requirements
As crucial component of a software system, requirement engineering is a cyclic process of finding the software requirements, by recognizing the stakeholders and their needs and archiving these needs in a form that is manageable for analysis, correspondence, and resulting execution [1] [3]
Summary
The essential proportion of accomplishment of a software system is how much it meets the goal for which it was developed [1]. To design and develop any software system, requirement engineering assumes an essential job as it portrays the functional and non-functional requirements of the system software [3]. Some of the examples of the functional requirements are business rules, authentication and authorization levels, external interfaces, administrative functions, etc These requirements depend on the type of software users are interested in and the nature of the environment where the software is expected to be deployed [8]. A non-functional requirement defines how the system performs certain functionality under specified conditions [9] [10]. The tool developed can be used to stimulate the domain understanding, and requirement elicitation and specification process for system qualities [3]. We will go in detail about the traceability of requirements, followed by some related works and some details about the developed requirement engineering tool and the traceability between the requirements that are linked with one another
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
