Automated Generation of Test Cases Using Model-Driven Architecture

2007 ◽  
Author(s):  
A. Z. Javed ◽  
P. A. Strooper ◽  
G. N. Watson
Keyword(s):  
Test Cases ◽  
Model Driven Architecture ◽  
Automated Generation ◽  
Model Driven

Use of Business Models within Model Driven Architecture

2009 ◽  
Vol 38 (38) ◽  
pp. 119-130
Author(s):  
Erika Asnina
Keyword(s):  
Business Models ◽  
Business Processes ◽  
Use Cases ◽  
Separation Of Concerns ◽  
Model Driven Architecture ◽  
Model Driven ◽  
Development Processes ◽  
Business Requirements ◽  
Complex Computer ◽  
Independent Model

Use of Business Models within Model Driven Architecture Model Driven Architecture is a framework dedicated for development of large and complex computer systems. It states and implements the principle of architectural separation of concerns. This means that a system can be modeled from three different but related to each other viewpoints. The viewpoint discussed in this paper is a Computation Independent one. MDA specification states that a model that shows a system from this viewpoint is a business model. Taking into account transformations foreseen by MDA, it should be useful for automation of software development processes. This paper discusses an essence of the Computation Independent Model (CIM) and the place of business models in the computation independent modeling. This paper considers four types of business models, namely, SBVR, BPMN, use cases and Topological Functioning Model (TFM). Business persons use SBVR to define business vocabularies and business rules of the existing and planned domains, BPMN to define business processes of both existing and planned domains, and use cases to define business requirements to the planned domain. The TFM is used to define functionality of both existing and planned domains. This paper discusses their capabilities to be used as complete CIMs with formally defined conformity between planned and existing domains.

scholarly journals Model‐driven architecture based security analysis

2021 ◽  
Author(s):  
Saoussen Mili ◽  
Nga Nguyen ◽  
Rachid Chelouah
Keyword(s):  
Security Analysis ◽  
Model Driven Architecture ◽  
Model Driven

MODEL CHECKING FOR VERIFICATION OF MANDATORY ACCESS CONTROL MODELS AND PROPERTIES

2011 ◽  
Vol 21 (01) ◽  
pp. 103-127 ◽  
Author(s):  
VINCENT C. HU ◽  
D. RICHARD KUHN ◽  
TAO XIE ◽  
JEEHYUN HWANG
Keyword(s):  
Access Control ◽  
Test Cases ◽  
Covering Array ◽  
Model Checker ◽  
Challenging Problem ◽  
Automated Generation ◽  
Mandatory Access Control ◽  
Access Control Models ◽  
Security Properties ◽  
Property Verification

Mandatory access control (MAC) mechanisms control which users or processes have access to which resources in a system. MAC policies are increasingly specified to facilitate managing and maintaining access control. However, the correct specification of the policies is a very challenging problem. To formally and precisely capture the security properties that MAC should adhere to, MAC models are usually written to bridge the rather wide gap in abstraction between policies and mechanisms. In this paper, we propose a general approach for property verification for MAC models. The approach defines a standardized structure for MAC models, providing for both property verification and automated generation of test cases. The approach expresses MAC models in the specification language of a model checker and expresses generic access control properties in the property language. Then the approach uses the model checker to verify the integrity, coverage, and confinement of these properties for the MAC models and finally generates test cases via combinatorial covering array for the system implementations of the models.

scholarly journals Model-driven acceptance test automation based on use cases

2015 ◽  
Vol 12 (2) ◽  
pp. 707-728 ◽  
Author(s):  
Tomasz Straszak ◽  
Michał Śmiałek
Keyword(s):  
Specification Language ◽  
Acceptance Testing ◽  
Functional Domain ◽  
Test Cases ◽  
Acceptance Test ◽  
Test Automation ◽  
Model Driven ◽  
Use Case Models ◽  
Model Driven Approach ◽  
Requirements Models

Acceptance testing is highly dependent on the formulation of requirements, as the final system is tested against user requirements. It is thus highly desirable to be able to automate transition from requirements to acceptance tests. In this paper we present a model-driven approach to this issue, where detailed use case models are transformed into test cases. Importantly, our approach facilitates synchronising functional test cases with other types of tests (non-functional, domain logic, user interface) and introducing test data. This leads to a unified approach where requirements models of various kind drive the acceptance testing process. This process is parallel to the development process which also involves automatic transformations from requirements models to software development artefacts (models and code). To show validity of the approach we present a case study which uses a new tool called ReDSeT, that transforms requirements formulated in the Requirements Specification Language (RSL) into tests in a newly proposed Test Specification Language (TSL).

scholarly journals Formalism Challenges of the Cougaar Model Driven Architecture

2004 ◽  
pp. 57-71 ◽  
Author(s):  
Shawn A. Bohner ◽  
Boby George ◽  
Denis Gračanin ◽  
Michael G. Hinchey
Keyword(s):  
Model Driven Architecture ◽  
Model Driven

scholarly journals Productivity Evaluation of Self-Adaptive Software Model Driven Architecture

2014 ◽  
pp. 191-210
Author(s):  
Basel Magableh ◽  
Stephen Barrett
Keyword(s):  
Dynamic Decision Making ◽  
Development Effort ◽  
Model Driven Architecture ◽  
Model Driven ◽  
Software Model ◽  
Source Line ◽  
Formal Procedure ◽  
Context Dependent ◽  
Application Requirements ◽  
Self Adaptive

Anticipating context changes using a model-based approach requires a formal procedure for analysing and modelling context-dependent functionality and stable description of the architecture which supports dynamic decision-making and architecture evolution. This article demonstrates the capabilities of the context-oriented component-based application model-driven architecture (COCA-MDA) to support the development of self-adaptive applications; the authors describe a state-of-the-art case study and evaluate the development effort involved in adopting the COCA-MDA in constructing the application. An intensive analysis of the application requirements simplified the process of modelling the application’s behavioural model; therefore, instead of modelling several variation models, the developers modelled an extra-functionality model. COCA-MDA reduces the development effort because it maintains a clear separation of concerns and employs a decomposition mechanism to produce a context-oriented component model which decouples the applications’ core functionality from the context-dependent functionality. Estimating the MDA approach’s productivity can help the software developers select the best MDA-based methodology from the available solutions. Thus, counting the source line of code is not adequate for evaluating the development effort of the MDA-based methodology. Quantifying the maintenance adjustment factor of the new, adapted, and reused code is a better estimate of the development effort of the MDA approaches.

Sign in / Sign up

Export Citation Format

Share Document