Failure
Information on the problem, possible symptoms that may lead to the problem, and the cause and remedy for the problem.
Causes and/or remedies could be reported against a failure in a multi-level hierarchical reporting. For example, failure analysis could be recorded as follows; for failure A, causes P and Q are the factors and remedies X, Y and Z are to be taken.
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..∞
Problem 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
You can save the file locally and use it, for example, in PowerPoint.
SVG File
@startuml
class Failure {
String TypeCode
CodeList ActionCode
String Identifier
String UUID
String SourceIdentifier
String PartyIdentifier
}
class "IdentifierSet"{}
class "RelatedIdentifier"{}
class "Problem"{}
Failure o-d- "0...∞" "IdentifierSet"
Failure o-r- "0...∞" "RelatedIdentifier"
Failure o-u- "0...∞" "Problem"
hide circle
@endumlWhere Used
Following is a list of components that have Failure as a child component.
Feedback
OAGi and its members welcome your feedback.
UUID: ebf6f6c568f64767af9cfed4d4512959
connectSpec (OAGIS) Version 10.12