An Architecture for Toolbox-based Software Architecture Reconstruction Solution


Published on

The Slide has been Presented on Modellbasierte und modellgetriebene Softwaremodernisierung - MMSM 2014
19. March 2014 - Universität Wien by M Firdaus Harun

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

An Architecture for Toolbox-based Software Architecture Reconstruction Solution

  1. 1. An Architecture for Toolbox-based Software Architecture Reconstruction Solutions Ana Dragomir, M. Firdaus Harun and Horst Lichter {ana.dragomir, firdaus.harun, horst.lichter} • Motivation • Related Work • Current State of the Practice • Improvement Potentials • Our Vision - ARAMIS • An ARAMIS Instantiation
  2. 2. • Up-to-date architecture views aid software architecture migration and modernization activities. • Understanding the dependencies of the various software systems and internals of each system in isolation. • Experience with 2 industry cooperation partners • Continuous effort to ensure the consistencies between intended architectures and implemented architectures. Motivation
  3. 3. • High-level architectural elements and communication rules between them • Software architecture metrics • Evolution of reconstructed architecture Related Work
  4. 4. Current State-of-the-Practice Large Company SME Company • >1000 IT employees • CMMI level 3 certified • Insurance • >200 developers • Employ internal process • Energy management consultation • Missing traceability links: Architecture decisions documentation unconnected to architecture documentation. • Architecture reconstruction and monitoring not employed: Manual maintenance in visualizing information flows between applications. • Missing traceability links: Architecture documentation and software artifacts / source code were unconnected. • Different terminologies: The terminology imposed by the employed architecture reconstruction tool lead to misunderstandings (it was not accepted by the architects). 2 Industry Cooperation Partners
  5. 5. 6 Improvement Potentials Traceability Links Common Terminology Metrics Variant Building Scalability and Heterogeneity
  6. 6. Our Vision … Architecture Monitoring and Analysis Infrastructure (ARAMIS) • Architecture Information Collector • Extract and abstract software artifacts from heterogeneous software landscape. • Architecture Repository • Store the collected information. • Architecture Information Provider • Provide relevant data or information to specified plugins. • Architecture Modeling Language Family • Corpus of various architecture description languages used in various projects (and their relations).
  7. 7. ARAMIS Instantiation ARAMIS-Run Time Running Software System Aspect Weaver Instrumented Running Software System Web-based Visualization Architectural Enhancer Violation Detector Java System Java Architecture Information Collector Architecture Modelling Language Sequence Diagram Visualization Plug-inViolation Analysis Plug-in Architecture Information Provider
  8. 8. • Aim: to improve the state-of-the art of architecture reconstructions and to achieve a better industry acceptance thereof. Summary Thank you for your attention …any questions?
  9. 9. • A. Dragomir, F. Harun, H. Lichter (2014): On Bridging the Gap between Practice and Vision for Software Architecture Reconstruction and Evolution- A Tool Perspective. In SAEroCon, First Workshop on Software Architecture Erosion and Architectural Consistency, co- located with the Working IEEE/IFIP Conference on Software Architecture (WICSA) 2014, Sydney, Australia, April 8, 2014. • A. Dragomir, H. Lichter (2013): Run-time Monitoring and Real-time Visualization of Software Architectures. In 20th Asia-Pacific Software Engineering Conference (APSEC 2013),Pullman Bangkok King Power Hotel, Bangkok, Thailand, December 2-5, 2013 (to be published). • A. Dragomir, H. Lichter (2012): Model-Based Software Architecture Evolution and Evaluation. In Software Engineering Conference (APSEC), 2012 19th Asia-Pacific, Vol. 1, 697-700. Reference