From analysis model to software architecture: a PIM2PIM mapping

Authors:
Jorge Enrique Pérez-Martínez;Almudena Sierra-Alonso
Affiliations:
Departamento de Informática Aplicada, Universidad Politécnica de Madrid, Madrid, Spain;Escuela Politécnica Superior, Universidad Autónoma de Madrid, Madrid, Spain
Venue:
ECMDA-FA'06 Proceedings of the Second European conference on Model Driven Architecture: foundations and Applications
Year:
2006

Citing 7
Cited 1

Software architecture: perspectives on an emerging discipline

Software architecture: perspectives on an emerging discipline
Objects, components, and frameworks with UML: the catalysis approach

Objects, components, and frameworks with UML: the catalysis approach
The unified software development process

The unified software development process
Embracing Change with Extreme Programming

Computer
Architecture-based specification-time software evolution

Architecture-based specification-time software evolution
Software Engineering (7th Edition)

Software Engineering (7th Edition)
MDA Distilled

MDA Distilled

Supporting consistency between architectural design decisions and component models through reusable architectural knowledge transformations

ECSA'13 Proceedings of the 7th European conference on Software Architecture

Quantified Score

Hi-index	0.00

Visualization

Abstract

To our knowledge, no current software development methodology explicitly describes how to transit from the analysis model to the software architecture of the application. This paper presents a method to derive the software architecture of a system from its analysis model. To do this, we are going to use MDA. Both the analysis model and the architectural model are PIMs described with UML 2. The model type mapping designed consists of several rules (expressed using OCL and natural language) that, when applied to the analysis artifacts, generate the software architecture of the application. Specifically the rules act on elements of the UML 2 metamodel (metamodel mapping). We have developed a tool (using Smalltalk) that permits the automatic application of these rules to an analysis model defined in RoseTM to generate the application architecture expressed in the architectural style C2.