1. The Documentary Hypothesis By Adam Hoffman

2. Basic Documents for a Computer Product Objectives Specifications Schedule Budget

3. Objectives “This defines the need to be met and the goals, desiderata (Something considered necessary or highly desirable), constraints, and priorities” (Brooks 108)‏

4. Schedule Although this document is often hard to produce it does provide a road map for you to follow It helps you see how well you are doing Shows how far along the project is

5. Specifications One of the first documents started, but the last one finished. This document is serves as both  The Manual and Details out how to use your product  The Performance Specifications Details out all the things your product does

6. Budget How much is your project going to cost? Keep in mind  Space Allocations Estimate, Forecast, Prices.  If prices are really lower than the estimate.  If prices are above the estimate

7. Why? It is important to develop a plan and then complete it. Only a precise written plan is communicable.  Ideas and specifications that are not written down are very fuzzy and may be confused.  Written down ideas are clear and concrete To have a check list