0% found this document useful (0 votes)
428 views2 pages

Appendix A - Project Report Format and Guide

The document provides guidelines for formatting a project report, including preliminary pages like a cover page, acknowledgements, abstract, table of contents, and lists of figures and tables. It also outlines the main body sections which should include an introduction, methodology, conclusion, and recommendations as well as a references section and any appendices.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
428 views2 pages

Appendix A - Project Report Format and Guide

The document provides guidelines for formatting a project report, including preliminary pages like a cover page, acknowledgements, abstract, table of contents, and lists of figures and tables. It also outlines the main body sections which should include an introduction, methodology, conclusion, and recommendations as well as a references section and any appendices.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Appendix A

PROJECT REPORT FORMAT AND GUIDE


The project report should contain the following:
(I) PRELIMINARY PAGES
a) Cover page: This should show the following in the given order:
Name of the Institute; name of department, title of the project report, name of the
student, student’s registration number, programme, student’s year of study,
project duration.
b) Acknowledgement The student should acknowledge all those who assisted in contributing to
the success of the project and report writing.
c) Summary/Abstract This should provide a summary of the most important practical
work/project the student learnt as well as the major challenges, conclusions and
recommendations.
d) Table of contents A table of contents should be generated which shows the
contents of the report and the page numbers for easy reading and referencing.
e) List of Figures: All figures must be captioned at the bottom, with figure numbers shown
against each caption. The pages where particular figures are found should be
indicated for easy reading and referencing. Figures should be preferably
numbered according to the chapter numbers.
f) List of tables: All tables must be given headers and with table number shown against each
table header as well. The pages where particular figures are found should be
indicated for easy reading and referencing. Tables should be preferably numbered
according to the chapter numbers.
g) List of acronyms/abbreviations: All acronyms or abbreviations used in the report should be
included in this section, with their full meanings.

(II) MAIN BODY


Chapter 1: Introduction

a) Background Information
b) Project Description
1
Appendix A

c) Project objectives

Chapter 2: Main Body (For Informatics students)


The student is supposed to specify the methodology used in doing the Project. Also should write
on:
a) Requirements Specification
b) Requirements Analysis
c) System Design
d) System Implementation / Simulation
e) System Testing

Chapter 3: Conclusion and Recommendation


a) In presenting the conclusion, remember to include the major strengths and weaknesses of
the project work and benefits derived from the project work.
b) Recommendation on how to improve the project work, in terms of planning and
operational logistics.

REFERENCES
All relevant citations such as textbooks, personal communications, internet material, codes of
practice and guidelines which student uses during the project and/or report writing must be
quoted using the Harvard style of referencing.

BACK PAGES
APPENDICES
This should include any other annexes to the report such as drawings, design charts, photographs
etc. If the student developed software then all codes should be included in this section.

You might also like