Requirement

Use the Requirement functionality to classify conceptual model classes and attributes with an engineering requirement value; either Functional, Physical, Functional and Physical or Installed.

These are industry recognized terms that communicates the context of the engineering object with respect to its current life cycle status as an indicator of the state of its maturity with respect to data integrity and engineering completeness.

The requirement definition is part of the base definitions in a new modelling project. It is automatically added to existing projects. The requirement value is set from the Properties pane or the Grid View, where 'fill down' editing is available.

In the Engineer module, it is possible to filter tags and attributes on the requirement value. A pseudo-attribute (ENGREQ) is provided on engineering, functional and simulation tags. This takes the tag element and returns the requirement value of the class which the tag is created from. The pseudo-attribute can be added to database views and engineer grids to appear as a grid column. Database view filters can be used to create pre-filtered views.

Attribute metadata filtering includes the built requirement definition. The name may include a numerical suffix if it clashes with an existing attribute named Requirement, for example, Requirement1.

In the underlying Dabacon model, the requirement definition is built as a UDA on UDETs and UDAs. The Dabacon value for Functional And Physical is FunctionalAndPhysical.