NAV-3b Metadata (Extensions)
The purpose of the NAV-3b Metadata Extensions subview is to document any deviations of the architecture's subviews from the standard subview guidelines of the NAF, in terms of deviations from the NAF metamodel (NMM), which underpins all standard subviews of the NAF.
Even though the NAV-3b subview is used to stress the differences between the NMM definition and the HOPEX NAF implementation, the default behavior will be to integrate the metamodel diagrams describing the HOPEX implementation of the NMM.
The user can add his/her own set of metamodels and can also note the differences as a link comment in the report instance or by adding comments in the diagrams themselves.
The NAV-3b Report Template
The NAV-3b report template comes with two parameters:
• The Architecture parameter which specifies the architecture to be analyzed.
• The Metamodels parameter, which is optional. This parameter is used to reduce the scope of the study to the selected metamodels. These metamodels describe the HOPEX implementation of the NAF architecture description. If this parameter is not set, all the metamodels used to support the NAF subviews of the architecture are taken into account.
The NAV-3b NAF Metamodel Chapter
The NAF Metamodel chapter lists the metamodels of HOPEX NAF used to support the different NAF subviews of the specified architecture. The list is arranged in alphabetical order.
A section is dedicated to each metamodel. This section presents:
• a diagram of the metamodel
• a list of all the concepts (metaclasses) used in the metamodel.
Each concept is presented with a definition as well as a list of its metaAttributes and their comments.
• associations that can be made between metaclasses.
For each association, the source and target metaclass as well as the source and target Roles are also displayed.