TY - CHAP
T1 - Transformation-Wise Design of Software Architectures
AU - Gilson, Fabian
AU - Englebert, Vincent
PY - 2015
Y1 - 2015
N2 - Stakeholders have to face requirements in increasing number and complexity, and the link between these requirements and design artifacts is primordial. Agile design methods and documentation techniques have emerged in the past years in order to trace the decision process and the rationale sustaining a software model. The present work proposes an integrated framework combining system requirement definitions, component-based models and model transformations. Architecturally significant requirements are explicitly linked to software architecture elements and iteratively refined or implemented by model transformations. Any transformation must be documented, even briefly, and the framework retains the transformations tree. This way, the iterative decision and design processes are completely documented for future reference or modification, i.e, designers can (i) see the mapping between a system requirement and its implementation in the architecture model, (ii) explore design alternatives or apply structural modifications without losing previous versions of the model, and finally (iii) at least understand partially the reasons why the model is how it is.
AB - Stakeholders have to face requirements in increasing number and complexity, and the link between these requirements and design artifacts is primordial. Agile design methods and documentation techniques have emerged in the past years in order to trace the decision process and the rationale sustaining a software model. The present work proposes an integrated framework combining system requirement definitions, component-based models and model transformations. Architecturally significant requirements are explicitly linked to software architecture elements and iteratively refined or implemented by model transformations. Any transformation must be documented, even briefly, and the framework retains the transformations tree. This way, the iterative decision and design processes are completely documented for future reference or modification, i.e, designers can (i) see the mapping between a system requirement and its implementation in the architecture model, (ii) explore design alternatives or apply structural modifications without losing previous versions of the model, and finally (iii) at least understand partially the reasons why the model is how it is.
KW - Design method
KW - Design rationale
KW - Model transformation
KW - Software architecture
KW - Traceability
UR - http://www.scopus.com/inward/record.url?scp=84952017492&partnerID=8YFLogxK
U2 - 10.1007/978-3-319-25156-1_4
DO - 10.1007/978-3-319-25156-1_4
M3 - Chapter (peer-reviewed)
AN - SCOPUS:84952017492
SN - 978-3-319-25155-4
VL - 506
T3 - Communications in Computer and Information Science
SP - 49
EP - 65
BT - Communications in Computer and Information Science
A2 - Hammoudi, Slimane
A2 - Ferreira Pires, Luís
A2 - Filipe, Joaquim
A2 - das Neves, Rui César
PB - Springer Verlag
T2 - 2nd International Conference on Model-Driven Engineering and Software Development, MODELSWARD 2014
Y2 - 7 January 2014 through 9 January 2014
ER -