Requirements Management

The Need

The majority of systems are specified by textual documents that are used initially to assess potential suppliers' bids and subsequently to assess the compliancy of the delivered system. A system may be specified in one or several such source documents that may include industry standards. In large projects, revisions to source documents will occur throughout the project, each revision associated with potential change to any or all of the requirements and thence on work completed to date.

Crucial to the supplier is the definition of a set of unambiguous, precise, comprehensive, consistent, and detailed requirements to which they will be contractually bound. These are necessarily separate from the customer's source documents but must be demonstrably equivalent to them.

A need exists to hold source documents, to derive cross referenced requirements from them, and to manage new iterations of them within a formal configuration management framework.

Cradle Requirements Management

The Capture & Engineering
of formal requirements with optional requirement hierarchies
linked into analysis and design models and/or user defined information types
from source statements in multiple versions of multiple source documents
providing
complete lifecycle traceability,
immediate impact analyses,
bi-directional, many-to-many, attributed, transitive cross referencing
that is supported by an integral Configuration Management System

There are four key elements that provide this functionality:

• Source Document Management & Control
• Requirements Capture
• Requirements Engineering
• Lifecycle Traceability

Requirements Management | Systems Modelling | Performance Modelling | Software Engineering
Document Composer | The Cradle Core | 3SL | Home