DMCA
Using AADL in Model Driven Development (2007)
| Venue: | IEEE-SEE Intl. Workshop on UML and AADL 2007, Intl. Conf. on Eng. Complex Computer Systems (ICECCS07 |
| Citations: | 2 - 0 self |
BibTeX
@INPROCEEDINGS{Delanote07usingaadl,
author = {Didier Delanote and Stefan Van Baelen and Wouter Joosen and E Berbers},
title = {Using AADL in Model Driven Development},
booktitle = {IEEE-SEE Intl. Workshop on UML and AADL 2007, Intl. Conf. on Eng. Complex Computer Systems (ICECCS07},
year = {2007}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
Software-intensive systems require the verification of functional and non-functional properties before the implementation and integration phases of the development process. In recent trends, the Architecture Analysis and Design Language (AADL) has proven a good candidate as a modeling language for software-intensive systems. At the same time, Model Driven Development (MDD) is gaining popularity as a development process. In this paper, we explore the use of AADL in a model driven development process from a usability point of view. Three issues regarding the usability of AADL as a modeling language for software-intensive systems are identified, namely system versus software level, complex component composition and property ambiguity. For resolving these issues, an approach is presented through integration of AADL models in a model driven development process with specifically designed model transformations. This approach enhances the usability of AADL for software developers.*
Keyphrases
model driven development development process software-intensive system modeling language recent trend model transformation aadl model usability point complex component composition non-functional property property ambiguity architecture analysis system versus software level integration phase good candidate software developer design language
