TRAK Architecture ViewpointsSVp-01 Solution Structure
This page reproduces part of the SVp-01 Solution Structure 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-01 Solution Structure 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 |
| Solutiom | SVp-01 | SV-01 | 19 | 2024-07-10 |
Summary
The TRAK SVp-01 Solution Structure architecture viewpoint defines the requirements for the TRAK SV-01 Solution Structure 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-01 Solution Structure 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-01 Solution Structure 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-01 Solution Structure Architecture Viewpoint
The TRAK SVp-01 Solution Structure architecture viewpoint addresses the following concerns:
- How does responsibility (scope/jurisdiction) apply to the solution components?
- Is the solution structured sensibly?
- What does the solution consist of?
- What is the organisation structure / membership?
Description
Describes solution structure in terms of parts, governance, membership, dependency and responsibility extent.
Allowed Content
TRAK architecture view content is defined in terms of triples - Node - connector - Node e.g. 'Role extends to Physical' that form short statements about the thing(s) being described.
'Role extends to Physical' is a Statement or Assertion in a SV-01 Architecture View
The rationale for this is explained separately.
Subject Statements (Triples)
These are statements (triples) that describe the subject of the SV-01 Solution Structure architecture view. Specifically these statements address the concerns for this SVp-01 Solution Structure architecture viewpoint. These form the basis for the well-formedness section of the SVp-01 Solution Structure architecture viewpoint.
There are 42 possible subject statements in total which include 10 metamodel elements ( Capability , Enterprise , Job , Node , Organisation , Physical , Role , Software , System and Zone ).
The subject statements are split into 4 groups:
Return to the top of the Solution Structure page.
Configuration
19 possible subject statements:
- Organisation has part Job
- Organisation has part Organisation
- Physical contains Physical
- Physical contains System
- Physical has part Physical
- Physical is attached to Physical
- Physical physically depends on Physical
- Physical physically supports Physical
- Software has part Software
- Software hosted on Physical
- 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
- Zone contains Physical
- Zone contains System
- Zone contains Zone
Return to the top of the SV-01 subject statements (triples).
Governance
6 possible subject statements:
- Job governs Job
- Organisation governs Organisation
- Organisation has part Job
- Organisation has part Organisation
- Organisation is member of Organisation
- Organisation owns Organisation
Return to the top of the SV-01 subject statements (triples).
Role Extent
9 possible subject statements:
- Job plays Role
- Organisation plays Role
- Role extends to Job
- Role extends to Organisation
- Role extends to Physical
- Role extends to Role
- Role extends to Software
- Role extends to System
- Role extends to Zone
Return to the top of the SV-01 subject statements (triples).
Solution Realises...
8 possible subject statements:
- Job realises Node
- Organisation realises Enterprise
- Organisation realises Node
- Physical realises Node
- Role realises Node
- Software realises Node
- System realises Capability
- System realises Node
Return to the top of the SV-01 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-01 Solution Structure 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 ...
'Capability traces to Requirement' - an optional statement or assertion for the SV-01 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-01 Solution Structure architecture view, split into 6 groups:
- Governance
- Universal - Applicable Requirements
- Universal - Assurance
- Universal - Concern Identified
- Universal - Requirement Compliance
- Universal - Traceability or Reference
Return to the top of the Solution Structure page.
Governance
1 additional context statements:
- Organisation governs Project
Return to the top of the SV-01 optional statements (triples).
Universal - Applicable Requirements
30 additional context statements:
- Contract governs Capability
- Contract governs Enterprise
- Contract governs Job
- Contract governs Node
- Contract governs Organisation
- Contract governs Physical
- Contract governs Role
- Contract governs Software
- Contract governs System
- Contract governs Zone
- Requirement governs Capability
- Requirement governs Enterprise
- Requirement governs Job
- Requirement governs Node
- Requirement governs Organisation
- Requirement governs Physical
- Requirement governs Role
- Requirement governs Software
- Requirement governs System
- Requirement governs Zone
- Standard governs Capability
- Standard governs Enterprise
- Standard governs Job
- Standard governs Node
- Standard governs Organisation
- Standard governs Physical
- Standard governs Role
- Standard governs Software
- Standard governs System
- Standard governs Zone
Return to the top of the SV-01 optional statements (triples).
Universal - Assurance
20 additional context statements:
- Capability traces to Argument
- Claim about Capability
- Claim about Enterprise
- Claim about Job
- Claim about Node
- Claim about Organisation
- Claim about Physical
- Claim about Role
- Claim about Software
- Claim about System
- Claim about Zone
- Enterprise 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
- Zone traces to Argument
Return to the top of the SV-01 optional statements (triples).
Universal - Concern Identified
10 additional context statements:
- Concern about Capability
- Concern about Enterprise
- Concern about Job
- Concern about Node
- Concern about Organisation
- Concern about Physical
- Concern about Role
- Concern about Software
- Concern about System
- Concern about Zone
Return to the top of the SV-01 optional statements (triples).
Universal - Requirement Compliance
30 additional context statements:
- Capability satisfies Contract
- Capability satisfies Requirement
- Capability satisfies Standard
- Enterprise satisfies Contract
- Enterprise satisfies Requirement
- Enterprise 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
- Zone satisfies Contract
- Zone satisfies Requirement
- Zone satisfies Standard
Return to the top of the SV-01 optional statements (triples).
Universal - Traceability or Reference
40 additional context statements:
- Capability traces to Contract
- Capability traces to Document
- Capability traces to Requirement
- Capability traces to Standard
- Enterprise traces to Contract
- Enterprise traces to Document
- Enterprise traces to Requirement
- Enterprise 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
- Zone traces to Contract
- Zone traces to Document
- Zone traces to Requirement
- Zone traces to Standard
Return to the top of the SV-01 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-01 Solution Structure definition within the TRAK00001. TRAK. Architecture Framework. Viewpoints specification.
Presentation Methods
The SV-01 Solution Structure architecture view may use any of following means to the statements (triples):
- Block diagram (Resource = block, TRAK metamodel relationship = line with text label and direction indicator).
Note that a textual presentation is acceptable for any TRAK architecture view.
Examples
Governance Form Describing an Organisation
Two Different Roles Applying to a System
MDG for TRAK UML Plugin for Sparx EA
Comments
The SV-01 Solution Structure architecture view is the master source (origin) on which you first create the following elements or statements:
The SV-01 provides 3 areas of coverage:
1. Describing organisational structure - governance, membership and roles as well as organisational breakdown.
2. Describing the extent or jurisdiction of roles.
3. Describing classic system or product breakdown structure.
If you need to show the effect of time on responsibility extent use the PrV-03 Procurement Responsibility View.
Software is hosted on Physical is an implicit statement of containment. To make an explicit statement it is acceptable to also state that Physical contains Software.
'contains' and 'has part' are transitive relationships / assertions i.e 'Physical contains System' means that any element of the System is also contained by the Physical.
Neighbouring Architecture Views
The SV-01 Solution Structure architecture view content may overlap that of the following neighbouring architecture views:
- CV-01 Concept Need
- EV-01 Enterprise Goal
- MV-01 Architecture Description Dictionary
- MV-02 Architecture Description Design Record
- MV-03 Requirements and Standards
- MV-04 Assurance
- PrV-02 Procurement Timeline
- SV-02 Solution Resource Interaction
- SV-04 Solution Function
- SV-05 Solution Function to Concept Activity Mapping
- SV-06 Solution Competence
- SV-07 Solution Sequence
- SV-11 Solution Event Causes
- SV-13 Solution Risk
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..