View TRAK:SVp-01 Solution Structure Viewpoint
Title
SVp-01:Solution Structure Viewpoint
Version
10
Date
3rd February 2011
Overview
The SVp-01 - Solution Structure Viewpoint is part of the TRAK Solution Perspective and one of the 21 TRAK Architecture Viewpoints.
The SVp-01 provides the means to describe solution structure in terms of parts, governance, membership, physical dependency, hosting of software and extent. ‘extent’ refers to the extent of a Role which can be used to indicate governance or jurisdiction scope over parts of the solution.
The SVp-01 viewpoint is the specification for the SV-01 Solution Structure View.
Stakeholders Addressed
- Owner of Solution
- Acquirer of Solution
- Developer of Solution
- Operator of Solution
- User of Solution
- Trainer of Solution
- Maintainer of Solution
- Disposer of Solution
Concerns Addressed
Full size:File:SVp 01 stakeholderConcerns.pdf
What does the solution consist of? Is it structured sensibly? What is the organisation structure / membership? How does responsibility (scope/jurisdiction) apply to the solution components?
Covered by TRAK IPR and licenses
Description
Describes solution structure in terms of parts, governance, membership, dependency and extent.
Covered by TRAK IPR and licenses
Mandatory Metamodel Tuples
Full size:File:SVp 01 fragment mandatoryTuples.jpg
Configuration
- Resource has part Resource (System, Physical, Software, Organisation, Job or Role)
- Physical physically depends on Physical
- Software hosted on Physical
- System is configured with Resource
Governance
- Job governs Job
- Organisation is member of Organisation
- Organisation governs Organisation
Role Extent
- Organisation plays Role
- Job plays Role
- Role extends to Resource (System, Physical, Software, Organisation, Job or Role)
Solution Realises ...
where Resource = System, Physical, Software, Organisation, Job or Role
Covered by TRAK IPR and licenses
Note: physically depends on has an attribute:
dependency type = ‘Unknown’, ‘Proximity’ or ‘Alignment’
which can be used to describe whether 2 things depend on each other in terms of location or, more specifically, an alignment.
Optional Metamodel Tuples
Covered by TRAK IPR and licenses
If any of these optional metamodel elements are added then the appropriate TRAK Master Architecture View must be provided.
Well-Formedness
A SV-01 view shall contain:
EITHER [configuration]
- at least the Resource (the subject of the view) connected to another Resource using is configured with or has part or hosted on or physically depends on
OR [governance]
- at least an Organisation or a Job (the subject of the view)
- that Organisation or Job connected to another Organisation or Job using governs/is member of or governs respectively
OR [role extent]
- at least 1 Organisation or Job (the subject of the view)
- the subject Organisation or Job connected to at least 1 Role (the subject role)
- the subject role connected to at least 1 System
Covered by TRAK IPR and licenses
Presentation
- block diagram (Resource = block, TRAK metamodel relationship = line with text label and direction indicator)
[configuration]
[governance]:
[role extent]:
Covered by TRAK IPR and licenses
Examples
See SV-01
Views Needed to Construct
- CV-01 specified by CVp-01 (if ‘... realises Node’ shown) - master architecture view for Node
Covered by TRAK IPR and licenses
Consistency Rules
- If the SV-01 is used to define the extents of system authority, manufacturer, design authority or independent safety authority using Resource plays Role extends to (different) Resource these must be consistent with the values of role-based attributes for System (system authority, design authority, manufacturer, independent safety authority) or Resource (design authority, manufacturer, independent safety authority).
- Functional Realisation of Node.: IF {Node conducts Concept Activity (CV-05)} AND {Resource performs Function realises (same) Operational Activity (SV-04 + SV-05) } THEN {Resource realises Node} must be made on the SV-01.
- Topological Realisation of Node : IF {Node has Need (CV-01) } AND {Resource Interaction realises (same) Need } THEN {Resource realises Node} must be made on the SV-01
If System is configured with Organisation is made in the SV-01:The Organisation that governs the Project cannot itself be part of the Solution since the former is part of the model of the business and the latter will be part of the model of the thing delivered or developed. The governing organisation might well provide the resource to deliver the project but it is a different organisation to that in the solution - it is important to keep these 2 models distinct.
- { organisation in Organisation governs Project}
NOT EQUAL
- { organisation IN
{
- (same) Project undertakes Project Activity delivers / removes (System is configured with Organisation)
OR
- (System is configured with Organisation) is necessary for Project Activity AND (same) Project undertakes Project Activity
OR
- (same) Project owns Milestone marks introduction of /marks removal of (System is configured with Organisation)
}
This also comes into play if Organisation owns Project is made in the PrV-01
Covered by TRAK IPR and licenses
Further rules are applied through the TRAK Bye Laws
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
The SV-01 is the master architecture view for Resource (Job, Organisation, Physical, Role, Software, System)
The SV-01 provides 3 areas of coverage:
- Describing organisational structure - governance, membership and roles as well as organisational breakdown.
- Describing the extent or jurisdiction of roles
- Describing classic system or product breakdown structure.
If you need to show the effect of time on responsibility extent use the PrV-03 Procurement Responsibility View.
Covered by TRAK IPR and licenses
References
- TRAK Enterprise Architecture Framework Viewpoints. trakviewpoints.sourceforge.net
Other Frameworks
There is no direct mapping onto DNDAF,DODAF, MODAF or NAF as the structural aspects of the solution are presented in their SV-1/SV-2/NOV-1/NOV-2 views together with exchanges at varying levels - there is no dedicated structural view of the solution.
The nearest equivalents are:
- Structural aspects of DNDAF::SV-1 Systems Interface Description Subview
- Structural aspects of DODAF::SV-1 Systems Interface Description Model (deprecated in favour of DODAF::SvcV-1 Services Context Description Model)
- Structural aspects of MODAF::SV-1 Resource Interaction Specification View and the MODAF::SV-2c System Connectivity Clusters View which shows how resources are organised (and covers exchanges)
- Structural aspects of NAF::NSV-1 System Interface Description Subview
Whilst in TRAK the organisational structure and communication between Roles and Jobs is covered using the SVp-01, other frameworks have dedicated architecture views:
- Organisation - Organisation structure is addressed by the DNDAF::OV-4a Organizational Relationships Chart Subview whereas Role - Organisation mapping and competence is addressed by the DNDAF::OV-4b Organization to Role/Skill Matrix Subview
- DODAF::OV-4 Organizational Relationships Chart Model
- MODAF::OV-4 - Organisational Relationships Chart View
- NAF::NOV-4 Organisational Relationship Chart Subview
Category:Framework -> Viewpoint
Category:Framework -> Specification
Category:Solution
Clip to Evernote
Bookmark this on Delicious
