Adapting Software Development Process towards the Model Driven Architecture

Nikulsins, Vladimirs; Nikiforova, Oksana

doi:10.1109/icsea.2008.25

Cited by 7 publications

(4 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The pervasive software development method requires that activities and technological choices should be familiar to the developers and be usable to the target project. On the other hand, the MDA does not give fixed guidelines in the aspect of software development processes such as activities and phases, roles and responsibilities [10].…”

Section: Discussionmentioning

confidence: 99%

“…"Refined" means that these methods are good and necessary complements for the traditional methods. Refined methods include: The model driven architecture (MDA) method [10] [5] [11], the agile methods [3] [12], the collaborative software engineering [13], the component library-based software development method [14], the opportunistic software development method [15] [16], the metadesign [17], the flexible software development method [18] [19] [20].…”

Section: Refined Software Development Methodsmentioning

confidence: 99%

See 1 more Smart Citation

Pervasive software development method

Wang

Tuo

2010

2010 3rd International Conference on Computer Science and Information Technology

View full text Add to dashboard Cite

Software development methods aim at solving the software crisis. Many presented methods gain reputations under special application environments. There are so many kinds of methods that developers are troubled when choosing the most suitable one. This article presents a pervasive software development method aiming at helping developers deal with the trouble. The pervasive method advocates logicality, comprehensiveness, flexibility and self-improvement as development guidelines. Logicality consists of business logic, functional logic and data logic; comprehensiveness clarifies advantages and shortcomings for a development; flexibility benefits developers in a variable or uncertain environment;self-improvement assures selection suitability to development processes and tools. The article compares solutions by the object-oriented method and the pervasive method in a web application as a paradigm. The paradigm shows that the pervasive method helps to decrease development cost.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Refined Software Development Methodsmentioning

confidence: 99%

Pervasive software development method

Wang

Tuo

2010

2010 3rd International Conference on Computer Science and Information Technology

View full text Add to dashboard Cite

show abstract

“…Along time, there was an evolution of concepts, models, processes and techniques in the area of Software Engineering, however, some problems still remain, namely: (i) portability due to update or frequently modification technology, (ii) interoperability, since there is a difficulty in communicating between systems, and (iii) documentation and maintenance, because of the documentation does not have any influence on code and vice versa, and (iv) productivity because developers often considers that code to be more productive than elaborate models and documentation [12], therefore hampering the development of software products with quality. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page.…”

Section: Introductionmentioning

confidence: 98%

Qualitas

Almeida

Oliveira

2014

Proceedings of the 7th Euro American Conference on Telematics and Information Systems

View full text Add to dashboard Cite

Software Engineering has as objective the development of software products that meet customer needs. For this, there are new approaches to development and testing of software, such as Model-Driven Development (MDD) and the Model Driven Testing (MDT), which aim to shift the focus of development and software testing for models and their transformations, and no longer in programming languages. This paper aims to propose a process model driven software development model by allowing tests accompany every stage of this, adding quality to the developed software. Categories and Subject Descriptors K.6.3 [Management of Computing and InformationSystems]: Software Management -software development, software process. General TermsVerification. KeywordsModel Process; Model-Driven Development (MDD); Model Driven Testing (MDT).

show abstract

“…The authors of this paper already concentrated their efforts on MDA integration into the traditional software development lifecycle from methodological point of view [8] - [10]. Software development activities, workflows and software development team organization were also analyzed in the previous researches [11], [12].…”

Section: A Related Workmentioning

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

Adapting Software Development Process towards the Model Driven Architecture

Cited by 7 publications

References 2 publications

Pervasive software development method

Pervasive software development method

Qualitas

Tool Integration to Support SPEM Model Transformations in Eclipse

Contact Info

Product

Resources

About