Providing early feedback in the development cycle through automated application of model checking to software architectures

Abstract

n e bene$ts of evaluating properties of software architectures stem from hvo important software architecture roles: (1) providing an opportunity to evaluate requirements and correct defects prior to implementation and (2) serving as a blueprint for system developers. Tliis paper focuses on a new software architecture evaluation tool called Architecture Analysis Dynamic Environment (Arcade) that uses model checking to provide software architecture safety and liveness evaluation during the requirements gathering and analysis phase. Model checking requires expertise not typically held by systems analysts and software developers. Thus, two barriers to applying model checking must be addressed: (1) translation of the software architecture specification to a form suitable for model checking, and (2) interpretation of the results of model checking. Arcade provides an automated approach to these barriers, allowing model checking of sofware architectures to be added to the list of techniques available to software analysts and developers focusing on requirements gathering and analysis.,

A classification and comparison of model checking software architecture techniques

“…It can reason on changes and evolution with respect to structural and behavioral constraints. Arcade (Barber et al, 2001) applies model checking to DRA (domain reference architecture) to provide software architects early feedbacks on safety and liveness properties. The main goal of the ArchWARE Oquendo, 2004;Mateescu and Oquendo, 2006) project is to specify and analyze evolvable SA at run-time; one of the project outcomes has been a model checking technique for evolvable architectures.…”

“…Recently, model checking has also been used to assess whether an SA specification satisfies desired architectural properties (Inverardi et al, 2001;Bose, 1999;Barber et al, 2001;Ciancarini and Mascolo, 1999;Corradini and Inverardi, 1998;He et al, 2002;Jerad and Barkaoui, 2005;Magee et al, 1999;Tsai et al, 1997;Colvin et al, 2008;Björnander et al, 2009). Although many different approaches have been proposed, little work has been done to provide a comprehensive classification and comparison.…”

Formal Verification Integration Approach for DSML

“…In [21], authors define an approach named Arcade that uses SPIN model checker for evaluating safety and liveness properties of a Domain Reference Architecture that is translated to Promela language. Arcade interprets SPIN counter-example and generates an Architecture Trace Diagram (ATD).…”

Incremental Validation of Formal Specifications

“…Model checking tends to require specialized expertise, and when it's performed by hand then it can be very time consuming or even error-prone [9]. Experts are often needed because model languages can be rather difficult to learn [37].…”

“…Experts are often needed because model languages can be rather difficult to learn [37]. These specialized experts may be called upon to translate a system into the model checking tool or language and then to interpret the results [9]. Given that experts may be involved and that this process can be time consuming, model checking can be costly [18] despite the overall savings it may offer.…”