Page 206 - Software and Systems Requirements Engineering in Practice

172 S o f t w a r e & S y s t e m s R e q u i r e m e n t s E n g i n e e r i n g : I n P r a c t i c e

3. How does one analyze design tradeoffs and the associated risks
with implementing a system that best meets requirements?

References
Bachmann, F., Bass, L., and Klein, M., Illuminating the Fundamental Contributors to
Software Architecture Quality (CMU/SEI-2002-TR-025), Software Engineering
Institute, Carnegie Mellon University, Pittsburgh, August 2002.
Barbacci, M., Ellison, R., Weinstock, C., and Wood, W., Quality Attribute Workshop
Participants Handbook (CMU/SEI-2000-SR-001), Software Engineering Institute,
Carnegie Mellon University, Pittsburgh, July 2000.
Bass, L., Clements, P., and Kazman, R., Software Architecture in Practice, 2nd ed.,
Addison-Wesley, Boston 2003.
Berenbach, B., “The Automated Extraction of Requirements from UML Models,”
Eleventh IEEE International Symposium on Requirements Engineering (RE ’03),
Monterey Bay, CA, September 2003, pp. 287–288.
Budgen, D., Software Design, Addison-Wesley, Boston, 2003.
Cleland-Huang, J., Marrero, W., and Berenbach, B., “Goal Centric Traceability: Using
Virtual-Plumblines to Maintain Critical Systemic Qualities,” IEEE Transactions
on Software Engineering, June 2008.
Clements, P., Kazman, R., and Klein, M., Evaluating Software Architectures: Methods
and Case Studies, Addison-Wesley, Boston, 2001.
Clements, P., Bachmann, F., Bass, L., Garlan, D., Ivers, J., Little, R., Nord, R., and
Stafford, J., Documenting Software Architectures, Addison-Wesley, Boston, 2003.
Cortellessa, V., Di Marco, A., Inverardi, P., Mancinelli, F., and Pelliccione, P., “A
Framework for the Integration of Functional and Non-functional Analysis of
Software Architectures,” Proceedings of the International Workshop on Test and
Analysis of Component Based Systems (TACoS 2004), 2005, pp. 31–44.
Dardenne, A., Lamsweerde, A., and Fickas, S., “Goal-Directed Requirements
Acquisition,” Science of Computer Programming, Vol. 20, Nos. 1–2, 1993, pp. 3–50.
Finkelstein, A. and Dowell, J., “A Comedy of Errors: the London Ambulance Service
Case Study,” Proceedings of the 8th International Workshop on Software Specification
and Design, 1996, pp. 2–4.
Glinz, M., “A Risk-Based, Value-Oriented Approach to Quality Requirements,”
IEEE Software, March–April 2008.
Hofmeister, C., Nord, R., and Soni, D., Applied Software Architecture, Addison-
Wesley, Boston, 1999.
Hofmeister, C., Krutchen, P., Nord, R., Obbink, H., Ran, A., and America, P.,
“Generalizing a Model of Software Architecture Design from Five Industrial
Approaches,” Proceedings of the 5th Working IEEE/IFIP Conference on Software
Architecture (WICSA ’05), 2005, pp. 77–88.
IEEE Std. 610.12-1990.
IEEE Std. 1471-2000.
ISO/IEC 9126 (2001). Software Engineering—Product Quality—Part 1: Quality Model.
International Standards Organization.
ISO/IEC 25030 (2007). Software Engineering—Software Product Quality Requirements
and Evaluation (SQuaRE)—Quality Requirements. International Standards
Organization.
Jackson, M., “The Meaning of Requirements,” Annals of Software Engineering,
Vol. 3, 1997, pp. 5–21.
Jones, C., Applied Software Measurement, 3rd ed., McGraw-Hill, New York, 2008.
Jones, C., Estimating Software Costs, 2nd ed., McGraw-Hill, New York, 2007.
Lamsweerde, A., “Requirements Engineering in the Year 00: A Research Perspective,”
Proceedings of the International Conference on Software Engineering, Limerick,
Ireland, 2000, pp. 5–19.
Nuseibeh, B., “Weaving Together Requirements and Architectures,” IEEE Computer,
Vol. 34, No. 3, 2001, pp. 115–119.