Achieving Quality Attribute

  • Lina Khalid


Patterns help you build the architecture on the shared experience of skilled software engineers. They capture experience in software development and help to promote good design practice. Every pattern deals with a specific, recurring problem in the design or implementation of a software system. Architectural styles and patterns define the way to manage the components of the system so that one can build a system and also achieve the requirements of the stakeholders. Several architectural styles and patterns exist in the world of the software architecture, so one needs to understand which particular architecture style/pattern will be suitable through building the system. Architectural tactic is a design decision that influences the achievement of quality attribute response. Every pattern deals with many qualities, while tactic deals with a specific type of quality. The important thing to know is that most patterns consist of several different types of tactics that serve a common purpose. The relation between pattern and tactic is described in this chapter.

At the end of the chapter you will learn:
  • Patterns and their roles in building architecture

  • Relation between tactics and patterns and how to achieve the quality through these tactics

  • Meaning of business patterns and the importance of these patterns in business

  • The SEI attribute-driven design (ADD) method and how this method works and what it will use for


Architectural pattern Architectural structure Architectural style Architectural drivers Tactics Business pattern Attribute-driven design 


  1. L. Bass, P. Clements, R. Kazman, Software Architecture in Practice, 3rd edn. (2013) United StatesGoogle Scholar
  2. H. Cervants, R. Kazman, Designing Software Architectures: A Practical Approach (Addison-Wesley, 2016)Google Scholar
  3. M. Fowler, Pattern of Enterprise Application Architecture (Addison-Wesely, 2003)Google Scholar
  4. P. Teale, Business Patterns for Software Engineering Use (Microsoft Corporation, Robert Jarvis SA Ltd, 2004)Google Scholar

Further Reading

  1. F. Bachmann, L. Bass, R. Nord, Modifiability Tactic, Technical report CMU/SEI (John Wiley & Sons Ltd, 2007) Chichester, West Sussex, EnglandGoogle Scholar
  2. J. Bosch, Software Architecture: The Next Step, University of Groningen, Department of Computing. LNCS 3047 (Springer, Berlin Heidelberg, 2004), pp. 194–199CrossRefGoogle Scholar
  3. F. Buchman, K. Hennery, D. Schmidt, Pattern-Oriented Software Architecture: A Pattern Language for Distributed Computing (Wiley, 2007)Google Scholar
  4. I. Gorton, Essential Software Architecture, 2nd edn. (Springer-Verlag, 2011) Berlin, HeidelbergGoogle Scholar
  5. T. Graves, Everyday Enterprise Architecture: Sensemaking, Strategy, Structures and Solutions (Tetradian Books, 2010).
  6. N. Harrison, P. Avgeriou, How do architecture patterns and tactics interact? A model and annotation. J. Syst. Softw. 83, 1735–1758 (2010). Scholar
  7. S. Kim, Dae-Kyoo Kim, et al., Quality-driven architecture development using architectural tactics. J. Syst. Softw. 82, 1211–1231 (2009)CrossRefGoogle Scholar
  8. A. Moore, L. Bass, M. Klein, F. Bachmann, Security and Survivability Reasoning Frameworks and Architectural Design Tactics, Technical note (2004)Google Scholar
  9. M. Richards, Software Architecture Patterns: Understanding Common Architecture Patterns and When to Use Them (O’Reilly Media, Inc, 2015) Sebastopol, CAGoogle Scholar
  10. A. Sharmaa, M. Kumarb, S. Agarwal, A Complete Survey on Software Architectural Styles and Patterns.4th International Conference on Eco-friendly Computing and Communication Systems, ICECCS, 2015 (Elsevier, 2015)Google Scholar

Copyright information

© Springer Nature Switzerland AG 2020

Authors and Affiliations

  • Lina Khalid
    • 1
  1. 1.AmmanJordan

Personalised recommendations