DoD Architecture Framework Version 1.0, Volume 2 - AcqNotes.com

Hereafter in this document, the term architecture will be used as a shortened reference toarchitecture description. Occasionally the term architecture description is used for emphasis.1.2 PURPOSE AND INTENDED AUDIENCEThe purpose of this volume is to define, provide a purpose for, and describe in detail eachFramework product. This volume is organized with various readers in mind.For the manager who needs to lead architecture development projects and who may needto use an architecture to make acquisition, budgeting, or resourcing decisions, productdefinition and product purpose subsections are provided in each product section to:− Help these managers understand the architecture components or products− Provide an appreciation of the potential level of effort involved indeveloping architectures− Assist in discerning the potential uses of an architectureFor the architect and engineering team who need to develop architecture products forhigh-level decision makers for use in decision support analysis, a product detailed descriptionand an architecture data element table subsection are provided in each product section to:− Enable the architect and his team to identify products to be included in thearchitecture based on the architecture’s intended use (see Figure 2-2,Architecture Products by Use)− Determine architecture data needs− Identify sources for the architecture data− Analyze and relate the architecture data gathered− Compose the architecture data into architecture productsFor the architecture data modelers, tool developers, and engineers who are involvedwith implementing an architecture data repository to store and manipulate Frameworkarchitecture data elements, a CADM support subsection (including entity-relationships [ER]diagram) is provided in each product section.1-2