SVp-02 Solution Resource Interaction

This page reproduces part of the SVp-02 Solution Resource Interaction architecture viewpoint definition from the specification - TRAK00001. TRAK. Architecture Framework. Viewpoints. The page content is therefore subject to the same GNU Free Documentation License terms and conditions - see https://www.gnu.org/licenses/fdl-1.3.html

Most of the content is produced from a model of TRAK produced using a different set of architecture viewpoints!

Version

The TRAK SVp-02 Solution Resource Interaction architecture viewpoint is one of 24 architecture viewpoints defined in TRAK00001. TRAK. Architecture Framework. Viewpoints - current release is dated 2024_07_10.

SVp-02 Solution Resource Interaction Architecture Viewpoint Configuration
Perspective	Viewpoint	View ID	Version	Modified
Solution	SVp-02	SV-02	14	2024-07-10

Summary

The TRAK SVp-02 Solution Resource Interaction architecture viewpoint defines the requirements for the TRAK SV-02 Solution Resource Interaction architecture view. This involves allowed content and minimum acceptable content ('well-formedness' criteria). The TRAK00001. TRAK. Architecture Framework. Viewpoints specification also defines consistency rules that apply to a set of architecture views (an Architecture Description).

The TRAK SVp-02 Solution Resource Interaction architecture viewpoint content is summarised under the following sections:

stakeholder concerns
description
allowed content
well-formedness criteria
presentation methods
examples
comments

The TRAK Architecture Viewpoints specification provides are complete definition not only of the SVp-02 Solution Resource Interaction architecture viewpoint but considerations for the architecture description formed from a set of architecture views.

Something needs fixing?

Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns.

Stakeholder Concerns

Stakeholder Concerns Addressed by the SVp-02 Solution Resource Interaction Architecture Viewpoint

The TRAK SVp-02 Solution Resource Interaction architecture viewpoint addresses the following concerns:

Do the solution interactions realise any conceptual exchange(s)?
Does the solution realise any concept?
Have the interactions / interfaces / exchanges been characterised?
How are resources connected together?
How are the organisations, jobs and roles connected?

Concerns addressed by all the TRAK architecture viewpoints.

Description

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

Allowed Content

TRAK architecture view content is defined in terms of triples - Node - connector - Node e.g. 'Resource Interaction carries Interaction Element' that form short statements about the thing(s) being described.

Example of a 'Resource Interaction carries Interaction Element' subject triple for the SV-02 Solution Resource Interaction Architecture View

'Resource Interaction carries Interaction Element' is a Statement or Assertion in a SV-02 Architecture View

The rationale for this is explained separately.

Subject Statements (Triples)

These are statements (triples) that describe the subject of the SV-02 Solution Resource Interaction architecture view. Specifically these statements address the concerns for this SVp-02 Solution Resource Interaction architecture viewpoint. These form the basis for the well-formedness section of the SVp-02 Solution Resource Interaction architecture viewpoint.

There are 18 possible subject statements in total which include 13 metamodel elements ( Interaction Element , Job , Need , Node , Organisation , Physical , Port , Port Connection , Protocol , Resource Interaction , Role , Software and System ).

The subject statements are split into 3 groups:

Interface Characterisation
Interface Identification
Realisation

Return to the top of the Solution Resource Interaction page.

Interface Characterisation

2 possible subject statements:

Port Connection uses Protocol
Port implements Protocol

Return to the top of the SV-02 subject statements (triples).

Interface Identification

13 possible subject statements:

Resource Interaction carries Interaction Element
Resource Interaction from Job
Resource Interaction from Organisation
Resource Interaction from Physical
Resource Interaction from Role
Resource Interaction from Software
Resource Interaction from System
Resource Interaction to Job
Resource Interaction to Organisation
Resource Interaction to Physical
Resource Interaction to Role
Resource Interaction to Software
Resource Interaction to System

Return to the top of the SV-02 subject statements (triples).

Realisation

3 possible subject statements:

Need for Node
Node has Need
Resource Interaction realises Need

Return to the top of the SV-02 subject statements (triples).

Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns..

Optional Statements (Triples)

These optional statements (triples) for the SV-02 Solution Resource Interaction architecture view provide useful context with respect to a subject or universally allowed statements involving the subject or object (start or finish) elements in the Subject Statements (triples).

Universal statements may be added to any TRAK architecture view and describe typical concepts such as compliance or traceability:

... traces to Argument, Contract, Requirement, Document or Standard
... satisfies Contract, Requirement, Document or Standard
Concern or Claim about ...
Contract, Requirement, Document or Standard governs ...

Example of a 'Standard governs Resource Interaction' optional triple for the SV-02 Solution Resource Interaction Architecture View

'Standard governs Resource Interaction' - an optional statement or assertion for the SV-02 Architecture View

These statements address the concerns of their respective architecture viewpoint and will have been created first on these other architecture views.

There are 175 possible statements which may be used to augment the SV-02 Solution Resource Interaction architecture view, split into 6 groups:

Context - Solution Realises Context
Universal - Applicable Requirements
Universal - Assurance
Universal - Concern Identified
Universal - Requirement Compliance
Universal - Traceability or Reference

Return to the top of the Solution Resource Interaction page.

Context - Solution Realises Context

6 additional context statements:

System is configured with Job
System is configured with Organisation
System is configured with Physical
System is configured with Role
System is configured with Software
System is configured with System

Return to the top of the SV-02 optional statements (triples).

Universal - Applicable Requirements

39 additional context statements:

Contract governs Interaction Element
Contract governs Job
Contract governs Need
Contract governs Node
Contract governs Organisation
Contract governs Physical
Contract governs Port
Contract governs Port Connection
Contract governs Protocol
Contract governs Resource Interaction
Contract governs Role
Contract governs Software
Contract governs System
Requirement governs Interaction Element
Requirement governs Job
Requirement governs Need
Requirement governs Node
Requirement governs Organisation
Requirement governs Physical
Requirement governs Port
Requirement governs Port Connection
Requirement governs Protocol
Requirement governs Resource Interaction
Requirement governs Role
Requirement governs Software
Requirement governs System
Standard governs Interaction Element
Standard governs Job
Standard governs Need
Standard governs Node
Standard governs Organisation
Standard governs Physical
Standard governs Port
Standard governs Port Connection
Standard governs Protocol
Standard governs Resource Interaction
Standard governs Role
Standard governs Software
Standard governs System

Return to the top of the SV-02 optional statements (triples).

Universal - Assurance

26 additional context statements:

Claim about Interaction Element
Claim about Job
Claim about Need
Claim about Node
Claim about Organisation
Claim about Physical
Claim about Port
Claim about Port Connection
Claim about Protocol
Claim about Resource Interaction
Claim about Role
Claim about Software
Claim about System
Interaction Element traces to Argument
Job traces to Argument
Need traces to Argument
Node traces to Argument
Organisation traces to Argument
Physical traces to Argument
Port Connection traces to Argument
Port traces to Argument
Protocol traces to Argument
Resource Interaction traces to Argument
Role traces to Argument
Software traces to Argument
System traces to Argument

Return to the top of the SV-02 optional statements (triples).

Universal - Concern Identified

13 additional context statements:

Concern about Interaction Element
Concern about Job
Concern about Need
Concern about Node
Concern about Organisation
Concern about Physical
Concern about Port
Concern about Port Connection
Concern about Protocol
Concern about Resource Interaction
Concern about Role
Concern about Software
Concern about System

Return to the top of the SV-02 optional statements (triples).

Universal - Requirement Compliance

39 additional context statements:

Interaction Element satisfies Contract
Interaction Element satisfies Requirement
Interaction Element satisfies Standard
Job satisfies Contract
Job satisfies Requirement
Job satisfies Standard
Need satisfies Contract
Need satisfies Requirement
Need satisfies Standard
Node satisfies Contract
Node satisfies Requirement
Node satisfies Standard
Organisation satisfies Contract
Organisation satisfies Requirement
Organisation satisfies Standard
Physical satisfies Contract
Physical satisfies Requirement
Physical satisfies Standard
Port Connection satisfies Contract
Port Connection satisfies Requirement
Port Connection satisfies Standard
Port satisfies Contract
Port satisfies Requirement
Port satisfies Standard
Protocol satisfies Contract
Protocol satisfies Requirement
Protocol satisfies Standard
Resource Interaction satisfies Contract
Resource Interaction satisfies Requirement
Resource Interaction satisfies Standard
Role satisfies Contract
Role satisfies Requirement
Role satisfies Standard
Software satisfies Contract
Software satisfies Requirement
Software satisfies Standard
System satisfies Contract
System satisfies Requirement
System satisfies Standard

Return to the top of the SV-02 optional statements (triples).

Universal - Traceability or Reference

52 additional context statements:

Interaction Element traces to Contract
Interaction Element traces to Document
Interaction Element traces to Requirement
Interaction Element traces to Standard
Job traces to Contract
Job traces to Document
Job traces to Requirement
Job traces to Standard
Need traces to Contract
Need traces to Document
Need traces to Requirement
Need traces to Standard
Node traces to Contract
Node traces to Document
Node traces to Requirement
Node traces to Standard
Organisation traces to Contract
Organisation traces to Document
Organisation traces to Requirement
Organisation traces to Standard
Physical traces to Contract
Physical traces to Document
Physical traces to Requirement
Physical traces to Standard
Port Connection traces to Contract
Port Connection traces to Document
Port Connection traces to Requirement
Port Connection traces to Standard
Port traces to Contract
Port traces to Document
Port traces to Requirement
Port traces to Standard
Protocol traces to Contract
Protocol traces to Document
Protocol traces to Requirement
Protocol traces to Standard
Resource Interaction traces to Contract
Resource Interaction traces to Document
Resource Interaction traces to Requirement
Resource Interaction traces to Standard
Role traces to Contract
Role traces to Document
Role traces to Requirement
Role traces to Standard
Software traces to Contract
Software traces to Document
Software traces to Requirement
Software traces to Standard
System traces to Contract
System traces to Document
System traces to Requirement
System traces to Standard

Return to the top of the SV-02 optional statements (triples).

Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns..

Well-Formedness Criteria

Well-formedness criteria define the minimum acceptable view content based on the subject statements (triples). These criteria are not yet represented within the model of TRAK. Please refer to the SVp-02 Solution Resource Interaction definition within the TRAK00001. TRAK. Architecture Framework. Viewpoints specification.

Presentation Methods

The SV-02 Solution Resource Interaction architecture view may use any of following means to the statements (triples):

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

Note that a textual presentation is acceptable for any TRAK architecture view.

Examples

Interface Identification Example of a SV-02 Solution Resource Interaction Architecture View - SV-02 Interface Identification Form Implemented using the UML

SV-02 Interface Identification Form Implemented using the UML

Note: This UML implementation uses the standard UML Ports, InformationFlows and nests Ports. This means that some relationships are hidden and this view is not wholly a graph.

The carried 'Demand_Health' is simply shown within the Resource Interaction label as a result of the default UML tool behaviour when picking InformationItems to be conveyed.

Interface Characterisation Example of a SV-02 Solution Resource Interaction Architecture View - SV-02 Implemented as SysML Internal Block Diagram

SV-02 Implemented as SysML Internal Block Diagram

Note: This SysML implementation uses the standard UML/SysML Ports, InformationFlows and nests Ports. This means that some relationships are hidden and this view is not wholly a graph.

The carried 'BIT Status Interaction Element' is simply shown within the Resource Interaction label ('{... BIT Status}') as a result of the default UML tool behaviour when picking InformationItems to be conveyed.

Comments

The SV-02 Solution Resource Interaction architecture view is the master source (origin) on which you first create the following elements or statements:

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 Mapping Views 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 Elements 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.

Neighbouring Architecture Views

The SV-02 Solution Resource Interaction architecture view content may overlap that of the following neighbouring architecture views:

Navigation & Website Tracker

Spotted an error or want to suggest something - create a ticket

Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns..