HOPEX Aquila EN

FRAMEWORKS - HOPEX DoDAF V2 > System Viewpoint Models > SV-2 Systems Resource Flow Description

SV-2 Systems Resource Flow Description

SV-2 Description

SV-2 HOPEX Implementation

Application Deployment Hierarchy

System Deployment Architectures

Deployable Application Packages

Application System Deployment Architectures

SV-2 Diagrams

SV-2 Description

SV-2

SV-2 Systems Resource Flow Description

A description of Resource Flows exchanged between systems.

For a more detailed description see the DoDAF web site: SV-2: Systems Resource Flow Description.

The SV-2 model specifies the system resource flows that exist between systems and may also list the protocol stacks used in connections.

The purpose of this model is to define the connectivity requirements between nodes. This model is then used to estimate the requirements for physical routing and bandwidth. An SV-2 model provides a different viewpoint of information already specified in the OV-2, OV-3 and SV-1.

The SV-2 is useful when planning physical connections and routings between nodes. It is also intended to assist with the analysis of the connectivity between systems within or between nodes.

SV-2 HOPEX Implementation

System Interaction Scenarios describe communications between System objects. They enable to exchange flows involving contents.

Simple flows facilitate exchange of contents between resources. There is no need to go into the details with exchange contracts.

From the various objects present in this viewpoint you can create an application deployment architecture diagram. For more information, see SV-2 Diagrams.

Application Deployment Hierarchy

Displays the hierarchical description of deployable application packages and architectures.

System Deployment Architectures

A deployment architecture describes one possible configuration of the deployment of a system. It describes how the different deployable application packages are connected to each other and the technologies and communication protocols they use. A system can have multiple possible deployment architectures (Ex: stand-alone installation, horizontal or vertical deployment, etc.).

Deployable Application Packages

A deployable application package is a split of a system according to technical criteria. For example, it may be GUI, process and data. Each technical area is associated with one or several technologies. Several deployable system packages need to be deployed to get the system operational.

Application System Deployment Architectures

An application system deployment architecture describes one possible configuration of the deployment of the system of this application system. It describes which deployment architecture is chosen for each of the systems involved and the communication protocol they use to communicate with each other.

SV-2 Diagrams

From the various objects of this viewpoint you can create an Application Deployment Architecture Diagram.

This diagram enables to respresent:

• application deployment architectures

A deployment architecture describes one possible configuration of the deployment of a system. It describes how the different deployable application packages connected to each other and the technologies and communication protocols they use.

• the deployable data packages of the described application deployment architecture

A deployable data package is a split of a system allowing access to the data required for the operation of this system. Each deployable data package is associated to one or several technologies (Ex: Oracle 12, SQL Server 2012, Windows file system, etc.). It can allow access one of several data stores.

• the techniques used for communications.

A technical communication line represents a technical connection between application deployment architectures or areas through input to output communication ports. The output technical port of a technical area or architecture asks the input technical port of the other technical architecture or area to open the communication line.

The application system deployment architecture below presents the eCommerce application deployment architecture as well as the deployment architecture for the customer management micro-system. The technical communication line between these two components is based on https.

Example of an application system deployment architecture for "Purchasing Request Processing".