What is included in software architecture? A case study in three software organizations

Software architecture is conventionally concerned with the structures at a high abstraction level describing the main constituents of a software system. However, there seems to be no common agreement of what these structures exactly are. This paper acts as an attempt to understand how the viewpoints from which we see the structures are selected. The rationale of having different viewpoints is reflected and a framework of the relationship between software architecture design and information systems development (ISD) is presented. It is noted that the selection of architectural viewpoints is based on the prevalent architectural practices in an organization and on the requirements from the project at hand. Examples of viewpoint selection are shown in the case study on the experiences from three different telecom-area software organizations. They end up using different sets of viewpoints in their software process, because of the differences in their resources, business practices, and technology.

[1]  Mary Shaw,et al.  Software architecture - perspectives on an emerging discipline , 1996 .

[2]  Robert L. Nord,et al.  Software Architecture in Industrial Applications , 1995, 1995 17th International Conference on Software Engineering.

[3]  Michael D. Myers,et al.  A Set of Principles for Conducting and Evaluating Interpretive Field Studies in Information Systems , 1999, MIS Q..

[4]  Philippe Kruchten,et al.  The Rational Unified Process: An Introduction , 1998 .

[5]  Oliver Sims,et al.  Business Component Factory : A Comprehensive Overview of Component-Based Development for the Enterprise , 1999 .

[6]  Rudy Hirschheim,et al.  Beyond methodologies: keeping up with information systems development approaches through dynamic classification , 1999, Proceedings of the 32nd Annual Hawaii International Conference on Systems Sciences. 1999. HICSS-32. Abstracts and CD-ROM of Full Papers.

[7]  Kalle Lyytinen,et al.  MetaEdit - A Flexible Graphical Environment for Methodology Modelling , 1991, CAiSE.

[8]  Kevin Barraclough,et al.  I and i , 2001, BMJ : British Medical Journal.

[9]  John A. Zachman,et al.  A Framework for Information Systems Architecture , 1987, IBM Syst. J..

[10]  Felix Bachmann,et al.  The Architecture Based Design Method , 2000 .

[11]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[12]  K. Lyytinen.  A taxonomic perspective of information systems development: theoretical constructs and recommendations , 1987 .

[13]  Philippe Kruchten,et al.  The 4+1 View Model of Architecture , 1995, IEEE Softw..

[14]  A. Strauss,et al.  The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .

[15]  Jan Bosch,et al.  Design and use of software architectures - adopting and evolving a product-line approach , 2000 .

[16]  Robert L. Nord,et al.  Applied Software Architecture , 1999, Addison Wesley object technology series.

[17]  John F. Sowa,et al.  Extending and Formalizing the Framework for Information Systems Architecture , 1992, IBM Syst. J..

[18]  Richard J. Welke,et al.  IS/DSS: DBMS Support for Information Systems Development , 1981, NATO ASI DBM.

[19]  Wanda J. Orlikowski,et al.  Technological frames: making sense of information technology in organizations , 1994, TOIS.

[20]  A. Strauss,et al.  Basics of qualitative research: Grounded theory procedures and techniques. , 1992 .