Use Rational tools to simplify J2EE-based projects (2) start projects

Part 2: start the project
Steven Franklin
Software designers and process experts
March 2004
This series of articles describes how to gradually apply the Rational Unified Process (RUP) and other Rational tools, the detailed plan of the sample project in this article is discussed around the management requirements and risks.
Part 2 snapshots
Part 1 shows the tools and technologies:
Rational Unified Process (RUP)-supporting the formulation of project plans
RUP Microsoft Word template-draft project vision document
Rational RequisitePro v2001A-required Database
Rational ClearQuest v2001A-for risk management
Products to be created or updated:
RequisitePro database-the database is created to store the requirements of the customer's work description (SOW). Later, the requirements will be converted into a more detailed system requirement specification for direct analysis.
ClearQuest risk database-created to track project risks (by modifying the ClearQuest plan)
Failed to plan from the beginning
In a software project, it is critical to get a good start. Not only do you want your early work to determine the tone of the entire project, but you also want to quickly identify the high risks and challenges in the system. The fate of more than half of projects is doomed in the first month of the project. The factors that determine the fate include:
Insufficient customer relationship
Insufficient budget
Poor management (including poor management capabilities, risk priority, and poor project scope management)
Too dependent on silver bullet
Lack of engineering skills and experience
Unrealistic time progress
By improving the efficiency and guidance of the team, the Rational Unified Process (RUP) can minimize the cause of project failure. Good data can affect project management by project managers, better tools can support engineering teams, and better processes can help software products develop in a foreseeable way. Part 1 of this series will focus on some of the early strategies we can apply to get something out of the box in our sample project.
Note that project management involves some activities that aren't currently addressed in the RUP. I highly recommend the book. Please Note that project management includes activities not currently included in the RUP. I strongly recommend this book fast development: it can serve as a further reference to reduce risk factors in development projects.
Refine the progress of stage 1
We want to start software engineering as soon as possible, but first we must get the customer's consent on a series of schedule issues. We have taken the time progress of the stage 1st we have created (end with a demo at a four-month time point) and reviewed the time progress more closely with the customer. The customer raised the following questions, all of which were justified and discussed: