CHAPTER ONE: INTRODUCTION

Chapter one should consist of the following sections

1.0 Introduction:
Introduction of the project area How it operates and how the problem exists
1.1 Background of the Study
 This is usually detailed background information about the project/ research area and about the client.
 It should be clear on what business the client is involved in and how operations are currently conducted.
1.2.1 Background:
 Give a background of the organization i.e. when it was started, reasons for starting, where it is located, how
it started (history) and its growth for it to require a system.
 Include organizational chart
1.2.2 Overview of existing system:
 Discuss how the existing system operates outlining all the procedures which have to be followed.
 This section presents and summarizes the problem you intend to solve and your solution to that problem.
 Clearly support your statement with documentation and references, and include a review of the literature that supports
the need for the study
 Outline the problems / disadvantages in existing system.
1.2.3 Overview of the New system:
 Discuss how the New system will operate
 How the system work outlining all the procedures which have to be followed.
 This section presents and Summarizes the benefits of the New system.
Problem Statement(s)
 This is a statement of the problem the project is intended to address.
 It should clearly show the problem in the light of the project research and its contribution to the solution.
 Ideally it should originate from the way the organization currently performs its functions.
 Each problem should be stated clearly with a brief explanation on how it arises from the functions be undertaken.
 Indicate what you're going to solve.
1.3 Objectives: -
Clear, concise "SMART" objectives should be provided including project/ research and system development related objectives.
(S- Specific, M Measurable, A bound/boxed.-Achievable, R- Realistic/Relevant, T- Time )
e.g. To activate the booking and reservation
1.4 The supervisor should guide the student on the minimum and maximum number of objectives
as per his/her project.
Key words like Investigate, develop and analyze should be used to list objectives
1.4.1 Project Goal (Major Objective)
Overall Goal: This gives us an overall picture of what your project seeks to address. A
statement that will address the solution of the problem statement
1.4.2 General Objectives
Gives the general objectives of the proposed system citing the section to cover in the project
documentation
1.4.3 Specific Objectives
Give the specific objectives of the proposed system i.e what you want your system to
achieve in terms of functionality.
Research Questions
 Gives a set of question the study seeks to answer.
 The questions should not be too many and should be answered by the objectives
of the study
Justification
 Student should justify their project by indicating the interestingness and
challenge that the project presents, the timeliness of the idea, the possible advantages
that realization System of such a project would bring.
  Describe the value the proposed system will add stating the beneficiaries and
how they will benefit from the system. Show clearly the need for the system and
how it will address the existing challenges in the domain area.
 Note: Advantages of the new system as opposed to the new system

1.6 Scope of the Study

 A brief description of the project scope - what will be covered and what will not and
why?
 Define the scope of the proposed system and ensure it is not too wide or too
narrow. The scope should be practical and achievable within the set timelines.
 The scope should be part of the departments in the organizational structure and
achievable within the set timelines e.g. Registration dept and Finance dept.
1.7 Limitations of the proposed system
These are the constraints that may hinder you from achieving the objectives of the proposed
system within the stipulated time in the project schedule. E.g. Lack of finances, time constraints,
lack of programming knowledge etc
1.8 Project Risk and Mitigation vins attack-
This section should contain a list of project risks and the mitigations to these risks.
 How you're going to solve problem.
 System failure

1.9 Project Schedule
 A brief description of the project work breaks down structure.
 Project Gantt and Network diagram clear showing the Critical path should be included in
the appendix section.
 This can be showed on a gantt chart where you are to give an overview of when you are
to carry out the specific steps in your project from the ideation of the project to final
writing of your final report. (Shown in the Appendix)
1.10 Budget and Resources
 This should generally address all the envisaged resources that will enable the
development of the system to succeed.
 The key items are hardware, software, human and any other costs that will be
incurred.

CHAPTER TWO: LITERATURE REVIEW

 This consists of what has been done in the area of study; related work to your
study and why you are not adopting or accepting their results for your study.
 Students are advised to use papers that are peer reviewed as they have
validated solutions. Google Scholar is a valuable tool where you can get up to
date works from different scholars.
 There should be in a chronological order and should not span more than 3 years
(latest research). What the researcher intends to do to bridge the gap.
 The literature review should not be just a compilation or reproduction of the
works of others. It requires the student to examine and comment critically on the
literature relevant to the student's project area or area of research.
2.1 Reviewed Similar Systems
Highlight the loopholes of gaps"
Identify similar systems that have been developed to address similar problems
2.2 Tools and Methodologies used in Reviewed Systems
Discuss the tools and methodologies of the reviewed systems stating the advantages and
disadvantages of each.

2.3. Gaps in the existing systems and the proposed solution

Identify the gaps and problems of the reviewed systems.
2.4. The proposed solution
Explain how the proposed solution is going to address the problems of the reviewed
systems and bridge the Gap.

CHAPTER THREE
The methodology chapter should describe a model/framework under which the system will be
developed. It should address at least the following areas:-
 Tools to implement and test the system
 Time schedule and project cost
 State the reasons for choosing the methodology.
 Describe the tools that will be used in the methodology –Entity relations, flowcharts, DFD etc
 The exact techniques used to collect facts and data - Interviews; Observation.
 Tools used to analyze the data and the processes

This is a work plan that explores your research questions, the methods to be used, the
population samples, experimental and control groups, the data collection techniques and
statistical analysis.
This section of the proposal should explain the details of the proposed plan. Be specific on what
you will be doing. The reasoning behind this research opportunity is to make sure that you have
a meaningful experience.
Describe the possible forms of the final product, contribution e.g., publishable manuscript,
conference paper, innovation, system, simulation etc. Be specific about how you intend to share
your results or project with others and the value it will add.
This section may also include an interpretation and explanation of results as related to your
question; a discussion on or suggestions for further work that may help address the problem
you are trying to solve; an analysis of the expected impact of the scholarly or creative work on
the audience; or a discussion on any problems that could hinder your creative endeavor.
3.1 Methodology
Describe the methodology used showing clearly all the phases. E.g. Evolutionary, waterfall,
SSADM
3.2 Source of data:
Primary and secondary
3.3 Data Gathering:
3.3.1 Describe Methods of data collection.
3.3.2 Data collection tools - Use the tool such as interview, questionnaire, record /
document etc to form documents to collect data
3.4 Resources required / materials

3.4.1 Hardware and Software specification

Hardware Specifications
The servers to host the application, Memory requirements, Processor speed, Hard disk
capacity
Software Specifications: Operating system to be used and antivirus, if any.
3.5 Fact Recording:
Program Requirement - input requirements, output requirements, process requirements,
file requirements, system requirements, personnel requirements

CHAPTER FOUR:
SYSTEM ANALYSIS AND REQUIREMENT MODELING, SYSTEM DESIGN
(FINDINGS, DATA ANALYSIS& DESIGN)
The chapter should address at least the following areas:-
• Description on how the current system works using system analysis modelling tools such as
flow charts, DFDs, Use cases, UML etc.
• How the facts and the data gathered including the methods used
• Requirement definitions and modelling of the current system and proposed system
• Requirement definitions and specifications of the project
4.1 Introduction
4.2 Objective
4.3 Feasibility Study
Give the different types of feasibility study that will be carried out e.g. technical, economical
operational and schedule feasibility.
Give a feasibility report to show that the project is feasible according to the feasibilities carried
above.
4.4. System analysis design tools
Discuss the design tools that will be used in the proposed system. E.g. DFDs, ELH, Context
Diagrams, Data flow diagram. These tools should be the ones within the methodology.
4.5 System investigation
Introduction
Data collection
These are the methods used to collect data during the feasibility study. They include
interviews, questionnaires, Observation and record inspection.
Fact Recording
Entities
Student
Introduction
Program requirements: Requirement definitions and specifications of the project
Entails the following;
i) Input requirement :give the entities, details, method of input and device used.
E.g
CHAPTER 5
SYSTEM DESIGN
This section should consist of a description of the system design, database design (conceptual,
logical and physical) using an appropriate modelling tool.
5.1 Introduction
5.2 Objectives
5.3 Program Design Tools
Discuss the design tools that will be used in the proposed system. E.g. ERDs, ELH, data dictionary, Algorithms - Pseudo codes,
flowcharts. These tools should be the ones within the methodology.
5.4 Logical Design
5.4.1 Logical Data Design: - Relational Data Analysis / Normalization to generate tables
5.4.2. Entity Attributes Relationships - For all tables
5.4.3 Entity Life History
5.5 Physical Design Description
5.5. 1 Data Dictionary
5.5.2 File/Database Design - For All Tables
5.5.3 Input Screen Design - For All Table Entries
5.5.4 Output Screen Design - For All Reports
5.5.5 Code Design - For All Record Keys
5.5.6 Block Diagram/Structured/Modular Chart - Hierarchical Chart Of Modules Or Activities
5.5.7 Process / Program Design / UML
5.5.8 System Flowchart - For Entire Project
5.5.9 Program Flowchart - Integrate All Modules
5.5.10 Modular Program Flowchart (Represent All Your Procedures / Each Module)
Should include a minimum of 10 Modular Program Flowchart represent various function/modules in the program