Professional Documents
Culture Documents
FYP Research-Based Template
FYP Research-Based Template
Project Name
Project Advisor:
Submitted By:
Session
Formatted: Font: 14 pt
Panel of Examiners
3) Supervisor ______________________
Department of Computer Science
UMT Lahore
4) Co-Supervisor ______________________
2. Controller of Examinations
______________________
This is one of the most important parts of your report. It should normally be written last. It should be:
Short and concise (not longer than 250 words and rarely longer than one paragraph)
State the objective
State the method used
State the result
State the conclusions
It should not:
Introduce anything new
Include references
If you have found anything interesting, it is important that you mention it here because after reading the
abstract, the reader might decide to quit reading the project and he might miss your superb result which is
only revealed at the end.
New paragraphs formatted as Heading 1, Heading 2, and Heading 3 will be added to the table
automatically. To update this table of contents in Microsoft Word, put the cursor anywhere in the table and
press F9. If you want the table to be easy to maintain, do not change it manually.
ACKNOWLEDGEMENTS ............................................................................................................................ 4
ABSTRACT ................................................................................................................................................ 5
CONTENTS................................................................................................................................................ 6
DEFINITIONS AND ACRONYMS ................................................................................................................. 8
LIST OF FIGURES ....................................................................................................................................... 9
LIST OF TABLES ....................................................................................................................................... 10
1 INTRODUCTION ............................................................................................................................. 11
1.1 PROBLEM OVERVIEW ............................................................................................................................11
1.2 RESEARCH QUESTIONS ..........................................................................................................................11
1.3 RESEARCH OBJECTIVES ..........................................................................................................................11
1.4 SCOPE ................................................................................................................................................11
1.5 METHODOLOGY ...................................................................................................................................11
1.6 SIGNIFICANCE/ POTENTIAL APPLICATIONS .................................................................................................11
2 BACKGROUND ............................................................................................................................... 12
3 LITERATURE REVIEW ...................................................................................................................... 13
3.1 GAP ANALYSIS .....................................................................................................................................13
4 PROPOSED METHODOLOGY........................................................................................................... 14
4.1 SUGGESTED APPROACH .........................................................................................................................14
4.2 WORKFLOW OF THE SYSTEM ...................................................................................................................14
4.3 ALGORITHMS/ARCHITECTURE .................................................................................................................14
5 DESIGN AND IMPLEMENTATION .................................................................................................... 15
5.1 SYSTEM DESIGN ...................................................................................................................................15
5.2 SYSTEM IMPLEMENTATION .....................................................................................................................15
5.3 ASSUMPTIONS/CONSTRAINTS (OPTIONAL) ................................................................................................15
6 EVALUATION ................................................................................................................................. 16
6.1 EXPERIMENTATION ...............................................................................................................................16
6.1.1 Experimental Setup ................................................................................................................16
6.1.2 Experiments Design/Details ...................................................................................................16
6.2 RESULTS .............................................................................................................................................16
6.3 DISCUSSION/ANALYSIS ..........................................................................................................................16
7 CONCLUSION AND FUTURE WORK ................................................................................................. 17
8 REFERENCES/ BIBLIOGRAPHY ........................................................................................................ 18
9 APPENDIX ...................................................................................................................................... 19
Formatted: Justified, Tab stops: 6", Right
9.1 GLOSSARY OF TERMS .............................................................................................................................19
Formatted: Font: 10 pt
9.2 PRE-REQUISITES ...................................................................................................................................19
9.3 REFERENCE/ SOURCE DOCUMENTS ..........................................................................................................19 Formatted: Font: 10 pt
Formatted: Font: 10 pt
Provide definitions or references to all the definitions of the special terms and acronyms used within this
document.
New figures that are given captions using the Caption paragraph style will be added to the table
automatically. To update this table of contents in Microsoft Word, put the cursor anywhere in the table and
press F9. If you want the table to be easy to maintain, do not change it manually.
This section can be deleted if the document contains no figures or if otherwise desired.
The introduction part is another trigger for the reader. If after reading this part, the user is not bored yet,
you have won him over.
It should:
2.41.4 Scope
2.51.5 Methodology
The research methodology should include the following points:
Data Collection Methods
Data Analysis Methods
Software Development Methods
The purpose of the Background section is to provide the typical reader with information that they cannot be
expected to know, but which they will need to know in order to fully understand and appreciate the rest of
the report. This section may describe such things as:
In this section students need to discuss thoroughly on literature which related to the area or topics selected.
In this section you should show where in current literature the problem was first recognized as well as what
serves as the foundation for your research proposal or final report. The more references you can find that
relate to the given problem statement, the more credibility it will have. This will give the reader an idea
whether you have done your “homework” and know enough about the topic to start with the research
project. Guideline for this chapter is such follow: -
This chapter should explain why the project is addressing the problem described in the report, indicate
an awareness of other work relevant to this problem and show clearly that the problem has not been
solved by anyone else.
What you have learnt from previous research and how you position yourself
Description of Research Design and Procedures Used
How you developed an appropriate research strategy
Sources of Data and Sampling Procedures
4.3 Algorithms/Architecture
Description of any novel procedures which you have proposed and implemented
Incorporation of existing systems (if any), their description and settings
This chapter should explain what you did and how you did it. It must be clearly written so it would be
easy for another researcher to duplicate the experiment if they wished to.
Performance
Robustness
Interactively
Flexibility
Security
In case of interactive software, the design should also consist of the following:
Interface Design
Implementation of different modules (including detail steps about how they were Developed)
6.1 Experimentation
This section should describe what was actually done. It is a clear exposition of the laboratory notebook,
describing procedures, techniques, instrumentation, special precautions, and so on. It should be sufficiently
detailed that other experienced researchers would be able to repeat the work and obtain comparable
results.
6.2 Results
In the section, relevant data, observations, and findings are summarized. Tabulation of data, equations,
charts, and figures can be used effectively to present results clearly and concisely.
6.3 Discussion/Analysis
The crux of the report is the analysis and interpretation of the results
What do the results mean? How do they relate to the objectives of the project? To what extent have
they resolved the problem?
An evaluation of the situation – what was expected/unexpected, proved/disproved, illustrated,
explored, highlighted by what you have investigated.
Comparative Analysis: An attempt to explain the results drawing in other research/theory
A discussion of limitations and possible sources of error
You should end the report with few paragraphs that sum up the project and any implications, conclusions
or recommendations and suggestions for future research/work you feel would expand the knowledge base
in this area. Don’t introduce any new ideas into your conclusion.
If you have cited evidence in the main body of your report, it must be referenced in this section.
Don’t neglect references – you can lose credit if you don’t reference your sources properly.
However, you don’t need to reference:
Common knowledge (things that most people would know)
Undisputed historical facts
Your own opinions, observations, and ideas – but make sure you make it clear in the report that
they are your views.
9.2 Pre-requisites