• DODAF Home 
• Background 
• Architectural Development 
• Meta Model 
  • Conceptual 
  • Logical 
  • PES 
  • IDEAS Foundation Ontology 
• Viewpoints & Models
  • All Viewpoint 
  • Capability Viewpoint 
  • Data and Information Viewpoint 
  • Operational Viewpoint 
  • Project Viewpoint 
  • Services Viewpoint 
  • Standards Viewpoint 
  • Systems Viewpoint 
  • Models 
  • Model Categories
  • Levels of Architecture
  • Architecture Interrogatives 
  • Architecture Modeling Primitives
  • Mapping to DM2 
• Presentation Techniques
  • Composite Views 
  • Fusion Views 
  • Reference Models 
• DODAF-DM2 Configuration Management
• Related Links 
• Acronyms List and Glossary of Terms 
• Site Map 
• Archives

DoDAF Viewpoints and Models

Project Viewpoint

PV-1: Project Portfolio Relationships

The PV-1 represents an organizational perspective on programs, projects, portfolios, or initiatives.

The PV-1 enables the user to model the organizational structures needed to manage programs, projects, portfolios, or initiatives. It shows dependency relationships between the actual organizations that own the programs, projects, portfolios, or initiatives. This model could be used to represent organizational relationships associated with transformation initiatives along with those who are responsible for managing programs, projects, and portfolios. The PV-1 provides a means of analyzing the main dependencies between acquisition elements or transformation elements.

The intended usage of the PV-1 includes, but is not limited to:

• Program management (specified acquisition program structure).
• Project organization.
• Cross-cutting initiatives to be tracked across portfolios.

Detailed Description:

The PV-1 describes how acquisition projects are grouped in organizational terms as a coherent portfolio of acquisition programs or projects, or initiatives related to several portfolios. The PV-1 provides a way of describing the organizational relationships between multiple acquisition projects or portfolios, each of which are responsible for delivering individual systems or capabilities. By definition, this model covers acquisition portfolios or programs consisting of multiple projects and is generally not for an individual project. In essence, PV-1 is an organizational breakdown consisting of actual organizations (see OV-4 Organizational Relationships Chart model). The model is strongly linked with the CV-4 Capability Dependencies model which shows capability groupings and dependencies.

The PV-1 is hierarchical in nature. Higher-level groupings of projects (the organizations that own these projects) form acquisition programs or initiatives.

The intent of a PV-1 is to show:

• All of the acquisition projects delivering services, systems, or SoS within the acquisition programs under consideration.
• Cross-cutting initiatives to be tracked across portfolios.
• Other services, systems, and SoS which may have a bearing on the architecture.
• How the services or systems will be best integrated into an acquisition program.
• The nesting of acquisition programs to form a hierarchy.

A PV-1 is specific to a particular point in the project lifecycle. This may change through time, i.e., the projects may change as new services, systems and capabilities are introduced into the acquisition program. Hence, it is possible that an acquisition program could have more than one PV-1, each showing how the acquisition projects are arranged for relevant periods of time. This is achieved by tying the PV-1 model to a capability phase in the CV-3 Capability Dependencies model.

PV-1: Project Portfolio Relationships

PV-2: Project Timelines

PV-3: Project to Capability Mapping