12.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

12 / 196Deliverable 2.3: <strong>Requirements</strong> <strong>Specification</strong> for <strong>the</strong> <strong>Vertical</strong> <strong>Industrial</strong> <strong>Use</strong> <strong>Case</strong>Polarion <strong>Requirements</strong> (2.0) / Polarion ALM (Polarion S<strong>of</strong>tware) 6CriteriaTraceability1. Horizontal linking <strong>of</strong> requirements(common level <strong>of</strong> abstraction)2. <strong>Vertical</strong> linking <strong>of</strong> requirements3. (different levels <strong>of</strong> abstraction)4. Different kinds <strong>of</strong> relations betweenrequirements5. Unique identification <strong>of</strong> <strong>the</strong> requirements6. Linking between requirementsand o<strong>the</strong>r artefacts7. Different kinds <strong>of</strong> relations betweenrequirements and o<strong>the</strong>rartefactsClustering & Annotation8. Definition <strong>of</strong> tags (user-definedor predefined)9. Annotation <strong>of</strong> artefacts usingtags10. Filtering and searching <strong>of</strong> artefactsby tags11. Clustering / categorization <strong>of</strong> artefactsConsolidation12. Checks for consistency betweenrequirements13. Checks for consistency <strong>of</strong> relationsbetween requirements14. Check requirements for redundancyPolarion <strong>Requirements</strong> 2.0 /Polarion ALM- Linking requirements, tasks, etc.- Traceability Matrix- Automatic linking by creating <strong>the</strong> requirements in a hierarchicalstructure- Predefined set <strong>of</strong> relations:o is related too is depended upono is duplicated byo is parent <strong>of</strong>o is follow-up <strong>of</strong>o is implemented by- Unique IDs for requirements- Imported design artefacts (e.g. Sparx Enterprise Architect)can be linked manually with work items like requirementsspecifications- Simple linking supported- <strong>Use</strong>r defined tags- Tags can be assigned to requirements (categories)- Creation <strong>of</strong> query for enhanced searching and filteringcapabilities- Clustering capability is partly achieved by query construction- Manually setting <strong>of</strong> “suspect” links between requirements- No (semi-) automatic consistency check- Manual setting <strong>of</strong> “suspect” links between requirements- No (semi-) automatic consistency check- No redundancy checks provided6 http://www.polarion.com© <strong>IKS</strong> Consortium2010

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!