SV-5 – Function to Operational Activity / Service Function Traceability Matrix

The SV-5 provides two alternate views:

• The mapping between functions described in SV-4, Functionality Description, and the operational activities in OV-5, Operational Activities Model.
• The mapping between functions in SV-4 and the service functions in SOV-5, Service Functionality.

The SV-5 depicts the mapping of functions (and optionally, the resources that perform them) to operational activities or service functions. It therefore identifies the transformation of an operational need into a purposeful action performed by a resource. For service functions, SV-5 provides the link between the services used at the operational level and the specific functions provided by the resources that implement the services.

During requirements definition, SV-5 plays a particularly important role in tracing the architectural elements associated with system requirements to those associated with user requirements.

Usage

The intended usage of the SV-5 includes:

• Tracing functional system requirements to user requirements.
• Tracing solution options to requirements.
• Identification of overlaps.

Product Description

The SV-5 is a specification of the mapping between the set of operational activities or service functions to the functions that realise them.

MODAF uses the term ‘operational activity’ in the OVs and the term ‘function’ in the SVs to refer to essentially the same kind of thing, that is, both activities and functions are tasks that are performed, accept inputs, and develop outputs. The distinction between an operational activity and a function is a question of “what” and “how”; an operational activity is a specification of what is to be done, regardless of the mechanism used whereas a function specifies how a resource carries it out. For this reason, the SV-5 is a significant view, as it ties together the logical specification in the OV-5 with the physical specification of the SV-4. This logic can also be applied to services where the service functions are a specification of what functionality is to be delivered, specified independently of implementation.

The relationship between functions and operational activities or service may be many-to-many (i.e. one activity / service function may be supported by multiple functions and one function may support multiple activities / service functions).

Creating a Function to Operational Activity / Service Function Traceability Matrix

To create a Function to Operational Activity / Service Function Traceability Matrix:

1. Click on Function to Operational Activity / Service Function Traceability Matrix in the Action Artifact area, and then select Create New Diagram.
2. Type the diagram name and press Enter.
3. A blank diagram is created and you can start constructing the view. Reuse OperationalActivities / ServiceFunctions and Functions (recommended) through dragging and dropping them from the Model Explorer. Functions are defined in SV-4. ServiceFunctions are defined in SOV-5. OperationalActivities are defined in OV-5.
4. Trace Functions to ServiceFunctions with Implements.
5. Trace Functions to OperationalActivities with Implements.

MODAF in Visual Paradigm

The MODAF is brought to you by Visual Paradigm, a full-featured development platform. Visual Paradigm provides an easy-to-use, model-driven MODAF tool that supports the development of MODAF views and models. You can create integrated MODAF products and generate architectural documents that facilitate organizations to efficiently coordinate enterprise architecture initiatives.