Search Results for: 2

The Standards Viewpoint (StdV) StdV-1 defines the technical, operational, and business standards, guidance, and policy applicable to the architecture being described. It also documents the policies and standards that apply to the operational or business context. The intended usage of the StdV-1 includes: Application of standards (informing project strategy). Standards compliance. Guide: DoDAF Architecture Framework […]

The PV-1 “Project Portfolio Relationships” represents an organizational perspective on programs, projects, portfolios, or initiatives. It 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

The PV-3 “Project to Capability Mapping” supports the acquisition and deployment processes, including the management of dependencies between projects and the integration of all relevant project and program elements to achieve a capability. It maps programs, projects, portfolios, or initiatives to capabilities to show how the specific elements help to achieve a capability. Programs, projects,

The Project Viewpoint (PV) describe how programs, projects, portfolios, or initiatives deliver capabilities and the organizations contributing to them and the dependencies between them. These models expand the usability of the DoDAF by including information about programs, projects, portfolios, or initiatives and relating that information to capabilities and other programs, projects, portfolios, or initiatives. This expands

  The physical architecture is the physical layout of a system and its components in a schema.  It refers to some  representation of the structure or organization of the physical elements of the system.  The physical architecture should be part of the Allocated and Product Baselines. SMC Systems Engineering Handbook Example – Page 25 The

The OV-6b “State Transition Description” is a graphical method of describing how an Operational Activity responds to various events by changing its state. The diagram represents the sets of events to which the Activities respond (by taking an action to move to a new state) as a function of its current state. Each transition specifies

The OV-6c “Event-Trace Description” provides a time-ordered examination of the Resource Flows as a result of a particular scenario. Each event-trace diagram should have an accompanying description that defines the particular scenario or situation. Operational Event/Trace Descriptions, sometimes called sequence diagrams, event scenarios, or timing diagrams, allow the tracing of actions in a scenario or

The OV-5a “Operational Activity Model” and the OV-5b describe the operations that are normally conducted in the course of achieving a mission or a business goal. It describes operational activities (or tasks); Input/Output flows between activities, and to/from activities that are outside the scope of the Architectural Description. Guide: DoDAF Architecture Framework Version 2.02 –

The OV-5a and the OV-5b “Operational Activity Model” describe the operations that are normally conducted in the course of achieving a mission or a business goal. It describes operational activities (or tasks); Input/Output flows between activities, and to/from activities that are outside the scope of the Architectural Description. Guide: DoDAF Architecture Framework Version 2.02 –

An OV-6a “Operational Rules Model” specifies operational or business rules that are constraints on the way that business is done in the enterprise. At a top-level, rules should at least embody the concepts of operations defined in OV-1 “High Level Operational Concept Graphic” and provide guidelines for the development and definition of more detailed rules