This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
November/December 2010 (vol. 27 no. 6)
pp. 20-24
ASCII Text
x 
 
Patricia Lago, Paris Avgeriou, Rich Hilliard, "Guest Editors' Introduction: Software Architecture: Framing Stakeholders' Concerns," IEEE Software, vol. 27, no. 6, pp. 20-24, November/December, 2010.
 
 
BibTex
x
 
@article{ 10.1109/MS.2010.142,
author = {Patricia Lago and Paris Avgeriou and Rich Hilliard},
title = {Guest Editors' Introduction: Software Architecture: Framing Stakeholders' Concerns},
journal ={IEEE Software},
volume = {27},
number = {6},
issn = {0740-7459},
year = {2010},
pages = {20-24},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2010.142},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Guest Editors' Introduction: Software Architecture: Framing Stakeholders' Concerns
IS - 6
SN - 0740-7459
SP20
EP24
EPD - 20-24
A1 - Patricia Lago,
A1 - Paris Avgeriou,
A1 - Rich Hilliard,
PY - 2010
KW - stakeholder concerns
KW - architecture
KW - framework
KW - viewpoints
KW - software development
KW - software life cycle
VL - 27
JA - IEEE Software
ER -
 
Patricia Lago, VU University Amsterdam
Paris Avgeriou, University of Groningen
Rich Hilliard, Freelance Software Architect
As noted earlier, some stakeholder concerns are well-served today by available architecture viewpoints, frameworks, or ADLs, while others aren't expressible with available, off-the-shelf approaches. Hence the theme of this special issue: exploring the space of architecting in the face of multiple stakeholder concerns and looking for solutions that help the architect in that space. The articles in this issue all demonstrate techniques for framing one or more stakeholder concerns. Some have confronted the topic within software architecture; others are included because they offer insights on concerns and viewpoints from other branches of software engineering.

1. P. Kruchten, "An Ontology of Architectural Design Decisions in Software Intensive Systems," 2nd Groningen Workshop on Software Variability, Dec. 2004, pp. 54–61.
1. E.W. Dijkstra, "On the Role of Scientific Thought," Springer-Verlag, 1974; www.cs.utexas.edu/users/EWD/transcriptions/ EWD04xxEWD447.html.
2. D. Parnas, "On the Criteria to Be Used in Decomposing Systems into Modules," Comm. ACM, vol. 15, no. 12, 1972, pp. 1053--1058.
3. G. Kiczales et al., "Aspect-Oriented Programming," Proc. European Conf. Object-Oriented Programming (ECOOP), LNCS 1241, Springer-Verlag, 1997, pp. 220--242.
4. S.M. Sutton Jr. and I. Rouvellou, "Concern Modeling for Aspect-Oriented Software Development," Aspect-Oriented Software Development, R.E. Filman et al., eds. Addison-Wesley, 2004, pp. 479--505.

Index Terms:
stakeholder concerns, architecture, framework, viewpoints, software development, software life cycle
Citation:
Patricia Lago, Paris Avgeriou, Rich Hilliard, "Guest Editors' Introduction: Software Architecture: Framing Stakeholders' Concerns," IEEE Software, vol. 27, no. 6, pp. 20-24, Nov.-Dec. 2010, doi:10.1109/MS.2010.142
Usage of this product signifies your acceptance of the Terms of Use.