Architecture

The Architecture parameter specifies the architecture to be analyzed.

Enterprise Phases Subset

 

NAV-1 - Entreprise Phase Composition Hierarchy

The NAV-1 - Entreprise Phase Composition Hierarchy Report Chapter gives details of how the enterprise of the architecture is structured. The structure of the enterprise is displayed through the use of Enterprise Phases, in the corresponding tree diagram and in table form. A table is displayed with the Enterprise Phases in hierarchical form with their Name and Comment. The associated Master Plans with their Milestones are also listed.

NAV-1 - Entreprise Phase Dictionary

The NAV-1 - Entreprise Phase Dictionary Report Chapter presents a list of all the Enterprise Phases of the architecture.

Each Enterprise Phase is presented with its long and short Name and its Comment. The associated Master Plans are also listed.

NAV-1 - Library Organization

Each architecture and its data are contained in a Library. Architectures are however dependent on each other and sometimes need to use data contained in other architectures. As such, each Library that contains the different architectures is connected to another Library through access links that express the need for data contained in another architecture.

This Report Chapter therefore shows how the Library containing the NAF architecture is structured hierarchically along with every other Library that it accesses for data.

 

 

NAV-1 - Overview and Summary Information

This Report Chapter lists all the overview information relating to the architecture. It is based on the following structure:

Architecture Project Identification: Identifies the name, the contributing projects and the architects of the architecture, as well as the organizations developing the architecture. It also includes the assumptions and constraints, identifies the approving authority and the completion date, and records the level of effort and costs (projected and actual) required to develop the architecture.

Scope: Architecture View(s) and Product Identification: Identifies the views and subviews that have been developed and the temporal nature of the architecture, such as the time frame covered, whether by specific years or by designation such as current, target, transitional, and so forth. Scope also identifies the organizations that fall within the scope of the architecture.

Purpose and Viewpoint: Explains the purpose and the objectives of the architecture, which include, for example, what the architecture will demonstrate, the types of analyses to be applied, the expected performers of the analyses, the decisions to be made on the basis of the analyses, the decision makers and the resulting actions. The viewpoint from which the architecture is developed is identified.

Context: Describes the setting in which an architecture exists. Context includes things such as mission, doctrine, relevant goals and vision statements, operation concepts, scenarios, information assurance context, other threats and environmental conditions, and geographical areas addressed, where applicable. Context also identifies the authoritative sources of the rules, criteria, and conventions that were followed.

Tools and File Formats Used: Identifies the tools used to develop the architecture as well as the file names and formats used for the architecture and each product. This includes the MEGA release version used, the name of the environment and the name of the repository.

Findings: States the findings and the recommendations that have been developed based on the architectural effort. During the course of developing an architecture, several versions of a product may be produced. An initial version may focus the effort and document its scope, the organization involved, and so forth. After other subviews within an architecture's scope have been developed and verified, another version may be produced to document adjustments to the scope and to other aspects of the architecture that may have been identified. Cost information, such as integration costs, equipment costs and other costs can be included in the findings.

If the Report is generated in the MEGA Modeling tool, additional information is inserted to help the user identify the appropriate properties to include, in order to obtain this information in each section of the Report. This additional information is removed in generated documents and Web sites.