Chapter 36. DoDAF Tool

  1. Home
  2. Docs
  3. Chapter 36. DoDAF Tool
  4. 7. Services Viewpoint
  5. SvcV-1 – Services Context Description

SvcV-1 – Services Context Description

Download PDF

An SvcV-1 specifies the composition and interaction of resources.

The SV-1 links together the operational and services architecture models by depicting how resources are structured and interact to realize the logical architecture specified in an OV-2 Operational Resource Flow Description. A SvcV-1 may represent the realization of a requirement specified in an OV-2 Operational Resource Flow Description (i.e., in a “To-Be” Architectural Description), and so there may be many alternative SvcV models that could realize the operational requirement.

A Service Resource Flow is a simplified representation of a pathway or network pattern, usually depicted graphically as a connector (i.e., a line with possible amplifying information). The SvcV-1 depicts all Resource Flows between resources that are of interest. Note that Resource Flows between resources may be further specified in detail in the SvcV-2 Services Resource Flow Description model and the SvcV-6 Services Resource Flow Matrix.

Sub-services may be identified in SvcV-1 to any level (i.e., depth) of decomposition the architect sees fit. The SvcV-1 may also identify the Physical Assets (e.g., Platforms) at which Resources are deployed, and optionally overlay Operational Activities and Locations that utilize those Resources. In many cases, an operational activity and locations depicted in an OV-2 Operational Resource Flow Description may well be the logical representation of the resource that is shown in SvcV-1.


The intended usage of the SvcV-1 includes:

  • Definition of service concepts.
  • Definition of service options.
  • Service Resource Flow requirements capture.
  • Capability integration planning.
  • Service integration management.
  • Operational planning (capability and performer definition).

Product Description

A primary purpose of a SvcV-1 model is to show resource structure, i.e., identify the primary sub-services, performer and activities (functions) and their interactions. SvcV-1 contributes to the user understanding of the structural characteristics of the solution.

The physical resources contributing to a capability are either an organizational resource or a physical asset, i.e., a service cannot contribute alone (it must be hosted on a physical asset used by an organizational resource of both). Organizational aspects can now be shown on SvcV-1 (e.g., who uses a service). Resource structures may be identified in SvcV-1 to any level (i.e., depth) of decomposition the architect sees fit.

A SvcV-1 can optionally be annotated with Operational Activities and Locations originally specified in OV-2 Operational Resource Flow Description. In this way, traceability can be established from the logical OV structure to the physical Service Model structure. If a single SvcV-1 is not possible, the resource of interest should be decomposed into multiple SvcV-1 models.

Creating a Services Context Description

To create a Services Context Description (diagram):

  1. Click on Services Context Description in the Action Artifact area, and then select Create New Diagram.
  2. Type the diagram name and press Enter.
  3. A blank diagram is created and you can start constructing the view.
  4. Draw the resource types – ResourceArchitecture / System / CapabilityConfiguration / Organization / Person / Post / Responsibility / Project / NaturalResource / ResourceArtifact / Software / Technology.
  5. Draw the resource flows among the resource types by creating ResourceExchanges / Commands / Controls between them.

DoDAF Example: Services Context Description

DoDAF in Visual Paradigm

The DoDAF is brought to you by Visual Paradigm, a full-featured development platform. Visual Paradigm provides an easy-to-use, model-driven DoDAF tool that supports the development of DoDAF 2.02 views and models. You can create integrated DoDAF products and generate architectural documents that facilitate organizations to efficiently coordinate enterprise architecture initiatives.