Sample Cover Sheet for Proposal

Project Proposal

Title Of Final Project

Submitted to the
Project Management Committee
Department of Computer Science & Information Technology
University Of Sargodha, Lahore Campus

Submitted By
Name of Student ID of Student

Name of Student ID of Student

University of Sargodha, Lahore Campus

Faculty of Computer Science & Information Technology

Project Management Committee

Faculty of Computer Science & Information Technology, University of Sargodha, Lahore Campus
1
 Faculty of Computer Science & Information Technology
APPROVALS

Project ID (for office use) ______________________________

Session: _______________________________________

Agree to Adviser: _________________________________

(Name of adviser)

Date Submitted: __________________________________

Approved by: ____________________________________

Date Approved: __________________________________

Project Management Committee

Faculty of Computer Science & Information Technology, University of Sargodha, Lahore Campus
2
Section 1 Project Proposal Outline
i. Title Page
ii. Approval Page
iii. Table of Contents
1. Introduction
1. 1 Project Title
1.2 Introduction and Background
1.3 Problem Statement
1.4 Previous Work
1.5 Objectives of the Project
1.6 Specific Project Goals
1.7 Scope of the Project (Abstract)
1.8 Glossary
1.9 Project Overview Statement Template
2. Benefits of the Project
2.1 Direct Customers / Beneficiaries of the Project
2.2 Outputs Expected from the Project

3. Project Description
3.1 Functional Specification
3.1.1 Functions Performed
3.1.2 Limitations and Restrictions
3.1.3 Application Architecture
3.1.4 Equipment Configuration
3.1.5 Implementation Tools and Technology
3.2 Implementation Plan
3.2.1 Deliverable Items
2.3.2 Milestone Identification
A-Key Milestones and Deliverables
3.3.3 Project Schedule / Milestone Chart
4. References
5. Qualifications
4.1 Personal Background
4.2 Courses Taken
4.3 Programs Written
4.4 Projects

Project Management Committee

Faculty of Computer Science & Information Technology, University of Sargodha, Lahore Campus
3
Section 2 Description of Outline Sections

This section describes the purpose or format of each of the sections indicated in the
preceding proposal outline.

i. Title Page
See the sample in Appendix- A for format.

ii. Approval Page

See the sample in Appendix- B for format.

iii. Table of Contents

This should follow the outline given in Section 1 of this document.

1 Introduction
This guide will tell you how to prepare and submit the final project proposal that
is the documented work for the Project. A good project proposal must define the
functional and non-functional requirements in unambiguous statements, Scope of
the Project, Development Schedule, Development Process, Techniques, Tools,
Platform with reasoning. However, a professional and well-defined proposal
should be composed under the following headings;

1.1 Project Title

The title should be clear and unambiguous (do not make it "cute"). Think of your
title as a mini-abstract. A good title should paint a quick picture for the reader of
the key idea(s) of your project. The words you use in your title should clearly
reflect the focus of your proposal. The most important words should come first,
then the less important words. Try to remove words from your title that really are
not necessary for understanding. Try and use only a single sentence for your title.
If the sentence is getting too long try removing some words. When all else fails
try using a two-part title with the parts separated by a colon (use only as a last
resort!). Do not attempt to use the title as an abstract of your entire proposal. If
your proposal is built on collaborating with other groups/organizations it is
usually a good idea to include their names on the Title/Cover Page.

1.2 Introduction and Background

The purpose of this section is to describe the general problem area.

1.3 Problem Statement

Give a brief, general statement of the problem to be investigated or solved by the
project. Assume the reader has little knowledge of the subject.
Project Management Committee
Faculty of Computer Science & Information Technology, University of Sargodha, Lahore Campus
4
1.4 Previous Work
This is an historical or conceptual survey of relevant work done in the area by
previous investigators. Each contribution must be accompanied by appropriate
references to be listed in the reference section.

1.5 Objectives of the Project

