HOPEX DoDAF2 (EN) : DoDAF 2.0 System Viewpoint Models : SV-1 Systems Interface Description
   
SV-1 Systems Interface Description
 
Creating Capability Configurations
The SV-1 Report Template
The SV-1 Application Composition Hierarchy Chapter
The SV-1 Application Specialization Hierarchy Chapter
The SV-1 Application Generalization Hierarchy Chapter
The SV-1 Application Dictionary Chapter
The SV-1 Application Exchange Balance Chapter
The SV-1 Artifact Composition Hierarchy Chapter
The SV-1 Artifact Specialization Hierarchy Chapter
The SV-1 Artifact Generalization Hierarchy Chapter
The SV-1 Artifact Dictionary Chapter
The SV-1 Artifact Exchange Balance Chapter
The SV-1 Resource Architecture Composition Hierarchy Chapter
The SV-1 Resource Architecture Specialization Hierarchy Chapter
The SV-1 Resource Architecture Generalization Hierarchy Chapter
The SV-1 Resource Architecture Dictionary Chapter
The SV-1 Resource Architecture Exchange Balance Chapter
The SV-1 System Exchange Chapter
The SV-1 System Exchange Compliance Chapter
The purpose of the System Interface Description is to illustrate which systems collaborate, and in what way they do so, to support the operational domain’s information and information exchange needs as defined in the Operational View; most notably in OV-2 and OV-3.
SV-1 links together the Operational Viewpoint and the System Viewpoint by depicting which systems and system connections realize which information exchanges. A system is defined as any organized assembly of resources and procedures united and regulated by interactions or interdependences to accomplish a set of specific functions. The term system in the System Viewpoint is used to denote software intensive systems (Federation of Systems (FoS), System of Systems (SoS), subsystems, and system components) and can include web services, network components and other hardware components, such as routers, satellites and network segments.
A system’s services are accessed through the system’s interfaces. Generally, an interface is a contract between the providers and consumers of (system) services. With software intensive systems, this contract is a declaration of a coherent set of public system functionalities. The system’s interfaces specify the system’s behaviour without specifying implementation aspects. An SV-1 connection between system interfaces is the systems representation of an OV-2 needline or OV-3 information exchange. A single needline or information exchange may translate into multiple connections between system interfaces.
An SV-1 documents:
Systems and their interfaces
System use dependencies between interfaces
System collaborations (systems interacting with each other through their interfaces)
Distributions of software systems to hardware systems
Connections between hardware systems
Patterns (optional); standard system collaborations that have been proven to be sound solutions to known problems).