2006
DOI: 10.1007/11916246_8
|View full text |Cite
|
Sign up to set email alerts
|

F(I)MEA-Technique of Web Services Analysis and Dependability Ensuring

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
13
0

Year Published

2007
2007
2020
2020

Publication Types

Select...
3
3
2

Relationship

1
7

Authors

Journals

citations
Cited by 22 publications
(13 citation statements)
references
References 7 publications
0
13
0
Order By: Relevance
“…The developed web service is recommended to be used in conjunction with the intrusion-tolerant architecture 12 or similar architectures for constructing complex software based systems.…”
Section: Implementation As a Web Servicementioning
confidence: 99%
“…The developed web service is recommended to be used in conjunction with the intrusion-tolerant architecture 12 or similar architectures for constructing complex software based systems.…”
Section: Implementation As a Web Servicementioning
confidence: 99%
“…To use FMEA for analyzing the dependability of Web Services, new failure taxonomy, intrusions and various failure effects (data loss, financial loss, denial of service, etc.) are taken into account in [9]. Utilization of FMEA is also proposed in [22] for early robustness analysis of Web-based systems.…”
Section: Related Workmentioning
confidence: 99%
“…On the other hand, there is a body of work focusing on tool-support for FMEA and FTA. In [9], for example, FMEA tables are being integrated with a web service deployment architecture so that they can be dynamically updated by the system. In [13], fault trees are synthesized automatically.…”
Section: Related Workmentioning
confidence: 99%
“…It is confirmed in the recent publications that method is appropriate for security assessment using F(I)MEA (Failure(Intrusion) Modes and Effects Analysis)-technique, failure effects analysis from the recovery time view etc. [15][16]. Other example is that FME(C)A-approach jointly with FTA was extended for reliability analysis at the software architecture design level [17].…”
Section: Introduction and Problem Statementmentioning
confidence: 98%