View MODAF:SV-5 Function to Opl Activity - Service Function Traceability Matrix View
Overview
The SV-5 Function to Operational Activity View is part of the MODAF System Viewpoint and one of the 47 MODAF views*.
Version & Date
Version 1.2.004.
+ = new at 1.2.004
The change history is derived from the definition of each MODAF view within the The MODAF System Viewpoint
viewpoint defining document from www.mod.uk/modaf.
Purpose
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.
Subject to Crown Copyright
Background
From The MODAF System Viewpoint (SV)
p29:
The SV-5 view depicts the mapping of functions (and optionally, the resources that provide them) to operational activities or service functions. For operational activities it thus identifies the transformation of an operational need into a purposeful action performed by a system or solution. For service functions it provides the link between the services used at the operational level and the specific functions provided by the resources supporting 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.
Subject to Crown Copyright
Description
From The MODAF System Viewpoint (SV)
p30:
The SV-5 Function to Operational Activity / System Function Traceability Matrix is a specification of the relationships between the set of operational activities / system functions applicable to an architecture and the set of functions applicable to that architecture.
The relationship between functions and operational activities / system functions can also be expected to be many-to-many (ie one activity / system function may be supported by multiple functions and one function may support multiple activities/system functions).
The SV-5 View is normally a tabular view of the relationship between functions and activities / system functions in the form of a simple matrix.
MODAF uses the term
operational activityin the OVs and the termfunctionin 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 ofwhatandhow; 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 signficant 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 is to be done.
Subject to Crown Copyright
Data Objects
From The MODAF System Viewpoint (SV)
p29:
The data in an SV-5 can include:
Full size:File:MODAF SV5 SystemFunctiontoOperationalActivityView mm.jpg
Subject to Crown Copyright
Presentation
From The MODAF System Viewpoint (SV)
p29:
- Tabulation
Configuration History
Comments
References
- The MODAF System Viewpoint (SV). 26th April 2010. https://www.mod.uk/DefenceInternet/AboutDefence/CorporatePublications/InformationManagement/MODAF/TheSystemViewpointsv.htm
Other Frameworks
See also:
- DNDAF::SV-5 Operational Activity to Systems Function Traceability Matrix Subview
- DODAF::SV-5a Operational Activity to Systems Function Traceability Matrix Model and DODAF::SV-5b Operational Activity to Systems Traceability Matrix Model (deprecated in favour of DODAF::SvcV-5 Operational Activity to Services Traceability Matrix Model)
- NAF::NSV-5 Systems Function to Operational Activity Traceability Matrix Subview
- TRAK::SV-05 Solution Function to Concept Activity Mapping View
Category:Framework -> View
Category:MODAF -> View
Category:Solution