TRAK Architecture ViewpointsSVp-11 Solution Event Causes
This page reproduces part of the SVp-11 Solution Event Causes 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-11 Solution Event Causes 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-11 | SV-11 | 4 | 2022-01-03 |
Summary
The TRAK SVp-11 Solution Event Causes architecture viewpoint defines the requirements for the TRAK SV-11 Solution Event Causes 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-11 Solution Event Causes 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-11 Solution Event Causes 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-11 Solution Event Causes Architecture Viewpoint
The TRAK SVp-11 Solution Event Causes architecture viewpoint addresses the following concerns:
- How dependable is the system?
- How robust is the system to unwanted events?
- What causes events?
Description
Describes causal or contributory relationships between events that are associated with the system of interest either owing to an error within the system or direct action from something external to the system.
Typically used to represent:
- fault trees for safety to identify a causal chain of events that lead to a set of top 'feared events' which need to be managed
- reliability analyses that provide the basis for predicting how reliable (dependable) a system is in delivering its intended behaviour or level of performance.
- the architecture within a solution that makes it robust in the presence of behaviours or inputs that affect its ability to deliver its intended behaviour or performance (diversity, redundancy, fault tolerance etc.)
Allowed Content
TRAK architecture view content is defined in terms of triples - Node - connector - Node e.g. 'Event impacts on System' that form short statements about the thing(s) being described.
'Event impacts on System' is a Statement or Assertion in a SV-11 Architecture View
The rationale for this is explained separately.
Subject Statements (Triples)
These are statements (triples) that describe the subject of the SV-11 Solution Event Causes architecture view. Specifically these statements address the concerns for this SVp-11 Solution Event Causes architecture viewpoint. These form the basis for the well-formedness section of the SVp-11 Solution Event Causes architecture viewpoint.
There are 17 possible subject statements in total which include 10 metamodel elements ( Event , Function , Interaction Element , Job , Organisation , Physical , Resource Interaction , Role , Software and System ).
Return to the top of the Solution Event Causes page.
- Event caused by Event
- Event caused by Function
- Event caused by Interaction Element
- Event caused by Job
- Event caused by Organisation
- Event caused by Physical
- Event caused by Resource Interaction
- Event caused by Role
- Event caused by Software
- Event caused by System
- Event impacts on Function
- Event impacts on Job
- Event impacts on Organisation
- Event impacts on Physical
- Event impacts on Role
- Event impacts on Software
- Event impacts on System
Return to the top of the SV-11 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-11 Solution Event Causes 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 ...
'Job traces to Standard' - an optional statement or assertion for the SV-11 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 152 possible statements which may be used to augment the SV-11 Solution Event Causes architecture view, split into 7 groups:
- Context - Containing System
- Context - Threat
- Universal - Applicable Requirements
- Universal - Assurance
- Universal - Concern Identified
- Universal - Requirement Compliance
- Universal - Traceability or Reference
Return to the top of the Solution Event Causes page.
Context - Containing System
21 additional context statements:
- Job performs Function
- Job plays Role
- Organisation has part Job
- Organisation has part Organisation
- Organisation is member of Organisation
- Organisation performs Function
- Organisation plays Role
- Physical contains System
- Physical has part Physical
- Physical performs Function
- Role performs Function
- Software has part Software
- Software hosted on Physical
- Software performs Function
- 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
- System performs Function
Return to the top of the SV-11 optional statements (triples).
Context - Threat
1 additional context statements:
- Event can lead to exposure to Threat
Return to the top of the SV-11 optional statements (triples).
Universal - Applicable Requirements
30 additional context statements:
- Contract governs Event
- 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 Event
- 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 Event
- 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-11 optional statements (triples).
Universal - Assurance
20 additional context statements:
- Claim about Event
- 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
- Event traces to Argument
- 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-11 optional statements (triples).
Universal - Concern Identified
10 additional context statements:
- Concern about Event
- 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-11 optional statements (triples).
Universal - Requirement Compliance
30 additional context statements:
- Event satisfies Contract
- Event satisfies Requirement
- Event satisfies Standard
- 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-11 optional statements (triples).
Universal - Traceability or Reference
40 additional context statements:
- Event traces to Contract
- Event traces to Document
- Event traces to Requirement
- Event traces to Standard
- 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-11 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-11 Solution Event Causes definition within the TRAK00001. TRAK. Architecture Framework. Viewpoints specification.
Presentation Methods
The SV-11 Solution Event Causes architecture view may use any of following means to the statements (triples):
- block diagram (Node = block, Need = line with text label and direction indicator)
- matrix (if only showing need relationships
- N-squared diagram (Nodes on diagonal, intersections marked to represent direction of Need)
Note that a textual presentation is acceptable for any TRAK architecture view.
Comments
The SV-11 Solution Event Causes architecture view is the master source (origin) on which you first create the following elements or statements:
Neighbouring Architecture Views
The SV-11 Solution Event Causes architecture view content may overlap that of the following neighbouring architecture views:
- MV-01 Architecture Description Dictionary
- MV-02 Architecture Description Design Record
- MV-03 Requirements and Standards
- MV-04 Assurance
- SV-01 Solution Structure
- SV-04 Solution Function
- 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..