trakmetamodel Project

TRAK SourceForge Projects

Definition

Implementation

TRAK Information

 

 

 

 

 

 

 

 

 

 

'Requirement' Node Element

A node element may form the start element or subject of a triple or it may form the end element or object of a triple, or both.

 Requirement - Relationships with Neighbouring Metamodel Elements

Requirement - Relationships with Neighbouring Metamodel Elements

Management Perspective
Name Requirement
Definition An atomic requirement or constraint - a statement of need.
OED:"requirement (n.), sense 3.b"
Comments It is NOT a requirements document. It is intended to represent a requirement - something that might be exported from a requirement management tool. It can be associated with any architecture element inside the boxed area.This provides a mechanism to associate requirements with model elements Desirable - Freedom e.g 'may' Desirable - Commitment e.g. 'will' Mandatory e.g.'shall'
Tests For Atomic
Tests Against Takes form of a document - would then be either a Standard or Contract.
Properties

verification method ('Analysis', 'Demonstration', 'Inspection', 'N/A', 'Similarity', 'Test', 'Unknown') Default: 'Unknown'

requirement type ('Commercial', 'Constraint', 'Interface', 'Legal', 'N/A - Heading', 'Other', 'Performance', 'Physical', 'Unknown') Default: 'Unknown'

compliance level required ('Desirable - Freedom', 'Desirable - Intent', 'Mandatory', 'N/A', 'Unknown') Default: 'Unknown'

requirement scope ('Enabling', 'Product', 'Unknown') Default: 'Unknown'

requirement priority ('High', 'Low', 'Medium', 'Not Specified') Default: 'Not Specified'

requirement identifier

requirement owner

requirement paragraph

requirement text

requirement title

sequence identifier

Sub Class of

Architecture Description Element

Parent Class Of ---
Neighbouring Elements Architecture Description Element , Contract and Standard
Appears in Triples (as subject or object) Architecture Description Element satisfies Requirement
Architecture Description Element traces to Requirement
Contract has part Requirement
Requirement derived from Requirement
Requirement governs Architecture Description Element
Requirement has part Requirement
Requirement is a Architecture Description Element
Standard has part Requirement
Originating Architecture View MV-03 Requirements and Standards - on trakviewpoints site
Configuration Created: 2010-02-15Modified: 2023-09-09
Specification TRAK00002.TRAK. Architecture Framework. Metamodel (2024-09-23)
GNU Free Documentation License (Version 1.3, November 2008) at https://www.gnu.org/licenses/fdl-1.3.html
Download the specification.
 

The contents of this web page are produced from a graph model of TRAK held in Neo4J using a set of (non-TRAK) architecture viewpoint definitions. More details are available...

Navigation

The TRAK metamodel is 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.

Spotted an error or want to make a suggestion?

Modification Date: 2024-10-01