• 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
• IDEAS 
• Related Links 
• Acronyms List and Glossary of Terms 
• Site Map 
• Archives

DoDAF Viewpoints and Models

Services Viewpoint

SvcV-2: Services Resource Flow Description

A SvcV-2 specifies the Resource Flows between Services and may also list the protocol stacks used in connections.

A SvcV-2 DoDAF-described Model is used to give a precise specification of a connection between Services. This may be an existing connection or a specification of a connection that is to be made for a future connection.

The intended usage of the SvcV-2 includes:

• Resource Flow specification.

Detailed Description:

For a network data service, a SvcV-2 comprises Services, their ports, and the Service Resource Flows between those ports. The SvcV-2 may also be used to describe non-IT type services such as Search and Rescue. The architect may choose to create a diagram for each Service Resource Flow and the producing Service, each Service Resource Flow and consuming Service, or to show all the Service Resource Flows on one diagram, if this is possible.

Each SvcV-2 model can show:

• Which ports are connected.
• The producing Services that the ports belong to.
• The Services that the Service Resource Flows are consumed by.
• The definition of the Service Resource Flow in terms of the physical/logical connectivity and any protocols that are used in the connection.

Note that networks are represented as Services. The architect may choose to show other Services being components of the network, i.e., if they are part of the network infrastructure.

Any protocol referred to in a SvcV-2 diagram needs be defined in the StdV-1 Standards Profile.

SvcV-1 Services Context Description

SvcV-2 Services Resource Flow Description

SvcV-3a Systems-Services Matrix

SvcV-3b Services-Services Matrix

SvcV-4 Services Functionality Description

SvcV-5 Operational Activity to Services Traceability Matrix

SvcV-6 Services Resource Flow Matrix

SvcV-7 Services Measures Matrix

SvcV-8 Services Evolution Description

SvcV-9 Services Technology & Skills Forecast

SvcV-10abc Introduction to SvcV-10a, SvcV-10b and SvcV-10c

SvcV-10a Services Rules Model

SvcV-10b Services State Transition Description

SvcV-10c Services Event-Trace Description