Académique Documents
Professionnel Documents
Culture Documents
for
Final Project
Summer 2007
This document forms the rules and guidelines for the successful completion of the
Final Project.
This handbook is also useful for the project advisors / supervisors to better
understand the university requirements and guide the students accordingly.
In this document you will find all information regarding the requirements and
procedures for doing project at the Faculty of Information Technology, University
of Central Punjab.
TABLE OF CONTENTS
1. Introduction 1
2. Objectives 1
3. Project Overall Procedure 2
4. Registration 2
5. Duration of Final Project 2
6. Basic Requirements and Necessary Skills 2
7. Choosing a topic 2
8. Grouping and Group Size 3
9. Transfer from Other Campuses / Universities 3
10. Extension / Re-Registration 3
11. Progress Reporting 3
12. System Allocation 3
13. Change of Project Title 4
14. Change of Project 4
15. Change of Group 4
16. Change of Advisor 4
17. Additional Help Through Seminars and Tutorials 4
18. Additional Hardware 4
19. Backups 5
20. Web – Based Projects 5
21. Evaluation and Results 5
22. Early Evaluation of Project 5
23. Re-Evaluation 6
24. Deadlines 6
25. Responsibilities of the Advisor 6
26. Plagiarism 6
27. Student Responsibilities 7
28. Future use of the Project 7
29. Final Submission Procedure & Requirements 7
a. Content Requirement for Documentation (Implementation Projects) 8
b. Content Requirement for CD 10
c. Formatting Requirements 11
30. Contents of Final Presentation 13
Handbook for Final Project / Research Thesis
INTRODUCTION
The final project at University of Central Punjab offers the challenge to demonstrate
your ability to set up and to carry out a scientific project in a self-responsible and
independent manner.
OBJECTIVES
The Project is an essential part of the education of students who hope to become
professionals in the field of computer science. In order that this is a learning
experience, the following outline of objectives is presented.
There are three objectives that should be accomplished within the project.
2. Diligent execution: The project will be independent work by the student / group,
developed under his / her own initiative and on a timetable under the student's
control. The instructor who supervises the senior project is expected to supply only
general advice and guidance and to help the student avoid pitfalls and blunders;
the day-to-day activities which affect the execution of the project are up to the
student.
Updated July-2007 1 of 13
Handbook for Final Project / Research Thesis
During the last year of degree a student is required to take Final Project.
The student then chooses a Project topic and Advisor preferably from within
the faculty members of Faculty of Information
Technology – UCP.
A project allocation form is submitted to project office, which is forwarded to
Board of Studies for approval.
On approval the students may start working on the project under the guidance
of their advisor.
A formal Project Proposal is required to be submitted to project office within
30 days after the first registration.
At the end of project term one month before the final submission the students
are required to give an intimation of their submission
Following the intimation, the final submission is required one week before the
evaluation dates.
In the announced dates the final evaluation is done and grades are forwarded
to the Controller of Exams.
REGISTRATION
Final Project is a 6 credit hours course, spread over a period of one full year.
In order that the student has an adequate background and maturity to effectively
under-take the senior project, students will be required to be within one year of
graduation before beginning a final project.
DURATION OF PROJECT
The Final Project is of one full year’s duration. No submissions will be entertained
before or after this one year’s duration (unless re-registered for extension).
A project can be started only after it has been approved by the board of studies. For
the commencement of final project an advisor is needed preferably should be part of
the UCP faculty.
For all students of BSCS and MCS it is necessary that they take up a final project which
should include sufficient amount of coding / implementation.
The minimum requirement for taking up a project is that you have the basic knowledge
of the domain and have studied the basic courses necessary for the particular project.
CHOOSING A TOPIC
Final Projects are offered by the faculty members, which are taken to board of studies
for approval and after approval offered to students, however a student may suggest a
project which will be presented in front of board of studies for final approval and upon
approval this may be taken as final project.
Updated July-2007 2 of 13
Handbook for Final Project / Research Thesis
two graduate courses. Regardless of the type of project, it must be researched-in an in-
depth and scholarly manner.
Student who want to work on a topic other that those suggested by advisors, they may
suggest projects through advisors at least one month before the projects are offered. In
such cases choose a project which is sellable in market and uses latest tools and
technologies or at least very stable technologies.
For the students of BSCS and MCS projects it is optional to work in groups or as a single
candidate. In case of BSCS the group size may NOT exceed 3 while for MCS the group
size may not exceed 2 group members.
A student is NOT allowed to join a running group. Preferably a student of one batch
may not make a group with student of another batch, unless they have registered Final
Project in the same semester. Similarly students of one degree program can not make a
group with students of another degree program.
If you have been transferred from other campuses of UCP or from other chartered
universities and you were already allotted a final project, your project title will be re-
evaluated by the Board of Studies, a new advisor will have to be chosen from within the
Faculty of Information Technology. If the board accepts the current project then you
may continue with the current project else you will have to choose a fresh project. In
case of a fresh project the time duration for project will start from the first day of the
semester in which the proposal is approved. In any case New Fees will not be required.
EXTENSION / RE-REGISTRATION
It is strongly recommended that the groups should complete their projects within the
specified time. However, a project may be submitted in later semesters after paying
half fee per semester for RT/Project. After two consecutive late semesters a grade ‘W’
will be awarded. No discount will be applicable to the re-registration fee.
PROGRESS REPORTING
Students are required to meet their advisors at least once a week in all academic
weeks. About this meeting they are required to submit a weekly report latest by the
Wednesday of following week. For all groups, at least 40 meeting in the whole project
life are must to qualify the project. The form for Progress Reporting is available at the
book store printed on blue page. Reports submitted after the due date, are considered
late and this will affect the final marks awarded for reports. Reports more than one
week late will be considered invalid and will not count towards the total reports.
Please note that the reports carry 10% value in the total project marks.
SYSTEM ALLOCATION
In the start of Second Term students are allocated systems in the project lab for
implementation of projects. The allocation is done on a request by the group using
“System Allocation Form”.
Updated July-2007 3 of 13
Handbook for Final Project / Research Thesis
A student may change the project title at any time before the final submission provided
that the title does not change the overall scope of the project. It is important that the
title should be carefully selected and should be small and relevant to the end product
or main problem area of thesis.
CHANGE OF PROJECT
You need to be extremely careful in selecting a project. A project once selected can
NOT be changed.
Within 21 days of the first course registration of Project, you may apply for a change of
project with a justified reason to change along with a fresh proposal and signatures of
the advisor. This change will only take effect if the change is permitted by the Project
Manager and Dean Faculty of Information Technology and the new project is approved
by the Board of Studies. Please note that such application will be initiated by the whole
group and there will be NO change in the number or members of the group.
Any such application will NOT be entertained that are submitted 21days after the
registration and do not justify the need for the desired change.
If after the 21 days period mentioned above, during the One Year period of project the
group wants to change the project they may drop the current project, register the
Project with MIS again along with fresh payment of Fee. In such cases the one year
duration of Project will start all over again and will last for One Full Year.
CHANGE OF GROUP
A student may NOT change the group once selected so it is advised that the students
should make the project group with extreme care.
CHANGE OF ADVISOR
All faculty members of the University are very well qualified and the projects offered
by them are from their areas of expertise. Any application for change of advisor will
NOT be entertained unless the faculty member has left the university and sufficient
amount / time of project work is remaining.
In case of any serious disagreement between the Advisor and Students the case will be
presented in front of the DEAN for an appropriate solution.
Additional help may be provided to students in areas where they find difficulty in the
conduct of their projects. This additional help can be in the form of Seminars,
Workshops, Tutorials, Study Material and/or Class Sessions. The procedure to invoke
such session is through “Seminar Request Form” duly endorsed by the project advisor.
Wherever such sessions are arranged, it is mandatory for interested students to get
registered with project office for attending the seminar. In case of students who
register and do not attend, attendance policy as per college rules applies.
ADDITIONAL HARDWARE
The University tries to provide all necessary hardware required by the students in the
fulfillment of their final project beforehand. However if additional hardware is needed,
the students may request for the hardware using “Hardware request Form”. Hardware
worth amount not exceeding 60% of the fee actually deposited by the group for final
project may be requested.
Updated July-2007 4 of 13
Handbook for Final Project / Research Thesis
BACKUPS
You cannot obtain a degree without having passed your project. Like with any
coursework, it is your responsibility to keep a back-up of your project. If you have lost
your project work due to, for example, a virus or a broken hard disc or a computer
theft, you will NOT be given any relaxation. In order to make a backup, you can
regularly copy your project work to your home directory and request for a backup on a
CD provided by you, or you can regularly copy your work on a Flash / Pen Drive or use
FTP from home and make backups.
All projects that are web-based (i.e., developed in JSP, ASP.NET or any other web
based programming language) are required to be hosted on a real time domain
purchased preferably from an outside domain vendor. This will provide students with a
real time hosting experience and they will be able to learn about and solve bottle necks
of actual hosting.
The final evaluation will be in form of a Seminar and Viva. The Seminar / Presentation
will be an open seminar. In this seminar at least one internal and one external
examiner related to the project area will be present. After this seminar / presentation
and Viva of the students will be conducted by these examiners.
All students will be evaluated for the Final Project based on 6 Credit Hours for a total
of 100 Marks. These marks will then be converted to an equivalent grade as per
prevailing Grading System of the University. A minimum of 50 percent marks are
required to qualify the Project. The attained grades will be displayed amongst other
semester grades. Please note that the Grade attained in Final Project will count in
calculation of your CGPA.
Division of Marks
Progress Reports 10
Advisor / Supervisor 35
Evaluator (s) 55
TOTAL 100
All project members must participate in all phases of the project development. The
distribution of work cannot be based on the phases of a project life cycle; it should
rather be based on the modules of a system project.
Although the students present their final project in groups but please be sure that the
examiners evaluate each student independently for his / her performance and the
students of the same group might get different grades based on his / her performance.
If a project is not the original work of students and it has been copied from some
source, the project will be cancelled, the case will be presented in front of the board
which may decide any further action.
Students will need to work consistently on the project over the period allocated to it.
As a policy the projects are evaluated only after the desired span of time has elapsed
but in some urgent circumstances subject to the approval by the DEAN Faculty of
Information Technology, if at least 80% time has lapsed, the project may be evaluated
before time.
Please note that students of the same group will NOT be evaluated separately at
different times, they will all be evaluated together and have to take part in
presentation at the time of evaluation.
Updated July-2007 5 of 13
Handbook for Final Project / Research Thesis
Updated July-2007 6 of 13
Handbook for Final Project / Research Thesis
RE-EVAULATION
Within three days of the declaration of result, a group of students may request for re-
evaluation (as a group) by paying a re-evaluation fee of Rs.1000/- per student, if they
are confident that they could get a better grade. Please keep in mind that as soon as
re-evaluation is applied, the previous grade becomes null and void and the Re-
Evaluation process can result in an increase or decrease of the grade.
A Re-Evaluation of project will be done one time only; a second request will NOT be
entertained.
DEADLINES
From start of the project till its completion there are various documents that must
reach the project office on time.
In addition to being a technical consultant to the student and providing suggestions that
will permit him or her to be more effective, the instructor who acts as project advisor
evaluates the work internally.
It is customary for the students and advisor to meet regularly so that their
communication will be continuous and effective. Regular contact with your advisor is
essential, whether you are working hard or have done little or no work. In the first case
your advisor can ensure that you are going in the right direction; in the second case
your advisor can help you to get you back on track, moreover the advisor pulls you out
of the bottle necks that you might have during the project work.
Establish a schedule for work and meetings with your advisor, meet him / her at least
once a week, even if it is only for 5 minutes. If things start to go awry contact your
advisor. If he / she is not giving you enough time, talk to the Project Manager. Don't
hesitate in doing this, as it will take us time to notice this - time is the most difficult
thing to replace.
The advisor may require supplementary reports and may modify the nature of the
required reports at his / her discretion. Although the advisor is proficient in the project
area you have chosen but he is not expected to write code of the project for you in any
circumstances.
PLAGIARISM
You should notice that you are required to make sure that, except where it is marked
to the contrary, all submitted work is your own. It is essential that no suspicion of
Updated July-2007 7 of 13
Handbook for Final Project / Research Thesis
plagiarism attaches to your report. It is unlikely in the extreme that the examiners will
award a passing mark to any project where plagiarism (as opposed to referenced
reporting) is suspected; if in doubt, check carefully with your advisor / supervisor.
STUDENT RESPONSIBILITIES
The project is a student’s original work and he or she is solely responsible for its
content. The student must pick a topic, select a advisor among the full time faculty
preferably in the Faculty of Information Technology, manage their own time, perform
and organize the project work which follow the appropriate set of rules and guidelines
for preparing a project / writing a logically cohesive thesis, and defend it. The advisor
is there to guide you and ensure you meet the quality standards as determined by the
faculty and complying with the UCP regulations but, it must be recognized that, in all
instances, the student is solely responsible for authorship and management of his or her
project.
You have an obligation to give your best work in exchange for the time the faculty
invests in you. Nothing less than your most outstanding work is acceptable.
Be sure to understand the UCP rules since they are not negotiable. If you do not defend
your project within the dates specified, you will be required to register again in the
following semester. These rules are among the most rigidly enforced in the University,
so please plan ahead. Faculty are not expected to be put in a position to "bend the
rules" on a student's behalf, nor is it considered appropriate for a student to seek
special dispensation from carrying out their responsibilities in a professional and timely
manner.
It is possible that you will have been helped in your project by use of material from a
similar project in the past, or by having the opportunity to study one or more reports
from previous years. Similarly you project will be placed in Library / Digital Library as a
reference material for University students who are interested to work in the same
domain.
Students are required to submit all of the items listed below to have their Projects
evaluated.
1. Form For Notifying Final Submission – one month before final submission
(Available at the college book store in green colour)
2. Final Project Completion Certificate
(Please do not include this in binding give one certificate only as a separate sheet)
3. Three Hard Bound Copies of Final Document
(one copy each for Library, Project Office and Department)
4. A Compact Disk (CD) containing the content as required
Updated July-2007 8 of 13
Handbook for Final Project / Research Thesis
Once the Project is complete, BS and MCS students are required to submit three hard
bound copies of documentation and CD containing the content as explained later. Final
evaluation will be conducted only after the submission of this. Document should not be
less than 50 pages and there is no limit for maximum number of pages. Following
should be the content/chapters of the documentation.
Updated July-2007 9 of 13
Handbook for Final Project / Research Thesis
Chapter 4 Design
Object Oriented Approach Structured Approach
Design Document Design Document
Database Design Database Design (Normalized),
Domain Model ERD, Data Dictionary.
Operations Contracts PLD (Pseudo Code)
System Sequence Diagrams Flowcharts
Sequence/Collaboration Diagrams Decision tables and Decision
Interaction Diagrams (Optional) trees
Design Class Diagram Data Flow Diagrams
Component Diagram Activity Diagram
Deployment Diagram Structure Charts
PSpecs
Data Dictionary
State Transition Diagrams
Component Diagram
Deployment Diagram
Chapter 5 Testing
a. Black Box Test Cases
i. Equivalence Partitions / Classes
b. White Box Test Cases
i. Cyclomatic Complexity
c. Performance Testing, Stress testing, System testing, Regression Testing
Chapter 6 Tools Used
a. Languages
b. Applications
c. Libraries
d. Classes
Chapter 7 Summary and Conclusions
Chapter 8 Lessons Learnt and Future Work / Enhancements
Appendices
Appendix A Project Management Documents
a. Team Structure
b. Roles & Responsibilities
c. WBS (Work Breakdown Structure)
d. PERT Diagram (Based on 10 Months of Work)
e. Critical Path
f. Scope Statement
g. Project Charter
h. Meetings Summary
Appendix B Bibliography/References
On standard format as explained in document “BibliographicCitation”
Blank Page
Updated July-2007 10 of 13
Handbook for Final Project / Research Thesis
The CD should be labeled by the Group ID, Project Title and Registration Numbers of all
students in group.
Group ID
Project Title
Advisor Name
UCP Logo
Registration Number 1 and Student Name 1
Registration Number 2 and Student Name 2
Registration Number 3 and Student Name 3
Updated July-2007 11 of 13
Handbook for Final Project / Research Thesis
NOTE: * Please make sure the CD contains all the requirements of the Deployment, because
at the time of evaluation you will have to compile and install the application you
submit on a newly formatted system containing only the operating system, without
any additional software help available.
FORMATTING REQUIREMENTS
(Thesis / Documentation / Report and Reference Manual)
BINDING
Note:
Spine of binding must contain Group ID and Project
Title as shown in figure on the left.
PAPER
Use 80 grams paper; A4 (8.27 x 11.69) except for oversized items. All copies to be
submitted should be printed, photocopies will not be accepted.
Updated July-2007 12 of 13
Handbook for Final Project / Research Thesis
PRINT QUALITY
Use laser printers or minimum 600 dpi inkjet printers.
Note: Do not put any lines or boxes in header and footer other than the content as
explained above.
ILLUSTRATIVE MATERIALS
OVERSIZED MATERIALS
Oversize foldout pages may be included, though ample margins for binding must
be included. Leave oversize pages unfolded.
All pages must be appropriately numbered if bound in the text.
If the oversize pages are bulky, place them in a special pocket at the back. If a
pocket is required, it must be listed in the Table of Contents, but no page
numbers are required.
A duplicate set of all oversized materials must be submitted.
PHOTOGRAPHS
Updated July-2007 13 of 13
Handbook for Final Project / Research Thesis
Photographs may be reproduced on 100 percent cotton paper and placed within the
standard text margins.
Updated July-2007 14 of 13
Handbook for Final Project / Research Thesis
The goal of almost all presentations is to get your evaluators interested enough in what
you are talking about that they will want to extract from your discussion and to make
evaluators understand and remember the most important idea from your project. You
cannot expect to convey a lot of technical information (which they already know), but
you should be able to motivate your work and convince them why it is important and
interesting, make it abundantly clear what you actually did. There should be some
technical content in your talk, including an explanation of conclusions that came out of
your work.
1. Introduction
a. Project Title, Advisor name and Group Members (with CGPAs)
b. What will you cover in your presentation
c. Motivation
i. Convey why the problem you are solving is interesting, important and
exciting
ii. Existing Solutions Studied : Place your work in context: how is it
different from what others have done
d. Scope (as per proposal submitted by you)
Project Main Goals & Key Issues: Give the audience a reason to listen to the
rest of your talk. Technical presentations should state the main conclusion up
front, so your audience knows the point you will be making.
e. Division of work
Do Include contribution of each group member
2. Guts
a. Explain what you did (in terms of design and/or implementation)
i. Use case model
ii. ERD
iii. Class diagram
b. Analysis
i. Did your work solve the problem?
ii. What are the important results of your work?
3. Tests performed on your system
4. Bottlenecks and Constraints of the system developed
5. Future Enhancements
6. Conclusion - Summarize your project with one key point.
7. Demonstration
IMPORTANT NOTES:
1. Try to avoid using long sentences or paragraphs.
2. Preferably make points and explain in your own words orally.
3. Limit your slides to a maximum of 30 – 35.
4. While choosing a template or background of slides, try using light colours, keep in
mind that the colours don’t look as bright on projector as it appears on your
monitors.
5. Avoid using snap shots of system, as you will be displaying them in demonstration as
well.
6. Including things you have not done yourself is plagiarism, include reference to the
content of slides in the footer of each slide.
7. For the demonstration of your project make sure to add sufficient data to your
database so that you don’t need to do this while presenting.
8. Upload your websites on real domains.
Updated July-2007 15 of 13