HOPEX Aquila EN

FRAMEWORKS - HOPEX DoDAF V2 > System Viewpoint Models > SV-1 Systems Interface Description > SV-1 HOPEX Implementation

SV-1 HOPEX Implementation

The SV-1 lists object types used for systems interface description.

System Hierarchy

This tile displays the hierarchical description of systems, application systems and hardware.

Flow Scenarios and Environments

This tile enables you to access all the scenarios available in SV-6.

Several tabs offer you to access:

• application system flow environments

• scenarios of application system flows

• scenarios of systems flows

• scenarios of system of resources

• system flow environments

For more information, see SV-6 Systems Data Exchange Matrix.

Application Systems

An application system is an assembly of other application systems, systems and end users, in order to realize one or more functionalities (e.g.Payroll System).

It can be decomposed (which is not the case of systems). It can be deployed through the deployment of the systems.

To define application systems, see SV-1 Defining Application Systems.

It is possible to design the environment of an application system. See Application System Environments.

Application System Environments

An application system environment presents an application system use context. It describes the interactions, between the application system and its external partners, which enables it to fulfill its mission and ensure the expected functionalities.

It shows how all application systems are used.

System users can be of the following types:

• organization (for example the Accounting department)

• position type (for example, sales representative)

It shows interactions between system users and partners.

Systems

A system is the combination of physical and organizational assets configured to supply a capability.

It is not possible to draw the environment of a system in HOPEX DoDAF. You need HOPEX IT Architecture for this. See the corresponding documentation.

Several types of diagrams are available for systems. See SV1- Defining Systems.

Exchange contracts

An exchange contract is a model of a contract between organizational entities. This contract is described by exchanges between an initiator role and one or several contributor roles.

For more information, see the corresponding documentation in HOPEX IT Architecture, section Describing information exchanges.

There are different types of exchange contracts:

• system exchange contracts

• business exchange contracts

• infrastructure exchange contracts

An exchange contract diagram displays the following objects:

• An exchange use represents the usage of an exchange in another exchange contract.

• An exchange contract use represents the usage of an exchange contract in another exchange contract.

Facilities

A facility is a model of location of interest for the enterprise. Examples: Data Center, Factory, Outlet.

Hardware

Hardware consists of non-IT equipment.

Non-IT Hardware can embed Computers. Together with their embedded computers, they provide information and IS services. Examples: Connected Truck with Delivery Calendar App, Connected Drone with Online Payment App.

Hardware device can also provide hardware functionalities. Example:- Connected fridge providing ordering functionalities and of course a freezing hardware functionality, connected drones fly and provide Online Payment.

IoT Devices

An IoT Device is both a hardware device and a computing device which provides combined hardware and information services to the users using it directly. As a hardware device, it embeds sensors - e.g. accelerometer - which provide data to the embedded computing device. As a computing device, it can host data stores or run systems.

Examples:

• on-line surveillance video camera with live IP video feed

• connected weighting scale with weight history management

IT Devices

An IT Device is a computing device which provides end-users with a service. This computing device can host data stores or run systems. Examples: workstation, laptop computer, smart phone.

IT Infrastructures

An IT Infrastructure consists of several connected IT Devices (IT Technical Devices or Computing Devices) and IT Networks.

IT Networks

An IT Network is an assembly of IT Technical Devices (e.g. routers, switches, firewalls) enabling remote communications between IT Devices (e.g. IT Servers). An IT Network may breakdown into sub-networks.

IT Peripherical Devices

An IT Peripheral Device can host and run Software Technology. Together with its hosted Software Technologies, it provides Technical Services. Examples:- Wifi Access Point, Firewall, Router, Switch, Printer, Hard Drive, etc.

IT Servers

An IT Server is a computing device which provides a service to the users connected to it via an IT network. This computing device can host data stores or run systems (applications).

Resource Architecture Environments

A resource architecture environment presents a resource architecture use context. It describes the service interactions, between the resource architecture and its external partners, which allows it to fulfill its mission and ensure the expected functionalities.

Resource Architectures

A resource architecture is the combination of physical and organizational assets configured to supply a capability.

You can create a resource architecture assembly diagram.

For more information, see the corresponding documentation in HOPEX IT Architecture. Search the following section: Adding a Resource Architecture

Resource Configurations

A Resource Configuration is a set of physical and human resources configured to provide a Business Capability. Example: Soldier with its communication device