The Case For Understanding Social Complexity In the Architecture-Based Analysis Process

Systems architecture is a discipline that seeks to model the abstract form of a system and reason about the qualities of the end system artefact with respect to the design representation. The analysis need has driven the development of several architecture-based evaluation techniques, which have evolved over the past decade from expert-centric, to stakeholder-centric analysis. The resulting group of participants can be considered, as they are in the broader design process, a human activity system, granting architecture-based analysis many of the attributes of a social or 'soft' process, The following paper examines the development of architecture-based evaluation techniques in light of soft systems theory and makes the case for the existence of, and need to understand, social complexity within the analysis process.

[1]  Per Galle,et al.  Design as intentional action: a conceptual analysis , 1999 .

[2]  Glenford J. Myers,et al.  Structured Design , 1974, IBM Syst. J..

[3]  Jan Bosch,et al.  Analyzing Software Architectures for Modifiability. , 2000 .

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

[5]  Marta López.  Application of an evaluation framework for analyzing the architecture tradeoff analysis methodSM , 2003, J. Syst. Softw..

[6]  Rikard Land.  Improving quality attributes of a complex system through architectural analysis-a case study , 2002, Proceedings Ninth Annual IEEE International Conference and Workshop on the Engineering of Computer-Based Systems.

[7]  M. C. Jackson.  Systems methodologies as complementary tools for managing situational complexity , 1988 .

[8]  Mark Klein,et al.  Experience with performing architecture tradeoff analysis , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[9]  L. J. Davies.  How SSM deals with complexity , 1988 .

[10]  R. Land.  A Brief Survey of Software Architecture Rikard Land Mälardalen , 2002 .

[11]  D. L. Parnas,et al.  On the criteria to be used in decomposing systems into modules , 1972, Software Pioneers.

[12]  Shivraj Kanungo,et al.  Beyond generic models for information system quality: the use of interpretive structural modeling (ISM)† , 2002 .

[13]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[14]  Rick Kazman,et al.  Evaluating Software Architectures: Methods and Case Studies , 2001 .

[15]  Michael Jackson,et al.  Software requirements & specifications , 1995 .

[16]  Paul Clements,et al.  Recommended Best Industrial Practice for Software Architecture Evaluation. , 1997 .

[17]  Sue Holwell,et al.  Information, Systems and Information Systems: Making Sense of the Field , 1998 .

[18]  R. Hilliard,et al.  Architecture Quality Assessment version 2 . 0 , 1996 .

[19]  Eila Niemelä,et al.  A Survey on Software Architecture Analysis Methods , 2002, IEEE Trans. Software Eng..

[20]  Lars Lundberg,et al.  Software architecture - Engineering quality attributes , 2003, J. Syst. Softw..

[21]  Richard Baskerville,et al.  Growing systems in emergent organizations , 1999, CACM.

[22]  Steve Joseph,et al.  Design systems and paradigms , 1996 .

[23]  Leonard J. Bass,et al.  Attribute-Based Architecture Styles , 1999, WICSA.

[24]  Ch Kees Dorst,et al.  Design and use as plans: an action-theoretical account , 2002 .

[25]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[26]  Philip Sargent,et al.  Design science or nonscience , 1994 .

[27]  Paul Clements,et al.  ATAM: Method for Architecture Evaluation , 2000 .

[28]  Leonard J. Bass,et al.  Making Architecture Reviews Work in the Real World , 2002, IEEE Softw..

[29]  Louis L. Bucciarelli,et al.  Designing Engineers , 1994 .

[30]  Ralph Johnson,et al.  design patterns elements of reusable object oriented software , 2019 .

[31]  Leonard J. Bass,et al.  SAAM: a method for analyzing the properties of software architectures , 1994, Proceedings of 16th International Conference on Software Engineering.

[32]  Phil F. Culverhouse,et al.  A study of electronics engineering design teams , 2000 .

[33]  David Budgen,et al.  Software design , 2020, International computer science series.

[34]  F. R. Janes,et al.  Interpretive structural modelling: a methodology for structuring complex issues , 1988 .

[35]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[36]  Louis L. Bucciarelli,et al.  Between thought and object in engineering design , 2002 .

[37]  Paul Clements,et al.  Software Architecture in Practice: Addison-Wesley , 1998 .

[38]  Susan Carlson Skalak.  House of Quality , 2002 .

[39]  Derek K. Hitchins,et al.  Putting Systems to Work , 1993 .

[40]  R. L. Flood,et al.  Situational complexity, systems modelling and methodology , 1988 .

[41]  R S Pressman,et al.  Software engineering: a practitioner's approach (2nd ed.) , 1986 .

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