11.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Tools and File Formats Used identifies the tool suite used to develop the architectureand file names and formats for the architecture and each product.Findings states the findings and re<strong>com</strong>mendations that have been developed based on thearchitecture effort. Examples of findings include identification of shortfalls, re<strong>com</strong>mendedsystem implementations, and opportunities for technology insertion.During the course of developing an architecture, several versions of this product may beproduced. An initial version may focus the effort and document its scope, the organizationsinvolved, and so forth. After other products within the architecture’s scope have been developedand verified, another version may be produced to document adjustments to the scope and to otherarchitecture aspects that may have been identified as a result of the architecture development.After the architecture has been used for its intended purpose, and the appropriate analysis hasbeen <strong>com</strong>pleted, yet another version may be produced to summarize these findings for the highleveldecision makers. In this version, the AV-1 product, along with a corresponding graphic inthe form of an OV-1 product, serve as the executive summary for the architecture. Figure 3-1shows a representative format for the AV-1 product.• <strong>Architecture</strong> Project Identification- Name- Architect- Organization Developing the <strong>Architecture</strong>- Assumptions and Constraints- Approval Authority- Date Completed- Level of Effort and Projected and Actual Costs to Develop the <strong>Architecture</strong>• Scope: <strong>Architecture</strong> View(s) and Products Identification- Views and Products Developed- Time Frames Addressed- Organizations Involved• Purpose and Viewpoint- Purpose, Analysis, Questions to be Answered by Analysis of the <strong>Architecture</strong>- From Whose Viewpoint the <strong>Architecture</strong> is Developed• Context- Mission- Doctrine, Goals, and Vision- Rules, Criteria, and Conventions Followed- Tasking for <strong>Architecture</strong> Project and Linkages to Other <strong>Architecture</strong>s• Tools and File Formats Used• Findings- Analysis Results- Re<strong>com</strong>mendationsFigure 3-1. Overview and Summary Information (AV-1) - Representative Format3.1.2 UML RepresentationThe Unified Modeling Language (UML) tool(s) used for analysis and design usuallyallow for the addition of documentation to annotate the model/architecture being designed.There is no specific UML product (diagram) that is equivalent to the AV-1 product.Documentation should be developed for AV-1, which can be input via a documentation field in aUML modeling tool, if desired.3-2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!