Java Reference
In-Depth Information
•
http://www.progsoc.uts.edu.au/~timj/thesis/web/srs.html
•
http://www2.ics.hawaii.edu/~johnson/413/lectures/5.2.html
•
http://www.cc.gatech.edu/people/home/tomoyo/rocky-axel.1.doc
For those who are serious about their software development process, the
Capability Maturity Model for Software from the Software Engineering Insti-
tute at Carnegie Mellon University is the standard. Visit their Web site at
http://www.sei.cmu.edu/cmm/
.
If you would like to know more about the spiral approach to software de-
sign, you might want to start with the seminal paper on the topic, “A Spiral
Model of Software Development and Enhancement,” in
Computer
21, no. 5
(May 1988), pages 61-72.
To see how the director of the Software Engineering Institute views
the spiral approach, check out the short and readable introduction at
http://www.dacs.dtic.mil/awareness/newsletteres/technews2-1/
disciplined.html
.
Another good look at the spiral, or iterative, approach can be found at
http://www.stickyminds.com/se/S3420.asp
which has a hyperlink for
a PDF file of a paper by Philippe Kruchten of Rational Software. The paper
covers some pitfalls common to the first uses of the iterative approach; worth
the read.
A great survey of key papers on three major approaches—spiral and related
topics (including newer work by Boehm), aspect-oriented programming (AOP),
and the rational unified process—is at
http://www.rspa.com/reflib/
PrescriptiveModels.html
.
11.11
E
XERCISES
1. Write requirements for a simple word processor or spreadsheet. Start with
some obvious functionality. Add only enough “bells and whistles” for it
to be usable for beginners. Show this list to others, especially people famil-
iar with similar applications. What features do they find missing that are
important to them? How quickly does your list expand? What might you
do to limit the size and the rate of growth of the features list?
