Discussing the Difference between Model Driven Architecture and Model Driven Development in the Context of Supporting Tools

Nikiforova, Oksana; Čerņičkins, Antons; Pavlova, Nataļja

doi:10.1109/icsea.2009.71

Cited by 8 publications

(11 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The idea of common consideration of both models is known; however, this usage in an objectoriented approach was not widely discussed. [26] proposes the way the classes and their object operations can be defined based on a two-hemisphere model [20], which essence is two interrelated models: 1) a business process model-describes the processes of the developed system; 2) a concept model-describes objects and their interaction during system work. Two-hemisphere model-driven approach (Fig.…”

Section: Two-hemisphere Model-driven Class Definitionmentioning

confidence: 99%

“…Two-hemisphere model-driven approach (Fig. 2) [26] proposes to start the process of software development based on the two-hemisphere problem domain model, where one model reflects functional (procedural) aspects of the business and the software system, and another model reflects the corresponding concept structures. The co-existence and interrelatedness of the models enables knowledge transfer from one model to another, as well as the utilization of particular knowledge completeness and consistency checks [20].…”

Section: Two-hemisphere Model-driven Class Definitionmentioning

confidence: 99%

“…Transformations from two-hemisphere model into class diagram in two-hemisphere model driven approach[26] …”

mentioning

confidence: 99%

See 2 more Smart Citations

Role of UML Class Diagram in Object-Oriented Software Development

Nikiforova¹,

Sejans²,

Čerņičkins³

2011

Scientific Journal of Riga Technical University. Computer Sciences

Self Cite

View full text Add to dashboard Cite

Role of UML Class Diagram in Object-Oriented Software DevelopmentUML is an industrial standard for object-oriented software specification which offers a notation for class modeling during object oriented software development. Since the UML class diagram is a so-called "bridge" between software specification at the user side and software realization at the developer side, it requires strong guidelines for identification of class objects from the problem domain and notational conventions for modeling of the class diagram for its further usage in system coding. This paper presents a discussion on problematic stages and possible element transformations into software components. Several conclusions are drawn on potential usage of the class diagram in industry.

show abstract

Section: Two-hemisphere Model-driven Class Definitionmentioning

confidence: 99%

Section: Two-hemisphere Model-driven Class Definitionmentioning

confidence: 99%

See 1 more Smart Citation

Role of UML Class Diagram in Object-Oriented Software Development

Nikiforova¹,

Sejans²,

Čerņičkins³

2011

Scientific Journal of Riga Technical University. Computer Sciences

Self Cite

View full text Add to dashboard Cite

show abstract

“…The process of software development as such continues to evolve [5]. Since the actual beginning of the software industry dozens of various approaches, techniques, and models have been proposed.…”

Section: A Backgroundmentioning

confidence: 99%

On Foundation for Certification of Model Driven Architecture (MDA) Tools: Defining a Specification

Čerņičkins¹,

Nikiforova²

2010

Scientific Journal of Riga Technical University. Computer Sciences

Self Cite

View full text Add to dashboard Cite

A modern approach to software development includes a wide variety of processes, which are used to regulate and manage the entire development life cycle. One of the main aspects to be considered during the preparation stage of software development is the selection of the right tools. Nowadays when software systems become more and more complex, an inappropriate selection of the tools may cause project not to succeed at all. That is why the main challenge of the industry is still aimed on the simplification, optimization, and automation of software development process. One of the ways to deal with an increasing complexity, as well as not to dig into the details of the source code, is to use modeling. A model-driven approach, mainly represented by OMG's Model Driven Architecture as the most advanced and popular one, purports to be the next evolutional milestone for the whole software industry. In fact, most of the tools currently available on the market are claimed as "MDA complaint," though have never been checked or analyzed for that compliance. Therefore, there should be a certification program defined to figure out the main features of each tool in accordance with OMG standards. The original article proposes a foundation for certification of MDA tools. In particular, this includes the specification of the most common features and options defined to clarify the accordance level of each tool from various perspectives.

show abstract

“…Another reason could be the lack of specific instructions on how to use MDA, which involves the low rate of adoption for MDA concepts by the software engineering industry, lack of transformation tools and integration between them (which is very essential if we think about usage in real projects) [3]. Also the transition to the model-driven software development process from currently used practices and methodologies is an issue.…”

Section: Introductionmentioning

confidence: 99%

Tool Integration to Support SPEM Model Transformations in Eclipse

Nikulsins¹,

Nikiforova²

2010

Scientific Journal of Riga Technical University. Computer Sciences

Self Cite

View full text Add to dashboard Cite

-This paper propose the approach for integrating SPEM modeling tools with the Query/View/Transformation (QVT) tools using Eclipse Modeling Framework (EMF). The aim of tool integration is to support the adoption of Model Driven Architecture within the organizations, which currently use "traditional" software development approaches. The software development process lifecycle of organization is supposed to be expressed with the help of OMG SPEM language. The approach presented in the paper is based on the model-level integration using EMF based interfaces, which will help to link the MOF based Ecore models with the QVT transformation tools. The outcomes of the work are: (i) the design of EMF based tool integration, (ii) solution prototype for Eclipse environment (iii) QVT Relations transformation rules. Model transformations are performed using mediniQVT tool, which is able to operate with the models expressed as Ecore metamodels and provides debugging features and transformation rules tracing. The QVT Relations transformations are applied to the source model, which corresponds to the "traditional" software development lifecycle. The outcome of such unidirectional transformation is the new software development process, which corresponds to the modeldriven software development process. The generated target model is SPEM compliant, and can be imported into the external tool supporting SPEM models in Ecore.

show abstract

Discussing the Difference between Model Driven Architecture and Model Driven Development in the Context of Supporting Tools

Cited by 8 publications

References 10 publications

Role of UML Class Diagram in Object-Oriented Software Development

Role of UML Class Diagram in Object-Oriented Software Development

On Foundation for Certification of Model Driven Architecture (MDA) Tools: Defining a Specification

Tool Integration to Support SPEM Model Transformations in Eclipse

Contact Info

Product

Resources

About