TABLE OF CONTENTS

COVER PAGE i
TITLE PAGE ii
CERTIFICATION iii
APPROVAL iv
DEDICATION v
ACKNOWLEDGEMENTS vi
ABSTRACT vii
TABLE OF CONTENTS **
LIST OF TABLES (If any) **
LIST OF FIGURES (If Any) **
LIST OF PLATES (If Any) **
Plates are pictures which so many confuse as figures

CHAPTER ONE: INTRODUCTION 1

1.1 Background of the Study
1.2 Statement of the Problem
1.3 Aim and Objectives of the Study
1.4 Significance of the Study
1.5 Scope of the Study
1.6 Limitations of the Study
1.7 Definition of Terms
CHAPTER TWO: LITERATURE REVIEW
2.1 Theoretical Review
(The student can choose subsections/subtitles to suit the project/work in this section).
2.2 Review of Related Works
The student is expected to reviews works by other authors related to the project or
topic of discourse (at least ten (10) works or more)
2.3 Summary of Literature Review and Knowledge Gap
A summary of literature review and knowledge gap to show how your work is
different from the others reviewed in Section 2.2

CHAPTER THREE: METHODOLOGY AND SYSTEM ANALYSIS

(For a Project WITH a Case Study)

3.1 Methodology Adopted
3.2 The Organization and Its Environment
3.3 Organizational Structure of the case study (get the name of the case study)
3.4 Analysis of the Existing System
3.4.1 Data Flow of the Existing System
3.4.2 Weaknesses of the Existing System
3.5 Analysis of the Proposed System
3.5.1 Advantages of the Proposed System
3.6 High Level Model of the Proposed System

(For a Project WITHOUT a Case Study)

3.1 Methodology Adopted
3.2 Analysis of the Existing System
3.2.1 Data Flow of the Existing System
3.2.2 Weaknesses of the Existing System
3.3 Analysis of the Proposed System
3.3.1 Advantages of the Proposed System
3.4 High Level Model of the Proposed System
Note: Articulate all the materials/methods/tools/techniques used in achieving the aim and
objectives theoretically. There must be at least two methods/methodologies. One used
theoretically and the other used in the software design. The type of system will determine
the type of software methodology in the software design (OOHDM, SHDM, OOADM,
SSADM, Agile, etc.) employed. Each of these methodologies has accompanied components.
For example, for OOADM, some of the components are - Data Flow Diagram (DFD), use
case diagram. Interaction diagram, sequence diagram, activity diagram, collaboration
diagram, package diagram etc.- these should be presented to depict two or more processes in
the system developed.

CHAPTER FOUR: SYSTEM DESIGN AND IMPLEMENTATION

Note: Choose the sections that are applicable to your work.

4.1 Objectives of the Design

4.2 Control Centre/Main Menu
4.3 The Submenus/Subsystems
4.4 System Specifications (Choose specifications that are applicable to your work)
4.4.1 Database Development Tool (if any)
4.4.2 Database Design and Structure (if any)
4.4.3 Math Specification (if any)
4.4.4 Program Module Specification (if any)
4.4.5 Input/Output Format
4.4.6 Algorithm
4.4.7 Data Dictionary
4.5 System Flowchart (If any)
4.6 Object Diagrams (If any)
4.7 System Implementation
4.7.1 Proposed System Requirements
4.7.1.1 Hardware Requirements
4.7.1.2 Software Requirements
4.7.2 Program Development
4.7.2.1 Choice of Programming Environment
4.7.3 Training
4.7.4 Documentation
4.7.5 System Conversion
4.7.5.1 Changeover Procedures
4.7.5.2 Recommended Procedure

CHAPTER FIVE: SUMMARY, CONCLUSION AND RECOMMENDATION

5.1 Summary
5.2 Conclusion
5.3 Recommendation
5.3.1 Application Areas
5.3.2 Suggestion for Further Research

REFERENCES

Appendix A: Program Listings

Appendix B: Sample Outputs
Appendix C: Questionnaire (Where it is applicable)
Main Body of Documentation
CHAPTER ONE
INTRODUCTION

1.1 Background of the Study

1.2 Statement of the Problem
1.3 Aim and Objectives of the Study
1.4 Significance of the Study
1.5 Scope of the Study
1.6 Limitations of the Study
1.7 Definition of Terms
CHAPTER TWO
LITERATURE REVIEW

2.1 Theoretical Review

2.2 Review of Related Works
2.3 Summary of Literature Review and Knowledge Gap

CHAPTER THREE
METHODOLOGY AND SYSTEM ANALYSIS
(For a Project WITH a Case Study)
3.1 Methodology Adopted
3.2 The Organization and Its Environment
3.3 Organizational Structure of the case study (get the name of the case study)
3.4 Analysis of the Existing System
3.4.1 Data Flow of the Existing System
3.4.2 Weaknesses of the Existing System
3.5 Analysis of the Proposed System
3.5.1 Advantages of the Proposed System
3.6 High Level Model of the Proposed System

(For a Project WITHOUT a Case Study)

3.1 Methodology Adopted
3.2 Analysis of the Existing System
3.2.1 Data Flow of the Existing System
3.2.2 Weaknesses of the Existing System
3.3 Analysis of the Proposed System
3.3.1 Advantages of the Proposed System
3.4 High Level Model of the Proposed System

CHAPTER FOUR
SYSTEM DESIGN AND IMPLEMENTATION

4.1 Objectives of the Design

4.2 Control Centre/Main Menu
4.3 The Submenus/Subsystems
4.4 System Specifications
4.4.1 Database Development Tool (if any)
4.4.2 Database Design and Structure (if any)
4.4.3 Math Specification (if any)y)
4.4.4 Program Module Specification (if any)
4.4.5 Input/Output Format
4.4.6 Algorithm
4.4.7 Data Dictionary
4.5 System Flowchart (If any)
4.6 Object Diagrams (If any)
4.7 System Implementation
4.7.1 Proposed System Requirements
4.7.1.1 Hardware Requirements
4.7.1.2 Software Requirements
4.7.2 Program Development
4.7.2.1 Choice of Programming Environment
4.7.3 Training
4.7.4 Documentation
4.7.5 System Conversion
4.7.5.1 Changeover Procedures
4.7.5.2 Recommended Procedure

CHAPTER FIVE
SUMMARY, CONCLUSION AND RECOMMENDATION

5.1 Summary
5.2 Conclusion
5.3 Recommendation
5.3.1 Application Areas
5.3.2 Suggestion for Further Research
NOTE: All tables, figures and plates must be chapter compliant
While the caption (title) of tables is at the top of the table, captions (titles) of figures and
plates are at the bottom of them.

Plate 1.1: A legume plant showing the watermark on the leaf

(Example of a plate, 1.1 means the first plate in chapter one)

Figure 3.2: The Different Types of Stipules

(Example of a figure, 3.2 means the second figure in chapter three)

Table 2.4: Privileges of the Administrator

S/N Privileges Description
1 Create Account: This module enables the administrator create account for the
user, users and assign roles.
2 Block/Unblock This enables the administrator block any suspected account
Account: and unblock customers account.
(Example of a Table, 2.4 means the fourth table in chapter two)