Chapter 4. The RUP for a Team of One: Project Deimos

We've talked about where different RUP configurations can fit on the process map. But how do you implement the RUP? Before we delve into detailed explanations of the RUP's phases and how to do iterative development, let's go through the simplest implementation possible ”the RUP for a team of one: Project Deimos. This example will give you a basic idea of how to use the process and its underlying principles and will give you a feel for iterative development.

For some, the phrase "software engineering process" evokes an image of a huge set of dusty binders full of policies, directives, and forms, all saturated with administrative jargon. But these are materials that would probably be used only by very large companies that deliver software at a snail 's pace to government agencies and Fortune 500 companies ”software developed by armies of programmers aligned in giant cubicle farms and herded by "pointy-haired managers," like the one in the famous Dilbert cartoons by Scott Adams.

The purpose of a software engineering process is not to make developers' lives miserable or to squash creativity under massive amounts of paperwork. Its only real purpose is to ensure that a software development organization can predictably engineer and deliver high-quality software that meets all of the needs and requirements of its users ”on schedule and within budget.

In this chapter, we will see that a software engineering process does not need to be such a monster. We will explain how "the Spirit of the RUP" (see Chapter 2) can be applied to a very small project by following the work of Nick, a fictitious software engineer with 12 years of development experience. Although Nick prefers to work alone, he deliberately and conscientiously follows a well-defined process. Let's take a look at the diary he kept of a one-week project that he recently completed for Gary, an old friend of his.



The Rational Unified Process Made Easy(c) A Practitioner's Guide to Rational Unified Process
Programming Microsoft Visual C++
ISBN: N/A
EAN: 2147483647
Year: 2005
Pages: 173

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net