TRAK Architecture ViewpointsSVp-07 Solution Sequence
This page reproduces part of the SVp-07 Solution Sequence 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-07 Solution Sequence architecture viewpoint is one of 24 architecture viewpoints defined in TRAK00001. TRAK. Architecture Framework. Viewpoints - current release is dated 2024_07_10.
| Perspective | Viewpoint | View ID | Version | Modified |
| Solution | SVp-07 | SV-07 | 13 | 2023-09-09 |
Summary
The TRAK SVp-07 Solution Sequence architecture viewpoint defines the requirements for the TRAK SV-07 Solution Sequence 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-07 Solution Sequence architecture viewpoint content is summarised under the following sections:
- stakeholder concerns
- description
- allowed content
- well-formedness criteria
- presentation methods
- comments
The TRAK Architecture Viewpoints specification provides are complete definition not only of the SVp-07 Solution Sequence architecture viewpoint but considerations for the architecture description formed from a set of architecture views.
Return to the Architecture Viewpoints list or Summary of Architecture Viewpoint Concerns.
Stakeholder Concerns
Stakeholder Concerns Addressed by the SVp-07 Solution Sequence Architecture Viewpoint
The TRAK SVp-07 Solution Sequence architecture viewpoint addresses the following concerns:
- In what order do things need to happen?
Description
Describes the order in which functions or events occur.
Allowed Content
TRAK architecture view content is defined in terms of triples - Node - connector - Node e.g. 'Software performs Function' that form short statements about the thing(s) being described.
'Software performs Function' is a Statement or Assertion in a SV-07 Architecture View
The rationale for this is explained separately.
Subject Statements (Triples)
These are statements (triples) that describe the subject of the SV-07 Solution Sequence architecture view. Specifically these statements address the concerns for this SVp-07 Solution Sequence architecture viewpoint. These form the basis for the well-formedness section of the SVp-07 Solution Sequence architecture viewpoint.
There are 23 possible subject statements in total which include 9 metamodel elements ( Function , Interaction Element , Job , Organisation , Physical , Resource Interaction , Role , Software and System ).
The subject statements are split into 2 groups:
Return to the top of the Solution Sequence page.
Functional Sequence
9 possible subject statements:
- Function precedes Function
- Function triggers Interaction Element
- Interaction Element triggers Function
- Job performs Function
- Organisation performs Function
- Physical performs Function
- Role performs Function
- Software performs Function
- System performs Function
Return to the top of the SV-07 subject statements (triples).
Interaction Sequence
14 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 precedes Resource Interaction
- 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-07 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-07 Solution Sequence 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 ...
'Role traces to Requirement' - an optional statement or assertion for the SV-07 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 131 possible statements which may be used to augment the SV-07 Solution Sequence architecture view, split into 6 groups:
- Context
- Universal - Applicable Requirements
- Universal - Assurance
- Universal - Concern Identified
- Universal - Requirement Compliance
- Universal - Traceability or Reference
Return to the top of the Solution Sequence page.
Context
14 additional context statements:
- Function has part Function
- Interaction Element has part Interaction Element
- Job plays Role
- Organisation has part Job
- Organisation has part Organisation
- Organisation is member of Organisation
- Organisation plays Role
- Software has part Software
- 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-07 optional statements (triples).
Universal - Applicable Requirements
27 additional context statements:
- Contract governs Function
- Contract governs Interaction Element
- 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 Interaction Element
- 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 Interaction Element
- 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-07 optional statements (triples).
Universal - Assurance
18 additional context statements:
- Claim about Function
- Claim about Interaction Element
- 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
- Interaction Element 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-07 optional statements (triples).
Universal - Concern Identified
9 additional context statements:
- Concern about Function
- Concern about Interaction Element
- 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-07 optional statements (triples).
Universal - Requirement Compliance
27 additional context statements:
- Function satisfies Contract
- Function satisfies Requirement
- Function satisfies Standard
- Interaction Element satisfies Contract
- Interaction Element satisfies Requirement
- Interaction Element 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-07 optional statements (triples).
Universal - Traceability or Reference
36 additional context statements:
- Function traces to Contract
- Function traces to Document
- Function traces to Requirement
- Function traces to Standard
- 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
- 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-07 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-07 Solution Sequence definition within the TRAK00001. TRAK. Architecture Framework. Viewpoints specification.
Presentation Methods
The SV-07 Solution Sequence architecture view may use any of following means to the statements (triples):
- communication diagram
- sequence diagram
Note that a textual presentation is acceptable for any TRAK architecture view.
Comments
The Interaction Sequence form requires 2 Resources because 'Function triggers Interaction Element' implies that there is another Resource with which that Interaction Element is exchanged.
Neighbouring Architecture Views
The SV-07 Solution Sequence architecture view content may overlap that of the following neighbouring architecture views:
- MV-02 Architecture Description Design Record
- MV-03 Requirements and Standards
- MV-04 Assurance
- SV-01 Solution Structure
- SV-02 Solution Resource Interaction
- SV-03 Solution Resource Interaction to Function Mapping
- SV-04 Solution Function
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..