View MODAF:AV-1 Overview and Summary Information View

mod_logo_60.jpg

Overview

The AV-1 Overview and Summary Information View is part of the MODAF All Views Viewpoint and one of the 46 MODAF views.

Version & Date

Version 1.2.003.

See MODAF Release History.

Purpose

From ‘The MODAF All Views (AV) Viewpoint’ p2:

The overview and summary information contained within the AV-1 product provides executive-level summary information in a consistent form that allows quick reference and comparison between architectural descriptions.

The AV-1 includes assumptions, constraints, and limitations that may affect high-level decisions relating to an architecture-based work programme.

Subject to Crown Copyright

Background

From ‘The MODAF All Views (AV) Viewpoint’ p2:

The architecture development must be framed in the context of the AV-1 product. AV-1 contains sufficient textual information to enable an analyst to identify relevant architectures.

The AV-1 also serves two additional purposes:

  • In the initial phases of architecture development, it serves as a planning guide.
  • When the architecture is built, this product provides summary information concerning the “who, what, when, why, and how” of the plan as well as a navigation aid to the views that have been created.


Subject to Crown Copyright

From ‘The MODAF All Views (AV) Viewpoint’ p8:

AV-1 provides an overview for an architecture description. The Overview and Summary Information provides executive-level summary information in a consistent form that allows quick reference and comparison between architectures. AV-1 includes assumptions, constraints, and limitations that may affect high-level decisions relating to the architecture.

AV-1 is usually a structured text product. An architecting organisation may create a template for the AV-1 that can then be used to create a consistent set of information across different architecture-based projects.

AV-1 provides a summary of a given Architecture and it documents the following descriptions:

  • Architecture Project Identification – Identifies the architecture project name, the architect, and the organisation developing the architecture. It also includes assumptions and constraints, identifies the approving authority and the completion date, and records the level of effort required to develop the architecture.
  • Scope – Identifies the Views and Products that have been developed and the temporal nature of the architecture, such as the time frame covered, whether by specific years or by designations such as current, target, transitional, and so forth. Scope also identifies the Enterprises and Enterprise Phases that fall within the scope of the architecture.
  • Purpose and perspective – Explains the need for the architecture, what it will demonstrate, the types of analyses that will be applied to it, who is expected to perform the analyses, what decisions are expected to be made on the basis of each form of analysis, who is expected to make those decisions, and what actions are expected to result. The perspective from which the architecture is developed is identified.
  • Context – Describes the setting in which an architecture exists. Context includes such things as mission, doctrine, relevant goals and vision statements, concepts of operation, scenarios, information assurance context (eg types of system data to be protected, such as classified or sensitive but unclassified, and expected information threat environment), other threats and environmental conditions, and geographical areas addressed, where applicable. Context also identifies authoritative sources for the standards, rules, criteria, and conventions that are used in the architecture. Any linkages to parallel architecture efforts should be identified.
  • Status – Describes the status of the architecture at the time of publication or development of the AV-1 (which might precede the architectural development itself). Status refers to creation, validation and assurance activities.
  • Tools and File Formats Used – Identifies the tool suite used to develop the architecture and file names and formats for the Architectural Products if appropriate.
  • Assumptions and Constraints.
  • Date Completed.

Subject to Crown Copyright

From ‘The MODAF All Views (AV) Viewpoint’ p2:

The data in an AV-1 can include:

  • Scope, purpose.
  • Listing of views used.

Subject to Crown Copyright

 

Comments

Other Frameworks

See also:

References


Category:Framework -> View
Category:MODAF -> View
Category:Solution

Categories:

 

© 2010 Eclectica Systems Ltd.