Architecting for evolvability by means of traceability and features

Aramis 2008 - 1st International Workshop on Automated engineeRing of Autonomous and runtiMe evolvIng Systems, and ASE2008 the 23rd IEEE/ACM Int. Conf. Automated Software Engineering

Volumn , Issue , 2008, Pages 72-81

  Brcina, Robert ^a   Riebisch, Matthias ^a  

^a ILMENAU UNIVERSITY OF TECHNOLOGY   (Germany)

Author keywords

[No Author keywords available]

Indexed keywords

ARCHITECTURAL MODELS; ARCHITECTURAL QUALITIES; DESIGN DECISIONS; EVOLVABILITY; FEATURE MODELS; IT INFRASTRUCTURES; LARGE SOFTWARE SYSTEMS; PROBLEM RESOLUTIONS; SOFTWARE PROJECTS; SOFTWARE SYSTEMS;

AUTOMATION; COMPUTER SOFTWARE; COMPUTER SOFTWARE SELECTION AND EVALUATION; SOFTWARE ENGINEERING; TECHNICAL PRESENTATIONS;

ARCHITECTURAL DESIGN;

EID: 58049183468     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ASEW.2008.4686323     Document Type: Conference Paper

References (29)

1. IEEE standard glossary of software engineering terminology. Technical report, 1990.
2. Maintenance of operational systems - an overview. Carnegie Mellon University, SEI; published online at http://www.sei.cmu.edu/str/descriptions/ mos.html. 01 1997.
3. K. Beck. Extreme Programming Explained: Embrace Change. Addison-Wesley Professional, October 1999.
4. P. Bengtsson, N. Lassing, J. Bosch, and H. van Vliet. Architecture-level modifiability analysis (ALMA). J. Syst. Softw., 69(1-2):129-147, 2004.
5. F. P. Brooks. The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley, 1995.
6. D. Coleman, D. Ash, B. Lowther, and P. Oman. Using metrics to evaluate software system maintainability. Computer, 27(8):44-49, 1994.
7. L. Davis and R. F. Gamble. Identifying evolvability for integration. In ICCBSS '02: Proceedings of the First International Conference on COTS-Based Software Systems, pages 65-75, London, UK, 2002. Springer-Verlag.
8. M. Eaddy and A. Aho. Towards assessing the impact of crosscutting concerns on modularity. In AOSD Workshop on Assessment ofAspect Techniques (ASAT 2007), page 3, Vancouver, BC, Canada, March 12, 2007.
9. M. Eaddy, A. Aho, and G. C. Murphy. Identifying, assigning, and quantifying crosscutting concerns. In ACoM '07: Proceedings of the First International Workshop on Assessment of Contemporary Modularization Techniques, page 2, Washington, DC, USA, 2007. IEEE Computer Society.
10. A. Egyed. A scenario-driven approach to traceability. IEEE, ICSE'01, 23rd International Conference on Software Engineering, 2001.
11. E. Figueiredo, C. Sant'Anna, A. Garcia, T. T. Bartolomei, W. Cazzola, and A. Marchetto. On the maintainability of aspect-oriented software: A concern-oriented measurement framework. In CSMR, pages 183-192, 2008.
12. M. Fowler. Improving the design of existing code. Addison Wesley, Longman, Inc., 1999.
13. K. Kang, S. Cohen, J. Hess, W. Novak, and A. Peterson. Feature-oriented domain analysis (FODA) feasibility study. Technical Report CMU/SEI-90-TR-021, SEI Institute, Carnegie Mellon University, 1990.
14. H. Ossher and P. Tarr. Software Architectures and Component Technology, chapter Multi-Dimensional Separation of Concerns and the Hyper- space Approach. Kluwer Academic Publishers, 2001.
15. D. L. Parnas. On the criteria to be used in decomposing systems into modules. Commun. ACM, 15(12):1053-1058, 1972.
16. F. A. C. Pinheiro. Requirements traceability. In Requirements traceability in Perspectives on Software Requirements. Julio C. S. P. Leite and Jorge Doom, Kluwer Academic Publishers, pp 91-113, 2004.
17. F. A. C. Pinheiro and J. Goguen. An object-oriented tool for tracing requirements. IEEE Software, 13(2):52-66, 1996.
18. K. Pohl. PRO-ART: Enabling requirements Pre-traceability. ICRE, 00:76, 1996.
19. K. Pohl, G. Böckle, and F. van der Linden. Software Product Line Engineering;Foundations, Principles, and Techniques. Springer-Verlag Berlin Heidelberg, 2005.
20. V. T. Rajlich and K. H. Bennett. A staged model for the software life cycle. Computer, 33(7):66-71, 2000.
21. B. Ramesh and M. Jarke. Toward reference models for requirements traceability. IEEE Trans. Softw. Eng., 27(1):5893, 2001.
22. W. Reimann. Building enterprise applications with an integrated application Platform. Erfurt, Germany, September. NET.ObjectDays Conference, 2004.
23. M. Riebisch. Supporting evolutionary development by feature models and traceability links. IEEE International Conference on Engineering of Computer-Based Systems, 00:370, 2004.
24. M. Riebisch and R. Brcina. Optimizing design for variability using traceability links. 15th IEEE International Conference on Engineering ofComputer-Based Systems, 0:235-244, 2008.
25. J. Rumbaugh, I. Jacobson, and G. Booch. Unified Modeling Language Reference Manual, The (2nd Edition) (Addison-Wesley Object Technology Series). Addison-Wesley Professional, 2004.
26. P. Sochos. The Feature-Architecture Mapping Method for Feature-Oriented Development of Software Product Lines. PhD thesis, Technical University of Ilmenau, Germany, 2006.
27. D. Streitferdt, M. Riebisch, and I. Philippow. Details of formalized relations in feature models using OCL. IEEE International Conference on Engineering of Computer-Based Systems, 2003.
28. K. van den Berg, J. M. Conejero, and I. Hern'andez. Analysis of crosscutting across software development phases based on traceability. In EA '06 Proceedings of the 2006 international workshop on Early aspects at ICSE, pages 43-50, New York, NY, USA, 2006. ACM.
29. D. Vogler. Design and implementation of an extensible java framework based on an ontology knowledge base to support software comprehension. Master's thesis, Brunel University, West London, 2007.