|
|
Application module:
Model parameter |
ISO/TS 10303-1703:2018-11(E)
© ISO
|
This clause specifies the information requirements for the
Model parameter
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
Model_parameter_arm
schema and identifies the necessary external references.
EXPRESS specification:
*)
SCHEMA Model_parameter_arm;
(*
The following EXPRESS interface statements specify the elements
imported from the ARMs of other application modules.
EXPRESS specification:
*)
USE FROM
Activity_method_assignment_arm;
--
ISO/TS 10303-1249
USE FROM
Characteristic_arm;
--
ISO/TS 10303-1654
USE FROM
Classification_with_attributes_arm;
--
ISO/TS 10303-1111
USE FROM
Independent_property_representation_arm;
--
ISO/TS 10303-1038
USE FROM
Group_arm;
--
ISO/TS 10303-1113
REFERENCE FROM
Specification_document_arm
--
ISO/TS 10303-1747
(get_document_definition);
(*
NOTE 1
The schemas referenced above are specified in the following
part of ISO 10303:
| Activity_method_assignment_arm |
ISO/TS 10303-1249 |
| Characteristic_arm |
ISO/TS 10303-1654 |
| Classification_with_attributes_arm |
ISO/TS 10303-1111 |
| Independent_property_representation_arm |
ISO/TS 10303-1038 |
| Group_arm |
ISO/TS 10303-1113 |
| Specification_document_arm |
ISO/TS 10303-1747 |
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 mp_activity_method_item_select type is an extension
of the
activity_method_item type.
It adds the data
type
Test_method_based_parameter_assignment
to the list of alternate data types.
EXPRESS specification:
*)
TYPE
mp_activity_method_item_select =
SELECT
BASED_ON
activity_method_item
WITH
(Test_method_based_parameter_assignment);
END_TYPE;
(*
The mp_documented_element_select type is an extension
of the
documented_element_select type.
It adds the data
type
Model_parameter
to the list of alternate data types.
EXPRESS specification:
*)
TYPE
mp_documented_element_select =
SELECT
BASED_ON
documented_element_select
WITH
(Model_parameter);
END_TYPE;
(*
The mp_groupable_item type is an extension
of the
groupable_item type.
It adds the data
type
Group_relationship
to the list of alternate data types.
NOTE
Added
Group_relationship
is only for dummy purposes to fulfill some odd modelling/Express requirements and that users shall savely ignore this.
EXPRESS specification:
*)
TYPE
mp_groupable_item =
SELECT
BASED_ON
groupable_item
WITH
(Group_relationship);
END_TYPE;
(*
The parameter_assignment_select type is an
extensible list of alternate data types
that allows for the designation of the data
type
Model_parameter.
NOTE
The list of entity data types may be
extended in application modules that use the constructs of
this module.
EXPRESS specification:
*)
TYPE
parameter_assignment_select =
EXTENSIBLE
GENERIC_ENTITY
SELECT
(Model_parameter);
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 Category_model_parameter is a type of
Model_parameter.
A Category_model_parameter is a formally declared variable of the Class
provided for an external application to populate at execution time in a computing environment.
The primary use for a Category_model_parameter is for creation and sharing of catalog data element definitions.
EXPRESS specification:
*)
ENTITY Category_model_parameter
SUBTYPE OF (Model_parameter);
INVERSE
associated_attribute : SET[1:1] OF Classification_attribute FOR attribute_definition;
END_ENTITY;
(*
Attribute definitions:
associated_attribute:
specifies an inverse relationship that specifies that the existence of the
Category_model_parameter is dependent on the existence of the
Classification_attribute
that specifies the Category_model_parameter as an
attribute_definition.
An Independent_property_with_unit is a type of
Independent_property.
An Independent_property_with_unit adds specific units that may be used for data assigned to an
Independent_property.
NOTE
In some cases, the type of property limits the type of units that are reasonable to supply with data.
EXAMPLE
An electric current property would be associated with the unit Ampere.
EXPRESS specification:
*)
ENTITY Independent_property_with_unit
SUBTYPE OF (Independent_property);
unit_of_measure : SET[1:?] OF Unit;
END_ENTITY;
(*
Attribute definitions:
unit_of_measure:
specifies a role of the
Unit
for the Independent_property_with_unit.
A Model_parameter is a type of Independent_property.
A Model_parameter is a formally declared variable provided for an external application to populate at execution time in a computing environment.
The unit_of_measure for the Model_parameter shall be consistent with the unit_of_measure for the values assigned
to the parameter, either as defaults or through explicit assignment.
The default values are explicitly intended to be overridden by explicit assignment, when that explicit assignment
references the Model_parameter.
EXAMPLE
In Spice, temperature is a Model_parameter that may be set at the execution time.
EXPRESS specification:
*)
ENTITY Model_parameter
SUBTYPE OF (Independent_property);
valid_range :
OPTIONAL
SET[1:?] OF Value_range;
default_value :
OPTIONAL
scalar_or_coordinated_characteristics;
DERIVE
reference_document : SET[0:?] OF Document_definition := get_document_definition(SELF, 'reference document',
'DOCUMENT_DEFINITION_ARM.DOCUMENT_DEFINITION');
WHERE
WR1: EXISTS (reference_document) AND (SIZEOF(reference_document) = 1);
END_ENTITY;
(*
Attribute definitions:
valid_range:
specifies the
Value_range
of the Model_parameter. The value of this attribute need not be specified. There shall be one or more
Value_ranges
for a Model_parameter.
The valid_ranges need not be contiguous.
default_value:
specifies the scalar_or_coordinated_characteristics for the Model_parameter.
The default_value specifies either a characteristic or a Property_value_representation
for the parameter.The value of this attribute need not be specified.
When a collection of data types needs to be defined, so that an instance of the collection may be referenced, the
Property_value_representation is used. The External_item_identification specifies the reference_document to define the
semantics of the collection.
reference_document:
specifies either an Document_definition or an identifier for the standard document that
contains the reference for the Model_parameter. The reference_document shall define the mapping between the
property_type
string
values and the semantics to be applied by a simulator, except for the case of
physical_property_type.
Formal propositions:
WR1:
The reference_document shall be provided and it's size shall be one.
A Model_parameter_with_unit is a type of
Independent_property_with_unit
and a type of
Model_parameter
that includes a specification of the allowed units to use for the parameter.
EXPRESS specification:
*)
ENTITY Model_parameter_with_unit
SUBTYPE OF (Independent_property_with_unit, Model_parameter);
WHERE
WR1: NOT('MODEL_PARAMETER_ARM.SCHEMA_BASED_MODEL_PARAMETER' IN TYPEOF(SELF));
END_ENTITY;
(*
Formal propositions:
WR1:
A Model_parameter_with_unit shall not also be a
Schema_based_model_parameter.
A Parameter_assignment is a type of
Property_definition_representation.
A Parameter_assignment is the association of either a characteristic
or Property_value_representation with a
parameter_assignment_select,
and is used to provide actual values for characteristics declared formally by
the
parameter_assignment_select.
The values assigned by the Parameter_assignment shall override
any default values specified by the parameter_assignment_select.
The Parameter_assignment declares to the receiving system that the types that are associated
are compatible. It is the responsibility of the sending system to ensure this is the case.
Type compatibility is in the end a matter of resolving data dictionaries. This standard
provides facilities for ensuring a common data dictionary is available for base types such as
length, frequency.
EXPRESS specification:
*)
ENTITY Parameter_assignment
SUBTYPE OF (Property_definition_representation);
SELF\Property_definition_representation.definition : parameter_assignment_select;
END_ENTITY;
(*
Attribute definitions:
definition:
an attribute inherited from the
Property_definition_representation
shall be redeclared as the
parameter_assignment_select
for the Parameter_assignment.
A Parameter_assignment_override is the association between a Parameter_assignment and another Parameter_assignment which replaces or overrides the first Parameter_assignment. Parameter_assignment_override is used when an Analytical_model_application is referenced but some of the Parameter_assignments need to be replaced.
EXPRESS specification:
*)
ENTITY Parameter_assignment_override;
overridden_parameter_assignment : Parameter_assignment;
overriding_parameter_assignment : Parameter_assignment;
END_ENTITY;
(*
Attribute definitions:
overridden_parameter_assignment:
specifies a role of the Parameter_assignment for the
Parameter_assignment_override. The model_parameter_assignment binds instance data to data slots in the Analytical_model_application.
NOTE
For each parameter declared in a model definition, an actual value must be assigned when that model is
referenced, unless there is a default assignment included in the source code for the model.
overriding_parameter_assignment:
specifies a role of the Parameter_assignment for the
Parameter_assignment_override.
A Product_specific_parameter_value_assignment is the assignment of a value to a parameter in the context of a specific Product.
EXPRESS specification:
*)
ENTITY Product_specific_parameter_value_assignment;
of_product : Product;
assigned_parameter : Parameter_assignment;
DERIVE
the_model_parameter : Model_parameter := assigned_parameter\Property_definition_representation.definition;
UNIQUE
UR1: the_model_parameter, of_product;
END_ENTITY;
(*
Attribute definitions:
of_product:
specifies a role of the Product for the Product_specific_parameter_value_assignment.
assigned_parameter:
specifies a role of the Parameter_assignment for the Product_specific_parameter_value_assignment.
the_model_parameter:
specifies the definition of assigned_parameter.
Formal propositions:
UR1:
The combination of of_product and the_model_parameter shall be unique within a population of
Product_specific_parameter_value_assignments.
A Schema_based_model_parameter is a type of Model_parameter.
A Schema_based_model_parameter is a reference to an attribute and entity in a formal
model for the purposes of later extracting data from a model instance or populating
data in a model instance. The schema identifier uses application of the ASN 1 notation
standardized in part 1 of this standard.
EXAMPLE
In rule definition, it is often necessary to reference entity data types or their attributes as a parameter.
EXPRESS specification:
*)
ENTITY Schema_based_model_parameter
SUBTYPE OF (Model_parameter);
entity_name : Independent_property;
attribute_name :
OPTIONAL
Independent_property;
schema_identifier : Independent_property;
UNIQUE
UR1: entity_name, attribute_name, schema_identifier;
END_ENTITY;
(*
Attribute definitions:
entity_name:
specifies the
Independent_property
used as the unambiguous identifier for the entity name for the Schema_based_model_parameter.
attribute_name:
specifies the
Independent_property
used as the unambiguous identifier for the attribute name for the Schema_based_model_parameter. The value of this attribute need not be specified.
schema_identifier:
specifies the string used as the unambiguous identifier for the schema for the Schema_based_model_parameter.
EXAMPLE
The identifier for the AIM schema from ISO 10303-210:2001 is "{ 1 0 10303 210 1 1 1 }".
Formal propositions:
UR1:
The combination of schema_identifier, entity_name, and attribute_name shall be unique within a population of
Schema_based_model_parameters.
A Test_method_based_parameter_assignment is a type of Parameter_assignment.
EXPRESS specification:
*)
ENTITY Test_method_based_parameter_assignment
SUBTYPE OF (Parameter_assignment);
WHERE
WR1: SIZEOF(USEDIN(SELF,'ACTIVITY_METHOD_ASSIGNMENT_ARM.APPLIED_ACTIVITY_METHOD_ASSIGNMENT.ITEMS')) = 1;
END_ENTITY;
(*
Formal propositions:
WR1:
There shall be exactly one Applied_activity_method_assignment
referencing this entity as a member of items.
*)
END_SCHEMA; -- Model_parameter_arm
(*
© ISO 2018 — All rights reserved
