TRAK-Community

Title

SVp-03 Solution Resource Interaction to Function Mapping Viewpoint

Version

3

Date

20th January 2011

Overview

The SVp-03 - Solution Resource Interaction to Function Mapping Viewpoint is part of the TRAK Solution Perspective and one of the 21 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

 

Mandatory Tuples

Subject

• Resource performs Function

Interface Identification

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

• Resource - from/to (Resource Interaction) - Resource

AND

• connecting the Ports and adding the Interaction Element exchanged.

Note that this is the minimum for interface characterisation since the basic interface identification form can be used if only the Interaction Element is known:

{ EITHER if Interaction Element Known:

• Resource Interaction carries Interaction Element
• Interaction Element triggers Function

OR

if Interaction Element not known:

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

}

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

Covered by TRAK IPR and licenses

Optional Tuples

Universal

• Concern about Architecture Description Element
• Document traces to Architecture Description Element
• Requirement traces to Architecture Description Element
• Standard governs Architecture Description Element

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 Identifier	Function (of that Resource)	Resource Interaction Identifier	Justification
#R1	F1 ...	RI08 ...	F2
#R2	F2 ...	RI09 ...	F2

Covered by TRAK IPR and licenses

Views Needed to Construct

• SV-01 specified by the SVp-01 - master architecture view for Resource (Job, Physical, Organisation, Role, Software, System)
• SV-02 specified by the SVp-02 - master architecture view for Interaction Element, Port, Port Connection, Protocol, Resource Interaction
• SV-04 - specified by the SVp-04 - master architecture view for Function

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

• Resource must appear in SV-01
• Resource Interaction must appear on SV-02
• Function must appear in SV-04

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

• TRAK Enterprise Architecture Framework Viewpoints. http://trakviewpoints.sourceforge.net

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:

• Framework
  • Specification
• Viewpoint

Solution