Scenario-Based Validation: Beyond the User Requirements Notation

Arnold, Dave; Corriveau, Jean-Pierre; Shi, Wei

doi:10.1109/aswec.2010.29

Cited by 11 publications

(12 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…]" Indeed, most model-based approach to testing [15] enable testability, that is, the generation of non-executable test purposes. Consequently, Arnold and Corriveau have discussed at length elsewhere [16] how to augment the URN modeling puzzle above to address requirements verification. In a nutshell, we suggest:…”

Section: Model-driven Requirements Verificationmentioning

confidence: 97%

Requirements verification in the presence of variability

Corriveau

Bashardoust

Radonjic

2011

2011 Model-Driven Requirements Engineering Workshop

View full text Add to dashboard Cite

The emergence of Software Product Lines and System Family Engineering emphasizes the importance of the notions of variability and commonalities across a domain. Yet, how to integrate these notions into the task of verifying requirements against the actual behavior of an implementation has received little attention. In this paper, our position is that a model-driven approach to requirements verification in the presence of variability is entirely feasible.

show abstract

Section: Model-driven Requirements Verificationmentioning

confidence: 97%

Requirements verification in the presence of variability

Corriveau

Bashardoust

Radonjic

2011

2011 Model-Driven Requirements Engineering Workshop

View full text Add to dashboard Cite

show abstract

“…ACL is a high-level contract language that is closely tied to the concept of requirements. It was developed by Arnold and Corriveau (2010a, 2010b, 2010c and offers several constructs, in particular scenarios and responsibilities, for system-level modeling.…”

Section: Research Question Thesis and Methodologymentioning

confidence: 99%

“…The specification language that is used for this thesis is called Another Contract Language (ACL). It was put forth by Arnold and Corriveau (2010a, 2010b, 2010c. In this section, we summarize the essential aspects of it through a simple example.…”

Section: Another Contract Language (Acl)mentioning

confidence: 99%

Modeling Use-Case Sequential Dependencies Using ACL

Haq¹

View full text Add to dashboard Cite

show abstract

“…ACL is a high-level, implementation-independent specification language, the goal of which was to provide a new approach to a testable requirements model (TRM) [10,22,23]. It is a textual specification and is intended to be implemented after the necessary user requirements notation (URN) specifications have been developed.…”

Section: Another Contract Languagementioning

confidence: 99%

“…More specifically, ACL is intended to be written based on refinements of the responsibilities, scenarios, and metrics of goal-oriented requirements language (GRL) and use case map (UCM) diagrams (developed from use cases) [22].…”

Section: Another Contract Languagementioning

confidence: 99%

Mapping ACL to JavaMOP: A Feasibility Study

Beltramin¹

View full text Add to dashboard Cite

Model-based testing (MBT) is a quality assurance technique where a test suite is generated from an abstract model. There are a number of different approaches to accomplish model-based testing. While state-based techniques dominate, they have a number of inherent issues. These issues have led to the pursuit of alternatives such as scenario-based approaches.ACL/VF is one such scenario-based approach. Developed by Dr. Corriveau and his students, the ACL/VF system provides both a language to specify an implementation-independent testable model of a specification and the tool to validate an implementation against this model. However, the current implementation of ACL/VF has a number of issues that prevent it from being a usable solution. In particular, the current version of ACL/VF is extremely .NET3.5 specific. Unfortunately, upgrading it to a more recent version of .NET essentially amounts to a complete rewrite. Given the widespread use of Java, a most immediate research question is to determine whether or not it is feasible to reimplement ACL/VF on that platform.Our claim is that this reimplementation can be accomplished through a mapping from ACL specifications to JavaMOP monitor specifications. The following thesis provides two case studies supporting this claim as well as an element-by-element proposed mapping.ii Acknowledgments I wish to thank my supervisor, Professor Jean-Pierre Corriveau, for his help in suggesting a topic, guiding me through it and editing this dissertation. I also want to thank my co-supervisor, Professor Wei Shi, for involving me in her Engage research project with Blueprint, as well as for her input and funding for this research.

show abstract

Scenario-Based Validation: Beyond the User Requirements Notation

Cited by 11 publications

References 9 publications

Requirements verification in the presence of variability

Requirements verification in the presence of variability

Modeling Use-Case Sequential Dependencies Using ACL

Mapping ACL to JavaMOP: A Feasibility Study

Contact Info

Product

Resources

About