Description
ABSTRACTS
It is a well-established fact, that proper financial management and adequate planning is the bedrock of every successful organization. Reports generated from the accounts are among the major tools used by the management of any establishment for policy formulation, major decisions taking etc.
Account is the statement of money paid out or to be paid out by an organization, and the ones received or to be received.
Due to the trend towards automation in world order, more data and information are generated in lesser time and the processes and procedures of conducting business and keeping account becomes more complex and complicated. The manual form of keeping account become more tedious, inefficient and cost ineffective due to huge material and human resources required.
There is need for an alternative to manual processing of account, which will ensure security of data and account information, data validation and accuracy, efficiency in accounting system, prevent un-authorized manipulation of data etc.
This project work critically analyzed the processes and procedures of manual methods of account keeping and the case study “Grail Movement”, carefully designed new more efficient procedure, which was coded into intelligent software, using a programming language suitable for database management.
TABLE OF CONTENTS
Cover page
Title page
Certification
Dedication
Acknowledgement
Abstract
Table of content
CHAPTER ONE
1.0 INTRODUCTION
1.1 Statement of problem
1.2 Purpose of the study
1.3 Aims and objectives
1.4 Scope of the study
1.5 Limitation
1.6 Assumption
1.7 Definition of terms
CHAPTER TWO
2.0 LITERATURE REVIEW
CHAPTER THREE
3.0 DESCRIPTION AND ANALYSIS OF THE EXISTING SYSTEM
3.1 Facts finding method used
3.2 Organizational structure
3.3 Input, process, output analysis
3.4 Objective of the existing system
3.5 Information flow diagram
3.6 Problem of the existing system
3.7 Justification for the new system
CHAPTER FOUR
4.0 DESIGN OF THE NEW SYSTEM
4.1 Input specification and design
4.2 Output specification and design
4.3 File design
4.4 Procedure chart
4.5 System flow chart
4.6 System requirements
CHAPTER FIVE
5.0 IMPLEMENTATION
5.1 program design
5.2 Program flow chart
5.3 Pseudo codes
CHAPTER SIX
6.0 DOCUMENTATION
CHAPTER SEVEN
7.1 Recommendation
7.2 Conclusion
Reference