|
|
Application module:
Requirement view definition |
ISO/TS 10303-1141:2014-02(E)
© ISO
|
This clause specifies the information requirements for the
Requirement view definition
application module. The information requirements are specified as the
Application Reference Model (ARM) of this application module.
NOTE 1 A graphical representation of the information
requirements is given in
Annex C.
NOTE 2 The mapping specification is specified in
5.1. It shows how
the information requirements are met by using common resources and
constructs defined or imported in the MIM schema of this application
module.
This clause defines the information requirements to which implementations shall
conform using the EXPRESS language as defined in ISO 10303-11.
The following begins the
Requirement_view_definition_arm
schema and identifies the necessary external references.
EXPRESS specification:
*)
SCHEMA Requirement_view_definition_arm;
(*
The following EXPRESS interface statements specify the elements
imported from the ARMs of other application modules.
EXPRESS specification:
*)
USE FROM
Property_as_definition_arm;
--
ISO/TS 10303-1399
USE FROM
Product_view_definition_arm;
--
ISO/TS 10303-1019
USE FROM
Requirement_identification_and_version_arm;
--
ISO/TS 10303-1140
(*
NOTE 1
The schemas referenced above are specified in the following
part of ISO 10303:
| Property_as_definition_arm |
ISO/TS 10303-1399 |
| Product_view_definition_arm |
ISO/TS 10303-1019 |
| Requirement_identification_and_version_arm |
ISO/TS 10303-1140 |
NOTE 2
See Annex C,
Figures
C.1and C.2
for a graphical representation of this schema.
This subclause specifies the ARM entities for this
module. Each ARM application entity is an atomic element that
embodies a unique application concept and contains attributes
specifying the data elements of the entity. The ARM
entities and definitions are specified below.
A Requirement_view_definition is a type of Product_view_definition
that provides a view of a requirement version relevant for one or more application
domains. This view collects requirement data for specific engineering purposes.
EXAMPLE
An engineer may have responsibility for collecting all requirements associated with the cooling
of an engine - covering engine block, tubing, water pump, electric fan.
Some requirements in a Requirement_view_definition might impact on different disciplines.
Multiple Requirement_view_definition objects may be used to present different views
of a given requirement for each discipline.
EXPRESS specification:
*)
ENTITY Requirement_view_definition
SUBTYPE OF (Product_view_definition);
SELF\Product_view_definition.defined_version : Requirement_version;
END_ENTITY;
(*
Attribute definitions:
defined_version:
the
Requirement_version
that the Requirement_view_definition defines.
A Single_requirement_view_definition is a type of
Requirement_view_definition
that is defined by a single property.
EXPRESS specification:
*)
ENTITY Single_requirement_view_definition
SUBTYPE OF (Requirement_view_definition);
INVERSE
definition : Single_property_is_definition FOR described_element;
END_ENTITY;
(*
Attribute definitions:
definition:
the
single_property_is_definition
that is the definition for the Single_requirement_view_definition.
*)
END_SCHEMA; -- Requirement_view_definition_arm
(*
© ISO 2014 — All rights reserved
