Business overview

This section provides a business level overview of this capability.

@@@@ section @@@@

Information model overview

This section provides an overview of the information model that supports this capability.

The EXPRESS-G for requirements is shown in Figure 1 below and explained in the following sections.

NOTE    See also the modules: Requirement assignment, Requirement identification and version, Requirement view definition, Product identification, Product version, Product view definition, Product view definition relationship, and Product version relationship.

Figure 1 —  Requirements EXPRESS-G

Where "source" may be:

• Activity_method,
• Applied_activity_method_assignment,
• Applied_state_assignment,
• Applied_state_definition_assignment,
• Document_version,
• Interface_connector_occurrence,
• Part_version,
• Product_as_individual_version,
• Product_view_definition,
• State, or
• State_definition.

• Activity_method,
• Alternate_part_relationship,
• Applied_activity_method_assignment,
• Applied_state_assignment,
• Applied_state_definition_assignment,
• Assembly_component_relationship,
• Assembly_relationship_substitution,
• Attachment_slot,
• Attachment_slot_version,
• Breakdown,
• Breakdown_element,
• Breakdown_element_realization,
• Breakdown_element_usage,
• Breakdown_element_version,
• Breakdown_version,
• Document_version,
• Interface_connector_occurrence,
• Interface_specification,
• Part_version,
• Product_as_individual_version,
• Product_as_planned,
• Product_as_realized,
• Product_configuration,
• Product_in_attachment_slot,
• Product_view_definition,
• Project,
• Required_resource_by_specification,
• State, or
• State_definition

Capability templates

The following sections define a set of templates for the capability, where a template is a specification of a set of entities that need to be instantiated to represent a given set of information.

This section specifies the template representing_requirements.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  Representation of requirement data (EXPRESS-G)

Figure 2 —  Representation of requirement data (Condensed EXPRESS-G)

Figure 3 —  Representation of requirement data (EXPRESS-I diagram)

Figure 4 —  Representing requirement data (condensed EXPRESS-I)

This section specifies the template representing_requirement.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  An EXPRESS-G representation of the Information model for representing_requirement

Figure 2 —  The graphical representation of the representing_requirement template

Figure 3 —  Entities instantiated by representing_requirement template

          #1 = REQUIREMENT('/IGNORE','/IGNORE','/IGNORE');
          #2 = REQUIREMENT_VERSION('/IGNORE','/IGNORE',#1);
          #3 = REQUIREMENT_VIEW_DEFINITION('/IGNORE','/IGNORE','/IGNORE',#4,(),#2);
          #4 = VIEW_DEFINITION_CONTEXT('/IGNORE','/IGNORE','/IGNORE');
          #6 = IDENTIFICATION_ASSIGNMENT('TR-3452','/IGNORE','/IGNORE',(#1));
          #8 = CLASSIFICATION_ASSIGNMENT(#9,(#6),'/IGNORE');
          #9 = EXTERNAL_CLASS('/NULL','Requirement_idenitification_code','/IGNORE',#10);
          #10 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std','/IGNORE');
          #13 = ORGANIZATION('/IGNORE','/IGNORE');
          #15 = IDENTIFICATION_ASSIGNMENT('Bicycle Inc.','/IGNORE','/IGNORE',(#13));
          #17 = CLASSIFICATION_ASSIGNMENT(#18,(#15),'/IGNORE');
          #18 = EXTERNAL_CLASS('/NULL','Organization_name','/IGNORE',#19);
          #19 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std','/IGNORE');
          #20 = ORGANIZATION_OR_PERSON_IN_ORGANIZATION_ASSIGNMENT(#13,'/IGNORE',(#6,#26));
          #22 = CLASSIFICATION_ASSIGNMENT(#23,(#20),'/IGNORE');
          #23 = EXTERNAL_CLASS('/NULL','Owner_of','/IGNORE',#10);
          #26 = IDENTIFICATION_ASSIGNMENT('1','/IGNORE','/IGNORE',(#2));
          #28 = CLASSIFICATION_ASSIGNMENT(#29,(#26),'/IGNORE');
          #29 = EXTERNAL_CLASS('/NULL','Progression_idenitification_code','/IGNORE',#10);
          #46 = CLASSIFICATION_ASSIGNMENT(#47,(#4),'/IGNORE');
          #47 = EXTERNAL_CLASS('/NULL','Logistics_support_analysis','/IGNORE',#48);
          #48 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:sample','/IGNORE');
          #50 = CLASSIFICATION_ASSIGNMENT(#51,(#4),'/IGNORE');
          #51 = EXTERNAL_CLASS('/NULL','Development_stage','/IGNORE',#10);
        

Figure 4 —  Instantiation of representing_requirement template

This section specifies the template assigning_requirements.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  Assigning requirement data (EXPRESS-G diagram)

Figure 2 —  Assigning requirement data (condensed EXPRESS-G diagram)

The following classes and their sub-classes can be used:

classifications: [Requirement_view_definition_identification_code]
Error RDL1: The class Requirement_view_definition_identification_code does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml

Figure 3 —  Assigning requirement data to a part version (EXPRESS-I diagram)

Figure 4 —  Assigning requirement data to a part version (condensed EXPRESS-I diagram)

This section specifies the template assigning_requirement.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  An EXPRESS-G representation of the Information model for assigning_requirement

Figure 2 —  The graphical representation of the assigning_requirement template

Figure 3 —  Entities instantiated by assigning_requirement template

          #1 = PART_VERSION('/IGNORE','/IGNORE',$);
          #2 = REQUIREMENT_VIEW_DEFINITION('/IGNORE','/IGNORE','/IGNORE',$,(),$);         
          #3 = REQUIREMENT_ASSIGNMENT('/IGNORE','/IGNORE',#2,#1);
          #5 = CLASSIFICATION_ASSIGNMENT(#6,(#3),'/IGNORE');
          #6 = EXTERNAL_CLASS('/NULL','Defined_for','/IGNORE',#7);
          #7 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:sample','/IGNORE');
        

Figure 4 —  Instantiation of assigning_requirement template

This section specifies the template relating_requirement_versions.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  Relating requirement versions (EXPRESS-G diagram)

Figure 2 —  Relating requirement versions (condensed EXPRESS-G diagram)

Figure 3 —  Entities instantiated by template relating_requirement_versions (EXPRESS-I diagram)

Figure 4 —  Instantiation of template relating_requirement_versions

This section specifies the template sourcing_requirements.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Error model_diag_1: Either delete A DESCRIPTION OF THE DIAGRAM or provide a description
EXAMPLE

Figure 14 —  Sourcing requirements (EXPRESS-G diagram)

Error model_diag_1: Either delete A DESCRIPTION OF THE DIAGRAM or provide a description
EXAMPLE

Figure 15 —  Sourcing requirements (condensed EXPRESS-G diagram)

The following classes and their sub-classes can be used:

classifications: [Requirement_view_definition_identification_code]
Error RDL1: The class Requirement_view_definition_identification_code does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml

Figure 16 —  Sourcing requirements (EXPRESS-I diagram)

Figure 17 —  Sourcing requirements (condensed EXPRESS-I diagram)

This section specifies the template relating_requirements.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 18 —  Relating requirements (EXPRESS-G diagram)

Figure 19 —  Sourcing requirements (condensed EXPRESS-G diagram)

The following classes and their sub-classes can be used:

classifications: [Requirement_view_definition_identification_code]
Error RDL1: The class Requirement_view_definition_identification_code does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml

Figure 20 —  Relating requirements (EXPRESS-I diagram)

Figure 21 —  Relating requirements (condensed EXPRESS-I diagram)

© OASIS 2010 — All rights reserved