In Model Driven Engineering, traceability is used to establish relationships between various software artifacts during the software life cycle. Traceability can be also used to define dependencies between related elements in different models, to propagate and verify properties from one model to another and to analyze the impact of changes. In this paper we describe how to define typed trace-links between different kinds of models in our model transformation chain PUMA4SOA, which generates Layered Queuing performance models from UML software models of service-oriented applications. The goal of PUMA4SOA is to help evaluate the performance of SOA systems in the early development phases. In our approach, the traceability links are stored externally in a new model, which maintain traces separately from the source and target models they refer to. We illustrate how traceability links can be used to propagate the results of the performance model back to the original software model.

Additional Metadata
Keywords Aspect-oriented modeling, Model transformation, Performance Analysis, SOA, Software Performance Engineering, Trace-Links, Traceability
Persistent URL dx.doi.org/10.1007/978-3-642-38911-5_12
Citation
Alhaj, M. (Mohammad), & Petriu, D. (2013). Traceability links in model transformations between software and performance models. doi:10.1007/978-3-642-38911-5_12