Fault
by
Antonio Bucchiarone
—
last modified
Apr 26, 2012 11:14
—
filed under:
KnowledgeModel
Definitions
Term: |
Domain: Cross-cutting issues | ||||
---|---|---|---|---|---|
Engineering and Design (KM-ED) |
Adaptation and Monitoring (KM-AM) |
Quality Definition, Negotiation and
Assurance (KM-QA) |
Generic (domain independent) |
||
D o m a i n : L a y e r s |
Business Process Management (KM-BPM) |
With respect to business process, a well-designed business process could be able to
handle fault in order to prevent possible failures. |
A fault could influence KPIs and result in a failure. It
can be defined as a deviation from a desired KPI |
||
Service Composition and
Coordination (KM-SC) |
A design process is necessary to identify and handle
faults at run time in a composite service |
A Monitoring mechanism could be applied to diagnose a fault. Once a fault has been identified an application may adapt by choosing an alternative service.[CD-JRA-1.1.4] | A fault could influence the non-functional
requirements |
||
Service Infrastructure (KM-SI) |
A fault can be defined as a deviation in a quality of service in terms of
performance dimensions [CD-JRA-1.2.4]
[CD-JRA-2.3.4] |
||||
Generic (domain independent) |
A manifestation of an error in software. A fault,
if encountered, may cause a failure. [FOLDOC] Fault is an (usually) observable event in the service execution that can produce an erroneous state and, as a consequence, a failure. [CD-JRA-1.2.2] |
A fault is defined in document ISO/CD 10303-226,as an
abnormal condition or defect at the component, equipment, or sub-system
level which may lead to a failure. According to the Federal Standard 1037C of the United States, the term fault has the following meanings: (i) An accidental condition that causes a functional unit to fail to perform its required function, (ii) A defect that causes a reproducible or catastrophic malfunction. A malfunction is considered reproducible if it occurs consistently under the same circumstances. Failures in hardware can be caused by random faults or systematic faults, but failures in software are always systematic. [Wikipedia] |
Competencies
-
UniDue: Quality Assurance; http://www.sse.uni-due.de/wms/en/?go=111; Klaus Pohl, Andreas Metzger
- POLIMI: Adaptive Web Services; http://home.dei.polimi.it/pernici/ws-research.html; Barbara Pernici, Anna Maria Rosati
- INRIA: Service-Based System Testing; http://www.irisa.fr/triskell/perso_pro/bbaudry/; Benoit Baudry, Sagar Sen
Scenarios
- Original Equipment Automotive Supply Chain (Case Study Solution -> Implementation)
References
- [CD-JRA-1.2.2] "Taxonomy of adaptation principles and mechanisms"
-
[CD-JRA-1.1.4] "Coordinated design knowledge models for software engineering and
service-based computing" - [FOLDOC] http://foldoc.org/index.cgi?fault
- [CD-JRA-2.3.4] CD-JRA-2.3.4: Decision support for local adaptation
- [CD-JRA-1.2.4] CD-JRA-1.2.4: Integrated adaptation and monitoring principles, techniques and methodologies across functional SBA layers
- [Wikipedia] Fault: http://en.wikipedia.org/wiki/Fault