FYP BSCS Students Handbook-V2.0

BSSE FINAL YEAR PROJECT
STUDENTS
HANDBOOK VERSION 2.0
Faculty of Computing
Riphah International University
Table of Contents:
01. Glossary 03
02. Introduction 04
2.1. Focus 05
2.2. Importance of Final Year Project 06
03. Selecting Your Project & Team Members 07
3.1 Project Team 07
3.2 Choosing Your Project & Supervisor 07
3.3 Finalizing Project Proposal 08
04. Literature / Markey Survey 10
05. Documentation 12
5.1 Project Report 12
5.2 A Very Short Guide to Good Writing 14
5.3 Giving Presentations 16
06. Project Assessment 18
07. Schedule & Milestones 20
08. Policies 21
09. Responsibilities of Project Students 23
10. Appendices 25
Page 2 of 39 Faculty of Computing

BSCS FYP Handbook (Version 2.0 / March 3, 2023) Riphah International University, Islamabad (Pakistan)
1. Glossary
FYP: Final Year Project (Also known as Final Year Project)
BSSE: Bachelor of Science in Software Engineering
FC: Faculty of Computing, Riphah International University
RIPHAH: Riphah International University
Faculty: Fulltime permanent faculty member
Supervisor: A fulltime faculty member of FC responsible for the

supervision of FYP.
Exam Committee: A group of faculty members responsible for evaluating and

grading projects.
Coordinator: A faculty member appointed by FC to coordinate the FYP

tasks
Student: A student registered for FYP in FC
Group/Team: A group of students formed as a team to work on the FYP.

2. Introduction
The Final Year Project (FYP) is a mandatory prerequisite for award of degree in BS (CS).
It provides you with an opportunity to apply the theories and principles learned in
different courses, and integrate material learned at different stages of your BSCS degree
program to solve a Complex Computing Problem. There may also be a need for
additional, domain specific knowledge in a project, which will necessitate additional
study.
Learning Outcome: On successful completion of the project, you should be able to

apply your knowledge and understanding of Computer Science to solve Complex
Computing Problems by analyzing problems, creating and evaluating solutions, and
critically assessing others and your own work. You should also be able to prepare project
plans, give presentations, and write reports.
Learning Method: FYP is a self-learning exercise, under the guidance of project

supervisor. The following six learning elements form the basis of a project: knowledge,
understanding, applying, analyzing, evaluating, and creating.
During the project you are expected to:
• Develop an understanding of the technical knowledge on which your project is

based.
• Analyze a problem.
• Create a solution (Synthesis).
• Apply your knowledge and understanding in executing the project.
• Evaluate your work.
Assessment:
• Semester 1: Proposal defense, Interim Report

• Semester 2: Final Report, Presentation, and Developed Solution
2.1. Focus
The objective of FYP is to provide solution of a Complex Computing Problem. A
Complex Computing Problem is a computing problem having some or all of the
following characteristics:
Characteristics of a Complex Computing Problem according to SeoulAccord.

Sr.
Characteristic Description
No.
Range of conflicting Involves wide-ranging or conflicting technical, computing, and other

1
requirements issues
Has no obvious solution, and requires conceptual thinking and

2 Depth of analysis required
innovative analysis to formulate suitable abstract models
A solution requires the use of in-depth computing or domain

3 Depth of knowledge required knowledge and an analytical approach that is based on well-
founded principles
4 Familiarity of issues Involves infrequently encountered issues
Is outside problems encompassed by standards and standard

5 Level of problem
practice for professional computing
Extent of stakeholder
6 involvement and level of Involves diverse groups of stakeholders with widely varying needs
conflicting requirements
7 Consequences Has significant consequences in a range of contexts
Is a high-level problem possibly including many component parts or

8 Interdependence
sub-problems
Identification of a requirement or the cause of a problem is ill

9 Requirement identification
defined or unknown
This may take many forms, for example: a program, an application, a server, a library, a
collection of programs, an embedded system, a hardware-software system, plug-ins,
extensions, modifications to existing solution/software, etc.
You should focus on following sound Computer Science principles and evaluating your
work thoroughly. You will do literature review (background research) into both the

