![\"REQ](\"https:\/\/www.threesl.com\/blog\/wp-content\/uploads\/2023\/05\/rc00219-UK_REQ.bmp\")
<\/a>Requirements management is part of every agile and phase process. Stakeholder needs are captured, analysed and engineered. Changes are tracked in a CM system. All needs will be linked to design, build, test and acceptance information. In agile, this is in every sprint. In phase-based processes, it is less frequent. But the techniques are the same, and the same tool needs apply that only Cradle provides:<\/p>\n
- \n
- User-defined information, attributes and links<\/li>\n
- Data query<\/a>, view<\/a> and manipulation<\/a> features<\/li>\n
- Built-in quality checks<\/a> on items’ contents<\/li>\n
- Integrated modelling<\/a><\/li>\n
- Built-in collaboration, discussions and alerts<\/li>\n
- Built-in configuration management<\/a> (CM) with baselines<\/a> and formal change<\/a> (CC)<\/li>\n<\/ul>\n
Requirement types can be defined (user, business, system, product, functional or non-functional), user stories and use cases. Link to codes, standards, regulations, knowledge or assumptions. You define other item types to be managed, such as functions, issues, tests, risks, SBS, PBS, WBS or defects. Attributes in these items are controlled, how they will be linked to each other, and their workflows.<\/p>\n
Item Attributes<\/h2>\n
Items have user-definable attributes, each storing or linking to up to 1 TByte of data. Attribute types are user-defined, including dates, numbers, plain and rich text, single or multi-value lists, Office and other documents, and calculations.<\/p>\n
The text in requirements, tests, verifications and other items can be quality checked against project-specific rules.<\/p>\n
Items can be in hierarchies<\/a>, groups and many:many relationships. You can create projects using a common library. Product ranges, models, variants and builds are supported. Items can be shared and reused in any of these structures.<\/p>\n
Capturing Items<\/h2>\n
Items can be captured from external documents by Document Loader<\/a>. It reproduces the document structure in a hierarchy of items. Each item is linked to its origin in the document. Figures are loaded automatically. Tables can be captured into items, images, Word objects or rich text.<\/p>\n
Document Loader finds differences in new versions of documents<\/a>. Loading the new version will update items and their links. Coverage analysis between documents and database items are provided.<\/p>\n
Full version management of source documents is provided. Regression to previous versions is supported, with reversal of all changes.<\/p>\n
Requirements and other items can be loaded from Word, Excel or other tools using plug-ins, data exchange or direct interfaces.<\/p>\n
Analyses<\/h2>\n
Coverage, traceability and impact analyses are easily run, then viewed as trees, lists, tables, matrices, or in dynamic Hierarchy Diagrams<\/a> with user-defined attributes. Items can be filtered, sorted, split and merged. All changes to items can be logged. Users can be alerted to changes by Cradle, email or both.<\/p>\n
Discussions<\/h2>\n
Users collaborate by adding discussions<\/a> to items and adding threads to items and adding threads of comments to these discussions.<\/p>\n
Reviews<\/h2>\n
Once stable, items can be progressed through a series of formal reviews that log comments from all reviewers. You define the workflows<\/a>. Once in a baseline, items can be subject to formal change control using change request<\/a> (proposals) and change tasks<\/a> (actions). You can view the database as it was in any previous baseline.<\/p>\n
Multiple generations of requirements can be maintained and compared. Multiple sets of variants can be managed to reflect different products in a common family.<\/p>\n
Items can be progressed within their lifecycles. The lifecycle of an item represents the series of stages that it can pass through between being created and reaching a final, rest, condition.<\/p>\n
User-defined tree, table and matrix views can be defined from a point-and-click UI to show traceability, coverage and compliance. This includes RTMs, VCRMs and PVMs.<\/p>\n
Linking Items<\/h2>\n
Cradle provides transitive cross referencing, in which it follows chains of multiple links between indirectly linked items, so you can see cross-lifecycle traceability in one step. For example, you can view user requirements to tests, where Cradle transparently follows intermediate links via system requirements, functions, architecture components and so on.<\/p>\n
Requirements can be linked to test data, safety and other critical issues, risks or any project data. When used with the Cradle-SYS<\/strong> module, user stories and requirements can be linked to functional, behavioural, UML, analysis, architecture and design models organised into any number of model hierarchies in both analysis and design domains.<\/p>\n
Publish Information<\/h2>\n
All information can be published in user-defined reports and formal documents.<\/p>\n
Feature Summary<\/h2>\n
![\"Feature](\"https:\/\/www.threesl.com\/blog\/wp-content\/uploads\/2023\/05\/feature_summary_req.png\")
Feature Summary – REQ<\/figcaption><\/figure>\n - Built-in quality checks<\/a> on items’ contents<\/li>\n