The AV-1 provides executive-level summary and overview information in a consistent form that allows quick reference and comparison between Architectural Descriptions. The written content of the AV-1 describes the concepts contained in the pictorial representation of the Operational View (OV)-1. 
Guide: DoDAF Architecture Framework Version 2.02 – Page 110
The AV-1 frames the context for the Architectural Description and includes assumptions, constraints, and limitations that may affect high-level decisions relating to an architecture-based work program. It should contain sufficient information to enable a reader to select a single Architectural Description from among many to read in more detail. The AV-1 serves two additional purposes: 
- In the initial phases of architecture development, it serves as a planning guide
- Provides summary information on the plan concerning who, what, when, why, and how
- Provides navigation aid to the models that have been created
The usage of the AV-1 is to: 
- Scope the architecture effort
- Provide context to the architecture effort
- Define the architecture effort
- Summarize the findings from the architecture effort
- Assist search within an architecture repository
The AV-1 is usually a structured text product. An architecting organization 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. While the AV-1 is often dispensed with or “retrofitted” to a finished architecture package, it’s desirable to do it up-front because the AV-1 provides a summary of a given Architectural Description and it documents the following descriptions: 
- Architectural Description Identification: Identifies the Architectural Description effort name, the architect, and the organization developing the Architectural Description. It also includes assumptions and constraints, identifies the approving authority and the completion date, and records the level of effort required to develop the Architectural Description.
- Scope: Identifies the Viewpoints, DoDAF-described Models, and Fit-for-Purpose Views that have been selected and developed. The AV-1 should address the temporal nature of the Architectural Description, such as the time frame covered, whether by specific years or by designations such as “current”, “target”, or transitional. Scope also identifies the organizational entities and timelines that fall within the scope of the Architectural Description.
- Purpose and Perspective: Explains the need for the Architectural Description, what it will demonstrate, the types of analyses that will be applied to it, who is expected to perform the analysis, what decisions are expected to be made based of each form of analysis, who is expected to make those decisions, and what actions are expected to result. The perspective from which the Architectural Description is developed is identified.
- Context: Describes the setting in which an Architectural Description exists. Context includes such things as: mission, doctrine, relevant goals and vision statements, concepts of operation, scenarios, information assurance context (e.g., types of system or service 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 Architectural Description and file names and formats for the Architectural Models if appropriate.
- Assumptions and Constraints
|DoDAF Viewpoint Matrix|
- The DoDAF descriptions in this website are very generic and are mostly taken from the DoDAF Architecture Framework website. Make sure you visit the actual website for the most update information and a more thorough explanation of each viewpoint.
- DoDAF Version 1.0, although outdated, has some good examples on how to construct AV’s, OV’s, and SV’s.
AcqLinks and References:
-  DoDAF Architecture Framework Version 2.02
- DoD Architecture Framework Working Group Version 1.0, Volume 1: Definition and Guideline, 9 Feb 04 (Old Version)
- DoD Architecture Framework Version 1.0, Volume 2: Product Description, 9 Feb 04 (Old Version)
- Website: DoDAF Architecture Framework – DoD Deputy Chief Information Officer
- Website: DoDAF Architecture Framework Version 2.02