Architecture

The Architecture parameter specifies the architecture to be analyzed.

Operational Node Subset

The Operational Node Subset parameter can be set with Service Interactions, operational nodes and diagrams. The type of values used for the parameter determines the scope of the report:

 

Operational Node: Only the specified operational nodes are considered. Embedded operational nodes are excluded. All incoming and outgoing Service Interactions are included as well as the targeted operational nodes. The process of operational node collection is not reiterated on operational nodes found from Service Interactions.

 

Service Interaction:These are the Service Interactions that exist between operational nodes. Only the specified Service Interactions are considered and source and target operational nodes are included.

 

Diagram: Operational nodes and interactions displayed in the diagrams are included. The diagrams must be described in the architecture analyzed.

 

 

Resource Type Subset

This parameter is used to reduce the scope of realizing resources in the NOV-2 - Operational Node Realization Report Chapter.

 

This parameter can be set with Applications, Artifacts, Org-Units or Resource Architectures.The type of values used for the parameter determines the scope of the report. If no parameter is set, all the Applications, Artifacts, Org-Units and Resource Architectures are included in the Report.

 

Application: Only the specified Applications are considered for the Report.

 

Artifact: These artifacts are the physical assets of the system that are neither applications or organizational elements.

 

Org-Unit: These can humans or simply organizational elements. They can be internal or external to the enterprise.

 

Resource Architecture: These Resource Architectures are combinations of the physical assets and organizations used to provide a capability.

 

 

NOV-2 - Operational Node Composition Hierarchy

The NOV-2 - Operational Node Connectivity Description Report Chapter details the hierarchical structure of the operational nodes.

NOV-2 - Operational Node Dictionary

The NOV-2 - Operational Node Dictionary Report Chapter lists in alphabetical order the operational nodes defined in the architecture, with their comments and component details. This enables the retrieval of items for which the names are known. It also displays the Operational Node Structure diagram for the different operational nodes.

 

NOV-2 - Operational Node Exchange

The NOV-2 - Operational Node Exchange provides information on all the interactions that are established between operational components within the context of a node.

This Report Chapter lists the needs that exist for the exchange of information from specific operational nodes to others. Depending on the scope defined (or the default scope: the entire architecture), the Report Chapter lists a set of needlines as well as the source and target operational nodes. For each needline, the exchanged information is also listed.

The structure diagrams in which the different needs are defined are also displayed.

 

NOV-2 - Operational Node Exchange Balance

The NOV-2 - Operational Node Exchange Balance Report Chapter is used to verify that the exchanges defined between operational nodes are correctly designed. All the incoming and outgoing exchanges of the operational nodes are compared and examined to reveal missing as well as unnecessary information for the exchange design. The report lists all the internal and outside messages and Service Interactions that detail the selected operational nodes.

 

NOV-2 - Operational Node Exchange Compliance

The NOV-2 - Operational Node Exchange Compliance Report Chapter indicates the level of compliance between the need to exchange information from one operational node to another and the information actually exchanged through the implemented missions.

Activities supported by the operational nodes actually exchange information within the context of designed missions. This information is compared with the need defined in the needlines/Service Interaction. Missing or unexpected information is detected.

This Report Chapter relies on the nodes defined in the NOV-2 - Operational Node Connectivity Description subview as well as the functional processes that describe how missions are performed. These processes are described in detail in NOV-5 - Operational Activity Model, however, a brief description is necessary to aid in understanding the content of this report.

A node structure does not indicate how missions are performed. It only describes the nodes involved in the mission and how they are structured. Through interactions, you can guess the potential information exchanges that occur between nodes. To add a dynamic perspective to nodes, a process must be described (see the NOV-5 - Operational Activity Model subview). This process is composed of activities that exchange information. Information is actually exchanged in the process while the node structure only describes the ability to perform such exchanges.

Activities are performed under the control of the operational nodes.

The Operational node exchange compliance report identifies three states for the information exchange:

Information Exchange Correctly Designed: an information item is defined at both the node and the process levels.

Missing Information: an information item can potentially be exchanged between two nodes, however, there is no process available to perform this exchange. The question is therefore, whether the interface described between the two nodes is still useful.

Unexpected Information: an information item is exchanged in a process between two activities, however, there is no interaction between the nodes carrying out the activities. The question is therefore, should the information be exchanged in this manner in the process and must the Service Interaction be reviewed to depict the ability to make such an exchange.

 

NOV-2 - Operational Node Generalization Hierarchy

The NOV-2 - Operational Node Generalization Hierarchy Report Chapter shows how the operational nodes of the architecture are generalized.

The operational nodes are presented in table form along with their comments and the Library to which they belong. If a variant of an operational node exists, this variant is also presented in the table along with the varied operational node (operational node from which the variant was created).

To add a new generalization, use the Connect