Page 207 - Software and Systems Requirements Engineering in Practice

t
y
l
i

t
r
A
t
r

t
e
5
u
a
:
Q
r
e
u
i
m
t
s
e
n
u
t
i
b
e
e
q

R
C
C h a p t e r 5 : Q u a l i t y A t t r i b u t e R e q u i r e m e n t s 173 173
h
p
a
Nuseibeh, B. and Easterbrook, S., “Requirements Engineering: A Roadmap,”
Proceedings of the International Conference on Software Engineering, Limerick,
Ireland, June 2000, pp. 35–46.
Ozkaya, I., Bass, L., Sangwan, R., and Nord, R. “Making Practical Use of Quality
Attribute Information,” IEEE Software, March–April, 2008, pp. 25–33.
Paech, B., Dutoit, A., Kerkow, D., and von Knethen, A., “Functional Requirements,
Non-Functional Requirements, and Architecture Should Not Be Separated,”
Proceedings of the International Workshop on Requirements Engineering: Foundations
for Software Quality, Essen, Germany, September 9–10, 2002, pp. 102–107.
Paulish, D., Architecture-Centric Software Project Management, Addison-Wesley,
Boston, 2002.
Peraire, P., Riemenschneider, R., and Stavridou, V., “Integrating the Unified
Modeling Language with an Architecture Description Language,” OOPSLA
’99 Workshop on Rigorous Modeling and Analysis with the UML: Challenges and
Limitations, 1999.
Robbins, J., Medvidovic, N., Redmiles, D., and Rosenblum, D., “Integrating
Architecture Description Languages with a Standard Design Method,”
Proceedings of the 20th International Conference on Software Engineering, Kyoto,
Japan, 1998, pp. 209–218.
Sangwan, R., Bass, M., Mullick, N., Paulish, D., and Kazmeier, J., Global Software
Development Handbook, Auerbach Publications, New York, 2007.
Sangwan, R. and Neill, C., “How Business Goals Drive Architectural Design,” IEEE
Computer, August 2007, pp. 101–103.
Sangwan, R., Neill, C., El Houda, Z., and Bass, M. “Integrating Software Architecture-
Centric Methods into Object-Oriented Analysis and Design,” Journal of Systems
and Software, May 2008, pp. 727–746.
Smith, C. and Williams, L., Performance Solutions: A Practical Guide to Creating
Responsive, Scalable Software, Addison-Wesley, Boston, 2002.
Zave, P. and Jackson, M., “Four Dark Corners of Requirements Engineering,”
ACM Transactions on Software Engineering and Methodology, Vol. 6, No. 1, 1997,
pp. 1–30.