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
Zahid Mehmood BSIT-F13-LC-387
Haseeb Munawar BSIT-F13-LC-57
Huzaifa Bin Zahoor BSIT-F13-LC-16
M.Noman Arshad BSIT-F13-LC-08
Rabay Akhter BSIT-F13-LC-409

University of Sargodha, Lahore Campus

Faculty of Computer Science & Information Technology

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: __________________________________

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

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

1.1 Project Title

Pakistan Cricket Board (PCB) Application.

1.2 Introduction and Background

To provide Android users, live feeds and newsletters of Pakistan Cricket.
//The purpose of this section is to describe the general problem area.

1.3 Problem Statement

Out of 1.4 billion (estimated) Android users all over the world, there are 40 million
(estimated) Android users in Pakistan. There is no such application for Pakistan Cricket
 fans from where they can see the live news feed & live streaming of Pakistan Cricket
while using there handheld devices.

1.4 Previous Work

There is no relevant work done in this era by anyone.

1.5 Objectives of the Project

Our objectives for this Android application are (Remove the written application
system)“Facilitating users with such options like online submit applications, Show your
personal data through face recognize, easily view monthly record, Easily view data or
record of staff(only HOD), submit Application in one click or quickly, quickly view
notification In case of accepted and rejected of application , view all holidays in
application.”

1.6 Specific Project Goals

Our goals states that “Providing the best solution to the staff of any institute which face
many difficulties to write Application and required to sign the different head of
department in case of emergency. Through our application member of any staff submit
online application in case of any emergency and HOD easily see the record of person and
accepted or rejected the application quickly to see the record of person. (For this process
applicant presence not neccessary in institute because all process perform online with
application.)
1.7 Scope the Project (Abstract):
This android application is not just for isntitute,its used in any company or any
department. This android application is more user attractive and reliable.
1.8 Glossary
Leaving System For All Domains Like Organizations,Industries,Institutions etc.

1.9 Project Overview Statement Template

Project Title: E-Leaving Application

Group Leader: Muhammad Shahzad

Project Members:
Name Registration # Email Address Signature
Mateen Ali 15F-US-L-CSC-940 [email protected]
Khizar Ashraf 15F-US-L-CSC-693 [email protected]
Muhammad Shahzad 14F-US-L-CSC-371 [email protected]

Project Goal: “ Providing the best available solution to the problem of leaving which is providing facility
to the Employees to take leave Online with interactive user interface of E-Leaving application as well as all
the functionalities on single platform.”

Objectives:
Sr.#
 1 Online Leave
2 Monitoring Holidays
3 Push notification
Project Success criteria: E-Leaving Application users, downloads hits and reviews form users will define
the success of this project:

• Risks of the Project:

(Please mark where applicable)
Low Medium High
• Technical risk   

• Timing risk   

• Budget risk   
Organization Address (if any): UOS Lahore

Type of project: Problem-Solving Development

Target End users: Handheld Android Users

Development Technology: Object Oriented Structured

Platform: Android -Based Distributed
Other_____________________
Suggested Project Supervisor: Sir Zeeshan Mubeen
Approved By:
Date:

2. Benefits of the Project

2.1 Direct Customers / Beneficiaries of the Project
The direct customers of this application is a flow of bottom up in
each domain. Employees of any organization, institute, corporation as well as upper level
management is used this application for leaving purpose.

2.2 Outputs Expected from the Project

For this project output is expected too much positive because we
neglect the use of paper by using online leaving application. The expected outcome of this
project is 99.9%.

3. Project Description
3.1 Functional Specification
Allowing users to read the articles of players and other activities that is happening in
PCB. Most important feature of this application will be live streaming on handheld
devices by direct access of live feeds or from YouTube. Keeping users up to date for
upcoming matches and events through Push notification. Through news and press
releases user can stay tuned about every event occur in PCB. Users can see Photos and
watch videos of current and past events by checking into Photo-Vides gallery. Users can
see Official page of PCB on Facebook, twitter and Instagram easily by tapping on to
Social Media option. Users will also have option for playlist of multiple videos of last
played matches and etc. There will always be a space for sponsors to add their
 Advertising banners on our application. Providing an opinion piece written by senior
editorial staff or publisher of newspaper.

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

Each and every activity will have their own timespan for their events on Application, like
live summery of match being played will remain on activity until unless it finished.
Articles will be limited. High speed internet will be needed for live streaming. We aren’t
able to show scorecard of matches (this will be our future goal). Only sponsors adds will
be entertained.

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

We will be using Core i5 for Development.
And application will run on lollipop OS minimum, nugget OS will be latest. 512MB of
RAM will must be needed.

3.1.5 Implementation Tools and Technology

• Android platform will be used for development.

• Target platform will also be android users or Android OS.
• The programming language will be Java.
 • Best existing tool is Android studio but also there is option for Eclipse for android
development, but we will user latest version of Android Studio because its best
suited and specially build for android development.
• The size of the development effort will be great because high skills are required
for this project.
• Budget will maybe needed for designing purposes. Time: more time the better.

3.2 Implementation Plan

3.2.1 Deliverable Items

Deliverable will only be Apk file.

3.2.2 Milestone Identification

• 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
• 2 months 1st 3 objectives Apk

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

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
5.1 Personal Background
Mateen Ali: Been Internship in Pakistan Tele Communication Limited (PTCL).
Muhammad Shahzad : Been working as intern in Software House from 3 months.
Khizar Ashraf : Been working as intern in Software House from 3 months.

5.2 Courses Taken

Mobile Application Development.

5.3 Programs Written

Only designing is relevant to this project.
5.4 Projects
Not even a single project.

Appendix A