Appendix
Here are HOPEX features which are used across the different viewpoints.
About Scenarios
Scenario is a common concept which is used across the DoDAF viewpoints.
Scenarios enable to describe use cases or user stories. We recommend to use them when you need to understand how exchanges are performed.
 
Types of scenarios
Scenarios can apply to several layers of the enterprise architecture:
operational (OV-2)
*For more details on operational scenarios, see OV-2 Operational Resource Flow Description.
system (SV-10c)
*For more details on system scenarios, see SV-10c Systems Event-Trace Description.
service (SVcV-10c)
*For more details on application system flow scenarios, see SvcV-10c Services Event-Trace Description.
 
Layer
Viewpoint
Type of Scenario
Scenario subjects
Operational
OV-2, OV-3
Operational Scenario
Org-Unit
Operational Activity (optional)
System
SV-10c
System Flow Scenario
System
System Process (optional)
System Service
SVcV-10c
Application System Flow Scenario
Application System
Editing Scenarios
HOPEX offers different possibilities to build a scenario. From the pop-up menu of the scenario you can use :
an editor
the flow editor
*With the flow editor you start with the description of flows and needlines exchanged between participants.
the lifeline editor
With the lifeline editor you start with the description of participants in the scenario. Then you describe the exchanges.
the corresponding scenario diagram
About Catalogs in HOPEX DoDAF
Service Catalogs
Service catalogs are available in the different layers of the architecture.
 
Type of service catalog
Contents
Viewpoint
See:
Business Service Catalog
Business Capability
CV-7
Technical Service Catalog
Technical functionalities
SvcV-1
Information Service Catalog
Functionalities
SvcV-1
Hardware Service Catalog
Hardware functionalities
SvcV-1
Asset Catalogs
 
Type of asset catalog
Viewpoint
See:
Hardware Catalog
SV-8
Software Catalog
SV-8
Other
SV-8
Other Catalogs
 
Type of catalog
Viewpoint
See:
Position Type Catalog
SV-9 (Systems)
SvcV-9 (Services)
System Technology Catalog
SV-9 (Systems)
SvcV-9 (Services)
About Realization and Fulfillment
Realization and fulfillment need to be distinguised as follows:
Fulfillment refers to the provision of services or functionalities.
A particular system fulfills project management functionalities.
Realization refers to compliance to an operating model.
A particular system realizes a logical application or a business function. It conforms to the standard architecture of management project tools.
*In this example the logical application is "Standard Project Management System".
About Object Life
Object life represents development of a component of your repository as it is actually planned following analyses carried out.
The life of an object is a set of time periods representing the real calendar of object states. Setting the life of an object enables you to view the life of components though a Gantt chart.
Here are the Viewpoints where the object life concept is used:
About Owned and Imported Object Lists
When viewpoints display lists of objects, HOPEX DoDAF offers two different lists:
Owned objects
This list displays objects owned by the current enterprise.
Imported objects
This list displays objects which are not owned by the current enterprise. Still they are displayed here so that you could use them.