Hazard analysis in object oriented design of dependable systems

Johannessen, Per; Grante, Christian; Alminger, Anders; Eklund, Ulrik; Torin, J.

doi:10.1109/dsn.2001.941436

Cited by 39 publications

(28 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The material presented in chapter 6 was presented & published in (Sharvia & Papadopoulos, 2008), and contributed to (Adachi et al, 2010). Tables Table 1: Example of FHA on car brake function (source: Johannessen et al, 2001) .... 30 …”

Section: Specificallymentioning

confidence: 99%

“…(Johannessen et al, 2001) highlights that "there is still uncovered demand for early hazard analysis at functional level", and SAE Aerospace Recommended Practices documents ARP4761 have recommended Preliminary System Safety Assessment (PSSA) to be performed at the earliest stages together with the design activities.…”

Section: Csa Approach Include Hierarchically Performed Hazards Originmentioning

confidence: 99%

“…FHA is extended in (Johannessen et al, 2001) and ) to include failure classes, similar to the classes used in HAZOP (Kletz, 1997). Failures are classified, although not restricted, into "Omission", "Commission", "Timing", and "Value".…”

Section: Functional Failure Analysis (Ffa)mentioning

confidence: 99%

See 2 more Smart Citations

Integrated Application of Compositional and Behavioural Safety Analysis

Sharvia

Papadopoulos

2011

Advances in Intelligent and Soft Computing

View full text Add to dashboard Cite

Section: Specificallymentioning

confidence: 99%

Section: Csa Approach Include Hierarchically Performed Hazards Originmentioning

confidence: 99%

See 1 more Smart Citation

Integrated Application of Compositional and Behavioural Safety Analysis

Sharvia

Papadopoulos

2011

Advances in Intelligent and Soft Computing

View full text Add to dashboard Cite

“…Our solution at the early stages, when we have no design description, to analyze, is to use a simple Preliminary Hazard Analysis (PHA), Functional Failure Analysis (FHA) or Functional Failure Analysis (FHA) [4]. Later in the development process, when developers have made a design, for instance, described in UML, they can use FMEA to identify hazards that can arise, and what effects these hazards will have.…”

Section: Failure Methods and Effect Analysismentioning

confidence: 99%

Safety Methods in Software Process Improvement

Lauritsen

Stålhane

2005

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Even if the application developers produce software in accordance with the customer requirements, they cannot guarantee that the software will behave in a safe way during the lifetime of the software. We define a system as safe if the risks related to its use are judged to be acceptable [1]. Safety must not be confused with security which broadly is defined as keeping the system unavailable for people who should not be able to access it. In this paper we introduce the Failure Mode and Effect Analysis (FMEA) technique into the software development process to improve the safety of business-critical software. In a business environment this means that the system does not behave in such a way that it causes the customer or his users to lose money or important information. We will use the term "business-safe" for this characteristic.

show abstract

“…Moreover, we have considered of interest to jointly analyze those works focussed on risk assessment, irrespective of the phase of the life-cycle they apply, they are presented in §4.4.5. [Johannessen et al 2001] provide also support to analyse the consequence of combined failures (C11 -DT.FMDep). Both the approaches are characterized by a low degree of automation (to the best of our knowledge, no tools are available to support them -C7).…”

Section: Safetymentioning

confidence: 99%

Dependability modeling and analysis of software systems specified with UML

2012

View full text Add to dashboard Cite

The goal is to survey dependability modeling and analysis of software and systems specified with UML, with focus on reliability, availability, maintainability and safety (RAMS). From the literature published in the last decade, 33 approaches presented in 43 papers were identified. They are evaluated according to three sets of criteria regarding UML modeling issues, addressed dependability characteristics and quality assessment of the surveyed approaches. The survey shows that more works are devoted to reliability and safety, fewer to availability and maintainability and none to integrity. Many methods support early life-cycle phases (from requirements to design). More research is needed for tool development to automate the derivation of analysis models and to give feedback to designers.

show abstract

Hazard analysis in object oriented design of dependable systems

Cited by 39 publications

References 3 publications

Integrated Application of Compositional and Behavioural Safety Analysis

Integrated Application of Compositional and Behavioural Safety Analysis

Safety Methods in Software Process Improvement

Dependability modeling and analysis of software systems specified with UML

Contact Info

Product

Resources

About