FYP TITLE

SESSION (2015-2018)
Master of Computer Science & Information Technology
(MCS&MIT)
(Final Project Proposal)

Group Members:
S. # Student Id Name
1
2
3
4
5

Submission Date: February 07, 2019

 SCHOOL OF PROFESSIONAL ADVANCEMENT
UNIVERSITY OF MANAGEMENT & TECHNOLOGY, LAHORE

Table of Contents
1. Introduction..............................................................................................................................1
1.1 Purpose..............................................................................................................................1
1.2 Scope.................................................................................................................................1
1.3 Final Deliverable of the Project and Beneficiaries...........................................................1
1.4 Overview...........................................................................................................................1
2 Positioning...............................................................................................................................1
2.1 Business Opportunity........................................................................................................2
2.2 Problem Statement............................................................................................................2
2.3 Product Position Statement...............................................................................................2
3 Stakeholder and User Descriptions..........................................................................................3
3.1 Stakeholder Summary.......................................................................................................3
3.2 User Summary...................................................................................................................4
3.3 User Environment.............................................................................................................4
3.4 User Needs........................................................................................................................4
3.5 Methodology.....................................................................................................................5
4 Product Overview....................................................................................................................6
4.1 Product Perspective...........................................................................................................6
4.2 Assumptions and Dependencies........................................................................................6
4.2.1 Assumption................................................................................................................6
4.2.2 Dependencies.............................................................................................................6
4.2.3 Constraint (optional)..................................................................................................6
4.3 Benefits of the Product......................................................................................................6
5 Feasibility Study......................................................................................................................6
6 Work Breakdown Structure.....................................................................................................6
6.1 Key Milestones.................................................................................................................6
6.2 Gantt Chart........................................................................................................................7
7 High-level Architecture Diagram............................................................................................8
8 Tools and Technologies...........................................................................................................8
9 References................................................................................................................................8

Table of Figures
Figure 1: Work Breakdown Structure..............................................................................................6
Figure 2: High Level Architecture Diagram....................................................................................6

Table of Tables
Table 1: Problem Statement.............................................................................................................2
Table 2: Product Position Statement................................................................................................3
Table 3: Stakeholder Summary.......................................................................................................3
Table 4: User Summary...................................................................................................................3
School of Professional Advancement (SPA) <Project Name>

1. Introduction
This section should provide the brief description of why are you writing the proposal document and the significance
of the proposal document in the overall project. Also just define in few lines your project title for which you are
developing this proposal document for.

Just keep in your mind before start. Text size must be 11 and font style should be Times New
Roman. Heading size should be 18 and sub-heading size should be 16. Line spacing should be 1.15.
The alignment should be justified (Ctrl+J).

1.1 Purpose
This section should:
a. describe the purpose of this document;
b. specify the intended readership of this document.

1.2 Scope
This section should:
a. identify the products to be produced;
b. explain what the proposed system will do (and will not do, if necessary);
c. define relevant benefits, objectives and goals as precisely as possible;
d. define any security risks associated with the system;
e. Be consistent with similar statements in higher-level specifications, if they exist.
f. Defining the boundaries of the project in multiple dimensions including approach, deliverables,
milestones, and budget.

1.3 Final Deliverable of the Project and Beneficiaries

(Specify only one of the following; subsequently state Direct/Indirect beneficiaries of the project)

1.4 Overview
Section 1 is the introduction and includes a description of the project, applicable and reference documents. Section
2 provides a Business overview and problem statement. Section 3 contains the stakeholders and users. Section 4
describes the product description. Section 5 contains the system requirements.

2 Positioning
[The purpose of this document is to collect, analyze, and define high-level needs and features of the <<System
Name>>. It focuses on the capabilities needed by the stakeholders and the target users, and why these needs exist.
The details of how the <<System Name>> fulfills these needs are detailed in the other specifications. ]

Page 1 of 12
Group Members: Name (ID), Name (ID)
Name (ID), Name (ID)
School of Professional Advancement (SPA) <Project Name>

2.1 Business Opportunity

