View TRAK:SVp-05 Solution Function to Concept Activity Mapping Viewpoint
Title
SVp-05 - Solution Function to Concept Activity Mapping Viewpoint
Version
7
Date
8th December 2017
Overview
The SVp-05 Solution Function to Concept Activity Mapping Viewpoint is part of the TRAK Solution Perspective and one of the 24 TRAK Architecture Viewpoints.
The SVp-05 provides the means to map functions from parts of the solution to the implementation-free concept activities. In doing so it provides a) justification for the solution functions b) ensures that there is nothing behavioural in the concept perspective that isn’t addressed within the solution and c) ensures that there is no unwanted functionality in the solution.
The SVp-05 architecture viewpoint is the specification for the TRAK::SV-05 Solution Function to Concept Activity Mapping architecture view.
Stakeholders Addressed
- Owner of Concept
- Developer of Concept
- Maintainer of Concept
- Operator of Concept
- Disposer of Concept
- Trainer of Concept
- User of Concept
- Owner of Solution
- Acquirer of Solution
- Developer of Solution
- Operator of Solution
- Maintainer of Solution
- Trainer of Solution
- User of Solution
Covered by TRAK IPR and licenses
Concerns Addressed
Do the solution functions meet all of the concept activities? Is there unwanted solution functionality?
Covered by TRAK IPR and licenses
Description
Maps the solution functions (SV-04) back up to the concept activities (defined in the CV-05).
Covered by TRAK IPR and licenses
Declared Tuples
Defining the Solution Function
- Resource performs Function
where Resource = System, Physical, Software, Organisation, Job or Role
Defining the Concept Activity
- Node conducts Concept Activity
- Concept Activity has part Concept Activity
Mapping the Solution to the Concept
- Function realises Concept Activity
Covered by TRAK IPR and licenses
Optional Tuples
Context - Concept Implementation
- Resource realises Node
where Resource = System, Physical, Software, Organisation, Job or Role
Universal
- Architecture Description Element satisfies Contract
- Architecture Description Element satisfies Requirement
- Architecture Description Element satisfies Standard
- Architecture Description Element traces to Argument
- Architecture Description Element traces to Document
- Claim about Architecture Description Element
- Concern about Architecture Description Element
- Contract governs Architecture Description Element
- Document traces to Architecture Description Element
- Requirement traces to Architecture Description Element
- Requirement governs Architecture Description Element
- Standard governs Architecture Description Element
If any of these optional metamodel elements are added then the appropriate TRAK Master Architecture View must be provided.
Covered by TRAK IPR and licenses
Well-Formedness
A SV-05 view shall contain:
- at least one Resource (the subject of the view)
- every Resource must be connected to at least one Function
- at least one Node
- every Node must be connected to at least one Concept Activity
- every Concept Activity must be connected to at least one Function, if not then a Concern *
- every Function must be connected to at least one Concept Activity, if not then a Concern *
* Note: The purpose of the viewpoint is to identify unmapped functions and unmatched concept activities. Unmapped items are to be flagged by connecting to a Concern identifying this concern and reported on in the MV-02. As items are mapped on this view they are disconnected from the Concern.
Covered by TRAK IPR and licenses
Presentation
- table or matrix
- block diagram (Node, Concept Activity, Resource, Function = block, TRAK relationship = line with text label and direction indicator)
Table or matrix:
SV-05 Solution Function to Concept Activity Mapping View -Table or Matrix Form Node Concept Activity Function Resource Description #N1 #CA_02 (missing) (missing) Concern - no Function identified to realise Concept Activity #N1 #CA_01 #F_02 #R6 mmm sss jj #N1 #CA_01 #F_03 #R9 mmm sss jj (missing) (missing) #F_04 #R9 Concern - is Function needed?
block diagram:
Full size:File:SV-05 examplePresentation.gif
Covered by TRAK IPR and licenses
Examples
Views Needed to Construct
- SV-01 (specified by the SVp-01 Solution Structure Viewpoint) - master architecture view for Resource (Job, Physical, Organisation, Role, Software, System)
- SV-04 (specified by the SVp-04 Solution Function Viewpoint) - master architecture view for Function.
- CV-01 (specified by the CVp-01 Concept Need Viewpoint) - master architecture view for Need.
- CV-05 (specified by the CVp-05 Concept Activity Viewpoint) - master architecture view for Concept Activity.
Covered by TRAK IPR and licenses
The SV-01 is the source for the definition of the solution structure Resource. The SV-04 is the source for the definition of the functions of each of the solution structure elements Function. The CV-05 is the source definition of the logical activities Concept Activity that the solution is implementing or realising.
Consistency Rules
- Resource must appear in SV-01
- any Node must appear in CV-01
- every Node conducts Concept Activity must appear in CV-05
- every Resource performs Function must appear in SV-04
- every Resource-performs-Function-realises-Concept Activity must be consistent with Resource-realises-Node in SV-01
- Functional Realisation of Node.: IF {Node conducts Concept Activity (CV-05)} AND {Resource performs Function realises (same) Concept Activity (SV-04 + SV-05) } THEN {Resource realises Node} must be made on the SV-01.
Covered by TRAK IPR and licenses
Configuration History
The TRAK Viewpoints project on Sourceforge (trakviewpoints.sourceforge.net) maintains a version-controlled repository. The change record is at trakviewpoints.svn.sourceforge.net/viewvc/trakviewpoints/trunk/?view=log
Comments
References
- TRAK Enterprise Architecture Framework Viewpoints. trakviewpoints.sourceforge.net
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)
- MODAF::MODAF:SV-5 Function to Operational Activity/Service Function Traceability Matrix View
- NAF::NSV-5 Systems Function to Operational Activity Traceability Matrix Subview
References
Category:Framework -> Viewpoint
Category:Framework -> Specification
Category:Solution
Clip to Evernote
Bookmark this on Delicious
