Abstract:The paper discusses a constructive approach to the temporal logic specification and analysis of dependability requirements of automation systems. The work is based on TRIO formal method, which supports a declarative temporal logic language with a linear notion of time, and makes use of UML class diagrams to describe the automation system. The general concepts presented for the automation system domain are here instantiated on a case study application taken from the energy distribution field.
Partially funded b… Show more
“…Both [Addouche and Antoine 2004;Addouche et al 2006] and [Bernardi et al 2004a;2004b] provide support in the requirement and design phases (C1) of the real-time software development (C4). In particular, the considered application domains are, respectively, automated production systems and distributed control automation systems (C5).…”
Section: Reliability Availability and Maintainabilitymentioning
confidence: 99%
“…The negative aspect of the approach is the poor separation of concerns, in fact new classes need to be defined and introduced in the system model, beside the classes representing the actual system components, for dependability analysis purposes (C17). [Bernardi et al 2004a;2004b] propose a set of UML class diagrams (C2), structured in packages (i.e., a CD framework), as a reusable pattern to collect dependability and real-time requirements of distributed control automation systems and to support the design of an appropriate fault tolerance strategy. They also propose a systematic method for the derivation of dependability analysis models, such as TRIO [Ghezzi et al 1990] temporal logic models (C10).…”
Section: M)mentioning
confidence: 99%
“…Criteria [Addouche and Antoine 2004;Addouche et al 2006] C1, C4, C5, C6, C8, C10, C11, C12, C17 [Bernardi et al 2004a;2004b] C1, C2, C4, C5, C8, C10, C11, C12, C13, C14, C15, C16, C17 Table XV. Reliability and safety.…”
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.
“…Both [Addouche and Antoine 2004;Addouche et al 2006] and [Bernardi et al 2004a;2004b] provide support in the requirement and design phases (C1) of the real-time software development (C4). In particular, the considered application domains are, respectively, automated production systems and distributed control automation systems (C5).…”
Section: Reliability Availability and Maintainabilitymentioning
confidence: 99%
“…The negative aspect of the approach is the poor separation of concerns, in fact new classes need to be defined and introduced in the system model, beside the classes representing the actual system components, for dependability analysis purposes (C17). [Bernardi et al 2004a;2004b] propose a set of UML class diagrams (C2), structured in packages (i.e., a CD framework), as a reusable pattern to collect dependability and real-time requirements of distributed control automation systems and to support the design of an appropriate fault tolerance strategy. They also propose a systematic method for the derivation of dependability analysis models, such as TRIO [Ghezzi et al 1990] temporal logic models (C10).…”
Section: M)mentioning
confidence: 99%
“…Criteria [Addouche and Antoine 2004;Addouche et al 2006] C1, C4, C5, C6, C8, C10, C11, C12, C17 [Bernardi et al 2004a;2004b] C1, C2, C4, C5, C8, C10, C11, C12, C13, C14, C15, C16, C17 Table XV. Reliability and safety.…”
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.
“…The specification and analysis of dependability requirements have been also addressed by structured methodologies integrating standard object-oriented notations such as UML (Bernardi 2004) with (logical and operational) formal languages.…”
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.