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

ND Projectformat

Uploaded by

vikifera7
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
10 views

ND Projectformat

Uploaded by

vikifera7
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

[Title]

By

[e.g.ZUBAIR Alhaji Halimat]


[Matric. No.]

A PROJECT SUBMITTED TO THE DEPARTMENT OF COMPUTER


SCIENCE, SCHOOL OF APPLIED SCIENCES, KOGI STATE
POLYTECHNIC, LOKOJA.
IN PARTIAL FULFILMENT OF THE REQUIREMENTS FOR THE AWARD
OF HIGHER NATIONAL DIPLOMA IN COMPUTER SCIENCE

[MONTH, YEAR]
CERTIFICATION

This is to certify that the project titled “Project topic” has been supervised, read and
approved by the Department of Computer Science, Kogi State Polytechnic, Lokoja in partial
fulfillment of the requirements for the award of Higher National Diploma (HND) in
Computer Science.

____________________________ ______________________
[e.g. Dr. A. O. Ayodele] Date
Supervisor

____________________________ ______________________
Mrs. Oluwaseyi I.O. Date
Head of Department

____________________________ ______________________
Title, initials and Surname Date
External Examiner
TABLE OF CONTENT
TITLE PAGE i
CERTIFICATION ii
DEDICATION iii
ACKNOWLEDGEMENT iv
ABSTRACT v
TABLE OF CONTENT vi

CHAPTER ONE: INTRODUCTION


1.1 Background to the Study
1.2 Problem Statement
1.3 Aim and Objectives
1.4 Significance of the Study
1.5 Scope and Delimitation of the Study
1.6 Definition of Terms

CHAPTER TWO: LITERATURE REVIEW


2.1 Theoretical Framework
2.2 Review of Related work

CHAPTER THREE: SYSTEM ANALYSIS AND DESIGN


3.1. Introduction
3.2. Analysis of the existing system
3.3. Weakness of the existing system
3.4. Data collection techniques
3.5. Analysis of the proposed system
3.6. System Flowchart
3.7. Entity Relational Diagram / Data flow diagram (if applicable)
3.7.1. Data Dictionary (if applicable)
CHAPTER FOUR: SYSTEM IMPLEMENTATION AND EVALUATION
4.1. Program Development
4.2. System Requirement
4.2.1. Software Requirement
4.2.2 Hardware Requirement
4.3 System Interface
4.3.1. Input Interface
4.3.2. Output Interface
4.4. System Performance
4.5. System Training
4.6. Conversion to the Proposed System
4.7. System Maintenance

CHAPTER FIVE: SUMMARY, RECOMMENDATION AND CONCLUSION


5.1. Summary
5.2. Recommendation(s)
5.3. Conclusion
References
Appendices
PROJECT CONTENT

A. ABSTRACT
The abstract should encourage the reader to find out more, and has to identify the main
technical aspects and distinguishing characteristics of the project. The abstract should not
exceed 250 words. It should not be broken into paragraphs neither contain materials nor
references. Use single spacing. It should contain:
 Problem: What you discover to do, and why this needed a solution(motivation)
 Objectives: What you set out to achieve, and how this addressed the problem.
 Methodology: How you went about solving the problem.
 Achievements/findings: What you managed to achieve, and how far it meets your
objectives.

B. CHAPTER ONE
INTRODUCTION
1.1 BACKGROUND TO THE STUDY
The background information should indicate the root of the problem being studied, its scope
and the extent to which previous studies have successfully investigated the problem, noting in
particular, where gaps exist that your study attempts to address. Trace the history of the
subject of investigation (topic). Background to the study differs from literature review in that
it places the research problem in proper context rather than thoroughly examining pertinent
literature.
1.2 STATEMENT OF THE PROBLEM
It should include:
 ideal thing or what you discover that need tackling
 The trend in research i.e what is obtainable
 How you intend to solve the problem
1.3 AIM AND OBJECTIVES OF THE STUDY
The objectives of the study, covers the single aim for conducting the investigation and the
stated steps to achieve the aim.
1.4 SIGNIFICANCE OF THE STUDY
State the benefits of the research and to whom such expected benefits would be meant.
1.5 SCOPE AND DELIMITATION OF THE STUDY
The scope of the study refers to the extent of coverage of the subject matter being
investigated while delimitation of the study is concerned with what was not intended to be
included.
1.6 DEFINFITION OF OPERATIONAL TERMS
Define terms that are not familiar. Arrange the terms in alphabetical order.

C.CHAPTER TWO
LITERATURE REVIEW
The literature review should start with an overview showing the approach adopted in the
review and the need for it. This is usually followed by the body of the review. The review
must use clear, simple and courteous language, so that the import of the analysis is made
clear and past contributions to knowledge are acknowledge. The significance of the literature
review is to evaluate the current work with respect to the existing works. This chapter should
be devoted to a critical review of the technical and academic literature on previous works on
the project. This will provide the researcher an insight into the existing and up-to-date
information on the project on which he is working. Limit the scope of the review to the topic.
It should contain:
1. Overview/Theoretical frame work
2. Review of the relevant work by other authors.
3. Relationship between the relevant work and your own work.

Quotations from previous works must be included in quotations marks (““) and be cited by
reference to the bibliography at the end of your project report.

D. CHAPTER THREE
SYSTEM ANALYSIS AND DESIGN
3.1 Analysis of the existing system

Understand what the existing system is doing and describe the operation of the existing
(current) system.
3.2 Weakness of the existing system
Highlight the weakness of the existing (current) system.

3.3 Data collection techniques


Highlight the techniques employed in gathering data e.g. questionnaire observation,
interview, and so on.

3.4 Analysis of the proposed system


Decide on how the new system will function and describe how the proposed system
will operate.

3.5 System Flowchart

Show how information will flow in the proposed system using flowcharts.
3.6 Entity Relationship Diagram
The Entity Relationship Diagram (ERD) describes stored data of a system. Show the
database tables and indicate the relationship between the tables.

3.6.1 Data Dictionary


Data dictionary should provide simple explanation, the manner to record
process’s names and the storage manner. For example
List of Attributes Data type Description
Phone num Integer User’s phone number

E. CHAPTER FOUR
SYSTEM IMPLEMENTATION AND EVALUATION
4.1 Program Development
Describe how the program (code) for the proposed system will be developed and choice of
programming language.
4.2 System Requirement
4.2.1 Software Requirement
This should clearly state the operating system, the compiler, libraries etc necessary to run the
software.
4.2.2 Hardware Requirement
Highlight the equipment’s, CPU, RAM capacity, camera etc to run the software.
4.3 System Interface
4.3.1 Input Interface
Describe the interface(s) that accepts data into the program. Screen shots of input interface
can be in the appendix.
4.3.2 Output Interface
Describe the interface(s) that displays information to users. Screen shots of output interface
can be in the appendix
4.4System Performance
Analyze your system in term of throughput, speed, services and so on.
4.5 System Training.
Clearly state who should be trained and how they will be trained.
4.6 Conversion to the Proposed System
Describe how to convert from the existing system to the proposed system.
4.7 System Maintenance
How will the system be maintained? Who will maintain it?

F. CHAPTER FIVE
SUMMARY, RECOMMENDATION AND CONCLUSION
5.1 SUMMARY
Briefly summarize the project report content
5.2 RECOMMENDATION
This should address two things: firstly, new areas of investigation prompted by developments
in this project, and secondly parts of the current work which was not completed due to time
constraints and / or problems encountered.
The recommendations are expected to address salient issues which might have been raised in
the course of the investigation.
5.3 CONCLUSION
Conclusion should indicate the extent to which the objectives outlined in chapter I have been
met.

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