Forces on architecture decisions - A viewpoint

Proceedings of the 2012 Joint Working Conference on Software Architecture and 6th European Conference on Software Architecture, WICSA/ECSA 2012

Volumn , Issue , 2012, Pages 101-110

  Van Heesch, Uwe ^a   Avgeriou, Paris ^a   Hilliard, Rich ^b  

^a UNIVERSITY OF GRONINGEN   (Netherlands)

^b University of Groningen ^*

Author keywords

architecture decisions; forces; ISO IEC IEEE 42010; Software architecture

Indexed keywords

ARCHITECTURE DECISIONS; ARCHITECTURE DESCRIPTION; FORCES; INDUSTRIAL CUSTOMER; ISO/IEC/IEEE 42010; SOFTWARE ENGINEERING STUDENTS; SOFTWARE PROJECT;

SOFTWARE ARCHITECTURE;

EID: 84870673254     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/WICSA-ECSA.212.18     Document Type: Conference Paper

References (26)

1. P. Kruchten, "An ontology of architectural design decisions in software intensive systems," in Proceedings of the 2nd Groningen Workshop on Software Variability, 2004, pp. 54-61.
2. J. Tyree and A. Akerman, "Architecture Decisions: Demystifying Architecture," IEEE Software, vol. 22, no. 2, pp. 19-27, 2005.
3. U. van Heesch, P. Avgeriou, and R. Hilliard, "A documentation framework for architecture decisions," Journal of Systems and Software, vol. 85, no. 4, pp. 795-820, 2012.
4. ISO/IEC/IEEE 42010, Systems and software engineering - Architecture description, ISO, December 2011.
5. D. Perry and A. Wolf, "Foundations for the study of software architecture," ACM SIGSOFT Software Engineering Notes, vol. 17, no. 4, pp. 40-52, 1992.
6. P. Kruchten, "The 4+ 1 View Model of Architecture," IEEE Software, vol. 12, no. 6, pp. 42-50, 1995.
7. IEEE Std 1471-2000, IEEE Recommended Practice for Architectural Description of Software-Intensive Systems, IEEE, October 2000.
8. F. Buschmann, R. Meunier, H. Rohnert, P. Sommerlad, and M. Stal, Pattern-oriented software architecture: a system of patterns. John Wiley & Sons, Inc. New York, NY, USA, 1996.
9. G. Mustapic, A. Wall, C. Norstrom, I. Crnkovic, K. Sandstrom, J. Froberg, and J. Andersson, "Real world influences on software architecture- interviews with industrial system experts," in Fourth Working IEEE/IFIP Conference on Software Architecture, 2004. WICSA 2004. IEEE, 2004, pp. 101-111.
10. P. Runeson and M. Höst, "Guidelines for conducting and reporting case study research in software engineering," Empirical Software Engineering, vol. 14, no. 2, pp. 131-164, 2009.
11. R. K. Yin, Case Study Research: Design and Methods, Applied Social Research Methods Series, Vol 5, 5th ed. Sage Inc., 2009.
12. C. Robson, Real world research. Wiley, 2011.
13. J. Carver, L. Jaccheri, S. Morasca, and F. Shull, "A checklist for integrating student empirical studies with research and teaching goals," Empirical Software Engineering, vol. 15, no. 1, pp. 35-59, 2010.
14. R. Stake, The art of case study research. Sage Publications, Inc, 1995.
15. J. Kontio, J. Bragge, and L. Lehtola, "The focus group method as an empirical tool in software engineering," Guide to advanced empirical software engineering, pp. 93-116, 2008.
16. B. Glaser and A. Strauss, The Discovery of Grounded Theory: Strategies for Qualitative Research. Aldine Publishing Company, 1967.
17. S. Adolph, W. Hall, and P. Kruchten, "Using grounded theory to study the experience of software development," Empirical Software Engineering, vol. 16, no. 4, pp. 487-513, 2011.
18. C. Urquhart, H. Lehmann, and M. Myers, "Putting the theory back into grounded theory: guidelines for grounded theory studies in information systems," Information systems journal, vol. 20, no. 4, pp. 357-381, 2010.
19. C. Wohlin, M. Hoest, P. Runeson, M. Ohlsson, B. Regnell, and A. Wesslén, Experimentation in software engineering: an introduction. Kluwer Academic Pub, 2000.
20. N. Mack, C. Woodsong, K. MacQueen, G. Guest, and E. Namey, Qualitative research methods: A data collector's field guide. FLI, 2005.
21. T. Lethbridge, S. Sim, and J. Singer, "Studying Software Engineers: Data Collection Techniques for Software Field Studies," Empirical Software Engineering, vol. 10, no. 3, pp. 311-341, 2005.
22. P. Avgeriou, J. Grundy, J. Hall, P. Lago, and I. Mistrik, Relating Software Requirements and Architectures. Springer Publishing Company, Incorporated, 2011.
23. O. Gotel and C. Finkelstein, "An analysis of the requirements traceability problem," in Proceedings of the First International Conference on Requirements Engineering. IEEE, 1994, pp. 94-101.
24. B. Ramesh and M. Jarke, "Toward reference models for requirements traceability," IEEE Transactions on Software Engineering, vol. 27, no. 1, pp. 58-93, 2001.
25. I. Malavolta, H. Muccini, and V. Smrithi Rekha, "Supporting architectural design decisions evolution through model driven engineering," Software Engineering for Resilient Systems, pp. 63-77, 2011.
26. A. Tang, Y. Jin, and J. Han, "A rationale-based architecture model for design traceability and reasoning," Journal of Systems and Software, vol. 80, no. 6, pp. 918-934, 2007.