Model-Based Software Quality Assurance with the Architecture Analysis and Design Language

Feiler, Peter H.; Gluch, David P.; Weiss, Kathryn Anne; Woodham, Kurt

doi:10.2514/6.2009-2034

Cited by 5 publications

(4 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To illustrate the approach, we take an example inspired by [28], that was used for flow latency analysis on AADL 2 specifications [29]. Figure 8 (on the top) considers a simple application described as a uml structured class.…”

Section: Example: Ccsl For Capturing the Architecture Application Anmentioning

confidence: 99%

Correctness issues on MARTE/CCSL constraints

Mallet

Simone

2015

Science of Computer Programming

View full text Add to dashboard Cite

The UML Profile for Modeling and Analysis of Real-Time and Embedded systems promises a general modeling framework to design and analyze systems. Lots of works have been published on the modeling capabilities offered by MARTE, much less on available verification techniques. The Clock Constraint Specification Language (CCSL), first introduced as a companion language for MARTE, was devised to offer a formal support to conduct causal and temporal analysis on MARTE models.This work relies on a state-based semantics for CCSL to establish correctness properties on MARTE/CCSL specifications. We propose and compare two different techniques to build the state-space of a specification. One is an extension of some previous work and is based on extended finite state machines. It relies on integer linear programming to solve the constraints and reduce the state-space. The other one, is based on an intentional representation and uses pure boolean abstractions but offers no guarantee to terminate when the specification is not safe.The approach is illustrated on one simple example where the architecture plays an important role. We describe a process where the logical description of the application is progressively refined to take into account the execution platform through allocation.

show abstract

Section: Example: Ccsl For Capturing the Architecture Application Anmentioning

confidence: 99%

Correctness issues on MARTE/CCSL constraints

Mallet

Simone

2015

Science of Computer Programming

View full text Add to dashboard Cite

show abstract

“…In [30] the style evaluation of a software architecture is studied, while failing to involve the concept of trustworthiness. In [20,21] the authors study the trusted modeling of a architecture while failing to involve trustworthiness evaluation and measurement. Paper [32] studies the service-oriented trustworthy software architecture and gives the corresponding algebraic model while it also fails to discuss trustworthiness evaluation and measurement.…”

Section: This Paper's Reviewsmentioning

confidence: 99%

“…In [21] embedded system architecture trusted modeling based on the architectural analysis and design language and error model is studied.…”

Section: Software Architecturementioning

confidence: 99%

A Trustworthiness Evaluation Method for Software Architectures Based on the Principle of Maximum Entropy (POME) and the Grey Decision-Making Method (GDMM)

Jiang

2014

Entropy

View full text Add to dashboard Cite

Abstract:As the early design decision-making structure, a software architecture plays a key role in the final software product quality and the whole project. In the software design and development process, an effective evaluation of the trustworthiness of a software architecture can help making scientific and reasonable decisions on the architecture, which are necessary for the construction of highly trustworthy software. In consideration of lacking the trustworthiness evaluation and measurement studies for software architecture, this paper provides one trustworthy attribute model of software architecture. Based on this model, the paper proposes to use the Principle of Maximum Entropy (POME) and Grey Decision-making Method (GDMM) as the trustworthiness evaluation method of a software architecture and proves the scientificity and rationality of this method, as well as verifies the feasibility through case analysis.

show abstract

“…More importantly though: Markov automata serve an important practical need. They are the obvious choice for providing semantics to the Architecture Analysis & Design Language (AADL [9]), an industry standard for the automotive and aerospace domain. As experienced in several ESA projects, this holds in particular for the AADL annex dealing with error models [3].…”

mentioning

confidence: 99%

Concurrency Meets Probability: Theory and Practice

Katoen

2013

CONCUR 2013 – Concurrency Theory

View full text Add to dashboard Cite

Model-Based Software Quality Assurance with the Architecture Analysis and Design Language

Cited by 5 publications

References 2 publications

Correctness issues on MARTE/CCSL constraints

Correctness issues on MARTE/CCSL constraints

A Trustworthiness Evaluation Method for Software Architectures Based on the Principle of Maximum Entropy (POME) and the Grey Decision-Making Method (GDMM)

Concurrency Meets Probability: Theory and Practice

Contact Info

Product

Resources

About