Requirement Statement

Expresses a single documented aspect which must be fulfilled by an item in order to qualify as the training system resource.

Child Components

Type Code 0..1
Action Code 0..1
Identifier 0..∞
UUID 0..1
Source Identifier 0..1
Party Identifier 0..1
Identifier Set 0..∞
Related Identifier 0..∞
Name 0..∞
Short Name 0..1
Description 0..∞
Classification 0..∞
Extension 1..1

UML Class Model

The following link opens the SVG image in a separate browser tab.
You can save the file locally and use it, for example, in PowerPoint.
SVG File 
@startuml

class RequirementStatement {
    String TypeCode
    CodeList ActionCode
    String Identifier
    String UUID
    String SourceIdentifier
    String PartyIdentifier
    String Name
    String ShortName
    String Description
}

class "IdentifierSet"{}
class "RelatedIdentifier"{}
class "Classification"{}

RequirementStatement o-d- "0...∞" "IdentifierSet"
RequirementStatement o-r- "0...∞" "RelatedIdentifier"
RequirementStatement o-u- "0...∞" "Classification"

hide circle
@enduml

Where Used

Following is a list of components that have Requirement Statement as a child component.

Feedback

OAGi and its members welcome your feedback.

UUID: b25653d309e648afab4e23a766d8043b

connectSpec (OAGIS) Version 10.12