The loss of architectural knowledge during system evolution: An industrial case study

IEEE International Conference on Program Comprehension

Volumn , Issue , 2009, Pages 188-197

  Feilkas, Martin ^a   Ratiu, Daniel ^a   Jürgens, Elmar ^a  

^a TECHNICAL UNIVERSITY OF MUNICH   (Germany)

Author keywords

[No Author keywords available]

Indexed keywords

ARCHITECTURAL KNOWLEDGE; IMPLICIT KNOWLEDGE; INDUSTRIAL CASE STUDY; INDUSTRIAL PROJECTS; NONCONFORMANCES; RESEARCH QUESTIONS; SOURCE CODES; SYSTEM EVOLUTION; SYSTEM STRUCTURES;

RESEARCH;

EID: 70349978552     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ICPC.2009.5090042     Document Type: Article

References (14)

1. M. A. Babar, R. C. de Boer, T. Dingsoyr, and R. Farenhorst. Architectural knowlege management strategies: Approaches in research and industry. In SHARK-ADI, page 2, Washington, DC, USA, 2007. IEEE CS.
2. F. Deissenboeck, E. Juergens, B. Hummel, S.Wagner, B. M. y Parareda, and M. Pizka. Tool support for continuous quality control. IEEE Software, 25(5):60-67, 2008.
3. M. Eichberg, S. Kloppenburg, K. Klose, and M. Mezini. Defining and continuous checking of structural program dependencies. In ICSE, pages 391-400, New York, NY, USA, 2008. ACM.
4. R. Fiutem and G. Antoniol. Identifying design-code inconsistencies in object-oriented software: a case study. In ICSM '98, page 94, Washington, DC, USA, 1998. IEEE CS.
5. D. Garlan. Software architecture: a roadmap. In ICSE, pages 91-101, New York, NY, USA, 2000. ACM.
6. M. T. Hansen, N. Nohria, and T. Tierney. What's your strategy for managing knowledge? Harvard Business Review 77 (2), pages 106-16, 1999.
7. E. Koutsofios and S. North. Drawing graphs with dot, 1993.
8. A. Mattsson, B. Lundell, B. Lings, and B. Fitzgerald. Experiences from representing software architecture in a large industrial project using model driven development. In SHARK-ADI, Washington, DC, USA, 2007. IEEE CS.
9. G. C. Murphy, D. Notkin, and K. J. Sullivan. Software reflexion models: Bridging the gap between design and implementation. IEEE Trans. Softw. Eng., 27(4):364-380, 2001.
10. S. Ornburn and S. Rugaber. Reverse engineering: resolving conflicts between expected and actual software designs. CSM'92, pages 32-40, Nov 1992.
11. D. E. Perry and A. L. Wolf. Foundations for the study of software architecture. SIGSOFT Softw. Eng. Notes, 17(4):40-52, 1992.
12. R. Tvedt, P. Costa, and M. Lindvall. Does the code match the design? a process for architecture evaluation. In ICSM '02, page 393, Washington, DC, USA, 2002. IEEE CS.
13. J. van Gurp and J. Bosch. Design erosion: problems and causes. J. Syst. Softw., 61(2):105-119, 2002.
14. J. van Gurp, S. Brinkkemper, and J. Bosch. Design preservation over subsequent releases of a software product: a case study of baan erp: Practice articles. J. Softw. Maint. Evol., 17(4):277-306, 2005.