[This includes application in real time or market opportunities of your system.]
a. What created the need or how need was recognized.
b. Magnitude of the need: (Resource Plan / size/ cost/ expense)
c. Contributing Factors: i.e. what factors involve in creating need.
d. What extent of Need would be addressed, if an Alternative Exist?
e. If Need is not addresses at the end, what will be the consequences for state and customers.
f. Mention the existing system in the market that are your competitors and highlight their drawbacks
and loopholes.

2.2 Problem Statement

The statement of the problem briefly addresses the question: What is the problem that the application will address?

The problem of State the need

Affects Stakeholder(s) affected by need

the impact of which is Impact of the problem on stakeholder(s)

a successful solution would be Your product with benefit

Table 1: Problem Statement

2.3 Product Position Statement

A positioning statement is a concise description of your target market as well as a compelling picture of how you
want that market to perceive your brand. Though it may read like something from your promotional materials,
your positioning statement is an internal tool.

Page 2 of 12
Group Members: Name (ID), Name (ID)
Name (ID), Name (ID)
School of Professional Advancement (SPA) <Project Name>

For who Target Customer

Why Statement of Opportunity or need

The (product name) Product Name

Is a Product Category
1. Industry: technology or hospitality.
2. Functionality: accounting software or running shoes.
3. Customer Needs: summer versus winter.
4. Customer Preferences: healthy ingredients or a particular style.
5. Demographics: children's goods or women's clothing.
6. Convenience: fast food.
7. Quality: economy versus business class..
8. Performance: bicycles versus racing bicycles.

That Key Benefit or reason to buy

Unlike (Optional) Primary Competitor / Alternative(s) of the product

Our product Statement of Primary Differentiation

Table 2: Product Position Statement

3 Stakeholder and User Descriptions

[The purpose of this document is to list down all the stakeholders and identify each one by their roles in the
<<System Name>>.all human resource is listed down in this section.]

3.1 Stakeholder Summary

[Following are the stakeholders may or may not involve in this project e.g.:]

Name Description Responsibilities

Sponsor(optional in case Sponsor of the Project Provides approval, has budget ownership for
your project is funded) the project and is the major stakeholder and
recipient for the project deliverables.

Owner (your real time Provides policy definition to Resolves all policy, makes final decisions and
client) the Project team. resolves conflicts or issues regarding project
expectation.

Manger Mange and handles project Provides management to the project.

administrative duties, project Responsible for, developing and managing the
and team. work plan, acquiring appropriate resources
and delegating the work and insuring
successful completion of the project.

Team Members Working project team Analyzes, designs and improves the business
member. processes, collaborate with other teams to
develop high level process designs and
models, identify appropriate opportunities,
Page 3 of 12
Group Members: Name (ID), Name (ID)
Name (ID), Name (ID)
School of Professional Advancement (SPA) <Project Name>

challenging the old rules of the business and

stimulating creating thinking, and identifying
organizational impact areas.
Table 3: Stakeholder Summary

3.2 User Summary

Name Description Responsibilities
End Users Key provider of requirements heads, CIO’s and project management
and recipient of project representatives etc. add their responsibility.
(List all users with their deliverable
roles)
Table 4: User Summary

3.3 User Environment

[In this section describe in detail about the environment of the user, i.e. how user is going to interact with the
system application according to their role to ensure user has correct access level. For example items such as the file
systems, , desktop Pc, printers and applications they should and shouldn’t have access].

3.4 User Needs

The issues for stated problems with solutions:
Problem 1:
Description of Problem 1:
 What are the reasons for this problem?
Describe Reasons.
 How is it solved now?
Proposed Solution.
 What solutions do the Stakeholders want?
Success Criteria set by Stakeholder. (Such metrics might include how to measure customer
satisfaction or might state what a “user friendly” system is)
Problem 2: (optional if more than one problems are addressed)
Description of Problem 2:
 What are the reasons for this problem?
Describe Reasons.
 How is it solved now?
Proposed Solution.
 What solutions do the Stakeholders want?

Page 4 of 12
Group Members: Name (ID), Name (ID)
Name (ID), Name (ID)
School of Professional Advancement (SPA) <Project Name>

Success Criteria set by Stakeholder. (Such metrics might include how to measure customer
satisfaction or might state what a “user friendly” system is)

3.5 Methodology
This section would address the ‘How’ part. Briefly write down your intended approach towards tackling above
problems. Name any algorithm or third party library you would use, any particular technique you are going to
follow etc.

Page 5 of 12
Group Members: Name (ID), Name (ID)
Name (ID), Name (ID)
School of Professional Advancement (SPA) <Project Name>

4 Product Overview
[This section provides a detail overview of the product with all constraint, dependencies on other projects and
assumptions. Further product features and its benefits are discussed thoroughly].

4.1 Product Perspective

[This subsection of the document puts the product in perspective to other related products and the user’s
environment. If the product is independent and totally self-contained, state it here. If the product is a component of
a larger system, then this subsection needs to relate how these systems interact and needs to identify the relevant
interfaces between the systems. One easy way to display the major components of the larger system,
interconnections, and external interfaces is with a block diagram.]

4.2 Assumptions and Dependencies

[List each factor that affects the features stated in the document.]

4.2.1 Assumption
[List assumptions that, if changed, will alter the Vision document. For example, an assumption may state that a
specific operating system will be available for the hardware designated for the software product. If the operating
system is not available, the Vision document will need to change.]

4.2.2 Dependencies
[Optional. Its mandatory to mention if your project is depending upon another project’s deliverable. This
needs to be identified and its progress monitored. In other cases, a project may be dependent upon information
from several agencies; the tasks and activities of the information gathering process need to monitored.]

4.2.3 Constraint (optional)

[Any type of limitations in the project e.g. limited resource (in terms of time, people, equipment or money).]

4.3 Benefits of the Product

Benefits of doing the project. Benefits should link back to the business need or opportunity.

 Benefit 1
 Benefit 2

5 Feasibility Study
With above defined scope, would you be able to meet your project schedule? Do mention following aspects:
i. Risks Involved: Identify the risks involved, and how you would be able to cater?
ii. Resource Requirement: What computing or any other resource you would need?

6 Work Breakdown Structure

MS Project tool can be used for project management purpose. Few links are given below for learning tools

https://www.youtube.com/watch?v=iUqbhkJWt_4
https://www.youtube.com/watch?v=_eD2u8bxecs

Page 6 of 12
Group Members: Name (ID), Name (ID)
Name (ID), Name (ID)
 School of Professional Advancement (SPA) <Project Name>

6.1 Key Milestones

Following are the major milestones of the project and their related information.

No. S. o. of Key Milestone Name / Description Duration

Predecessor (person-hours)
Milestone

2
3
…
…

If needed any details related to any item of the above table then describe them here.

Figure 1: Work Breakdown Structure

6.2 Gantt Chart

(A sample Gantt chart)

Activit
y 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Milesto
ne 1
Milesto
ne 2
Milesto
ne 3
Milesto
ne 4
Milesto
ne 5
Milesto
ne 6

Page 7 of 12
Group Members: Name (ID), Name (ID)
Name (ID), Name (ID)
School of Professional Advancement (SPA) <Project Name>

7 High-level Architecture Diagram

Figure 2: High Level Architecture Diagram

8 Tools and Technologies

This section should explain the tools and technologies that you will use in your project.

9 References
Mention all the literature or web references here. The references should be properly numbered and
correctly used in the text.
Reference text should be written in quotes and indented and the references marked in [square
brackets]. “Reference material”[1].
The Reference section should be in the following fashion:
 Book: Last Name, First Name. “Tide of Book”. City: Publisher, Copyright Date. Page numbers
 Magazine/ Newspaper Article: Author's last name, Author's first name. "Title of article," Name of
magazine/newspaper, date of magazine/newspaper, page number(s).
 Internet Web page: Author. “Title of Web page”. Date on the page. Company associated (if any).
Date you last saw the page. URL.
 Online Magazine or Newspaper Articles: Author's last name, Author's first name. "Title of
article." Name of magazine, date of magazine, page numbers. Reproduced in Name of Database.
Library where database was accessed, location of library. Date of access.

Page 8 of 12
Group Members: Name (ID), Name (ID)
Name (ID), Name (ID)