Design And Implementation Of Online Cash Receipt Generating System For A Supermarket

This research work on “Design And Implementation Of Online Cash Receipt Generating System For A Supermarket” is available in PDF/DOC. Click the below button to request or download the complete material

Abstract

This project work, is a computerization it cash receipt system of an organization. Different source of receipt whose scope and limitation are based on.
a. Sales and purchased receipts/ invoices inquiry on total balance and generation of report.
But before we venture into that, attention should be drawn to the introductory part, the literati on review, and later the analysis of the existing system, and the design of the new system.
Since there is constrain in time, this project will not go on exhaustive treatment of every expected module, module, rather will represent only sales and purchases receipts modules with two other operational modules subset of the broad menu.
Nevertheless, there is provision for onward development of those expected modules and for other source of receipts and other operations to suit any organization.
It is not the intention here to treat each module separately hence the entire project is menu driven to cover some of the facilities present.
Lastly, it is an optimistic fact that after going through the text, one would be able to.
1. Know what is achieved have a clear knowledge of the project have a clear knowledge of the project be able to in prove it to suit other organization in reaction to other source and problems.

Chapter One

INTRODUCTION
Cash receipt generating system is a viable source in any business organization and venture and so on, its main purpose is to maintain a more reliable records of money going out from the firm. This is look upon the view that the business organization most have business associates that exchange market with each other. It is a sure fact that the most have been a contract of which, there is an obligatory task that stands the terms of agreement, it could be a payment to their client or partners or from their client who pays into their own account. Another thing matters weather it will be cash without remark balance or install mental, and how many installment it is going to be.
This is clear stated in the organization activities and manner of operation. When ever there is payment, there is also the issuing of receipts this is centred on the writing of what each party has in stock.

1.1 JUSTIFICATION OF THE PROJECT
For there to be a computerized business operation, the business most be look upon in a new way of existence. No only being concerned with customers, prices output and so forth one should also consider the fact that data forms, information flows procedures etc. it is momentous on the basic that computers are used as a co-existing element to information system. This application is effective and productive because it enhance to process amore better information system.(Automated)
On this work, we shall basically look upon the possibility of making the outline orderly model of designing effect change. The process of changing system is systematic such that it is a repetition process. It is a fact to say that every system has what is called life cycle especially information system. By reviewing and modifying them, we say,

It is a system development cycle. The routine is always cyclical. It is on the system development that the familiar input processing output-feedback pattern of all system. The system development contains the output which consist of various organization information system. The feedback components help evaluate the effectiveness of the systems terms of changing requirements.

IN THE PROCESSING COMPONENTS WE HAVE THREE PARTS
System analysis
System design
System implementation.
None of these parts can be considered apart from the other two. To be courtesy, I would say that the activities involved in system development is interlinked set.

1.2 DEFINITION OF PURPOSE
The rate of accepting different sources of receipt by the topic of term paper into an organization, keeping track of the files can at any operates the organization and client’s financial report.

PROBLEM DEFINITION
Cash receipt system of Rorban Stores LTD. Is to keep records of all receipts of purchase and sales made.
By so doing, they keep information concerning each transaction such as the name of client, address, data of transaction, description of goods. Quantity of goods, model number of the goods, the amount of the goods.
Inside this record the company can the know the financial reports of both the client and the organization itself.

1.3 SCOPE (DELIMITATION) OF THE PROJECT
This terms paper is basically restricted to Rorban Stores LTD, as a case study for the term paper. Looking Rorban stores, the cash receipts system is restricted only to the.

1. Purchase receipts and/or invoice
2. Sales receipts and/or invoice

Other organization may run a different receipts system. At this term paper we shall base only on sales and purchases.

SCOPE OF PURCHASES
Out of this interview with the accountant and sales manager of Rarban stores LTD, I discovered that the organization do not keep any record on credits when purchases are made. Therefore the term paper nullifies the idea of computing credit in the purchase.
It will be right to say that Rorban stores do not go into purchasing on credit to avoid keeping much records that most often conflict matters.

SCOPE OF SALES
There is a particular sales file for all buyers and dealers (companies that buy from them) that buy on cash. It also maintain a separate buyer’ sales creditors files, and a separate buyers sales debtors files, that is kept by the company.
Therefore the term paper is basically on the above mention area as in sales. By this the company maintains one purchase data base file and three sales data base files, a total of four data base files.

Table of Contents

Title Page
Dedication
Acknowledgement
Abstract
Table of content

CHAPTER ONE
INTRODUCTION
Statement of the problem
Purpose of the study
Aim and Objectives
Scope Delimitation

CHAPTER TWO
LITERATURE REVIEW

CHAPTER THREE
DESCRIPTION AND ANALYSIS OF THE EXISTING SYSTEM
Fact finding method used
Objective of the existing system
Input, Process, Output analysis
Problem of the existing system
Justification of the new existing system

CHAPTER FOUR
DESIGN OF THE NEW SYSTEM
Output specification and design
Input specification and design
File design
Procedure chart
Expected Benefits Of The New System

CHAPTER FIVE
IMPLEMENTATION
Introduction

CHAPTER SIX
DOCUMENTATION
Constraint (Limitation)

CHAPTER SEVEN
Recommendation And Conclusion
Reference
Appendix
Program Coding