Abstract
The practical rationale for architecture design and description of software-based systems were inquired in three software-producing organizations. In addition to the traditional programming-in-the-large view that dominates the mainstream research on software architecture, this grounded-theory based study suggests that other important purposes for software architecture, especially such related to decision-making and mutual understanding among the stakeholders of software development, exist as well in practice. Their emergence depends on several factors associated with the software development organization in question: such as the variety of customers and other stakeholders, the characteristics of software products, and the nature of the business.
The updated original online version for this book can be found at DOI: 10.1007/978-0-387-35607-5_15
Chapter PDF
Similar content being viewed by others
Key words
References
Bass, L., P. Clements and R. Kazman (1998). Software Architecture in Practice,Addison-Wesley.
Bosch, J. (2000). Design and Use of Software Architectures: Adopting and Evolving a Product-Line Approach,Addison-Wesley.
Conklin, J. (1989). “Design Rationale and Maintainability”, Proceedings of the Twenty-Second Annual Hawaii International Conference on System Sciences, 3-6 Jan 1989, Kailua-Kona, HI, USA, 533 - 539.
DeRemer, F. and H. H. Kron (1976). “Programming-in-the-Large Versus Programming-in-the-Small”. IEEE Transactions on Software Engineering SE-2(2): 80-86.
Garlan, D. (2000). “Software Architecture: a Roadmap”. The Future of Software Engineering. A. Finkelstein, ACM Press.
Grinter, R. E. (1999). “Systems Architecture: Product Designing and Social Engineering”. ACM SIGSOFT Software Engineering Notes 24 (2): 11 - 18.
Hofmeister, C., R. Nord and D. Soni (1999). Applied Software Architecture. Reading, MA, Addison-Wesley.
IEEE (2000). IEEE Recommended Practice for Architectural Description of Software-Intensive Systems, IEEE, IEEE Std 1471 - 2000.
Kazman, R., P. Kruchten, C. Verhoef and H. van Vliet, Eds. (2001). Proceedings of the Working IEEE/IFIP Conference on Software Architecture, WICSA2001, Amsterdam, The Netherlands, 28-31 August 2001. Los Alamitos, CA, IEEE Computer Society.
Kruchten, P. (1999). “The Software Architect - and the Software Architecture Team”, Proceedings of WICSAI: 1st Working IFIP Conference on Software Architecture, San Antonio, TX, USA, 22-24 Feb 1999, Kluwer Academic Publishers, 565-583.
Kruchten, P. B. (1995). “The 4+1 View Model of Architecture”. IEEE Software 12 (6): 42 - 50.
Medvidovic, N. and R. N. Taylor (2000). “A Classification and Comparison Framework for Software Architecture Description Languages”. IEEE Transactions on Software Engineering 26 (1): 70 - 93.
Miles, M. B. and A. M. Huberman (1984). Qualitative Data Analysis: A Sourcebook of New Methods. Beverly Hills, Sage.
Potts, C. and G. Bruns (1988). “Recording The Reasons for Design Decisions”, Proceedings of The 10th International Conference on Software Engineering, Singapore, 418-427.
Robbins, J. E. and D. F. Redmiles (1998). “Software Architecture Critics in the Argo Design Environment”. Knowledge-Based Systems 11 (1): 47 - 60.
Schön, D. (1983). The Reflective Practitioner: How Professionals Think in Action. New York, Basic Books.
Shaw, M. (2001). “The Coming-of-Age of Software Architecture Research”, Proceedings of the 23rd International Conference on Software Engineering (ICSE 2001), 657 - 664a.
Smolander, K., K. Hoikka, J. Isokallio, M. Kataikko and T. Mäkelä (2002). “What is Included in Software Architecture? A Case Study in Three Software Organizations”, Proceedings of 9th annual IEEE Conference and Workshop on Engineering of Computer-Based Systems, Apr 8-11 2002, Lund, Sweden.
Smolander, K. and T. Päivärinta (2002). “Describing and Communicating Software Architecture in Practice: Observations on Stakeholders and Rationale”, CAiSE’02 - The Fourteenth International Conference on Advanced Information Systems Engineering, May 27-31, 2002, Toronto, Ontario, Canada.
Strauss, A. L. and J. Corbin (1990). Basics of Qualitative Research: Grounded Theory Procedures and Applications. Newbury Park, CA, Sage Publications.
Zachman, J. A. (1987). “A Framework for Information Systems Architecture”. IBM Systems Journal 26 (3).
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2002 IFIP International Federation for Information Processing
About this chapter
Cite this chapter
Smolander, K., Päivärinta, T. (2002). Practical Rationale for Describing Software Architecture. In: Bosch, J., Gentleman, M., Hofmeister, C., Kuusela, J. (eds) Software Architecture. WICSA 2002. IFIP — The International Federation for Information Processing, vol 97. Springer, Boston, MA. https://doi.org/10.1007/978-0-387-35607-5_7
Download citation
DOI: https://doi.org/10.1007/978-0-387-35607-5_7
Publisher Name: Springer, Boston, MA
Print ISBN: 978-1-4757-6538-0
Online ISBN: 978-0-387-35607-5
eBook Packages: Springer Book Archive