Describe the current state of the art specific to this research topic and the
motivation and need for this work Try and differentiate between your goals and
your objectives - and include both. Objectives are operational, describe specific
things you will be accomplishing in your project, and are very measurable. Your
objectives will form the basis for the activities of your project and will also serve
as the basis for the evaluation of your project. Measurable objectives for your
project should be presented. If you are dealing with "things" it is easier for them
to be measured than if you are dealing with abstract ideas. Your proposal is easier
for a prospective funding organization to understand (and the outcomes are much
more clear) if you describe your objectives in measurable ways.

1.6 Specific Project Goals

Goals are the large statements of what you hope to accomplish but usually aren't
very measurable. They create the setting for what you are proposing.
1.7 Scope the Project (Abstract):
Describe the current state of the art specific to this research topic and the
motivation and need for this work.

1.8 Glossary
This section defines all terms, concepts, symbols, and acronyms used in the
proposal.
1.9 Project Overview Statement Template

Project Title:

Group Leader:
Project Members:
Name Registration # Email Address Signature

Project Goal:

Project Management Committee

Faculty of Computer Science & Information Technology, University of Sargodha, Lahore Campus
5
Objectives:
Sr.#
1
2
3
4
5
6
Project Success criteria:

Risks of the Project:

(Please describe the factors that may cause delays in, or prevent implementation of, the project as
proposed above; estimate the degree of risk.)
(Please mark where applicable)
Low Medium High
Technical risk
Timing risk
Budget risk
Organization Address (if any):

Type of project: Research Development

Target End users:

Development Technology: Object Oriented Structured

Platform: Web based Distributed
Desktop based Setup Configurations
Other_____________________
Suggested Project Supervisor:
Approved By:
Date:

2. Benefits of the Project

2.1 Direct Customers / Beneficiaries of the Project
2.2 Outputs Expected from the Project

3. Project Description
The purpose of this section is to describe the proposed project in detail: what will
you do, how will you do it, and when will you do it.

3.1 Functional Specification

This is a detailed specification of functions performed by the proposed system,
from an external or user perspective, not from an internal or programmer
viewpoint. Thus, the system is regarded as a black box with various inputs and

Project Management Committee

Faculty of Computer Science & Information Technology, University of Sargodha, Lahore Campus
6
 outputs related by the functions performed by the system. The description should
be sufficient for another programmer to implement the system.

3.1.1 Functions Performed

List and briefly describe each of the functions which the system will be designed
to perform for its user: What the system will do.

3.1.2 Limitations and Restrictions

List and describe each of the internal (self) and external (environment) limitations
and/or restrictions on the range of system functions: What will the system not do.
DO NOT INSULT THE READER BY INCLUDING ITEMS THAT WOULD
NOT BE A SURPRISE.

3.1.3 Application Architecture

Defines the overall application architecture e.g. a two-tier architecture or a three-
tier architecture. It must contain a diagram depicting the system architecture
properly Architecture is the highest-level concept of a system in its environment.
The architecture of a software system (at a given point in time) is its organization
or structure of significant components interacting through interfaces, those
components being composed of successively smaller components and interfaces.
Architecture can also be defined as the organizational structure of a system.
Architecture can be recursively decomposed into parts that interact through
interfaces, relationships that connect parts, and constraints for assembling parts.
Parts that interact through interfaces include classes, components and subsystems.
There are a number of typical patterns of distribution in systems, depending on
the functionality of the system and the type of application. In many cases, the
distribution pattern is informally used to describe the 'architecture' of the system,
though the full architecture encompasses this but also many more things. For
example, many times a system will be described as having client-server
architecture', although this is only the distribution aspect of the architecture.

3.1.4 Equipment Configuration

Describe the equipment you will use to support the operation and development of
your system. Any hardware or software specifications e.g. machine type required,
operating system and other utilities should be clearly specified for the system to
be developed.

3.1.5 Implementation Tools and Technology

List the application tools and technologies which you plan to use for the
implementation of your project and give reasons for choosing each technology.
Identify what the needs for tool support are, and what the constraints are, by
looking at the following:

