|
|
Application module:
Requirement assignment |
ISO/TS 10303-1233:2011-10(E)
© ISO
|
This clause specifies the information requirements for the
Requirement assignment
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_assignment_arm
schema and identifies the necessary external references.
EXPRESS specification:
*)
SCHEMA Requirement_assignment_arm;
(*
The following EXPRESS interface statement specifies the elements
imported from the ARM of another application module.
EXPRESS specification:
*)
USE FROM
Requirement_view_definition_arm;
--
ISO/TS 10303-1141
(*
NOTE 1
The schemas referenced above are specified in the following
part of ISO 10303:
| Requirement_view_definition_arm |
ISO/TS 10303-1141 |
NOTE 2
See Annex C,
Figures
C.1and C.2
for a graphical representation of this schema.
This subclause specifies the ARM types
for this application module. The ARM types and
definitions are specified below.
The requirement_assignment_item type is an
extensible list of alternate data types.
Additional alternate data types are specified in select data
types that extend the
requirement_assignment_item type.
NOTE
This empty extensible select requires
extension in a further module to ensure that entities that refer to it have
at least one valid instantiation.
EXPRESS specification:
*)
TYPE
requirement_assignment_item =
EXTENSIBLE
GENERIC_ENTITY
SELECT;
END_TYPE;
(*
The requirement_satisfaction_item type is an
extensible list of alternate data types
that allows for the designation of the data
type
requirement_assignment_item.
NOTE
The list of entity data types may be
extended in application modules that use the constructs of
this module.
EXPRESS specification:
*)
TYPE
requirement_satisfaction_item =
EXTENSIBLE
GENERIC_ENTITY
SELECT
(requirement_assignment_item);
END_TYPE;
(*
The requirement_source_item type is an
extensible list of alternate data types.
Additional alternate data types are specified in select data
types that extend the
requirement_source_item type.
NOTE
This empty extensible select requires
extension in a further module to ensure that entities that refer to it have
at least one valid instantiation.
EXPRESS specification:
*)
TYPE
requirement_source_item =
EXTENSIBLE
GENERIC_ENTITY
SELECT;
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_assignment is used to relate a requirement (via the Requirement_view_definition entity) to data types representing the items
which are affected by the requirement.
EXAMPLE
A requirement "the vehicle shall have a maximum power output of at least 150BHP" could be assigned to the data types
which are used to represent the vehicle's engine.
EXPRESS specification:
*)
ENTITY Requirement_assignment;
id : STRING;
description :
OPTIONAL
STRING;
assigned_requirement : Requirement_view_definition;
assigned_to : requirement_assignment_item;
END_ENTITY;
(*
Attribute definitions:
id:
an identifier that distinguishes the Requirement_assignment.
description:
the text that provides further information about the Requirement_assignment.
The value of this attribute need not be specified.
assigned_requirement:
the Requirement_view_definition which is assigned.
assigned_to:
the item which has the requirement assigned to it.
A Requirement_satisfied_by is a relationship between an item (specified in requirement_satisfaction_item) and a requirement, asserting that the item satisfies the identified requirement.
EXAMPLE
A data type used to represent a vehicle's engine with a power output of 160BHP could be asserted to satisfy a requirement
"the vehicle shall have a maximum power output of at least 150BHP".
EXPRESS specification:
*)
ENTITY Requirement_satisfied_by;
id : STRING;
description :
OPTIONAL
STRING;
satisfied_by : requirement_satisfaction_item;
satisfied_requirement : Requirement_view_definition;
related_assignment :
OPTIONAL
Requirement_assignment;
END_ENTITY;
(*
Attribute definitions:
id:
the identifier that distinguishes theRequirement_satisfied_by.
description:
the text that provides further information about the
Requirement_satisfied_by.
The value of this attribute need not be specified.
satisfied_by:
the item that satisfies the requirement.
satisfied_requirement:
the requirement that is satisfied.
related_assignment:
the Requirement_assignment that is satisfied by the
Requirement_satisfied_by.
The value of this attribute need not be specified.
A Requirement_source is a relationship between a requirement (via the Requirement_view_definition entity) and the data types representing the source of the requirement
EXAMPLE
The source of the requirement "the vehicle shall have a maximum power output of at least 150BHP" could be a document representing
the findings of a
market survey of sports car buyers.
EXPRESS specification:
*)
ENTITY Requirement_source;
id : STRING;
description :
OPTIONAL
STRING;
source : requirement_source_item;
sourced_requirement : Requirement_view_definition;
END_ENTITY;
(*
Attribute definitions:
id:
the identifier that distinguishes theRequirement_source.
description:
the text that provides further information about the
Requirement_source.
The value of this attribute need not be specified.
source:
the item which is the source of the requirement.
sourced_requirement:
the requirement which is to be related to its source.
*)
END_SCHEMA; -- Requirement_assignment_arm
(*
© ISO 2011 — All rights reserved
