View TRAK:SVp-03 Solution Resource Interaction to Function Mapping Viewpoint

Title

SVp-03 Solution Resource Interaction to Function Mapping Viewpoint

Version

6

Date

8th December 2017

Overview

The SVp-03 - Solution Resource Interaction to Function Mapping Viewpoint is part of the TRAK Solution Perspective and one of the 24 TRAK Architecture Viewpoints.

The SVp-03 Solution Resource Interaction to Function Mapping Viewpoint provides a trace between every solution resource interaction and the function(s) that require the interaction.

The SVp-03 viewpoint is the specification for the TRAK SV-03 architecture view.

Stakeholders Addressed

  • Owner of Solution
  • Developer of Solution
  • Acquirer of Solution
  • Operator of Solution
  • Maintainer of Solution
  • Trainer of Solution
  • User of Solution

Covered by TRAK IPR and licenses

Concerns Addressed

Are there interactions/interfaces that cannot be justified by functional need? Do we have functions that cannot be realised because there isn’t an interchange?

Covered by TRAK IPR and licenses

 

Description

Maps resource interactions to functions for justification, completeness.

Covered by TRAK IPR and licenses

 

Declared Tuples

Subject

Interface Identification

Identifying the Resource Interaction between a pair of Resources requires 1 of the following tuples:

{{

}

OR

Interface Characterisation

{

}}

AND

{

}

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

Covered by TRAK IPR and licenses

Optional Tuples

Interface Characterisation

  • Resource exposes Port
  • Port Connection from/to Port
  • Port Connection exchanges Interaction Element
  • Interaction Element triggers Function
  • Function triggers Interaction Element
  • Port Connection realises Resource Interaction

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-03 view shall contain:

  • at least one Resource (by the subject of the view)
  • every Resource must be connected to at least one Function
  • at least one Resource Interaction (involving the subject Resource)
  • every Resource Interaction must be connected to at least one Function, if not then a Concern *
  • every Function must be connected to at least one Resource Interaction if not then a Concern *

* Note:  The purpose of the viewpoint is to identify unmapped resource interactions and unmatched functions. 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
                                     
  SV-03 Table or Matrix Form  
Resource IdentifierFunction (of that Resource)Resource Interaction IdentifierJustification
#R1F1 ...RI08 ...F2
#R2F2 ...RI09 ...F2

Covered by TRAK IPR and licenses

Views Needed to Construct

See Minimum Allowed View Sets

Covered by TRAK IPR and licenses

The SV-01 is the source for the definition of the solution structure. The SV-02 is the source for the definition of resource interactions between the solution structure elements. The SV-04 is the source for the definition of the functions of each of the solution structure elements.

Examples

Consistency Rules

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 http://trakviewpoints.svn.sourceforge.net/viewvc/trakviewpoints/trunk/?view=log

Comments

References

Other Frameworks

There are no equivalent views in DNDAF, DODAF, MODAF or the NATO Architecture Framework

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

Categories:

  • Solution
  •  

    © 2010 Eclectica Systems Ltd.