TRAK-Community

Title

SVp-02 Solution Resource Interaction Viewpoint

Version

9

Date

8th February 2011

Overview

The SVp-02 - Solution Resource Interaction Viewpoint is part of the TRAK Solution Perspective and one of the 21 TRAK Architecture Viewpoints.

The SVp-02 Solution Resource Interaction Viewpoint defines the content of the SV-02 architecture view that provides the means to identify and characterise interfaces and interactions within a solution. These interactions can be between any type of Resource i.e. System, Organisation, Job, Role, Physical, Software and be data, energy or materiel.

The SVp-02 viewpoint is the specification for the TRAK SV-02 Solution Resource Interaction architecture view.

Stakeholders Addressed

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

Covered by TRAK IPR and licenses

Concerns Addressed

How are resources connected together?

How are the organisations, jobs & roles connected?

Have the interactions/interfaces/exchanges been characterised?

Covered by TRAK IPR and licenses

Description

Describes and characterises resource interactions (energy, materiel, data) between solution resources.

Covered by TRAK IPR and licenses

Mandatory Metamodel Elements

Always at least [Interface Identification].

Note that not all theoretical combinations are likely or interesting from a systems engineering point of view.

Interface Identification

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

{

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

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

}

and may extend this to include,if known:

• Resource Interaction carries Interaction Element

Full size:File:SVp-02 mandatoryTuples identification.gif

Interface Characterisation

The other form builds on this to characterise the Resource Interaction between a pair of Resources:

[Interface Identification]+

At least a 2 of the following tuples to add Ports to the Resources to be characterised:

{

• Resource exposes Port

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

}

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:

{

• Port from Port Connection
• Port to Port Connection
• Port Connection exchanges Interaction Element
• Interaction Element has part Interaction Element

AND

• {Port Connection realises Resource Interaction
OR
• Port Connection uses Protocol
OR
• Port implements Protocol}

}

Full size:File:SVp-02 mandatoryTuples characterisation.gif

Covered by TRAK IPR and licenses

Optional Metamodel Elements

Context - Solution Realises Concept:

• Resource realises Node

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

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

[interface identification]

• at least 2 Resources connected by a Resource Interaction (one of the resources is the subject of the view)
• each Resource Interaction has a unique identifier
• every Item Exchange and Item must be typed (allowed values = Unknown, Data, Energy or Resource - see TRAK Metamodel document). Default= Unknown

[interface characterisation]

• at least 2 Resources ((one of the resources is the subject of the view)
• every Resource has at least 1 Port
• every Port has at least 1 Port Connection
• each Port Connection has a unique identifier
• every Port Connection has at least 1 Interaction Element
• every Interaction Element must be typed (allowed values = Unknown, Data, Energy or Resource - see TRAK Metamodel document). Default= Unknown - a possible concern in the architecture description.
• Resource Interaction realised by every Port Connection
• every Port Connection realises a Resource Interaction

Note:

1. interface identification must be completed before interface characterisation can begin
2. See also TRAK Bye Law BLV-4 in TRAK Architecture Framework document - views for each subject (system of interest)

Covered by TRAK IPR and licenses

 

Presentation

• block diagram (Resource, Port = block,  Resource Interaction, Port Connection, TRAK metamodel relationship = line with text label, identifier and direction indicator)
• table or matrix
  • column / row headings:
    • Resource Interaction identifier
    • Resource Interaction Type
    • Resource identifier (source)
    • Resource identifier (destination)
    • Resource Interaction description
    • Port Connection identifier
    • Port (source)
    • Port (destination)
    • Interaction Element(s)
    • Protocol(s)
    • Standard(s)

• N-squared diagram

  • Resource identifier (cells on diagonal)
  • Resource Interaction identifier - in cell(s) that form intersection(s) between a pair of Resources
  • Resource Interaction description - in cell(s) that form intersection(s) between a pair of Resources

block diagram - interface identification:

Note:The resource interactions are typed = Data. If this cannot be attached to the resource interaction(s) an accompanying list of typed resource interactions would be needed.

block diagram - interface characterisation:

Full size:File:SVp-02 examplePresentation characterisation.gif

Note: Assumes interface identification form exists

tabular form - interface characterisation:

                                                                   

  SV-02 Solution Resource Interaction -Table or Matrix Form   - Interface Characterisation  

Resource Interaction Identifier	Port Connection Identifier	Source Resource	Source Port	Dest. Resource	Dest. Port	Interaction Elements	Protocol(s)	Type
#RI01		R2		R7				Data
#RI02		R2		R13				Data

N-squared diagram form - interface characterisation:

                               

  SV-02 Solution Resource Interaction - N-Squared Diagram Form   - Interface Characterisation  

R2	#RI01 (Data)   + description	#RI02 (Data)   + description
	R7
		R13

Note that all Resources are on the diagonal and the connections are indicated by the content of the cell(s) that form the intersection(s).

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)

