|
|
Application module:
Requirement identification and version |
ISO/TS 10303-1140:2010-03(E)
© ISO
|
This clause specifies the information requirements for the
Requirement identification and version
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.
The following EXPRESS specification begins the
Requirement_identification_and_version_arm
schema and identifies the necessary external references.
EXPRESS specification:
*)
SCHEMA Requirement_identification_and_version_arm;
(*
The following EXPRESS interface statements specify the elements
imported from the ARMs of other application modules.
EXPRESS specification:
*)
USE FROM
Identification_assignment_arm;
--
ISO/TS 10303-1021
USE FROM
Product_version_relationship_arm;
--
ISO/TS 10303-1020
(*
NOTE 1
The schemas referenced above are specified in the following
part of ISO 10303:
| Identification_assignment_arm |
ISO/TS 10303-1021 |
| Product_version_relationship_arm |
ISO/TS 10303-1020 |
NOTE 2
See Annex C,
Figures
C.1and C.2
for a graphical representation of this schema.
This subclause specifies the ARM type
for this application module. The ARM type and
definition is specified below.
The requirement_identification_and_version_identification_item type is an extension
of the
identification_item type.
It adds the data
types
Requirement
and
Requirement_version
to the list of alternate data types.
EXPRESS specification:
*)
TYPE
requirement_identification_and_version_identification_item =
SELECT
BASED_ON
identification_item
WITH
(Requirement,
Requirement_version);
END_TYPE;
(*
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 is a type of
Product
that is used to uniquely identify a requirement.
NOTE 1
The term "requirement" is used here in the sense that term is used in
systems engineering and similar industrial domains.
NOTE 2
There may be many versions of a requirement Requirement_version
). There
may also be more than one domain-specific view of a given
Requirement_version
(using theRequirement_view_definition entity).
The requirement entity is simply a placeholder for holding a unique requirement. Most associations
and properties are defined at the Requirement_view_definition level - that is in the context of a domain.
EXAMPLE
A requirement may be identified as "NOx emissions requirement", and uniquely identified as "Req2".
NOTE 3
Systems engineering tools and organizations may use differing identification mechanisms. Multiple
identifiers may be assigned to a requirement using the Alias_identification entity.
EXPRESS specification:
*)
ENTITY Requirement
SUBTYPE OF (Product);
END_ENTITY;
(*
A Requirement_version is a type of
Product_version
that identifies a particular version of a requirement.
NOTE
This entity is used to record different versions of a requirement. In
this case, the word "version" implies "revision"
- that is a particular release of a requirement.
EXAMPLE
A given requirement might have versions 1.0, 1.1, 1.2 and 2.0.
EXPRESS specification:
*)
ENTITY Requirement_version
SUBTYPE OF (Product_version);
SELF\Product_version.of_product : Requirement;
END_ENTITY;
(*
Attribute definitions:
of_product:
the
Requirement
for which the Requirement_version identifies a version.
A Requirement_version_relationship is a type of
Product_version_relationship
that is used to relate a previous version (predecessor) of a requirement to the version that replaces it (successor).
EXPRESS specification:
*)
ENTITY Requirement_version_relationship
SUBTYPE OF (Product_version_relationship);
SELF\Product_version_relationship.relating_version RENAMED predecessor : Requirement_version;
SELF\Product_version_relationship.related_version RENAMED successor : Requirement_version;
END_ENTITY;
(*
Attribute definitions:
predecessor:
the preceding
Requirement_version
in the relationship.
successor:
the succeeding
Requirement_version
in the relationship.
*)
END_SCHEMA; -- Requirement_identification_and_version_arm
(*
© ISO 2009 — All rights reserved
