Modeling Use-Case Sequential Dependencies Using ACL

Haq, Inam Ul

doi:10.22215/etd/2014-10501

Cited by 1 publication

(4 citation statements)

References 20 publications

(28 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Implicitly, use cases and their scenarios capture the requirements of the stakeholders' and define the responsibilities (i.e., fine grained requirements) of the system [40,41]. In addition, a use case captures both the pre-conditions and post-conditions of the scenario itself.…”

Section: Model Driven Testing and Use Casesmentioning

confidence: 99%

“…Haq defines in his thesis, an eUC can be thought of as a parameterized use case where the parameters of each use case corresponds to the path sensitization variables required to cover the different paths or scenarios through the use case [40]. Second, in 1996 Buhr and Casselman introduced Use Case Maps in their book Use Case Maps (UCM's) for Object Oriented Systems [45].…”

Section: Model Driven Testing and Use Casesmentioning

confidence: 99%

“…Each time an instance of a class is created a corresponding instance of the contract is created. In addition ACL incorporates pre and post condition checks, invariants and event driven monitoring to observe and monitor scenarios [11,24,40].…”

Section: Another Contract Language and The Validation Framework (Acl/vf)mentioning

confidence: 99%

“…predetermined as the events are not always executed by predefined sequences and as such different event sequences may bring different results. So, in order to consider event execution sequences the event execution rules need to be studied and identified.As Ul Haq defines in his thesis, an eUC can be thought of as a parameterized use case where the parameters of each use case corresponds to the path sensitization variables required to cover the different paths or scenarios through the use case[40]. These parameters allow for the modeling of the sequential dependences and interleaving 3 between use cases.…”

mentioning

confidence: 99%

See 3 more Smart Citations

Mapping ACL/VF to a Java Environment: A Feasibility Study

Needham¹

View full text Add to dashboard Cite

There are a number of different approaches to runtime validation, and one such method is Model Based Testing (MBT), a quality assurance technique where a test suite is generated from an abstract model. While there exists a number of different approaches to accomplish modelbased testing, most are state-based (and thus faced with problems such as state explosion, correspondence to code, etc.). In this thesis, we instead focus on an alternative approach to MBT, namely scenario based testing, which we consider in the context of runtime validation. More specifically, we address scenario monitoring and validation in ACL/VF ACL/VF. This approach, developed by Dr. Corriveau and his research team, provides both a language (ACL-Another Contract Language) to specify an implementation-independent testable model and a tool (VF-the Validation Framework) to validate an implementation against an ACL model. The two current versions of the ACL/VF have a number of issues that prevent it from being a usable solution. The original version is .NET specific and incorporates external tools that are no longer supported. Upgrading it to a more recent version of .NET would amount to a complete rewrite. But, more importantly, this initial version has a major bug in its way of monitoring scenarios and a solution requires rethinking a significant and highly technical portion of the implementation of the VF. Instead a new version was implemented and tested with the JavaMOP framework. That solution requires manually mapping an ACL specification to a corresponding set of JavaMOP monitors. Experimentation with this second solution however revealed it cannot manage and monitor multiple scenarios running simultaneously! vi

show abstract

Section: Model Driven Testing and Use Casesmentioning

confidence: 99%

Section: Model Driven Testing and Use Casesmentioning

confidence: 99%