4 Information requirements

This clause specifies the information requirements for the Functional decomposition with nodal representation to packaged mapping 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 Functional_decomposition_with_nodal_representation_to_packaged_mapping_arm schema and identifies the necessary external references.

4.1 Required AM ARMs

The following EXPRESS interface statements specify the elements imported from the ARMs of other application modules.

EXPRESS specification:

*)
USE FROM Functional_decomposition_to_design_arm;    --  ISO/TS 10303-1676



USE FROM Physical_connectivity_definition_arm;    --  ISO/TS 10303-1755
(*



NOTE 1   The schemas referenced above are specified in the following part of ISO 10303:

Functional_decomposition_to_design_arm	ISO/TS 10303-1676
Physical_connectivity_definition_arm	ISO/TS 10303-1755

NOTE 2   See Annex C, Figures C.1and C.2 for a graphical representation of this schema.

4.2 ARM entity definitions

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.

4.2.1 Aggregate_connectivity_requirement   

An Aggregate_connectivity_requirement is the set of one or more Functional_unit_network_node_definition that are determined by a mapping application to be linked with a transitive closure based on a property of each member of the set.

NOTE    The mapping application will map the set to one node in a physical network.

EXAMPLE    A typical property to use to determine the members of the set is a common name, e.g., GND.

EXPRESS specification:

*)
ENTITY Aggregate_connectivity_requirement;
  connectivity_requirement : SET[1:?] OF Functional_unit_network_node_definition;
END_ENTITY;
(*

Attribute definitions:

connectivity_requirement: specifies the role of the Functional_unit_network_node_definition for the Aggregate_connectivity_requirement. There shall exist one or more Functional_unit_network_node_definitions for the Aggregate_connectivity_requirement.

Informal propositions:

IP1: Each of the terminals that participate in a connectivity_requirement shall be reachable from any other terminal in the connectivity_requirement that is specified by the same connectivity_requirement.

NOTE    This is a transitive closure requirement on the set of terminals. Since the hierarchical product structure is represented in this part of ISO 10303 as a directed acyclic graph, the closure state is evaluated by traversing the combined graph including both product structure and nodal representation at each node of the graph.

4.2.2 Connectivity_allocation   

A Connectivity_allocation is the relationship between a functional connectivity requirement and its implementation. The collection of functional terminals in the functional decomposition that are connected is allocated to one equivalent physical node. That equivalent physical node is an implementation in the Connectivity_allocation.

NOTE    This part of ISO 10303 does not separately represent a fully resolved functional node.

EXPRESS specification:

*)
ENTITY Connectivity_allocation;
  implementation : Physical_connectivity_definition;
  connectivity_requirement : Aggregate_connectivity_requirement;
UNIQUE
  UR1: implementation;
END_ENTITY;
(*

Attribute definitions:

implementation: specifies the role of the Physical_connectivity_definition for the Connectivity_allocation.

connectivity_requirement: specifies the role of the Aggregate_connectivity_requirement for the Connectivity_allocation.

NOTE    The connectivity_requirement effectively specifies one equivalent functional node.

Formal propositions:

UR1: The implementation shall be unique within a population of Connectivity_allocations.

© ISO 2006 — All rights reserved