Title of the Project
Final Year Project Proposal
Session 20XX-20XX
A project submitted in partial fulfilment of the
COMSATS University Degree
of
BS in Computer Science / Software Engineering (CUI)
Department of Computer Science
COMSATS University Islamabad, Lahore Campus
01 November 2020
Project Registration
Project ID (for office use)
Type (Nature of project) [ ] Development [ ] Research [ ] R&D
Area of specialization
Project Group Members
CGP
Sr.# Reg. # Student Name Email ID Phone # Signature
A
(i) Group Leader
(ii)
(iii)
Name & Signature of Batch Advisor
(If students are eligible for FYP)
Plagiarism Free Certificate
This is to certify that, I am ________________________ S/D/o _______________________, group leader of
FYP under registration no CIIT/_________________/LHR at Computer Science Department, COMSATS
Institute of Information Technology, Lahore. I declare that my FYP proposal is checked by my supervisor and
the similarity index is ________% that is less than 20%, an acceptable limit by HEC. Report is attached
herewith as Appendix A.
Date: ____________ Name of Group Leader: ________________________ Signature: _____________
Name of Supervisor: _____________________ Co-Supervisor (if any):____________________
Designation: _____________________ Designation: _____________________
Signature: _____________________ Signature: _____________________
Approval of FYP Management Committee
Committee Member 1: Name: _____________________
[ ] Accept [ ] *Defer [ ] *Reject Signature: _______________
*Remarks: _____________________________________________________________________
Committee Member 2: Name: _____________________
[ ] Accept [ ] *Defer [ ] *Reject Signature: _______________
*Remarks: _____________________________________________________________________
Convener: Name: _____________________
[ ] Accept [ ] *Defer [ ] *Reject Signature: _______________
*Remarks: _____________________________________________________________________
2 of 8
Project Abstract (mandatory)
Briefly describe your project.
Introduction of topic
Key problem
Solution or methodology
Scope of the solution
Introduction (mandatory)
- The introduction should set the stage for the paper. (typically, 0.5 -1 page)
-- Simplified it should include:
1a. Short introduction to the field
1b. Short introduction to the "problem/challenge/issue" that is the focus of the paper
1c. Shortly why this problem (1b) is important and for whom it is important
1d. Shortly what you do/present in the proposal, and how it relates to 1b (the contribution)
1e. Disposition of the proposal
-- General:
This should be about one page and be a teaser for the reader.
Observe, that any statements that need to be properly motivated and referenced as "opinions"
are not valid as motivation for research or a problem. In very rare cases, references can be
hard to obtain, then the parts in the introduction should be well motivated through arguments
(however, this is very seldom the case).
-- Example (below is a simple example of an introduction and its parts as they relate to the parts
described and coded above):
*Requirements elicitation [REF] covers a wide area of techniques aimed at catching and extracting
requirements from….. (1a)
*Most elicitation techniques, such as interviews, and workshops [REF], are not adapted for off-the-
shelf or market-driven (MDRE) scenarios…. In market-driven scenarios [REF], where access to
specific stakeholders is hard, there is very little in terms of scientific investigation as to what
elicitation techniques yield the best return on investment [REF]…. (1b)
*Elicitation techniques need to evolve to meet the demands of market-driven product development
[REF]…. (1c)
*This paper presents an experience report based on two industry projects conducted over a period of
one years at Doc Engineering Ltd, where several elicitation techniques where used…. (1d)
3 of 8
*The proposal is structured as follows (1e)
Motivation and Scope (mandatory)
Briefly describe your motivation in terms of benefits that your proposed software
product can offer to different stakeholders.
Scope means clarifying the proposed functional requirement that you will implement
in the software. The software product might have more functional requirements but
they might not be implemented in this version of product release.
Also describe assumptions in the project.
Related Work (mandatory)
Should cover what others have done in the field/area, and how the work presented in this paper
adds/confirms/disproves/extends/etc. related work (typically 0.5 to 1 page).
-- This can include (but does not have to be limited to):
3a. What others have done/presented in relation to the overall research area. Research in the domain
3b. What others have done specifically in relation to what you present in the paper. Specific to your
specific research domain
3c. (can include) Related work in relation to the research method you apply in the study/paper. 5 latest
research papers on your research idea.
-- General:
Regarding 3a, the area in our running example is RE and Elicitation in a MDRE context. What have
others done in this area as pertaining to RE+Elicitation+MDRE, also can you find others confirming
the "problems" you describe?
Regarding 3b, in our running example, what others have done in relation to using Personas and Focus
Groups…
-- Example:
*Gorschek et al. [REF] report that elicitation in an MDRE context presents new problems…. This is
confirmed by several studies [REF, REF, REF]. Several industry experience reports present the
possibility of using internal sources, such as product managers, as representatives for large customer
groups… [REF]…. However, there are very few studies reporting…., which is the main focus on the
study presented in this paper…. (3a)
*The use of personas has shown promise and Humangus and David [REF] report on a successful…..
However, there are problems of scalability and keeping personas up to [REF], a problem that we tried
to tackle as described in this paper…. (3a + 3b)
4 of 8
System Architecture (optional)
Example 1
Example 2:
Goals and Objectives (mandatory)
It has been said that Goals without objectives can never be achieved while objectives without goals
will never get you to where you want to be. Indeed the two concepts are related and yet separate.
Using both can enable you (or the organization) to be and do what you want to do. Objectives can be
defined in terms of milestones and deliverables.
Individual Tasks (mandatory if group project)
5 of 8
Please mention your individual tasks in group project justifying one year effort.
Function Requirements (Minimum 20)
Using following template
Non-Functional (Minimum 5)
6 of 8
They should be testable with all the required details for software
tester.
Gantt Chart (mandatory)
As per individual tasks mentioned in previous section, the Gantt chart shall graphically represent
which tasks would be done in which duration i.e. starting date, end date etc. What tasks shall be done
in parallel and what tasks shall be done in series, etc. Duration of individual task. (View few sample
from internet before making your own to get ideas)
Future Work (optional)
Please describe possible extensions of your work.
Tools and Technologies
Please describe tools and technologies that you have been planning to use in this project.
7 of 8
Appendix A
Include here the 1st page of Turnitin Report
Every supervisor has his/her own Turnitin account. If not then supervisors are requested to get the account from
Library as soon as possible.
8 of 8
