Page 219 -

190 PART TWO MANAGING SOFTWARE PROJECTS

[PRE99] Pressman, R.S., Adaptable Process Model, R.S. Pressman & Associates, 1999.
[PUT92] Putnam, L. and W. Myers, Measures for Excellence, Yourdon Press, 1992.
[RIG81] Riggs, J., Production Systems Planning, Analysis and Control, 3rd ed., Wiley,
1981.
[THE93] The’, L., “Project Management Software That’s IS Friendly,” Datamation,
October 1, 1993, pp. 55–58.
[WIL99] Wilkens, T.T., “Earned Value, Clear and Simple,” Primavera Systems, April
1, 1999, p. 2.
[ZAH95] Zahniser, R., “Time-Boxing for Top Team Performance,” Software Develop-
ment, March 1995, pp. 34–38.

PROBLEMS AND POINTS TO PONDER

7.1. “Unreasonable” deadlines are a fact of life in the software business. How should
you proceed if you’re faced with one?

7.2. What is the difference between a macroscopic schedule and a detailed sched-
ule. Is it possible to manage a project if only a macroscopic schedule is developed?
Why?

7.3. Is there ever a case where a software project milestone is not tied to a review?
If so, provide one or more examples.

7.4. In Section 7.2.1, we present an example of the “communication overhead” that
can occur when multiple people work on a software project. Develop a counterex-
ample that illustrates how engineers who are well-versed in good software engi-
neering practices and use formal technical reviews can increase the production rate
of a team (when compared to the sum of individual production rates). Hint: You can
assume that reviews reduce rework and that rework can account for 20–40 percent
of a person’s time.
7.5. Although adding people to a late software project can make it later, there are
circumstances in which this is not true. Describe them.
7.6. The relationship between people and time is highly nonlinear. Using Putnam's
software equation (described in Section 7.2.2), develop a table that relates number of
people to project duration for a software project requiring 50,000 LOC and 15 person-
years of effort (the productivity parameter is 5000 and B = 0.37). Assume that the soft-
ware must be delivered in 24 months plus or minus 12 months.

7.7. Assume that you have been contracted by a university to develop an on-line
course registration system (OLCRS). First, act as the customer (if you're a student,
that should be easy!) and specify the characteristics of a good system. (Alternatively,
your instructor will provide you with a set of preliminary requirements for the sys-
tem.) Using the estimation methods discussed in Chapter 5, develop an effort and
duration estimate for OLCRS. Suggest how you would: