Page 44 - Software and Systems Requirements Engineering in Practice

d
h
C
t
c
u

t
n
:
1
o
r
i
e
t
C h a p t e r 1 : I I n t r o d u c t i o n 17 17
r
p
a
n
o
described the characteristics of a good requirement and a good
requirements specification.
1.12 Discussion Questions
1. Why is good requirements engineering more important to
product development than it was ten years ago?
2. What are the differences between good requirements and a
good requirements specification?
3. What are some of the key full-time roles necessary for a
project to be successful?
4. What is the role of the chief architect?
References
Dekkers, C. and Aguiar, M., “Applying Function Point Analysis to Requirements
Completeness,” Crosstalk, February 2001.
DoD 91, U.S. Department of Defense, Software Technology Strategy, December
1991.
Ebert, C., “Requirements BEFORE the Requirements: Understanding the Upstream
Impact,” Proceedings of the 13th IEEE International Conference on Requirements
Engineering (RE’05), 2005, pp. 117–124.
Gotel, O. and Finkelstein, A., “An Analysis of the Requirements Traceability
Problem,” Proceedings of the First International Conference on Requirements
Engineering, Colorado Springs, CO, pp. 94–101, April 1994.
Hofmeister, C., Nord, R., and Soni, D., Applied Software Architecture, Addison-
Wesley, Boston, MA, 1999.
IEEE Standard 830, IEEE Recommended Practice for Software Requirements Specifications,
1998.
Johnson, J., “Turning Chaos into Success,” Software Magazine, Vol. 19, No. 3,
December 1999/January 2000, pp. 30–39.
Jones, C., Applied Software Measurement, 3rd ed., McGraw-Hill, New York, 2008.
Jones, C., Estimating Software Costs, 2nd ed., McGraw-Hill, New York, 2007.
Kamata, M.I. and Tamai, T., “How Does Requirements Quality Relate to Project
Success or Failure?” Proceedings of the International Requirements Engineering
Conference (RE‘07), 2007.
Paulish, D., Architecture-Centric Software Project Management, Addison-Wesley,
Boston, MA, 2002.
Standish Group Report, “CHAOS,” http://www.projectsmart.co.uk/docs/chaos_
report.pdf, 1995.
Thayer, R. and Dorfman, M., Software Requirements Engineering, 2nd ed., Los
Alamitos, CA: IEEE Computer Society Press, 1997.