Use Of Software Requirements Specification ( Srs )

2204 Words9 Pages
V. WHY TO USE TOOLS FOR RM Most project teams generally use software requirements specification (SRS) to document their requirements in natural language. However, a document based approach has some limitations: a document is difficult to keep current especially if it is a long one, it is hard to communicate changes to the team members who are affected by that change, it is difficult to associate supplementary information with each requirement and it is hard to define links between requirements and its decompositions or corresponding artifacts [7].You may do a great job at capturing all requirements in a SRS document at the beginning of a project but as development progresses, changes in SRS may become unmanageable and hard to track. This…show more content…
Classifying requirements according to attributes also helps team members who have different roles to view requirements from different viewpoints. For e.g. Developers may want to view requirements by difficulty and testers may want to view requirements by priority. • RM tools make requirement traceability easier by providing the functionality to link requirements with other requirements or components. Traceability makes it easier to estimate the impact of a change in subsequent phases when it happens in one phase. Figure 2: Impact of changing one requirement specification As shown in Figure 2 above, if there is a change in one requirement specification requested, then with the linkages already present between requirements and their corresponding phases, we can guess the complexity involved. For the example shown, if there is a change of 1 requirement specification, 7 design and 10 implementation requirements may be affected. Although not all of the linked requirements may be impacted but this can give managers a fair idea of the complexity involved with changing of a requirement. Link traceability can also exist when requirements are decomposed from one stage to another. For e.g. Figure 3: Requirement decomposition traceability example [1] Each requirement has a unique identifier associated with it so that traceability can be established. In the example above, a requirement E1 which is
Open Document