ABSTRACT
The work presents a design of a cashbook management system for IMT Enugu. A cashbook management for IMT Enugu is concerned with the computerization of cashbook records appraisal in order to achieve the aims and objective of the organization. The cashbook management system (CBMS) is a tool that will assist IMT administration in interpreting the financial outcomes of operational decision making. It will help administrators to decide whether their staff financial health is better or worse than during previous accounting period or past budget periods. The CBMS will also allow administrators to compare their operations with similar operations.
The cashbook normally will be a debit, credit and balance record. This record will be debited with remittances received and credited with revolving fund check downs.
The design was implemented to facilitate the cashbook management system for Institute of Management and Technology, IMT Enugu. It will be time conserving and cheap to run.
This project work was implemented with the help of visual basic programming language and Microsoft access. The Microsoft access is used to create the database for the effective storage of the cash record.
Dr. Mrs. Mercy and to my parents.
TABLE OF CONTENTS
page
TITLE PAGE -- -- -- -- -- -- i
CERTIFICATION -- -- - -- -- -- ii
DEDICATION -- -- -- ---- - - iii ACKNOWLEDGEMENT -- -- -- - -- iv
ABSTRACT -- - --- -- -- -- -- v
CHAPTER ONE
INTRODUCTION--- -- -- - -- - 1-6
1.1 Background of the study-- -- -- --
1.2 Statement of the problem-- -- -- -- 6-7
1.3 Purpose of the study-- -- - -- -- 7
1.4 Aims and objectives-- -- -- -- -- 8
1.5 Scope of the study-- -- -- -- -- 8
1.6 Limitations of the study-- -- -- -- 9
1.7 Assumptions-- -- -- -- - --- 9
1.8 Definition of terms -- -- -- -- -- 9-12
CHAPTER TWO
LITERATURE REVIEW-- -- -- -- -- -- 13-15
CHAPTER THREE
3.1 Description and analysis of existing system-- 15
3.2 Fact finding method used-- -- -- -- 16
3.3 Organization structure -- -- -- -- 16
3.4 Objectives of existing system-- -- -- 17
3.5 Input process and output analysis-- -- 17
3.6 Information flow diagrams-- -- -- -- 19
3.7 Problems of existing system- -- -- -- 20
3.8 Justification of the new system-- -- -- 20-21
CHAPTER FOUR
4.0 System design-- -- -- -- -- -- 22
4.1 Design of the new system-- -- -- - 22
4.2 Input specification and design-- -- -- 22
4.3 Output specification-- -- -- -- -- 22
4.4 File design-- -- -- -- -- -- 24
4.5 Procedure chart-- -- -- -- -- --
4.6 System flowchart--- -- -- -- -- 26
4.7 System requirements-- -- -- -- -- 27
CHAPTER FIVE
5.0 Implementation -- -- -- -- -- 28
5.1 Program design --- -- -- -- -- 28
5.2 Program flowchart-- -- -- -- -- 29
5.3 Pseudocode-- -- -- -- -- -- 30
5.4 Choice of program language-- - -- 32
5.5 Source program listing- -- -- -- -- 32
5.6 Test data-- -- -- -- -- -- -- 32
5.7 Sample report-- -- -- -- -- -- 32-33
CHAPTER SIX
6.0 Documentation-- -- -- -- -- -- 34
6.1 System documentation-- -- -- -- 34
6.2 Program documentation-- -- -- -- 34
6.3 User documentation-- -- -- -- -- 35
CHAPTER SEVEN
7.0 Recommendation and conclusion-- -- -- 36
7.1 Recommendation -- -- -- -- -- 36
7.2 Conclusion-- -- -- -- -- -- 36
REFERENCE-- -- -- -- -- -- 38