This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
The Business Goals Viewpoint
November/December 2010 (vol. 27 no. 6)
pp. 38-45
ASCII Text
x 
 
Paul Clements, Len Bass, "The Business Goals Viewpoint," IEEE Software, vol. 27, no. 6, pp. 38-45, November/December, 2010.
 
 
BibTex
x
 
@article{ 10.1109/MS.2010.116,
author = {Paul Clements and Len Bass},
title = {The Business Goals Viewpoint},
journal ={IEEE Software},
volume = {27},
number = {6},
issn = {0740-7459},
year = {2010},
pages = {38-45},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2010.116},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - The Business Goals Viewpoint
IS - 6
SN - 0740-7459
SP38
EP45
EPD - 38-45
A1 - Paul Clements,
A1 - Len Bass,
PY - 2010
KW - business goals
KW - business goals viewpoint
KW - software architecture
KW - business goals scenario
VL - 27
JA - IEEE Software
ER -
 
Paul Clements, Carnegie Mellon University, Pittsburgh
Len Bass, Carnegie Mellon University, Pittsburgh
Architectures come about through forces and needs other than those captured in traditional requirements documents. A business goal expresses why a system is being developed and what stakeholders in the developing organization, the customer organization, and beyond aspire to achieve through its production and use. Business goals can provide the rationale for requirements and help identify missing or superfluous requirements. Business goals can also influence architectures directly, even without affecting requirements at all. A business goals viewpoint can help architects and organizations capture their business goals in a precise and unambiguous form, which in turn will help architects design systems that are more responsive to organizational needs.

1. B. Boehm, Software Engineering Economics, Prentice Hall, 1981.
2. P. Clements et al., "The Duties, Skills, and Knowledge of Software Architects," Proc. 2007 Working IEEE/IFIP Conf. Software Architecture, IEEE CS Press, 2007, p. 20.
3. P. Clements and L. Bass, Relating Business Goals to Architecturally Significant Requirements for Software Systems, tech. note CMU/SEI-2010-TN-018, Software Eng. Inst., 2010.
4. A. Osterwalder and Y. Pigneur, "An Ontology for e-Business Models," Value Creation from e-Business Models, W. Currie ed., Butterworth-Heinemann, 2004, pp. 65–97.
5. P. Clements et al., , Documenting Software Architectures: Views and Beyond, 2nd ed., Addison-Wesley, 2010.
6. R.K. Mitchell, B.R. Agle, and D.J. Wood, "Toward a Theory of Stakeholder Identification and Salience: Defining the Principle of Who and What Really Counts," Academy of Management Rev., vol. 22, no. 4, 1997, pp. 853–886.
7. P. Eeles and P. Cripps, The Process of Software Architecting, Addison-Wesley, 2009.
8. A. van Lamsweerde, "Goal-Oriented Requirements Engineering: A Guided Tour," Proc. 5th Int'l IEEE Symp. Requirements Eng., IEEE CS Press, 2001, pp. 249–268.
9. Collins English Dictionary: Complete and Unabridged, 6th ed., Harper Collins, 2003.
10. P. Clements, R. Kazman, and M. Klein, Evaluating Software Architectures: Methods and Case Studies, Addison-Wesley, 2003.

Index Terms:
business goals, business goals viewpoint, software architecture, business goals scenario
Citation:
Paul Clements, Len Bass, "The Business Goals Viewpoint," IEEE Software, vol. 27, no. 6, pp. 38-45, Nov.-Dec. 2010, doi:10.1109/MS.2010.116
Usage of this product signifies your acceptance of the Terms of Use.