0% found this document useful (0 votes)
10 views

Final Project report 2025

The document outlines the format and assessment criteria for final year project reports in the Department of Computing and Informatics at the School of Science and Technology. It details the structure of the report, including required sections such as the title page, abstract, literature review, methodology, and references, along with the weightage of project work, presentation, and final report in the overall assessment. Additionally, it emphasizes the importance of originality, proper referencing, and the submission process, including binding and plagiarism guidelines.
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)
10 views

Final Project report 2025

The document outlines the format and assessment criteria for final year project reports in the Department of Computing and Informatics at the School of Science and Technology. It details the structure of the report, including required sections such as the title page, abstract, literature review, methodology, and references, along with the weightage of project work, presentation, and final report in the overall assessment. Additionally, it emphasizes the importance of originality, proper referencing, and the submission process, including binding and plagiarism guidelines.
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/ 14

SCHOOL OF SCIENCE AN TECHNOLOGY

DEPARTMENT OF COMPUTING AND INFORMATICS


FORMAT OF PROJECT REPORT
Final Year Project Report
Assessment
Your project work will be examined by your supervisor and a project committee.

Marks are divided into the following components, with the weights indicated:

• Project works: contributes 50% to the overall mark


• Presentation: contributes 20% to the overall mark
• Final report: contributes 30% to the overall mark

PROJECT REPORT FORMAT

The Structure of Page Arrangements for the Project Report

1. Title Page
2. Declaration of Project Paper and Copyright
3. Approval by the University supervisor
4. Dedication
5. Acknowledgements
6. Table of Contents
7. List of Figures
8. List of Tables
9. List of abbreviations
10. Abstract
11. Chapter one (Introduction)
1.1 Background of Study
1.2 Problems Statement
1.3 Main Objective and specific objectives
1.4 Project or research questions
SCHOOL OF SCIENCE AN TECHNOLOGY
DEPARTMENT OF COMPUTING AND INFORMATICS
FORMAT OF PROJECT REPORT
1.5 Scope of Study
1.6 Significance of Project
12. Chapter Two (Literature Review)
2.1 Introduction
2.2 Literature Review of Related IT Projects and Case Studies
Summary of previous IT-based projects addressing similar challenges.
2.3. Summary and research Gap (your summary must show the gap identified as a result of
reviewing the literature which must be in line with the problem statement in chapter 1)
13. Chapter Three (Research Methodology)

14. Analysis and Design


15. Development and testing
16. Implementation
17. Discussion, Conclusion and Recommendations
18. References
19. Appendix
A short outline for each sub-part is described below:

Title Page

As per the university's regulations, the title page of the report shall give the following information
in the order listed:

• Full title of the project as approved by the supervisor or the Faculty member or project
team.
• The full name of the author.
• The qualification for which the report is submitted.
• The Faculty name in which the project is to be submitted.
• The name of the institution to which the report is submitted.
SCHOOL OF SCIENCE AN TECHNOLOGY
DEPARTMENT OF COMPUTING AND INFORMATICS
FORMAT OF PROJECT REPORT
• The month and year of submission.
A good title should be relevant, short, concise and catchy. A good title will attract readers.

It should not:

• Leave the reader guessing what it is about


• Have spelling and grammatical errors.
Declaration of Project Paper

Tell the reader that this piece of work belongs to you and has never been submitted anywhere for
same or similar purposes. The declaration statement concludes with the signature of the student.

Approval

This page is where the supervisor shall endorse to confirm that he/she supervised your work,
without this endorsement, the project report shall not be accepted and the student shall not make
any presentation of defending their project

Acknowledgement

This part is all about thanking those who have helped you directly or indirectly on the completion
of the project. For example, your supervisor, your team mate and/or anyone who provided some
funding etc. Remember to be courteous. In this page, the author expresses his/her gratitude and
concern by using praising and thanksgiving words.

Table of Content

The table of contents is essential in any report as it helps the reader to go directly to where he/she
wants. It is important not to mislead the reader by indicating the wrong page number. Remember
that you can use a word processor’s Style feature to be able to create TOC, LOF etc. automatically
and this can be updated easily. The whole project report in a nutshell is made known in the table
of contents section, and therefore, it should include the titles of the first, second and third level
SCHOOL OF SCIENCE AN TECHNOLOGY
DEPARTMENT OF COMPUTING AND INFORMATICS
FORMAT OF PROJECT REPORT
headers, and must give a clear picture of the report to the reader. Preliminary pages should be
numbered in roman numerals.

List of Tables and List of Figures

Similarly, a list of figures and tables helps the reader to locate diagrams, charts and tables in the
document, and therefore, it should be numbered accordingly by chapter and page number.

List of abbreviations

Tell the reader all the words you have used in short and their full form so that they get to know
what you mean