technology and the marketplace. You must test your solution to make sure it works
correctly.
You must also consider the principles of quality software development studied in
Software Engineering/OOAD, which can be summarized as follows:
1. Understand what the problem is

2. Do a thorough literature review (background study)
a. Evaluate the solutions for performance, accuracy, or efficiency if
necessary
3. Design a solution
4. Design and implement a system to realize the solution
5. Verify that the implementation matches the design
6. Validate that the implementation correctly realizes solution
7. Evaluate how well the solution solves the problem
The developed solution(code) and final report will be the main output of the project,
which should show that your solution is of suitable quality and solves user needs.

2.2. Importance of Final Year Project
You will continue to gain experience after you graduate, but FYP will be your first
exposure to a significant Computer Science project. It is essential that you learn from
this exposure and practice all the methodologies involved. It is also important that you
learn not just how to apply what you know, but also to apply it with judgment, with the
ability to assess what you are doing and to be critical of it.
You should keep in mind that:
• It is the largest single piece of work you will do during your degree course.
• It is the part of the curriculum that allows you to specialize in a topic you are
good at or enjoy.
• It is the part of your degree program that prospective employers will most likely
ask you about at an interview.
• It allows you to show off a wide range of skills and knowledge learned during
your course.
• It encourages integration of material learned in several courses.
Responsibility: It is important to note that you are responsible for the success of your
project. Your supervisor is only supposed to provide you with guidance and feedback –
you must not rely on your supervisor as if he/she is your project manager or team lead. It
is also your responsibility to keep record and submit the monthly attendance status of the
meeting held with the supervisor, with supervisor’s consent (Template-08).

3. Selecting Your Project & Team Members
3.1. Project Team
The team size required for Computer Science FYP depends upon the problem scope. An
individual can pick FYP. However, a group of 2 members is encouraged. A group of 3
can also be formed only if the scope and complexity of the project justifies these
numbers.
Use “Template-01” to fill in the details of project team members and submit hard
copy to Project Coordinator before the end of first week (1st Semester).
3.2. Choosing Your Project & Supervisor

Given that you are going to spend a lot of time working on your project, it is essential
that you pick a project which you like and which you can do. Note that these are not
necessarily the same things: just because you like a project doesn’t mean you are
qualified to do it. You may not have taken all the requisite courses, or it may be a more
theoretically-aligned project whereas you might be a more practically-oriented student (or
vice versa). Think long and hard before making your final choice. At the very least, you
should take the following steps in assessing and choosing a project.
• Find out what are your options.

• Make a list consisting of at-least three projects.
• Write a brief description of each project, doing brief research will be helpful.
• Go and talk to faculty members you wish to supervise you during the project.
Discuss your ideas in detail and take notes. It is important that you demonstrate
your interest and necessary knowledge about the projects to convince a faculty
member of your choice to supervise you.

Once you have finalized your project & supervisor use “Template-02” to write down
initial proposal and submit hard copy to project coordinator before the end of
second week (1st Semester).
3.3. Finalizing Project Proposal

You will need to further refine your project proposal and present it to the entire faculty in
fourth week of the semester (1st Semester). Faculty members will evaluate your proposal
for scope, complexity, originality of idea (creativity) and amount of self-learning
involved. Faculty members will provide feedback on your proposal, which you will need
to incorporate in your project scope in consultation with your project supervisor. Faculty
members can also reject a proposal if you fail to effectively present scope, complexity,
originality of idea (creativity) and amount of self-learning involved.
Use “Template-03” to create project proposal presentation. You will need to submit
soft copy (PDF Format) of your presentation to project coordinator before the end
of fourth week (1st Semester).
After the proposal presentation you will need to finalize your project proposal (including
initial plan) in consultation with project supervisor.
Use “Template-04” to create final project proposal and submit both hard copy
(signed by project supervisor) and soft copy (PDF Format) to project coordinator
before the end of sixth week (1st Semester).
Your final project proposal should consist of:
• Full Name & Designation of Project Supervisor

• Introduction and Background: Briefly introduce opportunity and the
stakeholders for which software system is being developed.
• Literature Review: Description of the existing solutions and critical analysis
(GAP)

o Evaluation of existing solutions for performance, accuracy, or efficiency
(If necessary)
• Problem Statement: Describe the motivation for new solution.
• Proposed Solution and Methodology
• Scope of the Project: Discuss major modules in this section.
• Constraints and Limitations
• List of Faculty Proposed Changes
• Work Breakdown Structure: A work breakdown structure (WBS) is deliverable
based decomposition of project scope. The WBS includes 100% of the work
defined by the project scope and captures all deliverables – in terms of the work
to be completed, including project management.
• Roles & Responsibility Matrix: The purpose of roles & responsibility matrix is
to identify who will do what. You will need to list items in WBS and identify
activities needed to complete each deliverable. You will then identify which team
member(s) will be responsible for completing which activity and how long it
should take.
At this stage you are only finalizing project proposal, therefore your project plan (“Work
Breakdown Structure” and “Roles & Responsibility Matrix”) can be based on rough
estimates. You must regularly refine both “Work Breakdown Structure” and “Roles &
Responsibility Matrix” as you elicit more requirements during your project.
A critical factor that will determine quality and success of FYP is your ability to manage
time. Final Year Projects are completely different from smaller projects you may have
undertaken. This project will require a considerable amount of your time: approximately
240+ hours / person.
Begin your project early, work consistently at it, and track your progress. Your project
plan helps you to think about all the things you need to do, their inter-relationships, and
the time each will take.

4. Literature Review
Ideally you should conduct literature review for problem identification. However even
after you have defended your project proposal, you must conduct detailed literature
review to gain more insight about the problem you are trying to solve by critically
evaluating the state-of-the-art solutions. This is an essential step that will help you
become an expert in the problem at hand: a problem-domain expert.
• It shows that you not only understand what you want to do, but you understand
what others have done related to your project. If you can tell people about what
has already been done and what methods already exist, then your readers will
think that at least you are interested in your topic, have some self-initiative and
are informed and up-to-date.
• It shows that you are intelligent enough to evaluate the quality of the other work
done on the subject, i.e., it shows that you are capable of thinking critically and
identifying strengths and weakness.
• It gives you opportunity to tell how your project is related to previous work done
by others on the subject.
• It tells the reader if you are simply going to duplicate others’ work for the sake of
gaining a better understanding, improve upon others’ work or perhaps combine
the methodology of two or more existing approaches to solving a problem.
The only way to become an expert in both the problem domain and the solution domain is
to learn as much as possible about the area and to learn it as quickly and efficiently as
possible.
Go online and search for research articles, books and papers related to your subject. Be
creative and persistent in your keyword search until you hunt down good references or
examples. A separate guideline on keyword search (query string) will be provided
separately.

• When you read some literature that you think is useful and related, first record the
citation on your list of references, using IEEE format.
• When you read some literature that is not very useful, do not include it on your
list of references. More references do not mean a better list of references. Useless
references only confuse a careful reader and make you lose credibility.
• In each document, identify the approach(es) / method(s) for solving problem(s),
and compare this/these with what you already know.
• Identify which approaches and/or methods you will use and omit in your project.
• After you feel satisfied that you know all or most of the existing
approaches/methods, list out all the approaches/methods, in a logical sequence
(perhaps in chronological order).
• For each approach/method: describe how it works and what its components are;
mention its strengths and/or weaknesses; tell if you will use or omit the approach
for your project and why or why not.
Finally, it is very important that you realize that, to fully understand anything that you
read, you must write it up in your own words. If you can’t express or speak about a given
idea, then you haven’t truly understood it in any useful way.

5. Documentation
Writing is an essential part of understanding. In case of documentation, writing is

