trakviewpoints project

TRAK SourceForge Projects

Definition

Implementation

TRAK Information

 

 

 

 

 

 

 

 

 

 

 

SVp-05 Solution Function to Concept Activity Mapping

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

SVp-05 Solution Function to Concept Activity Mapping Architecture Viewpoint Configuration
Perspective Viewpoint View ID Version Modified
Solution SVp-05 SV-05 7 2017-12-08

Summary

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

The TRAK Architecture Viewpoints specification provides are complete definition not only of the SVp-05 Solution Function to Concept Activity 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-05 Solution Function to Concept Activity Mapping Architecture Viewpoint are : Do the solution functions meet all of the concept activities?, Is there unwanted solution functionality?, . The stakeholders for the SVp-05 Solution Function to Concept Activity Mapping Architecture Viewpoint are : Acquirer (of Solution), Developer (of Concept), Developer (of Solution), Maintainer (of Solution), Operator (of Solution), Owner (of Concept), Owner (of Solution), Trainer (of Solution), User (of Solution), .

Stakeholder Concerns Addressed by the SVp-05 Solution Function to Concept Activity Mapping Architecture Viewpoint

The TRAK SVp-05 Solution Function to Concept Activity Mapping architecture viewpoint addresses the following concerns:

  • Do the solution functions meet all of the concept activities?
  • Is there unwanted solution functionality?

Concerns addressed by all the TRAK architecture viewpoints.

Description

Maps the solution functions (SV-04) back up to the logical concept activities (defined in the CV-05).

Allowed Content

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

Example of a 'Function realises Concept Activity' subject triple for the SV-05 Solution Function to Concept Activity Mapping Architecture View

'Function realises Concept Activity' is a Statement or Assertion in a SV-05 Architecture View

The rationale for this is explained separately.

Subject Statements (Triples)

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

There are 10 possible subject statements in total which include 9 metamodel elements ( Concept Activity , Function , Job , Node , Organisation , Physical , Role , Software and System ).

Return to the top of the Solution Function to Concept Activity Mapping page.

  • Concept Activity has part Concept Activity
  • Function has part Function
  • Function realises Concept Activity
  • Job performs Function
  • Node conducts Concept Activity
  • Organisation performs Function
  • Physical performs Function
  • Role performs Function
  • Software performs Function
  • System performs Function

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

Optional Statements (Triples)

These optional statements (triples) for the SV-05 Solution Function to Concept Activity 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 'Job satisfies Standard' optional triple for the SV-05 Solution Function to Concept Activity Mapping Architecture View

'Job satisfies Standard' - an optional statement or assertion for the SV-05 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 123 possible statements which may be used to augment the SV-05 Solution Function to Concept Activity Mapping architecture view, split into 6 groups:

Return to the top of the Solution Function to Concept Activity Mapping page.

Context

6 additional context statements:

  • Job realises Node
  • Organisation realises Node
  • Physical realises Node
  • Role realises Node
  • Software realises Node
  • System realises Node

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

Universal - Applicable Requirements

27 additional context statements:

  • Contract governs Concept Activity
  • Contract governs Function
  • Contract governs Job
  • Contract governs Node
  • Contract governs Organisation
  • Contract governs Physical
  • Contract governs Role
  • Contract governs Software
  • Contract governs System
  • Requirement governs Concept Activity
  • Requirement governs Function
  • Requirement governs Job
  • Requirement governs Node
  • Requirement governs Organisation
  • Requirement governs Physical
  • Requirement governs Role
  • Requirement governs Software
  • Requirement governs System
  • Standard governs Concept Activity
  • Standard governs Function
  • Standard governs Job
  • Standard governs Node
  • Standard governs Organisation
  • Standard governs Physical
  • Standard governs Role
  • Standard governs Software
  • Standard governs System

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

Universal - Assurance

18 additional context statements:

  • Claim about Concept Activity
  • Claim about Function
  • Claim about Job
  • Claim about Node
  • Claim about Organisation
  • Claim about Physical
  • Claim about Role
  • Claim about Software
  • Claim about System
  • Concept Activity traces to Argument
  • Function traces to Argument
  • Job traces to Argument
  • Node traces to Argument
  • Organisation traces to Argument
  • Physical traces to Argument
  • Role traces to Argument
  • Software traces to Argument
  • System traces to Argument

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

Universal - Concern Identified

9 additional context statements:

  • Concern about Concept Activity
  • Concern about Function
  • Concern about Job
  • Concern about Node
  • Concern about Organisation
  • Concern about Physical
  • Concern about Role
  • Concern about Software
  • Concern about System

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

Universal - Requirement Compliance

27 additional context statements:

  • Concept Activity satisfies Contract
  • Concept Activity satisfies Requirement
  • Concept Activity satisfies Standard
  • Function satisfies Contract
  • Function satisfies Requirement
  • Function satisfies Standard
  • Job satisfies Contract
  • Job satisfies Requirement
  • Job 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
  • 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-05 optional statements (triples).

Universal - Traceability or Reference

36 additional context statements:

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

Presentation Methods

The SV-05 Solution Function to Concept Activity 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-05 is not the origin for any node elements. The SV-05 is the origin for 'Function realises Concept Activity' tuple. The originating architecture views needed to construct the SV-05 are the CV-05 ('Node conducts Concept Activity') and the SV-04 ('Resource performs Function').

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

Neighbouring Architecture Views

The SV-05 Solution Function to Concept Activity 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..

The TRAK architecture viewpoints are subject to the terms of open source license: GNU Free Documentation License (Version 1.3, November 2008) at https://www.gnu.org/licenses/fdl-1.3.html.

Modification Date: 2024-12-21

Eclectica Systems Ltd