Host (or development) platform(s).

Target platform(s).

Project Management Committee

Faculty of Computer Science & Information Technology, University of Sargodha, Lahore Campus
7
 The programming language(s) to be used.
Existing tools. Evaluate any existing and proven tools and decide whether
they can continue to be used.
The distribution of the development organization. Is the organization
physically distributed? Development tools generally support a physically
distributed organization differently.
The size of the development effort. Tools support large organizations
more or less well.
Budget and time constraints

3.2 Implementation Plan

3.2.1 Deliverable Items
List and describe each of the items you will submit in fulfillment of the project
requirements. Deliverable items include, but are not limited to, program
executable file(s), program data file(s), program listings, program documentation,
user manual and sample program runs.

3.2.2 Milestone Identification

Identify each of the milestones or check points that mark the completion of some
phase of project implementation. Milestones include, but are not limited to,
detailed system analysis, system design, file design, module design, system test
design, module coding, working breadboard with stubs, working system with
stubs, system testing and documentation.

A. Key Milestones and Deliverables:

(Please list and describe the principal milestones and associated deliverables of the
project. A key milestone is reached when a significant phase in the project is concluded,
e.g. selection and simulation of algorithms, completion of architectural design and
design documents, commissioning of equipment, completion of test, etc.)

The information given in this table will be the basis of monitoring by Project Coordination Office.

No. Elapsed time Milestone Deliverables

from start (in
months) of
the project
1.
2.
3.
4.

Project Management Committee

Faculty of Computer Science & Information Technology, University of Sargodha, Lahore Campus
8
5.
6.
(Please add more rows if required.)

3.3.3 Project Schedule / Milestone Chart

Project schedule using MS-Project (or similar tools) with all tasks, deliverables,
milestones, cost estimates, clearly indicated are preferred

Example:

4. References
In this section you list in standard bibliographic format the books, papers, course
notes and project or thesis reports which you have used in preparing your project
proposal. Each item listed here must be accompanied by a brief comment
indicating its importance and relevance to the proposal.

References must be numbered alphabetically. In the text they should be referred

to by squared bracketed numerals, e.g. [1]. The list of references must be typed on
a separate sheet(s), in the same format as the main text, and ordered
consecutively, according to the following models:

For a paper in a contributed volume:

[1] D.B. Lenat, R. Davis, J. Doyle, M. Genesereth, I. Goldstein and H. Schrobe,

"Reasoning about reasoning," in Building Expert Systems (F. Hayes-Roth, D.A.
Waterman and D.B. Lenat, eds.) Addison-Wesley Publishing Company, Inc.,
1983,pp. 219-240.

For a paper in a journal:

[2] D.W. Jones, "Concurrent operations on Priority Queues," Communications of

the ACM, 32, l(January 1989), pp- 132-137.

Project Management Committee

Faculty of Computer Science & Information Technology, University of Sargodha, Lahore Campus
9
 For a book:

[3] H.F. Korth and A. Silberschatz, Database System Concepts, McGraw-Hill,

New York, 1986.

For an unpublished paper:

[4] S.E. Feahlman, A system for representing and using real-world knowledge,
MIT Technical Report Al-TR-40, Cambridge, MA, 1977.

5. Qualifications
The purpose of this section is to show the advisor that you are capable of
successfully completing the proposed project.

5.1 Personal Background

Describe any personal experience such as outside employment that is
he proposed project.

5.2 Courses Taken

List by department, number and title all courses you have taken. Briefly
describe the courses you think have particular relevance to the project.

5.3 Programs Written

Describe any programs you have written which either are relevant to the
project or are indicative of your ability to complete the proposed work.

5.4 Projects
Describe any relevant projects you have been involved in or have
undertaken.

Project Management Committee

Faculty of Computer Science & Information Technology, University of Sargodha, Lahore Campus
10
 Appendix A

Project Management Committee

Faculty of Computer Science & Information Technology, University of Sargodha, Lahore Campus
11