trakviewpoints project

TRAK SourceForge Projects

Definition

Implementation

TRAK Information

 

 

 

 

 

 

 

 

 

 

 

SVp-03 Solution Resource Interaction to Function Mapping

This page reproduces part of the SVp-03 Solution Resource Interaction to Function Mapping 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-03 Solution Resource Interaction to Function Mapping architecture viewpoint is one of 24 architecture viewpoints defined in TRAK00001. TRAK. Architecture Framework. Viewpoints - current release is dated 2024_07_10.

SVp-03 Solution Resource Interaction to Function Mapping Architecture Viewpoint Configuration
Perspective Viewpoint View ID Version Modified
Solution SVp-03 SV-03 7 2024-07-10

Summary

The TRAK SVp-03 Solution Resource Interaction to Function Mapping architecture viewpoint defines the requirements for the TRAK SV-03 Solution Resource Interaction to Function Mapping 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-03 Solution Resource Interaction to Function Mapping architecture viewpoint content is summarised under the following sections:

The TRAK Architecture Viewpoints specification provides are complete definition not only of the SVp-03 Solution Resource Interaction to Function Mapping 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

The stakeholder concerns addressed by the SVp-03 Solution Resource Interaction to Function Mapping Architecture Viewpoint are : 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?, . The stakeholders for the SVp-03 Solution Resource Interaction to Function Mapping Architecture Viewpoint are : Acquirer (of Solution), Developer (of Concept), Maintainer (of Solution), Operator (of Solution), Owner (of Concept), Trainer (of Solution), User (of Solution), .

Stakeholder Concerns Addressed by the SVp-03 Solution Resource Interaction to Function Mapping Architecture Viewpoint

The TRAK SVp-03 Solution Resource Interaction to Function Mapping architecture viewpoint addresses the following concerns:

  • 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?

Concerns addressed by all the TRAK architecture viewpoints.

Description

Maps resource interactions to functions for justification, completeness.

Allowed Content

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

Example of a 'Job performs Function' subject triple for the SV-03 Solution Resource Interaction to Function Mapping Architecture View

'Job performs Function' is a Statement or Assertion in a SV-03 Architecture View

The rationale for this is explained separately.

Subject Statements (Triples)

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

There are 19 possible subject statements in total which include 8 metamodel elements ( Function , Job , Organisation , Physical , Resource Interaction , Role , Software and System ).

Return to the top of the Solution Resource Interaction to Function Mapping page.

  • Job performs Function
  • Organisation performs Function
  • Physical performs Function
  • 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 supports Function
  • Resource Interaction to Job
  • Resource Interaction to Organisation
  • Resource Interaction to Physical
  • Resource Interaction to Role
  • Resource Interaction to Software
  • Resource Interaction to System
  • Role performs Function
  • Software performs Function
  • System performs Function

Return to the top of the SV-03 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-03 Solution Resource Interaction to Function Mapping 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:

Example of a 'Software traces to Contract' optional triple for the SV-03 Solution Resource Interaction to Function Mapping Architecture View

'Software traces to Contract' - an optional statement or assertion for the SV-03 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 116 possible statements which may be used to augment the SV-03 Solution Resource Interaction to Function Mapping architecture view, split into 6 groups:

Return to the top of the Solution Resource Interaction to Function Mapping page.

Interface Characterisation

12 additional context statements:

  • Function triggers Interaction Element
  • Interaction Element triggers Function
  • Job exposes Port
  • Organisation exposes Port
  • Physical exposes Port
  • Port Connection exchanges Interaction Element
  • Port Connection from Port
  • Port Connection realises Resource Interaction
  • Port Connection to Port
  • Role exposes Port
  • Software exposes Port
  • System exposes Port

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

Universal - Applicable Requirements

24 additional context statements:

  • Contract governs Function
  • Contract governs Job
  • Contract governs Organisation
  • Contract governs Physical
  • Contract governs Resource Interaction
  • Contract governs Role
  • Contract governs Software
  • Contract governs System
  • Requirement governs Function
  • Requirement governs Job
  • Requirement governs Organisation
  • Requirement governs Physical
  • Requirement governs Resource Interaction
  • Requirement governs Role
  • Requirement governs Software
  • Requirement governs System
  • Standard governs Function
  • Standard governs Job
  • Standard governs Organisation
  • Standard governs Physical
  • Standard governs Resource Interaction
  • Standard governs Role
  • Standard governs Software
  • Standard governs System

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

Universal - Assurance

16 additional context statements:

  • Claim about Function
  • Claim about Job
  • Claim about Organisation
  • Claim about Physical
  • Claim about Resource Interaction
  • Claim about Role
  • Claim about Software
  • Claim about System
  • Function traces to Argument
  • Job traces to Argument
  • Organisation traces to Argument
  • Physical 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-03 optional statements (triples).

Universal - Concern Identified

8 additional context statements:

  • Concern about Function
  • Concern about Job
  • Concern about Organisation
  • Concern about Physical
  • Concern about Resource Interaction
  • Concern about Role
  • Concern about Software
  • Concern about System

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

Universal - Requirement Compliance

24 additional context statements:

  • Function satisfies Contract
  • Function satisfies Requirement
  • Function satisfies Standard
  • Job satisfies Contract
  • Job satisfies Requirement
  • Job satisfies Standard
  • Organisation satisfies Contract
  • Organisation satisfies Requirement
  • Organisation satisfies Standard
  • Physical satisfies Contract
  • Physical satisfies Requirement
  • Physical 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-03 optional statements (triples).

Universal - Traceability or Reference

32 additional context statements:

  • Function traces to Contract
  • Function traces to Document
  • Function traces to Requirement
  • Function traces to Standard
  • Job traces to Contract
  • Job traces to Document
  • Job traces to Requirement
  • Job 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
  • 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-03 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-03 Solution Resource Interaction to Function Mapping definition within the TRAK00001. TRAK. Architecture Framework. Viewpoints specification.

Presentation Methods

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

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

Comments

The SV-03 is not the origin for any node elements. The SV-03 is the origin for 'Resource Interaction supports Function' tuple. The originating architecture views needed to construct the SV-03 are the SV-04 ('Resource performs Function') and the SV-02 ('Resource Interaction from Resource', 'Resource Interaction to Resource').

Any unmapped Function or Resource Interaction elements should be identified as a concern using 'Concern about Function' or 'Concern about Resource Interaction' respectively.

Neighbouring Architecture Views

The SV-03 Solution Resource Interaction to Function Mapping architecture view content may overlap that of the following neighbouring architecture views:

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

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

Modification Date: 2024-09-12

Eclectica Systems Ltd