essential for others to understand what you have done. There are two reasons why you
want others to understand your work:
• So that you can be given credit for it (your marks depend on it);
• So that others can carry on your work and develop or maintain your system.
The best way to organize your writing is to keep a log book of all work in progress. You
should go out and buy a nice hard-cover notebook and write everything you do on the
project into this log book every day. Every thought and observation you have on your
project should go into this book, along with notes of meetings with your supervisor,
results, theoretical developments, calculations, everything. This log book will become an
invaluable source of material when you come to write up your project in the final report.
5.1. Project Report

Your project report is a critical part of your project. It defines what you have done and
why you have done it. It is also one of the main outputs on which your project will be
examined and graded.
Your final year project provides you with an opportunity to demonstrate your ability to
use your judgment. This means that you must show your skill at assimilating (to
incorporate, understand), synthesizing (to produce, blend) and critically appraising (to
critically evaluate) all material relevant to the project.
Your main opportunity to display your talents at assimilation and synthesis comes when
you describe the background material you read, the requirements, specification, and
design phases of your work. Needless to say, synthesis means that you must write the text
yourself, expressing your understanding of the material in your own words.

Resist the temptation, no matter how strong, to copy sentences or paragraphs (or
whole sections) from other books or articles. Copying is not synthesis, and it
demonstrates neither your assimilation of material nor your understanding of it. If you do
come across a sentence or paragraph which is so good that it must be used, then do so and
include it as a direct quotation, providing a reference to the original source.
It is extremely important that you also appraise, or assess, your work critically, i.e. with
objectivity and with a view to seeing how it could be improved. Such honest criticism
does not mean you will receive fewer marks; in fact, it is likely that you will receive
more. Typically, you exercise your talents of critical appraisal at the end of the report in
“conclusion and outlook” chapter (Chapter 7) but you can also exercise it throughout the
report wherever it seems appropriate. Note that this exercise of critical appraisal is
different from the testing processes of verification, validation, and evaluation, which refer
to the functionality of the system you have designed. The critique you write applies less
to the system and more to the overall objectives, methodologies, and findings of the
project.
The structure of your report is critical to the impact you make in your writing. Remember
that you are trying to convey a message to the reader and, since this message is likely to
be quite complicated, you must assist him or her by making your points clearly and in a
logical order.
Because all engineering projects involve (or should involve) the exercise of a fairly
standard engineering methodology (requirements, specification, modeling, realization,
testing & evaluation), you can, if you wish, adopt a fairly standard structure. However,
that this does not mean that you just simply have to fill in the gaps in a general report
template (Template-05): this standard structure simply provides you with a place to start
as you begin to design the final structure and content of your report. You will still have to
do quite a lot of work to make it fit your own project.

5.2. A Very Short Guide to Good Writing
Good writing is difficult. It takes practice and a willingness to revise your work, many
times. The goal of writing is to convey a message to the reader. However, writing, and
reading, is sequential processes. Therefore, you must construct the meaning of your
message, piece by piece, in a linear time-line. However, the meaning you intend to
convey may emerge from many sources, not all related in a nice orderly fashion. This
creates a problem for the writer: how to order the messages contained in each sentence
effectively. The job of a writer is to make the sequence of pieces as mutually-relevant as
possible so that the story or message builds naturally, each piece adding to the previous
one. When the pieces are presented out of order the impact on the reader is lessened. And
remember the golden rule in writing: keep it simple.
The following are some pointers to help you in your task:
• Use short sentences and make sure the sentences are complete.
• Good writing strikes a balance between short sentences and longer more
descriptive ones. Just as in oral communication, the full stops mean pauses: too
many pauses and the text sounds disconnected, too few and it can be hard to
follow the story line. Strike a balance but favour brevity over complexity.
• If you use pictures and diagrams (and you should), make sure each one has a self-
contained explanatory caption. Never refer to a picture or diagram in the main text
without saying what it is. For example, never say “Figure 2.3 shows the results of
the noise test” and then carry on to another topic. Help the reader. Summarize the
content of the figure in a short sentence: “Figure 2.3 shows the results of the noise
test which demonstrate the robustness of the system to Gaussian noise with a
standard deviation of 2.3 or less.” If you have copied the figure from a book or
article you must cite the source.
• Make the paragraph your unit of construction. Each paragraph should bind one or
more sentences about a given subject or idea. If the subject or idea changes, start a
new paragraph.

• Omit needless words. Unnecessary words distract the reader. Don’t write, “This is
a system the performance of which is very useful”. Instead, write, “This is a
useful system”.
• Write in a way that comes naturally. Speak the sentence. If it sounds correct, trust
your ear and use the sentence. If it sounds unnatural, rewrite it.
• Avoid fancy words; they don’t impress anyone.
• Be clear in your expression. If the idea you are trying to convey is getting lost in a
sea of words and phrases, draw a line through the sentence and start again.
• Don’t take short-cuts. Explain what you mean. Don’t leave the reader to struggle
trying to figure out what is the real meaning of your carefully constructed but
concentrated sentence. He may conclude there is none. Explain all acronyms the
first time you use them.
• Revise and rewrite. It is highly unlikely that you will manage to find the best way
of expressing an idea with your first attempt. Nonetheless, make that attempt and
then be prepared to revise it, again and again.
Remember, if you want to learn how to write a good report, you need to do two things:
you need to read other good reports and you need to practice your own writing.

5.3. Giving Presentations
During your project, you will be required to give several presentations:
1. Proposal presentation to entire faculty in 4th week of your first semester. (Use
Template-03)
2. Progress presentation with your prototype demo to FYP Evaluation Committee
in week immediately after finals of your first semester. (Use Template-07)
3. Final presentation along with your demo to FYP Evaluation Committee in 14th
week of second semester. (Use Template-06)
Important Requirement:
• All project deliverables (e.g., Presentations, Reports, Software System, etc.)

should be reviewed by supervisors at-least once before submission/presentation.
• You must state in your presentations, whether deliverables (including your
presentation) were reviewed by your supervisor or not.
You have learned much about presentation skills during your degree program and it
wouldn’t be appropriate to attempt to review everything you have been taught already.
However, a few pointers may help you give a professional and impressive presentation:
• Don’t depend too much on PowerPoint slides: your speech is the presentation and
the slides support you (not the other way around).
• Take your time: pause frequently. Sometimes, the best thing to say is nothing.
Short one-second rests create dramatic impact and also give your audience time to
assimilate what you’ve said. Of course, you also have to maintain continuity and
flow; otherwise people forget what you are talking about. It’s a question of
balance.

• Arrive early and make sure you know where all the equipment is. Know how to
use it.
• Look at the audience, not at your slides.
• Project your voice (but don’t shout).
• Smile: enjoy giving your presentation.
• Be confident: you’ve done some great work - here is your opportunity to get
credit for it.
• The people in the audience are on your side (though sometimes they disguise it
well!) They want you to succeed. If they ask you a question you don’t understand,
say so and ask their help. Ask them to explain and ask nicely. If you still don’t
understand, don’t bluff. Admit your ignorance and suggest ways of how you will
overcome that lack of knowledge.

6. Project Assessment
6.1. Final Year Project (Part I)
You are required to participate in the Open House (15th Week of first semester) and
showcase your Project Idea, Prototype, and Project Report. Failure to participate will earn
you “F” grade unless you have prior approval from both your supervisor and project
coordinator.
In the week immediately after finals you will make Progress Presentation (you will also
show first five chapters of your report and your working prototype) to FYP Evaluation
Committee. FYP Evaluation committee will evaluate your progress according to the
following criteria:
Part-I Evaluation Rubric

Evaluation Item Description Marks
Literature Quality of Project Analysis and Design 30
Models, Gap identification.
Review/Problem
Analysis
Progress Quality of prototype/initial experiments, 30
data collection/database creation, at least
one module completed.
Presentation Presentation Quality / Demonstration / 10
QA Session
Report Quality of Report and appropriate 20
artifacts
Total 100
Evaluation Method:
• 50% by Exam Committee Average + 50% by Supervisor
• Supervisor may evaluate each member of the project group individually
• Decision of the Exam Committee and Supervisor will be final.
For Example:
• Average Marks by Faculty for the Group: 68 (34 %)
• Supervisor Marks for Student 1: 76 (38%)

• Student 1 Grade: 34+38 = 72% (B Grade)
• Student 2 Grade: 34+30 = 64% (C Grade)
• Student 3 Grade: 34+46 = 80% (A Grade)

6.2. Final Year Project (Part II)
In 14th week of the semester, FYP Evaluation Committee and your Supervisor will grade
you based on your final report, presentation, and demonstration.
FYP Evaluation Committee will evaluate you based upon difficulty level (scope,
complexity, creativity and amount of self-learning involved in developing the final
system) and quality (presentation, usability, system design, documentation, and coding).
The following rubric will be used for evaluation:
Part-II Evaluation Rubric

Evaluation Item Description Marks
Report Qulatiy of Final Report, Market Survey, Gap Analysis, Use 30

cases/User Stories, Domain Model, Software Architecture
Diagram, Class Diagram, Test cases, ERD, Deployment
Diagram
Implementation Quality of code, Working Demo/Finished Product 50
Design and Scope Align scope and implemented outcome 10

Completeness Ratio
Presentation Presentation Quality / Demonstration / QA Session 10
Total 100
Evaluation Method:
• 50% by Exam Committee Average + 50% by Supervisor
• Supervisor may evaluate each member of the project group individually
• Decision of the Exam Committee and Supervisor will be final.
For Example:
• Average Marks by Faculty for the Group: 68 (34 %)

• Student 1 Grade: 34+38 = 72% (B Grade)
• Student 2 Grade: 34+30 = 64% (C Grade)
• Student 3 Grade: 34+46 = 80% (A Grade)
Tip: Important things that Exam Committee may thoroughly check during the exam:
• Functional & Non-Functional Requirements

• ERD & Class Diagrams
• Code
• Walkthrough of the Core Component(s)
• Documentation (Formatting and Completeness)

7. Schedule & Milestones
7.1. Final Year Project (Part I)
Deadline Milestone Submit To Notes / Actions / Deliverables
Week 1 Attend Orientation Project Coordinator • Submit Project Team List (Both SOFT
Seminar. & HARD COPY - Use Template-01)
Week 2 Develop Project Project Coordinator • Submit Initial Proposal (HARD

Ideas; Find a COPY - Use Template-02)
Supervisor
Week 4 Proposal Entire Faculty • Project Proposal Presentation (SOFT

Presentation COPY - Use Template-03)
Week 6 Finalize Project Project Coordinator • Submit Project Proposal & Plan (Both
Proposal SOFT & HARD COPY - Use
Template-04)
Week 15 Open House Industry, Faculty & • Banners, Posters, Brochure, Story
Students Board, Prototype, Project Report
Week Progress Exam Committee / • Presentation (Use Template-07),

Immediately Presentation / Supervisor Prototype, Project Report (SOFT
after Finals Assessment COPY - First 5 Chapters – Use
Template-05)
7.2. Final Year Project (Part II)

Deadline Milestone Submit To Notes / Actions / Deliverables
Week 13 Submit Report Project Coordinator • Complete Project Report (SOFT

COPY - Use Template-05)
Week 14 Final Demo / Exam Committee / • Final Presentation (Use Template-06)

Assessment Supervisor • Report (Use Template-05)
• Full Working Demo
Week 15 Open House Industry, Faculty & • Banners, Posters, Brochure, Story
Students Board, Prototype, Project Report,
Complete Software System
Week Submit Project Project Coordinator • Documentation (Hard Binding – 3

Immediately Copies)
After Finals • CD (Including Software – Source
Code, Appendix in PDF Format)

8. Policies
8.1. Registration Criteria
You can register in FYP if you have completed at-least 100 credit hours and are not under
probation for low CGPA.
8.2. Meetings with Supervisor

All FYP groups are expected to meet with their supervisor once a week to discuss their
project progress. For that purpose, the students should maintain their project log file, to
make record of their regular meetings. Your supervisor has the rights to assign “F” grade:
• To all group members if group skips three consecutive meetings.

• To individual group members if they fail to attend 75% of the meetings.
Student must submit monthly attendance status (Template-08) to the coordinator. See
Section 9 for details.
8.2.1 Supervisor Review Before Presentation

It is mandatory all FYP student to meet and request their supervisor to review various
deliverables due before all the presentations:
• You must state in the beginning of your presentations, whether deliverables

(including your presentation) were reviewed by your supervisor or not.
8.3. Plagiarism
Any piece of code, framework or component developed by someone else that you are
using in your project must be properly acknowledged / referenced in your documentation.
You cannot claim any such code, framework or component as your own. Your efforts

will be evaluated by the amount of work you have done yourself. You must write your
own documentation and cannot copy from any other source.
In case a group is found to be involved in plagiarism, all group members will

automatically earn “F” grade.

8.4. Group Size
FYP is a group activity, and a team consisting of 3 students is highly encouraged.
Groups consisting of 2, 4 or 5 students can also be formed, only if the scope and
complexity of the project justifies these numbers.
8.5. Open House

All students enrolled in FYP (Part 01) and all students enrolled and approved by faculty
in FYP (Part 02) are required to participate in the Open House and showcase their
projects. Failure to participate will earn them “F” grade; unless they have prior approval
from their supervisor and the project coordinator.
8.6. Other Policies

• Number of Group Members: See Section 3.1
• Assessments: See Chapter 6
• Schedule & Milestones: See Chapter 7

9. Responsibilities of Project Students
Success & effectiveness of FYP process depends on how everyone involved play their
role. It is therefore important that you clearly understand your responsibilities in this
course. Project students must:
• Take full responsibility for their project work

• Ensure that satisfactory progress is made
• Submit work (reports, proposals, plans, presentations) in a specified time
• Ensure that they are familiar with academic rules, regulations and policies
• Ensure that they consult with their supervisor on regular basis
• Prepare periodic progress reports on the project
o Submit monthly meeting attendance status via provided template signed
by supervisor.
• Accept responsibility for confirmation of project scope, presentations, and
demos
• Keep themselves up-to-date with the project documents/information on VLE
• Familiarize themselves with various milestones, deliverables and schedule of FYP
• Keep supervisors informed on their project activities, progress and problems
• Meet and request their supervisor to review various deliverables due before all the
presentations (See Section 8.2.1)
• Ensure that they have sufficient time available each week to work on their project
• Ask for project coordinator’s help, in case of serious problems with the supervisor
• Contact project coordinator on administration issues (including: enrolment,
assessment, schedule of key dates, open house, etc.)
• Consult their supervisor on technical issues (including scope of work, extension to
projects, theoretical technical questions, resources, project management, etc.)

It is also very important to realize that your supervisor is not your project manager or
team lead. A project supervisor is only expected to:
• Help/Advise students finalize their project proposal

• Advise students on any changes in project that are required by the faculty
• Make time available for regular meetings with students
• Give suggestions, comments on project progress
• Oversee the administration of project and help students from time to time to
identify the direction that the project should take. Also, review the monthly
meeting progress and give consent to the students.
• Give students reasonable assistance in obtaining access to advice, material and
resources with which to carry out the project
• Give students reasonable advice on documenting and presenting the project
• Evaluate and grade students and submit their marks to Project Coordinator
The project coordinator is responsible for overall administration (with assistance from
in-charge program and program coordinator) of the FYP process:
• Assist students in understanding the project process (seminar, handbook, VLE)

• Ensure faculty participation (supervisory and non-supervisory) in the process
• Ensure all project groups have been assigned a supervisor
• Ensure the submission of project ideas from students with supervisor signature in
the sixth semester
• Collect proposals, reports, attendance status, presentation from students at
specified time
• Help resolve problems between students and supervisor
• Ensure the submission of supervisor consent form before the schedule of Final
Year Project presentation. (In 12th Week for Part-II and in 15th for Week Part-I)
• Organize all FYP related activities (presentations, open house, external exams)
• Maintain record of faculty project load
• Communicate event dates/schedule to students & faculty members

