Transformation and composition of software design models for Model Driven Development

Dulani Apeksha Meedeniya, Galhenage Indika Udaya Shantha Perera, Juliana Kuster Filipe Bowles

Research output: Chapter in Book/Report/Conference proceedingConference contribution

2 Citations (Scopus)
2 Downloads (Pure)

Abstract

Software models play a significant role with the growth of software system development based on Model Driven Development (MDD) approach. Model transformations and compositions are the heart of MDD and allow the development of complex systems and their automated derivation. Moreover, software development of large and complex systems uses a collection of models, where model composition and decomposition are required. Various research studies have been done on specifying and executing MDD processes; however only a few of those have considered the validity of such transformations, thus safe composition and decomposition of models. This paper presents a general approach for model composition for the transformation from UML sequence diagrams to Coloured Petri Nets and validates the correctness of model composition using a mathematical proof. These transformations are based on formal rules, which have already been proven to be strongly consistent.
Original languageEnglish
Title of host publicationProceedings 2015 IEEE 10th International Conference on Industrial and Information Systems (ICIIS)
PublisherIEEE
Pages31-36
ISBN (Print)9781509017416
DOIs
Publication statusPublished - 18 Dec 2015
Event2015 IEEE 10th International Conference on Industrial and Information Systems (ICIIS) - Peradeniya, Sri Lanka
Duration: 17 Dec 201520 Dec 2015

Conference

Conference2015 IEEE 10th International Conference on Industrial and Information Systems (ICIIS)
Country/TerritorySri Lanka
CityPeradeniya
Period17/12/1520/12/15

Keywords

  • UML sequence diagram
  • Colour Petri net
  • Model transformation
  • Model composition

Fingerprint

Dive into the research topics of 'Transformation and composition of software design models for Model Driven Development'. Together they form a unique fingerprint.

Cite this