Managing Business Qualities

  • Lina Khalid


Business quality is a non-software system quality that influences other types of qualities in the system. This type of quality is very important because it is taken from the market’s point of view. This chapter is going through this type of quality and its goals (business goals). Business goals must be specific, measurable, attainable, realistic, and time bound.

Stakeholders of the system and their relations to business goals will be described in this chapter. Also the approach that shapes the relation between the organization and the stakeholder will be shown.

To enhance the quality of the software, many companies use an approach called software process improvement. This approach can reduce cost or increase their development process through it. It is a way to understand the existing process and then changing it to increase the quality of the product and/or reduce the time of development and cost. This approach will be described in this chapter.

In brief, at the end of this chapter, you will learn:
  • The meaning of business qualities and business goals and the main qualities in the business

  • The meaning of stakeholders, their types, and their roles in achieving the goals

  • The meaning of TQM and its main principles

  • The process improvement and its life cycle


Business quality Business goals Total quality management (TQM) Stakeholder Process improvement Pedigree Attribute eLicitation Method (PALM) 


  1. L. Bass, P. Clements, R. Kazman, Software Architecture in Practice, 3rd edn. (Addison-Wesley, Upper Saddle River, 2013)Google Scholar
  2. P. Clements, D. John, Mc Gregorand, L. Bass, Software Engineering Institute, Carnegie Mellon University, 14th international conference SPL 2010, Springer LNCS 6287 PP:393–403Google Scholar
  3. L. Khaled, Achieving goals through architectural design decision. J. Comput. Sci. 6(12), 1424–1429 (2010a)., 2010, ISSN 1549-3636 Science PublicationsCrossRefGoogle Scholar
  4. N. Rozanski, E. Woods. Software system architecture: Working with the stakeholder using viewpoints and perspectives. Prepared for Douglas Taylor (2009)Google Scholar
  5. N. Sanders, D. Reid, Operations Management:An Integrated Approach, 5th edn. (John Wiley & sons, New York, 2012). ISBN:9781118122679Google Scholar
  6. I. Somerville, Software Engineering, 9th edn. (Addission Wiesly, Boston, 2011)Google Scholar

Further Reading

  1. SEI on line training from SEI: Software Architecture: Principles and Practices,

Journal Papers

  1. L. Bass, P. Clements, R. Kazman, R. Nord, Architectural, Business Cycle Revisted, Software Engineering Institute, Carengie Mellon (2009)Google Scholar
  2. D. Gross, E. Yu, Evolving System Architecture to Meet Changing Business Goals: An Agent and Goal –Oriented Approach, University of Toronto. IEEE (2001).
  3. L. Khaled, Driving architectural design through bussiness goals, software engineering researcher. Int. J. Comput. Sci. Inf. Secur. 8(3), (2010b)Google Scholar
  4. I. Liu, E. Yu, From Requirment to Architectural Design -Using Goals and Scenarios, University of Toronto (2001)Google Scholar
  5. V. Omachouno, J. Ross, Principle of Total Quality (CRC Press, 2005)Google Scholar
  6. D. Susnienė, P. Vanaga, Integration of total quality management into stakeholder management policy and harmonization of their interests. Eng. Econ 44(4), 71–77 (2005). ISSN 1392–2785. Commerce of Engineering Decisions. Scholar
  7. R. Van Solingen, E. Berghout, The Goal Question Metric: A Practical Guide for Quality Improvement of Software Development (McGraw Hill, Chicago, 1999)Google Scholar
  8. M.K. Verma, Importance of Leadership In Total Quality Management (Mizoram University, 2014). http://www.reseachgate.ney/publication/295531927

Copyright information

© Springer Nature Switzerland AG 2020

Authors and Affiliations

  • Lina Khalid
    • 1
  1. 1.AmmanJordan

Personalised recommendations