Integrating Platform Selection Rules in the Model Driven Architecture Approach

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.

Download Full-text

Model‐driven architecture based security analysis

Systems Engineering ◽

10.1002/sys.21581 ◽

2021 ◽

Author(s):

Saoussen Mili ◽

Nga Nguyen ◽

Rachid Chelouah

Keyword(s):

Security Analysis ◽

Model Driven Architecture ◽

Model Driven

Download Full-text

Model driven architecture approach to logic controller design

10.1063/1.5079137 ◽

2018 ◽

Author(s):

Grzegorz Łabiak ◽

Grzegorz Bazydło

Keyword(s):

Controller Design ◽

Model Driven Architecture ◽

Model Driven

Download Full-text

Formalism Challenges of the Cougaar Model Driven Architecture

Formal Approaches to Agent-Based Systems - Lecture Notes in Computer Science ◽

10.1007/978-3-540-30960-4_5 ◽

2004 ◽

pp. 57-71 ◽

Cited By ~ 4

Author(s):

Shawn A. Bohner ◽

Boby George ◽

Denis Gračanin ◽

Michael G. Hinchey

Keyword(s):

Model Driven Architecture ◽

Model Driven

Download Full-text

Productivity Evaluation of Self-Adaptive Software Model Driven Architecture

Network and Communication Technology Innovations for Web and IT Advancement ◽

10.4018/978-1-4666-2157-2.ch013 ◽

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.

Download Full-text