文档介绍：Using the Rational Unified Process (RUP)
essfully for Small Development Projects
An Interview with Rational's "RUP Curmudgeon," Gary Pollice
by Liz Augustine
Technical Writer
Rational Software
At the Rational User Conference 2001,
I was pleased to hear many customers
speak of their ess using the
Rational Unified Process® on large
projects. But after hearing Grady
Booch's keynote address in which he
said that the average project team size
is only about seven people, I started to
wonder if you can use RUP essfully
on small projects, too. This week, I
caught up with Gary Pollice, one of
Rational's RUP experts, to talk with
him about this topic.
Liz: Hi Gary. Before we start talking
about RUP, perhaps you can give us an idea of what a "small project" is.
Gary: I think that most people intuitively recognize a small project. Some
people characterize small projects by the number of project members --
fewer than ten would constitute a small project for most people. Others
talk about the length of the project. Especially when people are developing
for the Web, projects are measured in increasingly shorter time spans.
And finally, some people think about the amount of software they're
building and measure by number of lines of code, number of functions, or
some other metric.
A key characteristic of most small projects is the level of