Page 72 -

Chapter 2 References 55

2.7. Explain why systems developed as prototypes should not normally be used as production
systems.
2.8. Explain why Boehm’s spiral model is an adaptable model that can support both change
avoidance and change tolerance activities. In practice, this model has not been widely used.
Suggest why this might be the case.
2.9. What are the advantages of providing static and dynamic views of the software process as in
the Rational Unified Process?
2.10. Historically, the introduction of technology has caused profound changes in the labor market and,
temporarily at least, displaced people from jobs. Discuss whether the introduction of extensive
process automation is likely to have the same consequences for software engineers. If you don’t
think it will, explain why not. If you think that it will reduce job opportunities, is it ethical for the
engineers affected to passively or actively resist the introduction of this technology?

REFERENCES

Arlow, J. and Neustadt, I. (2005). UML 2 and the Unified Process: Practical Object-Oriented
Analysis and Design (2nd Edition). Boston: Addison-Wesley.
Boehm, B. and Turner, R. (2003). Balancing Agility and Discipline: A Guide for the Perplexed.
Boston: Addison-Wesley.

Boehm, B. W. (1988). ‘A Spiral Model of Software Development and Enhancement’. IEEE
Computer, 21 (5), 61–72.

Budgen, D. (2003). Software Design (2nd Edition). Harlow, UK.: Addison-Wesley.
Krutchen, P. (2003). The Rational Unified Process—An Introduction (3rd Edition). Reading, MA:
Addison-Wesley.
Massol, V. and Husted, T. (2003). JUnit in Action. Greenwich, Conn.: Manning Publications Co.

Rettig, M. (1994). ‘Practical Programmer: Prototyping for Tiny Fingers’. Comm. ACM, 37 (4), 21–7.
Royce, W. W. (1970). ‘Managing the Development of Large Software Systems: Concepts and
Techniques’. IEEE WESTCON, Los Angeles CA: 1–9.
Rumbaugh, J., Jacobson, I. and Booch, G. (1999). The Unified Software Development Process.
Reading, Mass.: Addison-Wesley.
Schmidt, D. C. (2006). ‘Model-Driven Engineering’. IEEE Computer, 39 (2), 25–31.
Schneider, S. (2001). The B Method. Houndmills, UK: Palgrave Macmillan.

Wordsworth, J. (1996). Software Engineering with B. Wokingham: Addison-Wesley.