Requirements Specification of the Vertical Industrial Use Case ... - IKS

10 / 196Deliverable 2.3: Requirements Specification for the Vertical Industrial Use Case3. Different kinds of relations betweenrequirements4. Unique identification of the requirements5. Linking between requirementsand other artefacts6. Different kinds of relations betweenrequirements and otherartefactsbetween high-level requirements and related softwarerequirements).Different kinds of relations can be defined betweenrequirements (e.g.: “depends on”, “is extension of”).The different requirements can be identified by aunique identifier as a prerequisite for the traceability.The tool supports the creation of links between requirementsand other artefacts (e.g. design specifications).Different kinds of relations can be defined betweenrequirements and other artefacts (e.g.: “dependson”, “is extension of”).Clustering & AnnotationHandling artefacts in large software development projects requires an effective and wellarrangedorganization of the content items. Clustering and annotation of content are appropriatetechniques to manage the categorization and organization of content. By evaluatingwith respect to the following criteria, the support of such functionalities by existing RE/RMand ALM tools is analyzed.Criteria7. Definition of tags (user-definedor predefined)8. Annotation of artefacts usingtags9. Filtering and searching of artefactsby tags10. Clustering / categorization ofartefactsDescriptionThe tool supports the definition of tags of predefinedor user-defined types.Artefacts can be annotated by assigning tags tothem.The artefacts can be filtered or searched by thetags assigned to them.The artefacts can be clustered by using specific criteriaor rules.ConsolidationIn the field of requirements engineering and management, content gathered from differentpersons and perspectives is brought together. The consolidation of these requirements iscrucial for the further steps in the software engineering process. By analyzing the validationfunctionalities the support of the consolidation by existing tools is evaluated.Criteria11. Checks for consistency betweenrequirements12. Checks for consistency of relationsbetween requirements13. Check requirements for redundancyDescriptionThe tool provides a set of rules to check the consistencybetween requirements.The tool provides a set of rules to check the consistencyof relations between requirements.The tool provides a redundancy check, which identifiessimilar requirements.Addressing the criteria defined above, three different RE/RM and ALM tools have beenevaluated. The evaluation has been done with the following tools: IBM Rational DOORS / Rational Requirements Composer (IBM)© IKS Consortium2010