Project Proposal Guide Date: 17th October 2018

The University of Lahore

Final Project Proposal Guide

Version 1.0

Instructions:
 This is a group assignment.
 A group would consist of minimum 1 and maximum 3 students.
 All groups have to select a software project of considerable
complexity and submit the below project proposal for it.
 Mode of Submission: Hard Copy
 Submit to: Teacher’s mailing address.

UoL
1
Project Proposal Guide Date: 17th October 2018

TABLE OF CONTENTS

1.
FINAL PROJECT PROPOSAL GUIDE......................................................................................................2

1.1 PROJECT TITLE.......................................................................................................................................3

1.2 PROJECT OVERVIEW STATEMENT...........................................................................................................3
1.4 PROJECT GOALS & OBJECTIVES.............................................................................................................5
1.5 HIGH-LEVEL SYSTEM COMPONENTS.......................................................................................................5
1.6 LIST OF OPTIONAL FUNCTIONAL UNITS..................................................................................................5
1.7 EXCLUSIONS...........................................................................................................................................6
1.8 APPLICATION ARCHITECTURE.................................................................................................................6
1.9 GANTT CHART........................................................................................................................................7
1.10 HARDWARE AND SOFTWARE SPECIFICATION........................................................................................7
1.11 Tools and technologies used with reasoning........................................................................................7

UoL
2
Project Proposal Guide Date: 17th October 2018

Project Proposal Guidelines

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. Try and use only a single sentence for your title. Try to remove words
from your title that really are not necessary for understanding.
 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.

1.2 Project Overview Statement

 Think of the Project Overview as an Executive Summary (the busy executive
probably only has enough time to read your Overview - not the entire proposal).
 Be specific and concise. Do not go into detail on aspects of your proposal that are
further clarified at a later point in your proposal.
 Let the Overview be your last piece of writing and then insert it at the beginning
of your proposal. Try to keep in mind that someone will be reviewing your
proposal and you would like to have this person be very positive about what you
have written.
 The Project Overview will probably form a strong impression in the mind of the
reviewer.
 Work on your Project Overview so that you can avoid giving this person the
opportunity to say things like:

1. Not an original idea

2. Rationale is weak
3. Writing is vague
4. Uncertain outcomes
5. Does not have relevant experience
6. Problem is not important
7. Proposal is unfocused
8. Project is too large.

UoL
3
Project Proposal Guide Date: 17th October 2018

Project Overview Statement Template

Project Title:

Group Leader:
Project Members:
Name Roll Number Email Address Signature

Project Goal:

Objectives:
Sr.#
1
2
3
4
5
6
Project Success criteria:

Assumptions, Risks and Obstacles:

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_____________________
Date:

1.4 Project Goals & Objectives

 Try and differentiate between your goals and your objectives - and include both.
 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.
 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

UoL
4
Project Proposal Guide Date: 17th October 2018

activities of your project and will also serve as the basis for the evaluation of your
project.

1.5 High-level system components

 Information about the main functional units of the entire system should be
present. Functional units to be included will be the inclusive components of the
project developed so that the system must perform without taking any physical
constraint into consideration.
 High-level system components are generally, a set of cooperating components
assembled together to deliver a solution to a problem. They are frequently
identified in terms of inputs, outputs, processes, and stored data that are needed to
satisfy the system improvement objectives.
 If these components are missing the system fails to fulfill its primary mission.

1.6 List of optional functional units

 A list of functional units should be present which would include a description of
other features, characteristics, and constraints that define a satisfactory system.
 These functional units would be developed under certain conditions (technology,
expertise, or time dependent). Examples of these optional functional units would
include performance (throughput and response time); ease of learning and use;
budgets, costs, and cost savings; timetables and deadline; documentation and
training needs; quality management; and security and internal auditing controls.
 They are often requirements that specify need of compliance with any legal and
regulatory requirements.
 If the optional functional units are missing the system can still (for a while) fulfill
its fundamental mission, but with degraded service quality.

1.7 Exclusions
 A list of the functional units, which will not be intended to be develop or
discussed during any point in the project development, should be present.

1.8 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

1.9 Gantt chart

Sample Gantt chart
Jul 6, '03 Jul 13, '03 Jul 20, '03
ID Task Name Duration Start Finish Predecessors W T F S S M T W T F S S M T W T F S
1
2 billing 7 days Thu 7/10/03 Fri 7/18/03
3 computing 8 days Mon 7/14/03 Wed 7/23/03
4 accounting 3 days Mon 7/14/03 Wed 7/16/03
5 marketing 10 days Mon 7/21/03 Fri 8/1/03 2

UoL
5
Project Proposal Guide Date: 17th October 2018

1.10 Hardware and Software Specification

 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.

1.11 Tools and technologies used with reasoning

The application tools, which are to be used on front and back end of the system to be
developed, should be listed. The reasons for these tools should also be enlisted.
Identify what the needs for tool support are, and what the constraints are, by looking at
the following:
 The development process. What tool support is required to effectively work? For
example, if the organization decide to employ an iterative development process, it
is necessary to automate the tests, since you will be testing several times during
the project.
 Host (or development) platform(s).
 Target platform(s).
 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

UoL
6