Requirement Categories

The SysML specification provides a non-normative list of Requirement categories (types). These are stereotyped Requirements that refine or extend the base SysML Requirement, providing a mechanism to create Requirements that serve a particular purpose or describe a particular aspect of a system. For example Physical Requirements can be used to describe some physical aspect of a system such as the weight or size of a component. These and other user-created categories can have any number of additional properties defined such as:

• RiskKind
• VerificationMethodKind

Enterprise Architect conveniently provides these Requirement categories as elements on the SysML Requirement's Toolbox pages.

The tool also provides a sophisticated and fully functional profile system, allowing users to create extensions to the base SysML Requirement and any number of user-defined Requirement categories applicable to the modeling domain or problem space. These stereotyped Requirements can have user-defined properties added that are needed to model the specific Requirement element (or other model element).

For example a team might decide to include a property of volatility to a Requirement to ensure work is not commenced until the Requirement is stable (i.e. not volatile). As another example, a team might be creating medical devices and need to comply with various statutory standards. Each component that is used as part of the solution might be required to be compliant. A compliance-level property could be created and the component could be assigned a level indicating its compliance from a range of values defined in a spin control or a drop-down list. For more information see the Developing Profiless Help topic.