See Minimum Allowed View Sets.

Covered by TRAK IPR and licenses

Consistency Rules

• Resource must appear in SV-01
• IF { Role from/to (Resource Interaction} [Resource] (in SV-02) } THEN { Role extends to [Resource] (in SV-01) } }
• Topological Realisation of Node : IF {Node has Need (CV-01) } AND {Resource Interaction realises (same) Need (SV-02) } THEN {Resource realises Node} must be made on the SV-01
• {Resource Interaction from/to Resource pair in SV-02} must be consistent with (same) Resource performs Function triggers Interaction Element triggers Function performed by (second) Resource in SV-07}
• Interaction Element in {Resource Interaction from/to Resource carries Interaction Element (SV-02)} is same Interaction Element in {(same) Resource performs Function triggers Interaction Element triggers Function performed by (second) Resource (in SV-07)}

Further rules are applied through the TRAK Bye Laws

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

The SV-02 is the master architecture view for Interaction Element, Port, Port Connection, Protocol, Resource Interaction.

Note - the level of detail of the SV-02 view, whether identifying or characterising exchanges will, if a functional sequence is established using the SV-07, affect what is shown on a SV-03 Solution Resource Interaction to Function MappingViews within the architecture description.This is a because the Resource performs Function triggers Interaction Element triggers Function performed by (other) Resource on the SV-07 has to be consistent with the Resource Interaction between the two Resources. i.e. if Interaction Element are shown on the SV-02 then they will have to be shown on the SV-03 so that all Interaction Elements exchanged are linked to the Functions they support. If only Resource Interactions have been identified then the SV-03 will only show the Resource Interaction.

Covered by TRAK IPR and licenses

References

• TRAK Enterprise Architecture Framework Viewpoints. trakviewpoints.sourceforge.net
• TRAK Enterprise Architecture Framework Metamodel. trakmetamodel.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/SV-3/NSV-1/NSV-2/NSV-3 views together with exchanges at varying levels - there is no dedicated view of the solution resource interactions.

The nearest equivalents are:

• Interface aspects of DNDAF::SV-1 Systems Interface Description Subview and DNDAF::SV-2 Systems Communications Description Subview
• Interface aspects of DODAF::SV-1 Systems Interface Description Model (deprecated in favour of DODAF::SvcV-1 Services Context Description Model) and DODAF::SV-2 Systems Resource Flow Description Model (deprecated in favour of DODAF::SvcV-2 Services Resource Flow Description Model)
• Interface 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)
• Interface aspects of NAF::NSV-1 System Interface Description Subview

If an N-squared diagram is used then the nearest equivalent is the SV-3/NSV-3:

• DNDAF::SV-3 Systems-Systems Matrix Subview
• DODAF::SV-3 Systems - Systems Matrix Model (deprecated in favour of DODAF::SvcV-3a Systems - Services Matrix Model and DODAF::SvcV-3b Services - Services Matrix Model)
• MODAF::SV-3 Resource Interaction Matrix View
• NAF::NSV-3 Systems to Systems Matrix Subview

Alternatively data exchanges between systems are captured using the SV-6:

• DNDAF::SV-6 Systems Data Exchange Matrix Subview - automated exchanges only
• DODAF::SV-6 Systems Resource Flow Matrix Model (deprecated in favour of DODAF::SvcV-6 Services Resource Flow Matrix Model)
• MODAF::SV-06 Systems Data Exchange Matrix View
• NAF::NSV-6 Systems Data Exchange Matrix Subview - automated exchanges only

 

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

Categories:

• Framework
  • Specification
• Viewpoint

Solution