• Collect semester grades from supervisors & exam committees
• Compile results from evaluation and communicate results to students

10. Appendices
• Template-01: Project Team

• Template-02: Initial Proposal
• Template-03: Proposal Presentation
• Template-04: Proposal & Plan
• Template-05: Project Report
• Template-06: Final Presentation
• Template-07: Progress Presentation
• Template-08: Attendance Status

Template-01: Project Team
Microsoft Word Format

Template-02: Initial Proposal

Template-03: Proposal Presentation
Microsoft PowerPoint Format

Template-04: Proposal & Plan

Template-05: Project Report

Template-06: Final Presentation

Template-07: Progress Presentation

Template-08: Attendance Status


FYP BSCS Students Handbook-V2.0

Uploaded by

Copyright:

Available Formats

FYP BSCS Students Handbook-V2.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FYP BSCS Students Handbook-V2.0

Uploaded by

Copyright:

Available Formats

BSSE FINAL YEAR PROJECT

HANDBOOK VERSION 2.0

Page 2 of 39 Faculty of Computing

FYP: Final Year Project (Also known as Final Year Project)

BSSE: Bachelor of Science in Software Engineering

FC: Faculty of Computing, Riphah International University

RIPHAH: Riphah International University

Faculty: Fulltime permanent faculty member

Supervisor: A fulltime faculty member of FC responsible for the

Exam Committee: A group of faculty members responsible for evaluating and

Coordinator: A faculty member appointed by FC to coordinate the FYP

Student: A student registered for FYP in FC

Group/Team: A group of students formed as a team to work on the FYP.

Page 3 of 39 Faculty of Computing

Learning Outcome: On successful completion of the project, you should be able to

Learning Method: FYP is a self-learning exercise, under the guidance of project

During the project you are expected to:

• Develop an understanding of the technical knowledge on which your project is

• Semester 1: Proposal defense, Interim Report

Page 4 of 39 Faculty of Computing

Characteristics of a Complex Computing Problem according to SeoulAccord.

Range of conflicting Involves wide-ranging or conflicting technical, computing, and other

Has no obvious solution, and requires conceptual thinking and

A solution requires the use of in-depth computing or domain

4 Familiarity of issues Involves infrequently encountered issues

Is outside problems encompassed by standards and standard

7 Consequences Has significant consequences in a range of contexts

Is a high-level problem possibly including many component parts or

Identification of a requirement or the cause of a problem is ill

Page 5 of 39 Faculty of Computing

1. Understand what the problem is

Page 6 of 39 Faculty of Computing

You should keep in mind that:

Page 7 of 39 Faculty of Computing

3.2. Choosing Your Project & Supervisor

• Find out what are your options.

Page 8 of 39 Faculty of Computing

3.3. Finalizing Project Proposal

Your final project proposal should consist of:

• Full Name & Designation of Project Supervisor

Page 9 of 39 Faculty of Computing

Page 10 of 39 Faculty of Computing

Page 12 of 39 Faculty of Computing

Page 13 of 39 Faculty of Computing

Writing is an essential part of understanding. In case of documentation, writing is

5.1. Project Report

Page 14 of 39 Faculty of Computing

Page 15 of 39 Faculty of Computing

The following are some pointers to help you in your task:

Page 16 of 39 Faculty of Computing

Page 17 of 39 Faculty of Computing

• All project deliverables (e.g., Presentations, Reports, Software System, etc.)

Page 18 of 39 Faculty of Computing

Page 19 of 39 Faculty of Computing

Part-I Evaluation Rubric

Page 20 of 39 Faculty of Computing

Page 21 of 39 Faculty of Computing

Part-II Evaluation Rubric

Report Qulatiy of Final Report, Market Survey, Gap Analysis, Use 30