Project File Details


Download the complete Computer science topic and material (chapter 1-5) titled DESIGN AND IMPLEMENTATION OF COMPUTER BASED INVOICE GENERATING SYSTEM here on PROJECTS.ng. See below for the abstract, table of contents, list of figures, list of tables, list of appendices, list of abbreviations and chapter one. Click the DOWNLOAD NOW button to get the complete project work instantly.

 

3,000.00

Download the complete Computer science topic and material (chapter 1-5) titled DESIGN AND IMPLEMENTATION OF COMPUTER BASED INVOICE GENERATING SYSTEM here on PROJECTS.ng. See below for the abstract, table of contents, list of figures, list of tables, list of appendices, list of abbreviations and chapter one. Click the DOWNLOAD NOW button to get the complete project work instantly.

 

PROJECT TOPIC AND MATERIAL ON DESIGN AND IMPLEMENTATION OF COMPUTER BASED INVOICE GENERATING SYSTEM

The Project File Details

  • Name: DESIGN AND IMPLEMENTATION OF COMPUTER BASED INVOICE GENERATING SYSTEM
  • Type: PDF and MS Word (DOC)
  • Size: [890KB]
  • Length: [74] Pages

 

ABSTRACT

Design and implementation of computer based invoice generating system is one that generates a commercial recording document for both buyer and seller. It also identifies trading parties and list, describes and quantifies the items sold. Different record keeping systems has been practiced by different companies in this country Nigeria. This has resulted in not having a comprehensive data base for invoice recording. This has led to customers wasting a lot of time in an attempt to collect the manual invoice. Also there is poor accountability which has led to the embezzlement of fund. Design and implementation of computer based  invoice generating system is aimed at building a web database for storing and recording of goods sold with invoice id number, giving account of invoice generated within a specified period of time and helps to manage and record payment. The methodology used is UNIFIED MODELING LANGUAGE (UML). UML is a standardized modeling language enabling developers to specify, visualize, construct and document artifacts of the system. The researcher used this methodology in the design of the software and it was implemented using notepad++ on a Microsoft windows system using HTML codes, PHP, CSS, and MySQL language for the relational database. The result gotten from this project was a computer based invoice generating system whereby the users of the system have to create account before having access to use the system and admin is the only person that has the privilege to edit, delete an invoice that is discarded by a customer.

TABLE OF CONTENTS

Title Page                                                                                          I

Certification                                                                                                II

Approval Page                                                                                  III

Dedication Page                                                                                IV

Acknowledge Page                                                                            V

Abstract                                                                                            VI

Table of Contents                                                                             VII-VIII

List of Figures                                                                                   IX

List of Tables                                                                                    X

CHAPTER 1

  • Background of study 1

1.1     Statement of the problem                                                                  2

1.2     Objective of the study                                                             2

1.3     Significance of the study                                                                   2

CHAPTER 2

  • Introduction 4

2.1     Theoretical background                                                           4

2.2     Review of related literature                                                     7

2.3     Summary                                                                                 11

CHAPTER 3

3.0     Introduction                                                                                      12

3.1     Analysis of existing system                                                     16

3.2     Use case diagram                                                                     18

3.3     Analysis of proposed system                                                  21

3.4     Design of the proposed system                                                         21

3.4.1  Design of proposed system                                                     21

3.4.2  System architecture                                                                 25

3.4.3  Input design                                                                                      25

3.4.4  Output design                                                                          27

CHAPTER 4

4.0     Introduction                                                                                      28

4.1     Choice of development environment                                       28

4.2     Implementation Architecture                                                   31

4.3     Software Testing                                                                     32

4.3.1  Input Specification                                                                            33

4.3.2  Output Specification                                                               34

4.4     Documentation                                                                        35

4.4.1  User Manual                                                                            36

CHAPTER 5

5.0     Summary                                                                                 38

5.1     Conclusion                                                                              38

5.2     Recommendation                                                                     39

References                                                                                        40

Appendix                                                                                         42

  

 

LIST OF FIGURES

Fig 3.1 UML Class Diagram                                                             15

Fig 3.2 UML Activity Diagram                                                                  16

Fig 3.3 Sample of invoice Used during manual registration              17

Fig 3.4 Use case Diagram                                                                 19

Fig 3.5 Flow chart                                                                                      20

Fig 3.6 System Architecture                                                              25

Fig 3.7 Registration form                                                                           26

Fig 3.8 Screenshot of the invoice page                                                        27

Fig 4.1 Screenshot of Admin login page                                           29

Fig 4.2 Screenshot of Registration page                                            30

Fig 4.3 Implementation architecture                                                 31

Fig 4.4 Screenshot of the Input form                                                          33

Fig 4.5 Screenshot of the output form                                                        34

Fig 4.6 Screenshot of output specification of invoice generated                 35

 

 

LIST OF TABLES

Table 3.1 Aigs Reg Table                                                                  22

Table 3.1 Aigs Invoice Table                                                            22

 

CHAPTER ONE

INTRODUCTION

  • BACKGROUND OF STUDY

Record Keeping is the process of collecting, inputting, storing, classifying summarizing and interpreting data. Record keeping has two facets – financial record keeping and managerial record keeping such as date, address, number of goods purchased, unit price of goods, description of the goods, total amount of specified goods and ground total of all the goods (items) listed in the invoice. The basic purpose of financial record is to assist decision makers in evaluating the financial strength, profitability and future prospects of a business.

The purpose of financial record keeping is to produce financial statement about a business entity. Therefore, this study has been narrowed down to the record keeping system that has been practiced by different companies in Nigeria.

Automatic invoice generation system uses a sequential order of list of items that are entered in an invoice platform, to generate an invoice with items and its price per unit from the relational data base.The system automatically summarizes the listed items due for transactions in the ordered goods document and stores them in the invoice table.

But when invoice information is created manually, the system does not adhere to any sequence/summarization rules you have defined. Rather you manually control the sequence/summarization logic in the way you manually create the pay items.

  • STATEMENT OF THE PROBLEM
  1. Lack of comprehensive database for recording the invoicing,
  2. Time wasted when many customers are waiting to collect manual invoice,
  3. Manually written invoice are subjected to physical damage,
  4. Embezzlement of fund due to poor accountability.

 

  • AIM AND OBJECTIVES OF STUDY

The objectives include to develop a system that can:

  1. Store and record all the goods sold with an invoice id number.
  2. Manage and record payments.
  3. Provide a unique identification number.
  4. Give account of income generated within a specified period of time,
    • SIGNIFICANCE OF STUDY

With growth of information technology, the study offers numerous values in sales invoice recording system.

 

  1. Customers get good services, which include assurance of goods purchased: with this system the company knows that the customer can easy track them down if any of the goods sold to him/ her substandard goods or refurbished and with this the company will make it as a law to abide with the selling of original goods.
  2. It will provide efficient, effective and timely services: there is no much time wasted when someone is using this system to run his/her business.
  3. Corruption will be reduced: the apprentice hired to assist to attend to customers will not have access to the admin dashboard so that there won’t temper with the price of the goods sold.
  4. There will be no conflict between the company and the customers since terms and conditions are clearly stated.
  5. To make report and company audition easy and accountable: annual report writing will be easy since the system have a way of searching all the invoice produced with the customers’ business name and identification number of the invoice which make the invoice more authenticity in the labour market

 

GET THE FULL WORK