4 Information requirements

This clause specifies the information requirements for the Functional specification 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 Functional_specification_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 Signal_arm;    --  ISO/TS 10303-1745



USE FROM Network_functional_design_view_arm;    --  ISO/TS 10303-1704



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:

Signal_arm	ISO/TS 10303-1745
Network_functional_design_view_arm	ISO/TS 10303-1704
Specification_document_arm	ISO/TS 10303-1747

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

4.2 ARM type definitions

This subclause specifies the ARM types for this application module. The ARM types and definitions are specified below.

4.2.1 fs_documented_element_select   

The fs_documented_element_select type is an extension of the documented_element_select type. It adds the data type Signal_specification to the list of alternate data types.

EXPRESS specification:

*)
TYPE fs_documented_element_select = SELECT BASED_ON documented_element_select WITH
   (Signal_specification);
END_TYPE;
(*

4.2.2 fs_external_identification_item   

The fs_external_identification_item type is an extension of the external_identification_item type. It adds the data type Functional_specification to the list of alternate data types.

EXPRESS specification:

*)
TYPE fs_external_identification_item = SELECT BASED_ON external_identification_item WITH
   (Functional_specification);
END_TYPE;
(*

4.2.3 fs_node_or_terminal   

The fs_node_or_terminal type allows for the designation of the data types Functional_unit_network_node_definition, and Functional_unit_terminal.

EXPRESS specification:

*)
TYPE fs_node_or_terminal = SELECT
   (Functional_unit_network_node_definition,
    Functional_unit_terminal);
END_TYPE;
(*

4.3 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.3.1 Functional_specification   

A Functional_specification is the information that characterizes the behaviour of a Functional_unit under controlled circumstances using stimulus-response test methods. Detailed properties of the relationship between the reference and characterizing signals define the behaviour.

NOTE    The evaluation or categorization of this relationship is not standardized in this document.

EXPRESS specification:

*)
ENTITY Functional_specification;
  associated_definition : Functional_specification_definition;
  reference_signal : SET[1:?] OF Signal_specification;
  characterizing_functional_unit : Functional_unit;
  characterizing_signal : SET[1:?] OF Signal_specification;
INVERSE
  characteristic_category : External_source_identification FOR item;
WHERE
  WR1: characterizing_functional_unit.composed_network = associated_definition;
END_ENTITY;
(*

Attribute definitions:

associated_definition: specifies a role of the Functional_specification_definition for the Functional_specification. The associated_definition is an aggregation of all the Functional_specification with which it is associated.

reference_signal: specifies the reference or stimulus Signal_specification for the Functional_specification.

characterizing_functional_unit: specifies the Functional_unit for the Functional_specification.

characterizing_signal: specifies the response Signal_specification for the Functional_specification.

characteristic_category: specifies an inverse relationship that specifies that the existence of the Functional_specification is dependent on the existence of the External_source_identification that specifies the Functional_specification as its item.

Formal propositions:

WR1: The composed_network attribute of the Functional_unit shall be associated_definition for the characterizing_functional_unit.

4.3.2 Functional_specification_definition   

EXPRESS specification:

*)
ENTITY Functional_specification_definition
  SUBTYPE OF (Functional_unit_network_definition);
INVERSE
  composing_specification : SET[1:?] OF Functional_specification FOR associated_definition;
END_ENTITY;
(*

Attribute definitions:

composing_specification: specifies an inverse relationship that specifies that the existence of the Functional_specification_definition is dependent on the existence of the Functional_specification that specifies the Functional_specification_definition as its associated_definition. There shall be one or more Functional_specification for a Functional_specification_definition.

4.3.3 Signal_specification   

EXPRESS specification:

*)
ENTITY Signal_specification;
  signal_access_mechanism : fs_node_or_terminal;
  reference_access_mechanism : OPTIONAL fs_node_or_terminal;
  minimum_characteristic : OPTIONAL Signal_property;
  maximum_characteristic : OPTIONAL Signal_property;
  characterization_network : Functional_unit_network_definition;
  nominal_characteristic : OPTIONAL Signal_property;
DERIVE
  measurement_condition : SET[1:1] OF Document_definition := get_document_definition(SELF, 'measurement condition', 'SPECIFICATION_DOCUMENT_ARM.TEST_SPECIFICATION');
WHERE
  WR1: EXISTS (minimum_characteristic) OR EXISTS (maximum_characteristic) OR EXISTS (nominal_characteristic);
END_ENTITY;
(*

Attribute definitions:

signal_access_mechanism: specifies the role of the fs_node_or_terminal for the Signal_specification. The value of this attribute need not be specified.

reference_access_mechanism: specifies the Functional_unit_terminal on the Functional_unit being characterized by this Signal_specification. The value of this attribute need not be specified. The purpose of the reference_access_mechanism is to provide a reference facility for measurements.

EXAMPLE 1   The reference_access_mechanism need not be supplied for evaluation of non-causal systems such as s- or z-plane characterized control system elements or digital elements. There is no assumption in this part of ISO 10303 that reference_access_mechanism is related to any standard reference node, for example, "0" in certain continuous system simulators. Example names of the terminal specified by reference_access_mechanism include Ground, Analogue ground, Digital ground, Trigger in, Gate out.

minimum_characteristic: specifies the lower bound for the valid range of the Signal_property for the Signal_specification.

maximum_characteristic: specifies the upper bound for the valid range of the Signal_property for the Signal_specification.

characterization_network: specifies the Functional_unit_network_definition for this Signal_specification. In this part of ISO 10303, the characterization_network shall include all required simulated stimulus sources and measurement sensors.

EXAMPLE 2   Examples of characterization_network types include test bench (VHDL), test fixture, test circuit.

nominal_characteristic: specifies the nominal bound for the valid range of the Signal_property for the Signal_specification.

measurement_condition: specifies the Test_specification under which the measurements are valid, including allowed ranges for stimulus conditions, for the Signal_specification.

NOTE    The measurement_condition may specify data using text or graphics.

Formal propositions:

WR1: At least one of attributes minimum_characteristic or maximum_characteristic, or nominal_characteristic shall be set.

© ISO 2018 — All rights reserved