Viability for codifying and documenting architectural design decisions with tool support

Journal of Software Maintenance and Evolution

Volumn 22, Issue 2, 2010, Pages 81-119

  Capilla, Rafael ^a   Dueñas, Juan C ^b   Nava, Francisco ^a  

^a UNIVERSIDAD REY JUAN CARLOS   (Spain)

^b UNIVERSIDAD POLITÉCNICA DE MADRID   (Spain)

Author keywords

Architectural knowledge; Design decisions; Design rationale; Software architecture; Software maintenance; Traceability

Indexed keywords

ARTIFICIAL INTELLIGENCE; COMPUTER ARCHITECTURE; COMPUTER SOFTWARE MAINTENANCE; DECISION SUPPORT SYSTEMS; SOFTWARE ARCHITECTURE;

ARCHITECTURAL DESIGN DECISIONS; ARCHITECTURAL KNOWLEDGE; ARCHITECTURE PRACTICE; DESIGN DECISIONS; DESIGN RATIONALE; MAINTENANCE OPERATIONS; STANDARD ARCHITECTURE; TRACEABILITY;

ARCHITECTURAL DESIGN;

EID: 77749315848     PISSN: 1532060X     EISSN: 15320618     Source Type: Journal    
DOI: 10.1002/smr.419     Document Type: Article

References (54)

