Annex L Project Report Format
Annex L Project Report Format
Prepared by
Student Name 1 (Registration Number)
Student Name 2 (Registration Number)
Student Name 3 (Registration Number)
We accept the work contained in the report titled “TITLE OF THE REPORT”, written by Mr.
AUTHOR1, Mr. AUTHOR2 and Mr. AUTHOR3 as a confirmation to the required standard for
the partial fulfillment of the degree of Bachelor of Science in Computer Science.
Approved by:
_____________________________ _____________________________
Head of Department/Coordinator DEAN
Date: _______________________ Date: ________________________
______________________________
Director/Deputy Director Research
Date: ________________________
ii
DECLARATION
We hereby declare that this project report entitled “TITLE” submitted to the “DEPARTMENT
NAME”, is a record of an original work done by us under the guidance of Supervisor “NAME”
and that no part has been plagiarized without citations. Also, this project work is submitted in the
partial fulfillment of the requirements for the degree of Bachelor of Science in Computer
Science.
Name ________________________
Name ________________________
Name ________________________
Name ________________________
Date: _______________
iii
iv
PLAGIARISM UNDERTAKING
We understand the zero tolerance policy of the HEC and Alhamd Islamic University towards
plagiarism. Therefore, we as Authors of the above titled report/thesis declare that no portion of
our report/thesis has been plagiarized and any material used as reference is properly
referred/cited.
We undertake that if we are found guilty of any formal plagiarism in the above titled
report/thesis even after award of BS degree and that HEC and the University has the right to
publish our names of the HEC/University Website on which names of students are placed who
submitted plagiarized report/thesis.
Department: ___________________________________________________________________
v
ACKNOWLEDGMENT
vi
Table of Contents
CERTIFICATE OF APPROVAL..................................................................................................................ii
DECLARATION..........................................................................................................................................iii
PLAGIARISM UNDERTAKING................................................................................................................iv
ACKNOWLEDGMENT................................................................................................................................v
List of Tables...............................................................................................................................................vii
List of Figures.............................................................................................................................................viii
List of Abbreviations....................................................................................................................................ix
ABSTRACT...................................................................................................................................................x
CHAPTER 1..................................................................................................................................................1
INTRODUCTION.........................................................................................................................................1
1.1 OVERVIEW........................................................................................................................................1
1.2 BACKGROUND OF THE STUDY....................................................................................................1
1.3 PROBLEM STATEMENT/IDENTIFICATION.................................................................................1
1.4 SIGNIFICANCE / JUSTIFICATION OF THE STUDY....................................................................1
1.5 OBJECTIVES OF THE STUDY/RESEARCH QUESTIONS............................................................2
1.6 JUSTIFICATION AND PROJECT TIMELINE.................................................................................2
CHAPTER 2..................................................................................................................................................3
LITERATURE REVIEW..............................................................................................................................3
CHAPTER 3..................................................................................................................................................4
RESEARCH METHODOLOGY...................................................................................................................4
CHAPTER 4..................................................................................................................................................5
SYSTEM DESIGN AND ARCHTECTURE................................................................................................5
4.1 SYSTEM ARCHIECTURE.................................................................................................................5
CHAPTER 5..................................................................................................................................................7
IMPLEMENTATION AND TESTING........................................................................................................7
CHAPTER 6..................................................................................................................................................8
RESULT AND DISCUSSION......................................................................................................................8
CHAPTER 7..................................................................................................................................................9
CONCLUSION AND FUTURE WORK......................................................................................................9
REFERENCES............................................................................................................................................10
APPENDICES.............................................................................................................................................11
vii
List of Tables
This page should list all the tables found in the thesis. The page number of the table must
also be included. The table numbers should be arranged according to the chapters.
viii
List of Figures
Diagrams, photographs, drawings, graphs, charts and maps are included as figures. The list
should be written similar as the List of Tables
ix
List of Abbreviations
List of abbreviations should be tied closely in the body of the report, and should not be
included if there are less than five abbreviations in the document.
x
ABSTRACT
This page should include a brief overview of your project. A maximum of one page, it should
allow a reader who is unfamiliar with the work to gain a swift and accurate impression of what
the project is about or why was it required, and what has been achieved.
xi
CHAPTER 1
INTRODUCTION
Introduction is mostly written for non-specialists so that they can get an overview of the project
without technical details. It should provide a brief overview of the project aims and structure of
the solution. It should also specify what unmet need or problem the FYP caters for and who
needs it.
At the end of chapter, provide a summary of the report organization, chapter outlining what has
been covered in this chapter and explain what comes in the following chapters.
This chapter of your FYP documentation provides a background of the project, states, i what the
documentation is about and how it has been structured. This could contain additional portions
and sections such as Overview, Background, Problem Statement, Objectives, Justification and
Project Timeline.
1.1 OVERVIEW
2
CHAPTER 2
LITERATURE REVIEW
Provide an overview to the projects background knowledge without too much in detail (stick to
the scope of the project). The background can refer to previous work referenced from journals,
articles, newspapers, or any academic literature providing evidence that the proposed problem is
significant and real problem worth solving.
If available, provide closely related work done within the project scope and the challenges or
defects identified which can be considered as part of the new solution. Describe why you worked
on this project in light of the literature review?
3
CHAPTER 3
RESEARCH METHODOLOGY
The methods, approaches, tools, techniques, algorithms, or other aspects of the solution are
sufficiently discussed with sufficient details and supporting figures.
The Methodology section is very important because it documents how you plan to tackle your
research problem. Describe the research that whether it is Exploratory, Descriptive, Causal or a
Case study or other method.
To solve actual problems in a company setting, software engineer or a team of engineers must
incorporate a development strategy that encompasses the process, methods and tools layers and
the generic phase. This strategy is often referred to as a process Model or a software engineering
paradigm. A process model of software engineering is chosen based on the nature of the project
and application, the methods and tools to be used and the controls and deliverables that are
required. A software process model has predefined steps, accomplishing those steps untimely
results in software. So, the software process model is followed step-by-step to develop software.
There are many software process models like:
Waterfall Model
4
CHAPTER 4
In this chapter of FYP theis report process, the available system designing components have
been utilized. A systematic design is critical for a reliable computer system.
The main purpose here is to gain a general understanding of how and why the system was
decomposed, and how the individual parts work together to provide the desired functionality. At
the top-most level, describe the major responsibilities that the software must undertake and the
various roles that the system (or portions of the system) must play. Describe how the system was
broken down into its components/subsystems (identifying each top-level component/subsystem
and the roles/responsibilities assigned to it). Describe how the higher-level components
collaborate with each other in order to achieve the required results. Don't forget to provide some
sort of rationale for choosing this particular decomposition of the system.
The system design in this documentation is designed to cater the working environment. The
system designing is divided into the following parts below.
Flowcharts
Data Flow Diagrams (DFDs)
Normalized Tables
Data Dictionary
Low Level Design
High Level Design
Entity Relationship Diagram (ER-Diagram)
Input and Out Screen Layouts
Depending on your methodology this chapter would contain different materials. However,
structuring it as three subsections can be a good idea.
Software Design
User Interface Design
Database Design
Implementation
5
6
CHAPTER 5
Explain the methods, tools and techniques used to develop the software. What kind of software
and testing methodologies implemented. Explain core functionalities in narrative format.
Controlled libraries, templates, code walkthroughs.
Explain how the proposed software has been evaluated and compared at runtime with the
original specifications. The Accuracy, Performance and Scalability of the proposed software
must be critically analyzed and should solve identified problem statement.
7
CHAPTER 6
A comprehensive evaluation of the solution is presented with supporting figures and graphics.
System testing is performed through a strong testing strategy and the test cases cover all the use
cases.
8
CHAPTER 7
Include a brief summary of how the proposed solution is going to/has addressed the problem
statement specified in the introduction section. Provide an overview of what kind of evaluations
were undertaken in order to prove that the solution really solves the problem with evidence on
results findings.
Provide an overview of the recommendations and Include a future directions which is required as
part of the future work.
9
REFERENCES
The title of references should be center aligned, bold face, 12pt time new Roman. This section
should include all relevant references cited in the document. Only references cited in the text are
to be included in the reference list. The students should use APA 6th manual for citation.
Following are some examples provided on how to cite a study using APA 6 th manual in text and
references section. Furthermore, any source not mentioned below please refer to APA 6th
manual for help.
Article in a Magazine:
Henry, W. A., III. (1990, April 9). Making the grade in today's schools. Time, 135, 28-31
Article in a Newspaper:
Unlike other periodicals, p. or pp. precedes page numbers for a newspaper reference in APA
style. Single pages take p., e.g., p. B2; multiple pages take pp., e.g., pp. B2, B4 or pp. C1, C3-
C4.
Schultz, S. (2005, December 28). Calls made to strengthen state energy policies. The Country
Today, pp. 1A, 2A.
Examples:
Abratt, R., & Russell, J. (1999). Relationship marketing in private banking in South Africa, The
International Journal of Bank Marketing, 17(1), 5-19.
Efron, B. (1979). Bootstrap Methods: another look at the Jackknife, Annals of Statistics, 7, 1-26.
Furer, O., Ching-Liu, B.S. & Sudharshan, D. (2002). The relationship between culture and
service quality perceptions, Journal of Service Research, 2 (4), 355-370.
10
APPENDICES
The title of appendices should be center aligned, bold face, 12pt time new Roman. This section
should include all relevant materials which support the document written. Appendices should be
assigned alphabets, like Appendix-A. Appendix-A.1. Appendix-B.2 etc. All included appendices
should be coated in the text body of synopsis.
Appendices are provided to give supplementary information, which is included in the main text
may serve as a distraction and cloud the central theme.
• Appendices shall carry the title of the work reported and the same title shall be written in the
contents page.
11
Instructions: Documents Description and Specification
1. Style
The synopsis documentation should be written clear and concise, and use following
specifications.
a. Paper size: A4 (8.27" x 11.69).
b. Font style: Times New Roman.
c. Font Size: 12pt normal for writing in English and 16pt normal for writing in Urdu.
d. All Headings: 12pt bold for writing in English and 16pt bold for writing in Urdu.
e. Line Spacing: 1.5 space.
f. Margins: Left: 1.5 in, Right: 1in, Top: 1 in, Bottom: 1 in.
g. Include a page header, insert page numbers flush right, in page header
2. Parts of a Synopsis
BS/MS/M.Phil/Ph.D synopsis/report should consist of following parts:
a. Title Page
b. Certificate of Completion
c. Decleration
d. Acknolwedgment
e. Abstract
f. Table of Contents
g. List of Tables
h. List of Figures
i. List of Abbreviations
j. Main Text Body
k. References
l. Appendices
12
5. Plagiarism
a. Definition
Presenting someone else’s idea, work, project, or words as your own. This also includes
using someone’s exact words, figures, tables, etc or even modifying them but not providing
citation or reference to the actual work.
13