Dependability
This ontology describes the measure of non-functional attributes of a system in terms of readiness and continuity for correct service, absence of catastrophic consequences on the user(s) and the environment and absence of improper system alteration and ability for a process to undergo recovery.
This ontology is complete and is officially in the ontologies trunk (as of November 2012, v1.3.0 SNAPSHOT). http://forge.universaal.org/svn/ontologies/trunk/ont.dependability
- Dependability
- The root concept of this ontology.
- Fault
- This class is used to classify an instance of a fault that can be further described by the properties whose range are subclasses from the Elementary Fault class.
- FCR (Fault Containment Region)
- This class is used to classify a subsystem that operates correctly regardless of any arbitrary Fault outside the region
- Symptom
- This class is used to classify the behaviour of a system as an indication of a possible problem in the system
- ErrorDetector
- This class is used to classify an instance of a component that detects an error using Symptom instances
- RecoveryAction
- This class is used to classify the instances of the actions to be taken in case of a Failure occurance
- Sensor
- This class is the device concept of the ontology
- SoftwareFault
- Software faults are faults that affect software, i.e, programs or data.
- HardwareFault
- Hardware faults are faults that originate in, or affect, hardware.
- ValueFault
- Value faults are those faults of incorrect value of any parameter
- TimingFault
- A timing failure is when the time of arrival or the duration of the information delivered at the service interface deviates from implementing the system function.
- EarlyTimingFault
- An early timing failure is when the time of arrival or the duration of the information delivered at the service interface is earlier than implementing the system function.
- LateTimingFault
- A late timing failure is when the time of arrival or the duration of the information delivered at the service interface is later than implementing the system function.
- TranseintFault
- A transient fault is short time fault.
- PermanentFault
- A permanent fault is the malfunction of the component that is always present.
- IntermittentFault
- An intermittent fault is the fault which occurs at irregular intervals.
- NonMaliciousFault
- A fault that is an intentional flaw where the objective is not to cause harm or damage to a system.
- InternalCauseFault
- An internal cause fault is the fault that is caused by the internal system structure malfunction.
- ContinuedFault
- A fault is occured once and since then continues
- DevelopmentFault
- Development faults are all faults that occur during development.
- ParametricFault
- A parametric fault is associated with system parameters such as physical system parameters, as e.g. mass, friction, viscosity
- NonParametricFault
- The faults which is not associated with system parameters
- OperationalFault
- Operational faults occur during service delivery when the system is accepted for use and starts delivery of its service to users (use phase).
- DirectFault
- This is the class of fault which affects the system directly
- IndirectFault
- This is the class of fault in which occuring this fault triggers other faults rather than affecting a system component directly.
- StructuralFault
- Structural fault refers to the physical structure of a component such as loss of the load-carrying capacity of a component or member within a structure or of the structure itself.
- ShapeFault
- Shape fault refers to the fault directly associated with the physical shape of a component.
- PropertyFault
- Property faults refer to those faults that are associated with either physical properties or logical ones of a system component.