Using Business Goals to Inform a Software Architecture

Requirements specifications seldom allow software and system architects to understand the business goals for a system. Architects need that information in order to design an appropriate architecture for the problem at hand. In this paper, we present a lightweight method based on goal oriented requirements engineering that begins with a canonical list of business goals and elicits specific business goals from the perspective of various stakeholders. It then interprets those business goals in terms of the quality attribute requirements that are so important to software architectures. Experience with using this method for a Boeing Air Transport System is presented.

[1]  C. Cocklin,et al.  Conceptualizing a “Sustainability Business Model” , 2008 .

[2]  Anna Kotsalo-Mustonen.  Diagnosis of Business Success. Perceptual Assessment of Success in Industrial Buyer-Seller Business Relationship , 1996 .

[3]  H. Bouwman,et al.  What Drives Business Model Dynamics? A Case Survey , 2007, Eighth World Congress on the Management of eBusiness (WCMeB 2007).

[4]  Annie I. Antón,et al.  Goal Decomposition and Scenario Analysis in Business Process Reengineering , 1994, CAiSE.

[5]  Karen Holtzblatt,et al.  Contextual design , 1997, INTR.

[6]  Colin J. Neill,et al.  How Business Goals Drive Architectural Design , 2007, Computer.

[7]  Pwg Morris,et al.  Moving from Corporate Strategy to Project Strategy , 2005 .

[8]  Michael Weiss,et al.  Goal-Oriented Design of Business Models and Software Architectures , 2006, 2006 Canadian Conference on Electrical and Computer Engineering.

[9]  Barbara Paech,et al.  MOQARE: misuse-oriented quality requirements engineering , 2008, Requirements Engineering.

[10]  Daniel Gross,et al.  Evolving system architecture to meet changing business goals: an agent and goal-oriented approach , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[11]  Yves Pigneur,et al.  4 – An ontology for e-Business models , 2004 .

[12]  A. Sousa-Poza,et al.  Project Management: A Cultural Literary Review , 2005 .

[13]  Rebecca E. Grinter.  Systems architecture: product designing and social engineering , 1999 .

[14]  Fereidoun Ghasemzadeh,et al.  An integrated framework for project portfolio selection , 1999 .

[15]  Thomas A. Charles,et al.  What Goals Do Business Leaders Pursue? A Study in Fifteen Countries , 2002 .

[16]  R. Freeman.  Strategic Management: A Stakeholder Approach , 2010 .

[17]  Carol Bruckner Coles,et al.  Building better business models , 2003 .

[18]  K. Artto,et al.  Strategic Business Management through Multiple Projects , 2007 .

[19]  Mark Klein,et al.  The Duties, Skills, and Knowledge of Software Architects , 2007, 2007 Working IEEE/IFIP Conference on Software Architecture (WICSA'07).

[20]  A. Armitage,et al.  Undertaking a structured literature review or structuring a literature review: tales from the field , 2008 .

[21]  L. Preston,et al.  The Stakeholder Theory of the Corporation: Concepts, Evidence, and Implications , 1995 .

[22]  Paul Clements,et al.  Relating Business Goals to Architecturally Significant Requirements for Software Systems , 2010 .

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

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

[25]  Ali Saravirta.  Project Success through Effective Decisions: Case Studies on Project Goal Setting, Success Evaluation and Managerial Decision Making , 2001 .

[26]  Robert G. Cooper,et al.  Portfolio Management for New Products (Управление портфелем новых продуктов) , 1998 .

[27]  Ronald K. Mitchell,et al.  Toward a Theory of Stakeholder Identification and Salience: Defining the Principle of who and What Really Counts , 1997 .

[28]  S. Mäkinen,et al.  Assessing Business Model Concepts with Taxonomical Research Criteria - A Preliminary Study , 2007 .

[29]  Rick Kazman,et al.  Categorizing Business Goals for Software Architectures , 2005 .