|
|
|
Project PlanIntroduction The project plan is a detailed description of what you will do to build your project. You will refine your plan through the design review, which will cover the major highlights. You will create a Web site containing your plan, which you will continue to update through the project. Design ReviewThe review will be held in class. Each review will last approximately 15 minutes. All team members should speak during the review. The review should cover: · the motivation for the project; · requirements; · specification; · architecture; · testing; · time estimates. Since your review is brief, you should concentrate on highlights in each area. The PlanYour plan will be captured on a Web site that you will maintain throughout the project. You can use the Web site to coordinate team members. A variety of tools, including Microsoft Word, can be used to create basic Web sites. Design documents on the Web site should begin with a title, a list of authors, and a revision list. The revision list gives the date of each major revision in the document and a brief description of the reason for the change. Your Web site should, at this stage, include: · Motivation: A brief description of what the project is and why it is interesting. · Requirements: A requirements form in the book format. · Specification: A detailed specification of the system. Use UML where appropriate. · Architecture: A detailed description of the software and hardware architectures of your system. Use UML where appropriate. · Testing: A detailed description of how you plan to validate the design at various stages of the design processs. You should relate testing steps to your specification and architecture descriptions. · Time estimates: A set of milestones, what you want to accomplish at each milestone, and the estimated time required for accomplishing each milestone. One milestone should coincide with the project milestone deadline. Turn in A URL for a Web site that
gives: ·
A requirements form describing the project. ·
A specification, using UML wherever appropriate. ·
Descriptions of the software and hardware
architectures, using UML where appropriate. ·
A testing and verification plan. ·
A timeline with milestones and time estimates. Copyright ã 2000 Wayne Wolf |
|
|