GUIDELINE FOR RESEARCH PROJECT IN COMPUTER SCIENCE DEPARTMENT

FEDERAL POLYTECHNIC NEKEDE OWERRI

COM 429 & COM 229

 TABLE OF CONTENTS
 Preliminary pages
 Title Page
This page usually contents the following information
a. The main title of the work and the subtitle (if any)
b. The complete names of the student (s) as the case may be.
c. A follow-up statement describing the research project, the department, school/faculty,
the institution to which it is being submitted and the purpose of the submission.
d. The month and year of publication

 Approval page
This Page expresses statements confirming the fact that the work had been properly
supervised and approved; having met the standard requirements of the department and
institution.

 Dedication
Here, the student researcher writes his/her dedication on this page. Usually, this comes in
a few lines of sentences to form a single paragraph.

 Acknowledgement
In this page, you are expected to recognize all those that made noteworthy contributions
to the success of your project. It allows for comments regarding the roles played by
significant contributors to the successful completion of the project work. The first person
to acknowledge after God is your supervisor followed by HOD and the department (Staff)
before other persons.

 Table of contents
This page usually runs into more pages than one. It outlines all the contents headings
(chapters, headings and sub-heading) of the entire project with the corresponding pages
where they can be found. The content pages are set out in such a way that to its left
hand side, the contents are outlined beginning with the preliminary pages (in roman
numerals) running through the entire chapters (in digital/arabic numerals). Each of the
content item listed is followed by the corresponding page numbers on the right hand while
each of the main and sub-headings carry some designated numbers corresponding to
the chapter number to the inner left-hand margin.
 List of tables
 It outlines all the table labels in the project with the corresponding pages where they can
be found. The tables are usually numbered using chapter heading. E.g. first table in
chapter 3 will be table 3.1.

 List of figures
 It outlines all the figures in the project with the corresponding pages where they can be
found. The figures are usually numbered using chapter heading. E.g. first figure in
chapter 1 will be figure 1.

 Abstract
An abstract is short account of something much longer such that only the salient issues
contained are brought to the fore. This section provides an outline of the prominent issues in
entire project work using future tenses. The abstract is often the last item that you write, but
the first thing people read when they want to have a quick overview of the whole project
work. If done well, it makes the reader want to learn more about your research. The basic
components of an abstract in any discipline are: (1) Motivation/problem statement (2)Aim of
study (3) Methods/procedure/approach/tools (4) Results/findings/product (5) Conclusion/
implications. Note, abstract should be written in one paragraph with single line spacing not
more than 250 words.
 CHAPTER ONE
INTRODUCTION

1.1 Introduction
In this section, you introduce the project topic and what the entire chapter is all
about or covers.

1.2 Background of Study

In this section, you document the general description of the topic, events, trends
or reason that necessitated the choice of the project. You are to document
background information (prevailing circumstance at that point in time that prompted
the project) of the system been understudied with focus on the events that led you
to embark on the project.

1.3 Statement of Problem

Here, the obvious problems and difficulties experienced in the existing system that
you want to solve are highlighted

1.4 Objectives of the Study

State clearly the main goal of the research work and the specific objectives aimed
at solving the problems stated in 1.3. Each of the specific objectives should
mitigate the problems one after the other.

1.5 Significance of Study

Under this section, you are expected to write the overall impact and potential
benefits of the research work. That is when this work is completed; what will
contribute to humanity or what impact will it make to the organization or related
organizations being understudied.

1.6 Scope of study

The precise area (s) the project will cover from the whole topic is discussed in this
section.

1.7 Limitations of the study

The factors that deterred you and how the deterred you in course of the project
should be documented here.

1.8 Definition of terms

Technical terms and other used in the project that have specific meaning based on
the project are explained in this section. When you finish your work you have to
make sure you update this list.
 CHAPTER TWO
REVIEW OF RELATED LITERATURE
2.1 Introduction
In this section, you introduce the literature review and topics/concepts to be reviewed
are highlighted.
2.2 -….. Body of the work. Literature review is an account of what has been published
on a topic by accredited scholars and researchers that aim at showing you convince
your readers that you have read extensively and have a good grasp of the published
works concerning the topic, related topics or questions in the research. It is also aimed
at closing some research gap in the area understudy. In closing a research gap, the
researcher (s) will have to explain his/her/their own view about the issue or area
understudy. Efforts must be made to give credit to authors you are using their work by
citing and referencing them properly.

What is literature review

A Literature review is a survey or comprehensive summary of relevant and significant scholarly
publications on a particular topic.  The main reason for writing literature review in a research
work is to convey to the reader what knowledge and ideas have been established on a topic,
and what their strengths and weaknesses are. A literature review can be said to be both the
process and the product.

 It is a process because it involves a systematic examination of prior scholarly works.

 While It is a product because it is a descriptive and analytic summary of the existing
material relating to a particular topic or area of study.

In writing a literature review, you must define a guiding concept such as your research objective,
the problem or issues you are discussing/ working to mitigate.

Objectives of literature review

The 3 main objectives literature review are as follows:
1. It surveys the literature in a chosen area of study or topic
2. It synthesizes the information in those literature into a summary
3. It critically analyses the information gathered by identifying gaps in current knowledge;
showing their limitations, formulating areas for further research and identify areas of
controversy

Purposes of literature review

The main purpose of a literature review in a research project is to provide a review of writings on a given
topic in order to establish the reviewer’s own position on that topic. A literature review provides a
reader with a comprehensive look at previous discussions prior to the one the researcher is making in
his or her own work.

Literature review is written in a research project to achieve the following purposes

 1. To help understand a research topic.
2. To establish the importance of a topic
3. To Determine what has already been written on a topic
4. Provide an overview of key concepts in the topic under study
5. Identify strengths and weaknesses of the scholarly publications on the topic.
6. To help one develop his or her own ideas on a given topic.
7. To ensure a researcher is not replicating research others have been successfully
completed.
8. To demonstrate knowledge and show how the current work is situated within, builds on,
or departs from earlier works published on the topic.
9. To Identify gaps and conflicting evidence in the research
10. To understand where one’s own research fits into and adds to an existing body of
agreed knowledge.

What does your literature review say about your research Project?
Your literature review shows your readers whether or not you have an in-depth grasp of your
subject. When you have a rich literature review, it convinces your readers that you have sound
knowledge of the subject you are working on and that your work is not based on assumptions.

Structure of a literature review

A Literature review is usually divided into 3 main parts, as follows

1.Introduction,

2. Body paragraphs or body of the work

3. Conclusion.

NOTE: That the fourth part of the literature is references which usually comes at the end of the
entire project report. The referencing is done using APA referencing style 7th edition

What is APA?

APA referencing style is an author-date referencing system published by the American

Psychological Association (APA). The APA referencing style is made up of two components: in-
text citations and the reference list entries. In-text citations enable one to acknowledge the
source of a particular writing in the body of the work while the reference entries enables one to
include at the end of the work all the sources cited to in the review.

How to cite in the body of your work using APA style otherwise known as
APA in-text citation
An APA in-text citation consists of the author’s last name and year of publication, for example:
(Nwoduh, 2020). If you're quoting the exact words of someone else, then you need introduce
the quote with an in-text citation in parenthesis and you have to include the page number as
well, for example: (Nwoduh, 2020, page. 17). For sources such as websites that have no
page numbers, you have to use the paragraph number, for example: (Nwoduh, 2020, para 2).
In-text citation is used in review, when you summarize, paraphrase, or quote from another
source. For every in-text citation in your work, there must be a corresponding entry in your
reference list.

How to cite a source when there is no author:

When you want to cite a source whose author is unknown, instead of the author's name, include
the first few words of the work's title in the in-text citation. Enclose the title in double quotation
marks when citing an article, web page or book chapter. Italicize the title of periodicals, books,
and reports. Example:( How to site a source without an author, 2019)

How to cite a source when there is No publication date

If you have a publication you want to cite but the publication date is unknown, use “n.d.” (no
date) in the column where you are suppose to have year of publication. For example: (Nwoduh,
n.d.).

How to cite sources with multiple authors

When you have only two authors in source you want to cite, you have to list the two
authors surname connecting both names with & (ampersand) and include the year. Example
(Nwoduh & Emejeamara, 2020).

Sources with more than two authors

APA 7th edition recommends that in-text citation, works or sources with three or more
authors should shortened right from the first citation. You only include th e first
author’s surname followed by “et al.”. Note that in 6 th edition you only shorten with “et
al.” from the second citation but with 7th edition you start using et al from the first
citation.

How to cite group author

Group author refers to when the author of work is an organization or corporate entity such as
central bank of Nigeria (CBN), National center for disease control (NCDC), National Bureau for
statistics (NBS) etc.
When citing such organizations in the body of your work, you have to write the full name with
abbreviation and year of publication the first time you are citing it and subsequently you will be
using abbreviation and year of publication.

The Reference List

All in-text citations in the body of your work should be listed in the reference list at the end of
your review. The purpose of the reference list entry is to contain all the information that a reader
of your work needs to follow-up on your sources. An important principle in referencing is to be
consistent.

When compiling your Reference List using APA stlye, you should do the following:

1. List references on a new page with a centred heading titled: References.

2. Include all your references in one alphabetical listing from A - Z regardless the type or
format of the sources, e.g books, journal articles, online sources,.
3. Order entries alphabetically by surname of author(s).
4. List works with no author under the first significant word of the title. In other words cited
a work whose author is unknown, you have to use part of title as the name of the author
and the first significant word in that title takes the place of the surname
5. Indent second and subsequent lines of each entry (5-7 spaces).
6. Use double spacing.
7. Note that all references in APA end with a full stop except when the reference ends with
a URL or a DOI.

How to Journal article into your reference list

A basic reference list entry for a journal article in APA must include:

1. Author or authors surname. The surname is followed by first initials.

2. Year of publication of the article (in round brackets).
3. Article title.
4. Journal title (in italics).
5. Volume of journal (in italics).
6. Issue of journal .
7. Page range of article.
8. DOI (presented as a hyperlink, for example https://doi.org/xxxxx).
9. The first line of each citation is left adjusted. Every subsequent line is indented 5-7
spaces.

Example:
Ruxton, C. (2016). Tea: Hydration and other health benefits. Primary Health Care, 26(8), 34-42.
https://doi.org/10.7748/phc.2016.e1162.

How to enter Book sources into your reference list

A basic reference list entry for a book from a library database in APA must include:

1. Author or authors surname. The surname is followed by first initials.

2. Year of publication of the book (in round brackets).
3. Book title (in italics).
 4. Edition (in round brackets), if other than first edition.
5. Publisher.
6. DOI (where a book has a DOI this must be included, even if you are referring to a print
book).
7. The first line of each citation is left adjusted. Every subsequent line is indented 5-7
spaces.

Example: Arnott, G. D. (2017). The disability support worker (2nd ed.). Cengage Learning. 

How to enter resources from web pages into your reference list

A basic reference list entry for a web page in APA must include:

1. Author or authors. (The surname is followed by first initials if applicable). The author

could be an organization otherwise known as cooperate author.
2. Date of publication (in round brackets).
3. Article title (in italics).
4. URL
5. Website name except the author’s name is the same with the website name
6. The first line of each citation is left adjusted. Every subsequent line is indented 5-7
spaces.
7. Note that date of retrieval is no longer necessary according on APA 7th edition

Example.
Asmelash, L. (2019, August 14). Social media use may harm teens' mental health by disrupting
positive activities, study says. CNN. https://www.cnn.com/2019/08/13/health/social-media-
mental-health-trnd/index.html

Notable changes made in APA 7th edition.

The biggest changes in the 7th edition are as follows:

1. The publisher location is no longer included in the reference.

2. The in-text citation for works with three or more authors is now shortened right
from the first citation. You only include the first author’s name and “et al.”.
3. Surnames and initials for up to 20 authors (instead of 7 as obtained in 6 th edition)
should be provided in the reference list.
4. DOIs are formatted the same way as URLs. The label “DOI:” is no longer
necessary.
5. URLs are no longer preceded by “Retrieved from,” unless a retrieval date is
needed. The website name is included (unless it’s the same as the author), and
web page titles are italicized.
6. For ebooks, the format, platform, or device (e.g. Kindle or PDF) is no longer
included in the reference, and the publisher is included.
7. When citing a podcast episode, the author, the editor and the host of the episode
should be included; for a TV series episode, the writer and director of that episode
are cited.
8. There is Increased flexibility regarding use of fonts: options such as Calibri 11,
Arial 11, Lucida Sans Unicode 10, Times New Roman 12, and Georgia 11 are
included.

CHAPTER THREE
SYSTEM ANALYSIS AND DESIGN.
Systems analysis is a method of figuring out the basic elements of a project and
deciding how to combine them in the best way to solve a problem. System analysis,
then, is the process of gathering and interpreting facts, diagnosing problems, and
using the information to recommend improvements to the system. On the other
hand, System design is the process of defining the components, modules, interfaces,
and data for a system to satisfy specified requirements.

3.1 Introduction
In this section you are to explain briefly what the chapter is all about, such as why you
have to analyze the system and why it is important you do that. It also shows what aspects of
the analysis and design will be discussed in the chapter.

3.2. Detailed Analysis of the existing system.

Here, you are expected to document how things are done in the existing system. Make
your reader to see a clear picture of what the existing system looks like and the
operations involved in the system. You have to document how the existing system uses
hardware, software (if any) and people to collect input data, the required activities for
converting input to output, storage/ backup procedure and how generate information
suitable for decision making. This sub section of the report should show your reader
how you understand the operation of existing system.

3.2.1. Problems of the existing system.

From the analysis of the existing system in 3.2 above, identified challenges in the
existing system are documented here. The identified challenges shouldn’t be far from
the ones already in statements of problem in your chapter one; however it may be more
detailed.

3.3 Research Methodology

Here, you are expected to document the research methodology you used for your work,
why you choose it. Some notable research methodology used for software development
project like ours include Structured System Analysis and Design Methodology
(SSADM), Waterfall, Rapid Application Development, Agile software development etc.
Also expected to be documented under this heading are the techniques used to collect
data for analysis such as interview, observation, questionnaire, focus group discussion,
examination of forms and documents, review of similar systems obtainable elsewhere
etc.

3.4. Objectives of the new system.

In this section, the objectives of the new system are documented. Considering the fact
that main aim of our project (study) is software development, the objectives of the study
in chapter one shouldn’t deviate from the objectives of the system. Note that, the
objectives of a system must be precise, effective and measurable.

3.5. Feasibility study

A feasibility study involves taking a judgment call on whether a project is achievable or
not. It evaluates the project's potential for success. Feasibility study investigates the
problem in the existing and the information needs of the critical stakeholders use it to
determine the resources required to provide information systems solution, the cost and
benefits of such solution and the practicability of such a solution. The feasibility of a
proposed systems solution is evaluated based on these 3 components

3.5.1. Technical Feasibility - Technical feasibility study involves evaluation of the

hardware and the software requirements of the proposed system. It looks at the
possibility that the organization under study has or can procure the necessary resources
for the development of the new system. This assessment is centered on the technical
resources available for the development and implementation of the new system such as
software, hardware and technical man power. A system is said to be technically feasible
if it demonstrates that the needed hardware, software and man power are available in
the marketplace and can be procured or developed by the time of implementation.

3.5.2. Operational Feasibility – This is the ability, desire and willingness of the
stakeholders to use, support and operate the proposed system. Operational feasibility
study involves undertaking a study to analyze and determine how seemingly the
proposed system will integrate into the operation of the organization for which it is being
designed and meet the needs (requirements) of the organization. It includes design-
dependent parameters such as usability (skills the users need to have and how to get
it), reliability, maintainability (is the maintenance requirements available), supportability
(can the new system support other sub or main system), sustainability (how do we
sustain it) and affordability (in all how affordable are all these other factors). The
stakeholders include management, employees, suppliers (if applicable) and customers.
A system is said to be operationally feasible if the system seamlessly integrate into the
operations of the organization under study and there is show of wiliness by the critical
stakeholders to adopt and use the system.

3.5.3. Economic Feasibility – This aspect or component of the feasibility study

assesses the economic viability of the proposed system. It looks at the cost, and
benefits associated with project (new system) before financial resources are allocated.
This assessment typically involves a cost/ benefits analysis of the project.

3.6. New system Structure (Program structure)

In this section, a detailed description of the new system is documented using suitable
model diagram like context/dataflow diagram, modularity, system flow chart, program
flowcharts diagram, should be used to show the structure of the new system.

3.6.1. Context/ Dataflow Diagram This diagram show the system as a whole and its
inputs and outputs from/to external. It defines the boundary between the system and its
environment showing the entities that interact with it.

3.6.2. Modularity: This refers to the extent to which software application may be
divided into smaller modules. The modules are most often divided based on
functionality. In this subsection, you are expected to describe the various modules in
your system and their functions.

3.6.3. System Flowchart: System flowchart is a type of flowchart that explains the
functionality of an entire system. A system flowchart shows the flow of activity within the
entire system while a program flowchart represents a single program module in the
system. You are to draw here a system flowchart showing the functionality of the entire
system and relationship/link between the sub systems.

3.6.4. Program flowchart: An entire software system is collection of multiple program

modules. A program flowchart therefore describes the flow of activities in a single
program module. You are expected to draw in this section a flowchart detailing the flow
of activities (processes, data and information) in each of the major program modules.

3.7. System Design/Menu Specifications

This section should explain important processes of the system design such as inputs,
outputs, database, security and interface design for the new system. Model diagrams
such as use case diagram can be used to show the core processes of each of the
specifications.

3.7.1. Input Design Specification: In this section a clear description of what the inputs
to the new system are, the input interface, how the inputs to the system will be collected
and processed and devices required for the input are documented in this sub-section.
So you are expected to describe here, the input interface, method of input and tools
required to feed the system with inputs.

3.7.2. Output Design Specification: In this sub-section a description of the main

outputs from the new system and the format of presentation are documented. In other
words you are to present here, the major outputs from the system and how the outputs
will be presented to the users.

3.7.3 File/Database Design Specification: In this sub-section, a description of the

identified entities and their relationship, data model and database schema for the new
system is documented. An entity relationship diagram should be used to explain the
data model where possible and a table should be used to present the database schema
for the new system.

3.7.4 Security Design Specification: This sub-section describes security

specifications and features for the new system and how it works. Example, how a user
is identified and authenticated before granting access to the system or some aspects of
the system.

Appendix 1: SOME SAMPLE MODEL DIAGRAMS

ENTITY RELATIONSHIP DIAGRAM

CUSTOMER L_STATUS PROPERTY SALE_STATUS

CONTACT AGENT LISTING

Figure 1.1: Sample Entity Relationship Diagram

DATA DICTIONARY

Table 1.1 Data dictionary for the entity CUSTOMER

Entity: CUSTOMER

Attribute Description Data type Constraint

Cust_no Customers ID number Text Primary key

custName Customer name Text Not null

custCity City of the customer Lookup wizard Not null

Table 1.2 Data dictionary for the entity AGENT

Entity: AGENT

Attribute Description Data type Constraint

AgentID ID of the agent Text Primary key

Agent_name Name of the sales agent Text Not null

AgentEmail Email address of the agent Text

Table 1.3 Data dictionary for the entity CONTACT

Entity: CONTACT

Attribute Description Data type Constraint

Cust_no Customers ID number Text FK, PK

AgentID ID of the agent Text FK, PK

Intention Reason for contact Text Not Null

Table 1.4 Data dictionary for the entity LISTING

Entity: LISTING

Attribute Description Data type Constraint

ListingID Listing number Text Primary key

AgentID ID of the agent Text FK

PropertyID Property identification number Autonumber FK

beginList Begin listing date Date Not null

endList End listing date Date Not null

Price Price of the property Currency Not null

 Table 1.5 Data dictionary for the entity PROPERTY

Entity: PROPERTY

Attribute Description Data type Constraint

PropertyID Property identification number Autonumber PK

measurement Area covered by the property Text Not null

Year Year built Currency Not null

address Address of the property text Not null

postcode Postal address text Not null

Table 1.6 Data dictionary for the entity SALE-STATUS

Entity: SALE_STATUS

Attribute Description Data type Constraint

PropertyID Property identification number Autonumber PK

Status Sale status Text Not null

Table 1.7 Data dictionary for the entity L-STATUS

Entity: L_STATUS

Attribute Description Data type Constraint

licenseID Vendor code Text Primary key

AgentID ID of the agent Text FK

L_status License status Text Not null

CONTEXT DIAGRAM

1. SAMPLE CONTEXT DIAGRAM FOR ECOMMERCE WEBSITE

The context diagram below is for ecommerce website used to show the relationship among the
external components made up of the customers, staff, management, and payment system.

Figure 1.2: Context Diagram for E-commerce Website

Image Source: https://www.analyze.co.za

2. SAMPLE CONTEXT DIAGRAM FOR AN ATM SYSTEM

In the diagram below, a context diagram is used to display the Automatic Teller System
software plus the hardware that interacts with it. The arrows indicate the directions and
the types of data flowing between the software and every single hardware component.
 Figure 1.3 Context-Diagram for ATM-System
Image Source: https://online.visual-paradigm/system-context-diagram-atm-system

3. SAMPLE CONTEXT-DIAGRAM FOR A HOTEL-RESERVATION-SYSTEM

The context diagram below depicts the necessary components of a computerized system
that distributes and stores the hotel reservation information.
 Figure 1.4 Context-Diagram for a Hotel-Reservation-System
ImageSource: https://online.visula-paradigm/system-context-diagram-example/hotel-
reservation-system

SYSTEM FLOCHART

A system flowchart describes how an entire system operates. It helps to recognize the
flow of operations in the system and in preparing the required documents of the system.
Figure 1.5: System Flowchart for Attendance Management System
Source: Shoewu O., Makanjuola N.T. & Olatinwo S.O. (2014) American Journal of Computing
Research Repository. 2014, 2(1), 8-14 doi:10.12691/ajcrr-2-1-2

Figure 1.6: Stockbridge system flowchart –

Image source: Wikimedia Commons
Figure 1.7: System Flowchart for Account creation
Image source: Wikimedia Commons
 PROGRAM FLOWCHART
An entire software system is collection of multiple program modules. A program flowchart
therefore describes the flow of activities in a single program module.

START

RATE = 300

INPUT EMPYNAME

WAGE = RATE*HOURS

PRINT EMPYNAME, RATE, HOURS, WAGE

STOP

Figure 1.8: Program Flowchart to compute the wage earned by an employee

 Figure 1.9: Program flowchart
Image Source: lucidchart.com
 CHAPTER FOUR
IMPLEMENTATION, RESULT AND DISCUSSION
4.1 Introduction
Here, you are expected to document a concise description of what the entire chapter is
all about

4.2. Software development tools and Justification

In this section, various tools used for the development of the system are discussed, the
reason for using them are also highlighted.

4.3 System Requirements

All the tools (software, hardware and people) required to get the developed system
running are stated here in the order below. It includes hardware requirements, (such as
processor speed, network configuration etc), software deployment requirements and
skills expected of the users. Note: This does not include tools required to develop the
program.

4.3.1 Software Requirements (All software required for the new system to run)
4.3.2 Hardware requirements (All hardware tools required for the new system to work)
4.3.3 People Requirements (The basic skills the users are expected to have)

4.4 System testing

In this section various types of test (such as modular/unit testing and integrated testing)
carried out to ensure that the developed software did not deviate from the design
specification are discussed.

4.5 Implementation Details

4.5.1 Coding. State the code size used and the type of programming structrure used.

4.5.2 End user training and manual

Here, procedures and materials (such as help lines and manuals) that are developed to
aid users familiarize with the system are discussed.

4.5.3 File conversion

In this section, a brief explanation should be given on how existing files and other
documents will be converted or digitalized if they manually done initially.

4.5.4 Changeover Procedure

In this section, the major system changeover procedures are discussed briefly and a
changeover procedure that best suits your work is recommended with reasons.
4.5.5 Commissioning. Here you have to explain the process of verification and
validation of the software. Verification is used to ascertain that the software conforms to
the behavior of conventional software. While validation involves ascertaining it meets
the need for which it is produced. In other words commissioning has to do process of
ascertaining if the software is user friendly, appropriate and efficient. (Verification deals
with user friendliness while validation deals with appropriateness and efficiency)

4.5.6 Maintenance details

Recommend ways the new system should be maintained to give effective services. For
instance, if some components need to be updated; how and when is it going to be
done? Also things like error handling can be discussed under maintenance details
.
4.6 Results
The output of the new system is evaluated in line with the objectives stated in chapter
one and the specific objectives achieved by the system are documented here as the
results.

4.7 Discussion
In this section, the results gotten in 4.6 above are discussed in details. That is how the
new system accomplishes each results one after the other. If there are shortcoming
observed with the result (such as high use of computer resources compared to the
existing system) it is also noted here.
 CHAPTER FIVE
SUMMARY, CONCLUSION AND RECOMMENDATIONS
5.1 Summary: This section provides a summary of the entire project work. It represents the
main essence of what the researcher had done and found as a result of his
investigations.
5.2 Conclusion: The conclusion states whether you have achieved your objectives,
gives a brief summary of the key finding or information in your project and highlight the
major outcomes of the project work and their significance.

5.3 Recommendation: Recommendations are meant to serve as suggestions on how

to improve the present state of affairs as revealed by the study’s findings. The
recommendations are expected to address salient issues, which might have been
raised in the course of the investigation. This section is also used to suggest related and
follow-up studies, which interested future researchers can consider. This is with a view
to filling the gaps, which the present study left unattended to, as a result of its own
limitations.
References Style : APA Reference style 7th edition.

Appendix 1: Source Code

Appendix 2 : Snapshots of output

PRINTING FORMAT FOR THE PROJECT

Font type: Time new Roman

Font size: 12

Line Spacing: Double line Spacing (2.0)

Paper Size: A4 (21x29.7 cm)

Cover color: Black for HND and Yellow for ND

Chapter headings: All in Upper case

Sub Headings: Title case