Part 1
The Project Proposal
1. The first two weeks of software development will be devoted to the creation of the project proposal, which in effect is an initial recommendation to the customer of whom the project group has been nominated to serve. In a practical sense, the customer will then decide the actual scope of the project.
2. The most common projects taken up by previous project groups have been systems simulating a computerised Car Rental System, Cinema Ticketing System, Payroll System, Student Registration System, Tour Packaging System, Leave Application System, etc. Needless to say, these projects have been literally done to death, and your project supervisor has been instructed to strongly advise your project group to not put up proposals like these as first choice.
The Proposal
1. In some ways, the Project Proposal can be thought of as a “watered-down” or briefly-summarised version of the Analysis report. Keep in mind that this proposal is simply an initial recommendation that will help the customer to only decide whether they are interested in commissioning the project group to undertake an in-depth study of the current system. In other words, the Project Proposal does not attempt to provide enough information for the customer to decide whether to go ahead with the actual implementation of such a system.
2. Although the precise contents of the proposal may be altered to suit your project group and its selected project type, typically, the proposal should at least contain the following sections:
* A short introduction to the organisation: history, turnover. * A description of the current system, or the “current way of doing things”. * A section explaining the basic problems and limitations as faced by the customer’s point of view. * An proposal of the new system, containing the objectives of the new system (should be made relevant to the basic problems and