A typical project plan document would have the followings: A short introduction to the organisation / system (history, achievements)

) A description of the current system, or the current way of doing things. A section about basic problems and limitations as faced by the customers point of view. A proposal of the new system, containing the objectives of the new system (should be made relevant to the basic problems and limitations of the current system), and a description of the new system, with an identification of the major modules of the new system. The initial new system requirements (also known as the Initial Specifications). This in effect is preliminary statement in precise terms what exactly the project team recommends the proposed system be able to do. A section explaining the benefits of the implementation of such a system. The hardware and software equipments to be used in the development, and also hardware and software equipments of the target platform as used by the system. A cost/benefit study. The cost/benefit study should not simply be a theoretical presentation but preferably contain a breakdown of monetary costs and expected benefits of the proposed system, payback periods and Return of Investment (ROI). A Gantt chart indicating the planned progress for the project group. The Gantt chart should be reasonably detailed The Gantt chart in the proposal should be broken into a week by week basis. For example, the Analysis phase can be broken into the following sub-activities: Preliminary survey Collection of relative information Interview phase Observation phase Hard-data investigation Consolidation of information Development of Data Flow Diagram DFD Analysis Requirement Specification Documentation Note : Contoh hotel Kyoto ada yang terbalik antara A proposal of the new system dengan the initial new system requirements