1. Bosch J. Design and use of software architectures. Adopting and Evolving a Product Line Approach. Addison-Wesley: Reading MA, 2000.
2. Tang A, Babar MA, Gorton I, Han JA. A survey of the use and documentation of architecture design rationale. Fifth IEEE/IFIP Working Conference on Software Architecture, 2005; 89-98.
3. Bosch J. Software architecture: The next step. Proceedings of the 1st European Workshop on Software Architecture (EWSA2004) (Lecture Notes in Computer Science, vol. 3047). Springer: Berlin, 2004; 194-199.
4. Bass L, Clements P, Kazman R. Software Architecture in Practice (2nd edn). Addison-Wesley Professional: U.S.A., 2003.
5. Perry DE, Wolf AL. Foundations for the study of software architecture. Software Engineering Notes. ACM SIGSOFT, 1992; 40-52.
6. Kruchten P, Lago P, van Vliet H. Building up and reasoning about architectural knowledge. QoSA2006. Springer: Berlin, 2006; 43-58.
7. Dingsøyr T. Knowledge management in medium-sized software consulting companies. Empirical Software Engineering 2002; 7(4):377-381.
8. Hansen MT, Nohria N, Tierney T. What's your strategy for managing knowledge. Harvard Business Review 1999; 54(7):106-116.
9. Dueñas JC, Capilla R. The decision view of software architecture. Proceedings of the 2nd European Workshop on Software Architecture (EWSA 2005) (Lecture Notes in Computer Science, vol. 3047). Springer: Berlin, 2005; 222-230.
10. Kruchten P. Architectural blueprints, the '4+1' view model of software architecture. IEEE Software 1995; 12(6):42-45.
11. Capilla R, Nava F, Pérez S, Dueñas JC. A web-based tool for managing architectural design decisions. SIGSOFT Software Engineering Notes 2006; 31(5):4. DOI: http://doi.acm.org/10.1145/1163514.1178644.
12. IEEE Recommended Practice for Architectural Description of Software-Intensive Systems. IEEE Std., 2000; 1471-2000.
13. Dutoit AH, McCall R, Mistrík I, Paech B. Rationale management in software engineering: Concepts and techniques. Rationale Management in Software Engineering, Dutoit AH, McCall R, Mistrík I, Paech B (eds.). Springer: Berlin, 2006; 1-48.
14. Tyree J, Akerman A. Architecture decisions: Demystifying architecture. IEEE Software 2005; 22(2):19-27.
15. Burge JE, Brown DC. Rationale-based support for software maintenance. Rationale Management in Software Engineering, Dutoit AH, McCall R, Mistrík I, Paech B (eds.). Springer: Berlin, 2006; 273-296.
16. Chapin N. Software maintenance types-A fresh view. Proceeding of the International Conference on Software Maintenance, 2000; 247-252.
17. Jansen A, Bosch J. Evaluation of tool support for architectural evolution. 19th International Conference on Automated Software Engineering (ASE'04), 2004; 375-378.
18. Li X, Adve SV, Bose P, Rivers JA. SoftArch: An architecture-level tool for modeling and analyzing soft errors. Dependable Systems and Networks, 28 June-1 July 2005; 496-505.
19. van Gurp J, Bosch J. Design erosion: Problems and causes. Journal of Systems and Software 2002; 61(2):105-119.
20. van der Ven JS, Jensen AGJ, Nijhuis JA, Bosch J. Rationale-based support for software maintenance. Rationale Management in Software Engineering, Dutoit AH, McCall R Mistrík I, Paech B (eds.). Springer: Berlin, 2006; 329-348.
21. Jansen A, van der Ven J, Avgeriuou P, Hammer DKJ. Tool support for architectural decisions. Sixth IEEE/IFIP Working Conference on Software Architecture, 2007; 44-53.
22. Rozanski N, Woods E. Software Systems Architecture. Addison-Wesley: Reading MA, 2005.
23. Woods E. Experiences using viewpoints for information systems architecture: An industrial experience report. Proceedings of the First European Workshop on Software Architecture (Lecture Notes in Computer Science, vol. 3047), Oquendo F (ed.). Springer: Berlin, 2004.
24. Clements P, Bachman F, Bass L, Garlan D, Ivers J, Little R, Nord R, Stafford J. Documenting software architectures. Views and Beyond. Addison-Wesley: Reading MA, 2003.
25. Tang A, Jin Y, Han J. A rationale-based architecture model for design traceability and reasoning. Journal of Systems and Software 2007; 80(6):918-934.
26. Ali-Babar M, Gorton I. A tool for managing software architecture knowledge. Proceedings of the Second Workshop on SHAring and Reusing Architectural Knowledge Architecture, Rationale, and Design Intent, ICSE Workshops (ICSEW'07). IEEE Computer Society: Silver Spring MD, 2007.
27. Ali-Babar M, Gorton I, Kitchenham B. A framework for supporting architecture knowledge and rationale management. Rationale Management in Software Engineering, Dutoit AH, McCall R, Mistrik I, Paech B (eds.). Springer: Berlin, 2006; 237-254.
28. Jansen A, Vries Td, Avgeriou P, Veelen Mv. Sharing the architectural knowledge of quantitative analysis. Proceedings of the Quality of Software-Architectures (QoSA 2008), 2008.
29. Buschmann F, Meunier R, Rohnert H, Sommerlad P, Stal M. Pattern-oriented software architecture. A System of Patterns. Wiley: New York, 1996.
30. Gamma E, Helm R, Johnson R, Vlissides J. Design Patterns-Elements of Reusable Object-oriented Software. Addison-Wesley: Reading MA, 1995.
31. Ecklund EF, Delcambre LML, Freiling MJ. Change cases: Use cases that identify future requirements. SIGPLAN Notices 1996; 31(10):342-358.
32. Lago P, van Vliet H. Explicit assumptions enrich architectural models. Proceedings 27th International Conference on Software Engineering. ACM: New York, 2005; 206-214.
33. Roeller R, Lago P, van Vliet H. Recovering architectural assumptions. The Journal of Systems and Software 2006; 79:552-573.
34. Uchitel S, Yankelevich D. Enhancing architectural mismatch detection with assumptions. Seventh IEEE International Conference and Workshop on the Engineering of Computer Based, Edinburgh, Scotland, 2000; 138-147.
35. Jansen A, Bosch J. Software architecture as a set of architectural design decisions. 5th IEEE/IFIP Working Conference on Software Architecture 2005; 109-118.
36. Akerman A, Tyree J. Using ontology to support the development of software architecture. IBM Systems Journal 2006; 45(4):813-826.
37. Kruchten P. An ontology of architectural design decisions in software-intensive systems. Proceedings of 2nd Groningen Workshop on Software Variability Management, 2004; 54-61.
38. Capilla R, Martínez M. Software architectures for designing virtual reality systems. Proceedings of the 1st European Workshop on Software Architecture (EWSA2004) (Lecture Notes in Computer Science, vol. 3047). Springer: Berlin, 2004; 135-147.
39. Capilla R, Nava F, Dueñas JC. Modeling and documenting the evolution of architectural design decisions. Proceedings of the Second Workshop on SHAring and Reusing Architectural Knowledge Architecture, Rationale, and Design Intent, ICSE Workshops (ICSEW'07). IEEE Computer Society: Silver Spring MD, 2007.
40. Capilla R, Nava F, Tang A. Attributes for characterizing the evolution of architectural design decisions. Proceedings of the 3rd International IEEE Workshop on Software Evolvability. IEEE Computer Society: Silver Spring MD, 2007.
41. Yin RK. Case Study Research: Design and Methods (3rd edn), vol.5. Sage Publications: Beverley Hills CA, 2002.
42. Knodel J, Lindvall M, Muthig D, Naab M. Static evaluation of software architectures. Tenth European Conference on Software Maintenance and Reengineering, 2006; 279-294.
43. Knodel J. Evolution support by recording architecture design decisions. Fraunhofer IESE Technical Report, IESE-Report 104.07E, version 1.0, 2007.
44. Capilla R, Nava F, Carrillo C. Effort estimation in capturing architectural knowledge. Automated Software Engineering (ASE'2008). IEEE Computer Society: Silver Spring MD, 2008.
45. Falessi D, Cantone G, Kruchten P. Do architecture design methods meet architect's needs, Seventh Working IEEE/IFIP Conference on Software Architecture (WICSA 2007), 2008; 5.
46. Capilla R, Nava F. Extending Software Architecting with Decision-making Activities. CEE-SET 2007. Springer: Berlin, 2007; 182-195.
47. Lago P, van Vliet H. Observations from the recovery of a software product family. Third Software Product Line Conference (SPLC) (Lecture Notes in Computer Science, vol. 3281). Springer: Berlin, 2004; 214-227.
48. Wang A, Sherdil K, Madhavji NH. ACCA: An architecture-centric concern analysis method. Fifth IEEE/IFIP Working Conference on Software Architecture, 2005; 99-108.
49. Ali-Babar M. The application of knowledge-sharing workspace paradigm for software architecture processes. Proceedings of the Third Workshop on SHAring and Reusing Architectural Knowledge Architecture. ACM DL: U.S.A., 2008; 45-48.
50. Farenhorst R, Izaks R, Lago P, van Vliet H. A just-in time architectural knowledge sharing portal. WICSA 2008. IEEE Computer Society: Silver Spring MD, 2008; 125-134.
51. Farenhorst R, Lago P, van Vliet H. Effective Tool Support for Architectural Knowledge Sharing. ECSA 2007. Springer: Berlin, 2007; 27-38.
52. Fritsch C, Lehn A, Strohm T. Evaluating variability implementation mechanisms. International Workshop on Product Line Engineering the Early Steps (PLEES2002). Fraunhofer IESE Technical Report 056.02/E, 2002; 59-64.
53. Lee K, Kang K. Feature dependency analysis for product line component design. International Conference on Software Reuse (Lecture Notes in Computer Science, vol. 3107). Springer: Berlin, 2004; 69-85.
54. van Gurp J, Bosch J, Svahnberg M. On the notion of variability in software product lines. WICSA, 2001.