Automatic Generation of Simulation Models for the Evaluation of Performance and Reliability of Architectures Specified in UML

Miguel, Miguel De; Lambolais, Thomas; Piekarec, Sophie; Betgé-Brezetz, Stéphane; Pequery, Jerome

doi:10.1007/3-540-45254-0_9

Cited by 13 publications

(4 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In the following we analyze them. [Bondavalli et al 2001;Pataricza 2000], [DeMiguel et al 2001] and [Leangsuksun et al 2003] aim at analyzing the reliability and availability of UML-based software systems in different phases of the software life-cycle (from requirement to deployment, C1), using stochastic techniques (C9). They all adopt a model transformation approach to get an analyzable model from UML annotated models.…”

Section: More Than One Dependability Attributementioning

confidence: 99%

“…[ DeMiguel et al 2001] consider the software architecture and detailed design UML specification of distributed real-time systems (C1,C4). Simulation models are generated automatically from UML models, annotated with dependability input parameters (C11) -i.e., object and network error occurrence, object time to failure and repair (DT.EB, DT.EQ, DM.R, DM.M).…”

Section: Reliability and Availabilitymentioning

confidence: 99%

“…Criteria [Bondavalli et al 2001;Pataricza 2000] C1, C2, C6, C9, C10, C11, C12, C17 [DeMiguel et al 2001] C1, C4, C9, C11, C12 [Leangsuksun et al 2003] C1, C2, C6, C8, C9, C10, C11, C12 [Dal Cin 2003] C4, C6, C9,, C11, C12, C13, C17…”

Section: Workunclassified

See 2 more Smart Citations

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

Section: More Than One Dependability Attributementioning

confidence: 99%

Section: Reliability and Availabilitymentioning

confidence: 99%

See 1 more Smart Citation

Dependability modeling and analysis of software systems specified with UML

2012

View full text Add to dashboard Cite

show abstract

“…UML (Unified Modelling Language) has been defined by OMG as a general object-oriented modelling language, and a lot of industrial software tools supporting UML syntax are currently available. At this moment, extensions of UML are submitted to OMG in order to introduce the specification of temporal characteristics (Terrier and Gérard, 2000) and to improve the model analysis (Mellor, 2000;Miguel, et al, 2000)). Therefore, in order to take advantages of both ADL and object-oriented approach, AIL has been defined as a modelling language dedicated to the specification of architectures described as an assembly of standard components.…”

Section: Architecture Description Languagesmentioning

confidence: 99%

An Architecture Description Language for in-Vehicle Embedded System Development

Elloy¹,

Simonot-Lion

2002

IFAC Proceedings Volumes

View full text Add to dashboard Cite

This paper presents the AEE project, a French cooperative research and development program whose purpose is to specify new solutions for in-vehicle embedded system development. The Architecture Implementation Language (AIL) has been defined to specify and to describe precisely any vehicle electronic architecture. AIL supports the AEE design process, and is used by all designers as the backbone of the architecture development. Finally AIL is used to define reusable architecture objects.

show abstract

What Must (Not) Be Available Where?

Bübl¹

2003

On the Move to Meaningful Internet Systems 2003: CoopIS, DOA, and ODBASE

View full text Add to dashboard Cite

Arranging the distribution of data, objects or components is a critical task that can ultimately affect the performance, integrity and reliability of distributed system. This paper suggests to write down what must (not) be available where in order to reveal conflicting distribution requirements and to detect problems early on. Distribution requirements are expressed via a new notion of constraints: a context-based constraint (CoCon) can indirectly select its constrained elements according to their context. The context of an element characterizes the situation in which this element resides and is annotated via metadata. CoCons facilitate checking the compliance of a system or a model with distribution requirements during (re-)design, during (re-)configuration or at runtime. This paper focuses on validating UML models for compliance with distribution CoCons in order to take distribution requirements into account right from start of the development process.

show abstract

Automatic Generation of Simulation Models for the Evaluation of Performance and Reliability of Architectures Specified in UML

Cited by 13 publications

References 3 publications

Dependability modeling and analysis of software systems specified with UML

Dependability modeling and analysis of software systems specified with UML

An Architecture Description Language for in-Vehicle Embedded System Development

What Must (Not) Be Available Where?

Contact Info

Product

Resources

About