Abstract

Abstract represents a summarized report of the complete project in a very concise and informative
format covering main objective and aim of the project, the background information, processes and
methods used, and methodologies implemented, followed with a brief conclusion of two to three
lines talking about the results and scope of the project.

This is one of the most important parts of your report. It should normally be written last. It should
be:

• Short and concise (should be between 250- 350 words in a single Paragraph)
• State the objective
• State the method used
• State the result
• State the conclusions
• Recommendation
• Brief introduction (the writing does not follow any specific order but make sure that all the
above areas are included in the abstract
It should not:
SCHOOL OF SCIENCE AN TECHNOLOGY
DEPARTMENT OF COMPUTING AND INFORMATICS
FORMAT OF PROJECT REPORT
• 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.

Chapter 1: Introduction

The introduction part is another trigger for the reader it should contain brief background
information about the project

It should contain:

• Brief background
• Present the problem under investigation
• Indicate the main objective and specific Objectives of the project
• Scope of Project
• Significance
This part might sound like the abstract but it is much longer. It will most likely be a few pages
long.

Introduction chapter should include the following sub chapter:

1.1 Background of Study

1.2 Problems Statement

1.3 Main Objective and specific objectives

1.4 Project or research questions

1.5 Scope of Study

1.6 Significance of Project


SCHOOL OF SCIENCE AN TECHNOLOGY
DEPARTMENT OF COMPUTING AND INFORMATICS
FORMAT OF PROJECT REPORT
Chapter 2: Literature Review

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:-

• What are the past literatures in your selected topic/area?

• Is there any related and suitable theories with your selected topic/area?

• How the literatures/theories help you in determining problem statement and ideas

• Why your selected topic/area is important to do the research/system

The literature review chapter should include the following sub chapter:

2.1 Introduction

2.2 Review of Literature in your area (The breakdown of sub-chapter is depending on the student
creativity and make sure your literature supports your study) could include the SWOT

2.3. Summary (your summary must show the gap identified as a result of reviewing the literature
which must be in line with the problem statement in chapter 1)

Chapter 3: Research Methodology


Describe methods used along the research or project activities. In other words, it describes the flow
of research activities from the beginning till the end and we need to thoroughly explain the
involved steps in the activities right from selecting the right research design for your project.
The research methodology chapter should include the following sub chapter:
3.1 Introduction
3.2 Research design selected
SCHOOL OF SCIENCE AN TECHNOLOGY
DEPARTMENT OF COMPUTING AND INFORMATICS
FORMAT OF PROJECT REPORT
3.3 Data Collection Methods
3.4 Data Analysis Methods
3.5 Software Development Methods (select one that fits in your system)
3.6 Any limitations and how you mitigated such limitations
Chapter 4: Requirements, Analysis and design
This section documents the analysis of the system to be implemented, documents the design
decisions that have been taken. The structure of the system and its components has to be
established. It consists of the following:
• Feasibility Study ( optional)
• Functional and Non Functional Requirement
• Alternative ways of solving the problem
• Proposed Solution with reasons
• Evaluation of tools- Pros and Cons
• Choice of Final Tool(s) with justification
• Detailed description of the system
• Functional Modeling of the system- Data Flow Diagram
Software Design Approach
Architecture Design – Interaction between components and/or modules
• Interface Design
• System Modeling – UML diagrams
• Database Design – ERD diagram
• Story Board
The requirement, analysis and design chapter should include the following sub chapter:
4.1 Introduction
4.2 User Requirements
4.3 System Requirements
4.3.1 Functional
4.3.2 Nonfunctional
SCHOOL OF SCIENCE AN TECHNOLOGY
DEPARTMENT OF COMPUTING AND INFORMATICS
FORMAT OF PROJECT REPORT
4.4 System Design
4.5 Database design
4.6 Interface Design
Chapter 5: Implementation and Testing
The implementation section describes how the different components in the project have been
implemented.
It should also consist of:
• Development tools and environment used
• Implementation of different modules (including detail steps about how they were developed)
• Sample codes (including standards and conventions)
• Difficulties faced and how they were addressed. Moreover, the implementation issues that have
been addressed can be discussed:
• Performance
• Consistency
Scalability
• Security issues
• Real-time issues
• Concurrency Control
• Flexibility
• Adaptability
• Fault-Tolerance
Testing
Testing starts alongside with the Implementation. The testing part will document the testing carried
out – the test data and the results obtained. When independent modules have been implemented
and tested, they can be integrated and tested as a whole.
Different types of testing Carried out:
• Unit Test – testing a single component
• Integration Testing – Combining different components
SCHOOL OF SCIENCE AN TECHNOLOGY
DEPARTMENT OF COMPUTING AND INFORMATICS
FORMAT OF PROJECT REPORT
• System test – Testing the system as a whole
• User acceptance test – user perspective of the system to check if requirements have been met.
Note that you should be able to provide details about how the above tests have been carried out
and not just list them. A test script could be used to demonstrate this. It would be very helpful if
you start documenting the tests carried out together with their test results during the
Implementation stage itself.
Testing and Implementation chapter should include the following sub chapter:
5.1 Introduction
5.2 Implementation
5.3 Testing (test results like screenshots)
Chapter 6: Discussion, Conclusion and Recommendations
This is usually the last chapter in the report which contains three main parts:
• Achievements:
It should critically assess the work done including the strengths and weaknesses and try to explain
the results obtained.
• Future Works:
No report is totally complete or has completely explored a domain. You can give some indications
where future work might be carried out or what other domain you would have explored without
the current time/resource constraints.
This chapter should include the following sub chapter:
6.1 Introduction.
6.2 Discussion of your findings/results
6.3 Conclusion
6.4 Recommendation
6.5 Future research areas
References
It is a major offense to copy the work of others without proper referencing. This practice is termed
as “plagiarism”. It is the equivalent of theft in the academic world. It is therefore very important
SCHOOL OF SCIENCE AN TECHNOLOGY
DEPARTMENT OF COMPUTING AND INFORMATICS
FORMAT OF PROJECT REPORT
that you add proper references at the end of your report and to add proper links of those references
to your report. References are important because they acknowledge the work of others and prove
that you have done enough investigation. Do not bring new references in your work which does
not appear in your in-text citation and also do not leave out any reference which is in your in-text
citation, (all references must be written in APA referencing style for all Bugema University
research projects or any research)
There are two types of copying:
• Copying whole paragraphs
• Using the idea of someone else
Different styles are needed depending on what you are referencing:
• Books
• Articles in journals
• Web pages
• Discussion groups (google APA referencing style for further guidance on this matter)
Appendix
It contains things that could not be directly included in the report but which will nevertheless help
the reader gain a better understanding of the project if included.
It usually includes part of the code, data sets, algorithms, extra illustrations (charts, barcharts,
photos), surveys, forms and templates.
5. Binding
5.1 For the purpose of presentation, the copies of the FYP report writing should be submitted in a
comb binding.
5.2 For the purpose of final submission, copies of the report writing must be submitted in
hardbound bindings.
6. Final submission of a final year project report
Students should submit the Final Year Project report as follows:
i. Three copies of the report (without binding) to the Supervisor for approval.
SCHOOL OF SCIENCE AN TECHNOLOGY
DEPARTMENT OF COMPUTING AND INFORMATICS
FORMAT OF PROJECT REPORT
ii. The electronic version of thesis in PDF format and the system in .exe format (DVD).
iii. Students are expected to meet the scheduled date of submission. Late submissions will be
penalized.
iv. Failure to submit the FYP report without a valid reason will be considered failed.
7 Plagiarism
Plagiarism is copying the work of another author without giving them the proper credits or
acknowledgement.
Report should get below 20% of similarities to existing source from plagiarism checker software.
If found >20% similarities, student need to re write FYP report.
8 Assessment objective
It is an assessment of a student's ability to:
1. Develop the contents of final year project report writing which are well structured, relevant and
coherent.
2. Demonstrate an exceptional quality of writing with excellent language style.
3. Demonstrate the originality and practically of the research project.

STUDENT PROJECT SUPERVISION FORM

STUDENT NAME:

SUPERVISOR NAME:

PROJECT TITLE:

NO. DATE OF COMMENT STUDENT SUPERVISOR SIGN


SUPERVISION SIGN
SCHOOL OF SCIENCE AN TECHNOLOGY
DEPARTMENT OF COMPUTING AND INFORMATICS
FORMAT OF PROJECT REPORT
SCHOOL OF SCIENCE AN TECHNOLOGY
DEPARTMENT OF COMPUTING AND INFORMATICS
FORMAT OF PROJECT REPORT

SUPERVISOR COMMENT: …………………………………………………………………………………………………………………………

HEAD OF DEPARTMENT COMMENT: ……………………………………………………………………………………………………

NB: FOR ANY GROUP TO APPEAR FOR PROJECT PRESENTATION, MUST HAVE SATISFIED THE NCHE AND
BUGEMA UNIVERSITY REQUIREMENTS OF 75% CONTACT WITH THE SUPERVISOR.

THE DOCUMENTS MUST BE APPROVED BY BOTH THE SUPERVISOR AND HEAD OF DEPARTMENT A
WEEK BEFORE PRESENTATION.
SCHOOL OF SCIENCE AN TECHNOLOGY
DEPARTMENT OF COMPUTING AND INFORMATICS
FORMAT OF PROJECT REPORT

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy