FYP - Proposal-Version 1.2 Final
FYP - Proposal-Version 1.2 Final
Submitted By
Supervisor
Name
Designation
Year
Project ID GIMS-BSCS-201701
Project Title
Group Leader: Member Name
Group Members:3
Name Registration # Email Address Class
Member 1 Reg # membermailid@gmail.com BSCS
Member 2 Reg # membermailid@gmail.com BSCS
_____________________
Mr. / Ms. XYZ
PMO, GIMS
Date Format:
October 23, 2017
(Hand Written)
Dated: _____________________
i
© Gujrat Institute of Management Sciences
PMAS-Arid Agriculture University, Rawalpindi
Approval
Supervisor
Mr / Ms. XYZ
Designation, GIMS
Dated: _____________________
ii
© Gujrat Institute of Management Sciences
PMAS-Arid Agriculture University, Rawalpindi
The BLUE text enclosed in [ ] is description of
the corresponding section followed by an
example i.e. to assist that what and how you
should write in each heading/section.
Note: Same pattern will be followed in rest of the
sections. You are required to write your own
description in each section.
Line Spacing: 1-1.5 (Adjust able in case of large Abstract
abstract)
[A good introduction should tell the reader what the project is about without assuming
special knowledge and without introducing any specific material that might obscure
the overview. It should anticipate and combine main points described in more detail in
the rest of the project report. Also, importantly, it should enthuse the reader about the
project, to encourage them to read the whole report. Normally it should include such
things as:
The BLUEtext enclosed in [ ] is
description of the corresponding section
The aim(s) or goal(s) of the project; followed by an example i.e. to assist that
what and how you should write in each
heading/section.
The intended audience or “beneficiaries” of the work done; Note: Same pattern will be followed in
rest of the sections. You are required to
The scope of the project; write your own description in each
section.
The approach used in carrying out the project;
Assumptions on which the work is based; and
A broad summary of important outcomes.
]
The proposed system will provide functions that are need for ones to keep track
on hashtag. Data analysis, graph and report generation can be done after data is
collected. Public reaction and their satisfaction towards the event can be seen after
analysis is being done.
[The rest of the introduction chapter will include the below mentioned elements:
1
o Problem Statement
o Project Goals
o Significance
o Objectives
o Overview
o Limitations and Restrictions
o System Architecture
Component no.1
Component no.2
Component no.3
Component no.4
o Software/Hardware Requirements
o Implementation tools and Technologies
o Implementation Plan
Deliverable Items
Milestone chart (Gant chart)
]
[This section describes the problem that is to be addressed during the project work.
This is the rationale for what you will be doing and why it is important, why it
demands your attention. You might present this statement in terms of quantitative
metrics or qualitative criteria, or you may simply state the problem in the form of one
or more questions: "what if"? Since the problems can be theoretical or applied in
nature, the statement of the problem can vary according to these forms. So, it becomes
a matter of what is most appropriate, given the type of project work that is to be
conducted, the domain(s) in which the work is being done, and on the nature and
scope of the problem to be solved.
It is no use coming up with a problem such as "I want to solve the problems of
software maintenance". The Assessors here are looking for clear focus and a clearly
identified problem. Also, be sure to identify both the particular problem you are
2
solving and also the foundational issues you are addressing. The latter will consist of
the generic problem you are solving, and its solution will enable you to clarify the
contribution to your field. ]
Re-state the problem clearly and precisely and say what your project intends to
do or what you plan to do with the problem. In other words, what is the purpose of
your study?
3
1.2 Significance
[Why is your project important? How is it different from other projects on related
topic? What new will it contribute to already existing solutions? What are its policy
implications?]
1.3 Objectives
[In this section, the current state of the art specific to this project 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 prospective
stakeholders if you describe your objectives in measurable ways.]
FOR EXAMPLE: The aim of the project is to create the propose system that to allow
event organizers to keep track and analyze on hashtag campaigns; allow user to
capture and monitor public responses and to further make use of captured data.
4
1.4 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.]
Same table formatting should be followed i.e. no Left and
Right Border, Top table border style: , Bottom
1.5 Overview
Table border style: , in-between border
Project Goal:
[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.]
Type of project: R&D Development
Project Success criteria:
[Project success criteria are the standards by which the project will be judged at the end
to decide whether or not it has been successful in the eyes of the stakeholders, in your
case, evaluators.]
Timing risk
Budget risk
PHP
BOOTSTRAP(CSS, JavaScript, J Query )
MYSQL
XAMP Server
Code Igniter
SUBLIME TEXT 2
Platform:
6
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.]
FOR EXAMPLE:
[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.
7
Identify what the needs for tool support are, and what the constraints are, by
looking at the following:
[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 CD.]
FOR EXAMPLE:
Project Proposal
Software Requirement Specification (SRS)
Project Presentation and Final Documentation
Executable Files
CD
8
User manual
[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, and documentation.
The Gantt chart enumerates the activities to be performed on the vertical axis
and their corresponding duration on the horizontal axis. It is possible to schedule
activities by either early start or late start logic. In the early start approach; each
activity is initiated as early as possible without violating the precedence relations. In
the late start approach; each activity is delayed as much as possible as long as the
earliest finish time of the project is not compromised.
9
1.10 Functional Requirements
FOR EXAMPLE:
For Customers
Facility of Login:
o Customers have to be logged in by their username and password.
Facility of search:
o We provided the search facility whether manual or auto to the
customers.
For Employees
Facility of search:
o Employees can search the portal to be the part of that portal.
Posting facility:
o Provides the facility of post about the services given by the employee
himself.
For Admin
Facility of Login:
o Admin has to be logged in by their username and password.
Manages the portal:
o Admin is the authorized person that manages the whole portal i.e.
registration of workers, confirmation of the registration, addition of
workers, deletion of workers, any updating in information, and can
check the rating of performance of the workers.
10
1.11 Non Functional Requirement
Usability
Reliability
Performance
Design Constraints
Portability
Maintainability
License Agreement]
FOR EXAMPLE:
Application availability will be 24/7 in a year. It means user can use this
platform at any time anywhere.
Application security is good. User data is secure and can be seen by only that
user.
Interactive Design/Usability is good. It is easy to use this application.
Performance/Efficiency of this application is good. It do not take long time to
open and do not hang on any browser.
This application secures data of each user and do not involve third party to use
his all user data. It means privacy of this application is good.
11
References:
[If you take another person's work as your own and do not cite your sources of
information you are being dishonest; in other words you are cheating. When referring
to other pieces of work, cite the sources where they are referred to or used, rather than
just listing them at the end.
In this section you list in standard bibliographic format the books, papers,
course notes, websites and project or thesis reports which you have used in preparing
your project report.
FOR EXAMPLE:
For URL:
[1] “AT Commands API for SMS sending” (Last Retrieved: January 2015).
Retrieved from http://www.nbcmiami.com/news/local/Teen-Posed-as-Doctor-
at-West-Palm-Beach-Hospital-Police-288810831.html
For a paper in a journal/ conference:
[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.
12