Sample Proposal
Proposal
System Name
12/3/2002
TableofContents
1.0 EXECUTIVE SUMMARY................................................................................................................ - 2 1.1 BACKGROUND ...................................................................................................................................- 2 1.2 OVERVIEW .........................................................................................................................................- 2 1.25 EXPERTISE .......................................................................................................................................- 2 1.3 GOAL .................................................................................................................................................- 2 2.0 CURRENT ENVIRONMENT .......................................................................................................... - 3 2.1 BUSINESS OVERVIEW .........................................................................................................................- 3 2.15 SYSTEM OVERVIEW .........................................................................................................................- 3 2.2 EXISTING FUNCTIONALITY.................................................................................................................- 3 2.3 SYSTEM ARCHITECTURE ....................................................................................................................- 3 2.4 LIMITATIONS OF EXISTING SYSTEMS .................................................................................................- 3 3.0 USER REQUIREMENTS ................................................................................................................. - 4 3.1 OVERVIEW .........................................................................................................................................- 4 3.2 HARDWARE........................................................................................................................................- 4 3.3 APPLICATION .....................................................................................................................................- 4 4.0 RATIONALE FOR APPROACH (OPTIONAL)............................................................................ - 5 5.0 SYSTEM DESIGN............................................................................................................................. - 6 5.1 OVERVIEW .........................................................................................................................................- 6 5.2 HARDWARE........................................................................................................................................- 6 5.3 SOFTWARE .........................................................................................................................................- 6 5.4 CONTEXT DIAGRAM...........................................................................................................................- 6 5.45 FLOW DIAGRAM...............................................................................................................................- 6 5.5 DATA DIAGRAM.................................................................................................................................- 6 5.6 SCREEN LAYOUTS ..............................................................................................................................- 6 5.7 REPORT SAMPLES ..............................................................................................................................- 6 6.0 ESTIMATE OF COSTS.................................................................................................................... - 7 6.1 MATERIALS........................................................................................................................................- 7 6.2 SERVICES ...........................................................................................................................................- 7 6.3 SCHEDULE PLAN ................................................................................................................................- 7 6.4 SUMMARY ..........................................................................................................................................- 7 7.0 ABOUT THE COMPANY PROPOSING THE WORK ................................................................ - 8 APPENDICES.......................................................................................................................................... - 9 -
-1-
Proposal
System Name
12/3/2002
1.0 Executive Summary
The executive summary will describe the foursub-topics depicted below and should be
business oriented rather than highly technical.
1.1 Background
This section contains a general description of problems to be solved and a brief description of
the current, if any, solution. The description of the current solution should include both its
assets and shortcomings.
1.2 Overview
This section describes the proposed solution, how the solution addresses the aforementioned
problem and how it adds value to the court.
1.25 Expertise
This section should briefly describe the consultant’s qualifications and experience in the area
of concern.
1.3 Goal
This a general list of objectives which need to be met for the project to be considered
successful.
-2-
Proposal
System Name
12/3/2002
2.0 Current Environment
This section should discuss the existing environment, including system architecture, existing
application functionality and any limitations that the existing environment poses to the court.
Include any diagrams that will make it easier to understand the environment.
2.1 Business Overview
This section should discuss the different department dependencies (inter and intra
departmental) and interaction.
2.15 System Overview
This section should provide an overview of the current system.
2.2 Existing Functionality
This section should list the existing functionality of the client application.
2.3 System Architecture
This section should discuss the architecture of the client system (network topology, OS
structure, Database systems, etc.)
2.4 Limitations of Existing Systems
This section should list all limitations of the existing system.
-3-
Proposal
System Name
12/3/2002
3.0 User Requirements
This section should be geared toward the end user. It describes the users’ needs and how the
proposed system addresses those needs.
3.1 Overview
This section should describe the goals of the system, including the scope of the system. Visual
aids (ERD’s, process flows, and other diagrams) are extremely useful.
3.2 Hardware
This section should describe hardware requirements and their parameters.
3.3 Application
This section should describe software requirements and their parameters.
-4-
Proposal
System Name
12/3/2002
4.0 Rationale For Approach (Optional)
This section should list advantages and disadvantages of alternative approaches and provide
a summary of the logic used to decide which alternative is best.
-5-
Proposal
System Name
12/3/2002
5.0 System Design
This section is geared toward those with the technical aptitude to make an assessment of the
system proposed. It describes the system design in depth.
5.1 Overview
This section should describe the system architecture...process flow, etc.
5.2 Hardware
This section should describe hardware requirements and their parameters.
5.3 Software
This section should describe software requirements and their parameters.
5.4 Context Diagram
This section should provide a diagram of the broad system overview.
5.45 Flow Diagram
This section should provide a diagram of the process overview and process interaction.
5.5 Data Diagram
This section should provide a diagram of the relationship between the various components of
the proposed system.
5.6 Screen Layouts
5.7 Report Samples
-6-
Proposal
System Name
12/3/2002
6.0 Estimate of Costs
This section should give a breakdown of costs. Justification of cost, where applicable, is
helpful.
6.1 Materials
This section should list hardware, configuration, quantity, unit price and total price.
6.2 Services
This section should list implementation roles (DBA, Junior Application Developers, etc.) and
their associated costs.
6.3 Schedule Plan
This project plan should include resources and costs as well as milestones and guidelines to
reach objectives.
6.4 Summary
This section should describe the bottom line: the deliverable and its cost.
-7-
Proposal
System Name
12/3/2002
7.0 About the company proposing the work
This section will give an overview, and should emphasize experience with the proposed
solution at hand.
-8-
Proposal
System Name
12/3/2002
Appendices
This section will include information that is not directly required in the above text, but is
relevant and meaningful.
-9-