| Description | A Requirement is a generic statement used in system engineering to constrain what a Business System Asset should or should not be. The Requirement concept is kept in SysFEAT to maintain compatibility with traditional system engineering methodologies. The preferred approach is to follow capability-based engineering, as promoted by modern enterprise & system architecture (see OMG - UAF - View - Strategic Views) and agile frameworks (see SAFe© - SAFe Requirements Model).
The SOF - Business System Operating Pattern domain defines concepts and relationships used to model how a Business System operates/functions in its Operating Eco-System.. | ||
|---|---|---|---|
| External references |
OMG - SysML 1.X - Requirement SEBoK - Capability Engineering | ||
| Super Types |
Asset Property | ||
| Dictionary |
Dictionary of SysFEAT concepts | ||
| Framework Mapping | UAF - Motivation : Requirement |
Composition: ➝ Classification: ➝ Specialization: ➝ Instance Of: --> Enumerated definition: ➝ Syntax: ➝
Click node rectangle to collapse/expand one level. Click triangle for full recursive collapse/expand. Double-click on a node to open its URL. Hover for description.