View TRAK:SVp-01 Solution Structure Viewpoint

Title

TRAK_logo_60.jpgSVp-01:Solution Structure Viewpoint

Version

16

Date

31st January 2018

Overview

The SVp-01 - Solution Structure Viewpoint is part of the TRAK Solution Perspective and one of the 24 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

SVp-01_stakeholderConcerns_430.jpg

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

Declared Tuples

Configuration

  • Resource has part Resource (System, Physical, Software, Organisation, Job or Role)
  • Physical physically depends on Physical
  • Software hosted on Physical
  • Physical contains System
  • Physical contains Physical
  • Physical is attached to Physical
  • Physical physically supports Physical
  • System is configured with Resource

Governance

  • Job governs Job
  • Organisation is member of Organisation
  • Organisation governs Organisation

Role Extent

Solution Realises ...

where Resource = System, Physical, Software, Organisation, Job or Role

  • Organisation realises Enterprise
  • System realises Capability
  • 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 Tuples

    Universal:

    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 contains (as permitted by the metamodel)

    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]

    SV-01example_configuration.gif

    [governance]:

    SV-01example_governance.gif

    [role extent]:

    SV-01example_roleExtent.gif

    Covered by TRAK IPR and licenses

    Examples

    See SV-01

    Views Needed to Construct

    See Minimum Allowed View Sets

    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

    {

    OR

    OR

    }

    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:

    1. Describing organisational structure - governance, membership and roles as well as organisational breakdown.
    2. Describing the extent or jurisdiction of roles
    3. 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

    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:

    Whilst in TRAK the organisational structure and communication between Roles and Jobs is covered using the SVp-01, other frameworks have dedicated architecture views:


    Category:Framework -> Viewpoint
    Category:Framework -> Specification
    Category:Solution

    Categories:

  • Solution
  •  

    © 2010 Eclectica Systems Ltd.