0% found this document useful (0 votes)
7 views

DOCUMENTATION ACCOUNTING SYSTEMMM

The document outlines the development and analysis of the Wiltshire Accounting System, aimed at improving the management of school fee transactions at Wiltshire High. It includes sections on problem definition, existing system evaluation, design considerations, and testing plans, emphasizing the need for a more efficient and automated solution. The system aims to streamline record-keeping, reduce errors, and enhance data accessibility for better financial management.

Uploaded by

delroyrusike
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
7 views

DOCUMENTATION ACCOUNTING SYSTEMMM

The document outlines the development and analysis of the Wiltshire Accounting System, aimed at improving the management of school fee transactions at Wiltshire High. It includes sections on problem definition, existing system evaluation, design considerations, and testing plans, emphasizing the need for a more efficient and automated solution. The system aims to streamline record-keeping, reduce errors, and enhance data accessibility for better financial management.

Uploaded by

delroyrusike
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 46

0|Page

CANDIDATE NAME:
DELROY T. RUSIKE
CANDIDATE
NUMBER:3077
Wiltshire Accounting system CENTRE
NUMBER:030918
1|Page

TABLE OF CONTENTS
Section A: Selection, Investigation And Analysis.....................................................................2

Problem Definition/Choice of problem area and background analysis.....................................2

QUESTIONNAIRE For the Clerk..........................................................................................4

iii. Broad Description of the existing system......................................................................4

iv. Evaluation of existing solution......................................................................................5

V. Requirements specification...................................................................................................5

vii. Evidence of research............................................................................................................6

SECTION B:DESIGN...............................................................................................................7

i.CONSIDERATION OF ALTERNATIVE METHOD............................................................7

OF MANUAL RECORDING TRANSACTION OF THE FEES DATABASE.......................7

ii.Bespoke solution.....................................................................................................................8

iii> JUSTIFICATION OF METHODS OF SOLUTION...........................................................8

iv. INPUT DESIGN...................................................................................................................9

iii.Data capture form..................................................................................................................9

iv. OUTPUT DESIGN.............................................................................................................10

v. Test Plan...............................................................................................................................12

i.)TECHNICAL DOCUMENTATION....................................................................................14

ii. User Documentation............................................................................................................33

SECTION D: Testing and Evaluation......................................................................................39

i.USER TESTING....................................................................................................................39

ii.EVALLUATION OF THE SYSTEM..................................................................................41


2|Page

SECTION A: SELECTION, INVESTIGATION AND ANALYSIS

PROBLEM DEFINITION/CHOICE OF PROBLEM AREA AND BACKGROUND

ANALYSIS

Name of system: WILTHSIRE ACCOUNTING SYSTEM


Wiltshire accounting system is a system
established in terms of the Accounting acts. The
accounting system has prioritized the
enhancement of a good accounting system for
the school. The accounting system consists with
the transactions of the capital coming in in the
Wiltshire bank account. The physical location of
the accounting system is at Wiltshire High
located in Chivhu 40km away from Furtherstone.
The company comprises of six board members
and is having over 40-60 workers employed in
the same platform. It was founded by Mr
Munhangu the owner of the school in the year
2019 the accounting system was then
established. The system was introduced to
facilitate the transactions of the schools bank
accounting system, since many parents come
and pay school fees especially when schools are
re-opening. Too much labour is required in
recording transactions and carrying out
calculations and these problem started in 2017.
So the system was introduced to provide the
School with the records of the transactions that
comes in and out of the school. The recording of
information into the School account is done
automatically by use of computers.

Investigation of the current system


3|Page

1) Are you comfortable with the system?

----------------------------------------------------------------------------------------------------------------

---------------------------------------------------------------

2) How did you record your income statement account?

----------------------------------------------------------------------------------------------------------------

-------------------------------------------------------

3) Who is responsible for managing the system?

----------------------------------------------------------------------------------------------------------------

-----------------------------------------------

4) Who is in charge of the Fees department?

----------------------------------------------------------------------------------------------------------------

--------------------------------------------------

5) How reliable is the system?

----------------------------------------------------------------------------------------------------------------

--------------------------------------------------

6) Is it wise to use this system?

----------------------------------------------------------------------------------------------------------------

------------------------------------------------------

7) Are there any problems with the current system?

----------------------------------------------------------------------------------------------------------------

--------------------------------------------------------
4|Page

8) Is the system productive?

----------------------------------------------------------------------------------------------------------------

-------------------------------------------------------

QUESTIONNAIRE For the Clerk

Please kindly complete the questionnaire with the questions that follows. Information

should remain confidential and by doing so you should not write your name on the

questionnaire

Put a tick on the space provided

1) Does your system keep up with the current technology?

Yes No

2) Is it easy to retrieve your data?

Yes No

3) Are you comfortable with the system?

Yes No

4) Does it require a lot of time for workers to be trained?

Yes No

5) Is it easy to manage

Yes No
5|Page

iii. Broad Description of the existing system

INPUT

You will be entering data in the books of accounts

Record student details

PROCESSING

Performing calculations

Searching records

STORAGE

Storing in a flat file and box

OUTPUT

Producing receipts as a proof of payment

Producing daily reports

iv. Evaluation of existing solution

1. Weakness

 Data may be entered incorrectly

 It required more space to store the information

 Lot of errors can occur

 Data may be entered twice causing errors

 Loss of files

 Wrong calculations

2. STRENGTHS

 It provides adequate information

 Data that is kept is permanent

 It is easy to access the past transactions made


6|Page

V. REQUIREMENTS SPECIFICATION

Hardware requirements

Keyboard- for typing information

Monitor- for displaying information

Mouse-for selection

Printer cannon Desk Jet G2411-for printing

Software Requirements

Publisher

Microsoft Access

SMADAV antivirus

AIMS AND OBJECTIVES

 Aims

 to record and calculate transactions of the schools generated income

 To see past transactions

 To see if there’s a progress of profit or loss in the schools generated income

 To develop a system which enables the backing up of data

Objectives

 To Develop a system which records and keeps transactions in the system

 To develop a system which will be helpful for future use in terms of capital

 To eliminate unnecessary costs that is affecting the schools revenue

 To eliminate large numbers of stationery being used


7|Page

VII. EVIDENCE OF RESEARCH

see on appendix at the back

ISECTION B:DESIGN

I.CONSIDERATION OF ALTERNATIVE METHOD

OF MANUAL RECORDING TRANSACTION OF THE FEES DATABASE

This involves paying recording transactions of the fees paid in the database

ADVANTAGES

Paperwork is reduced

Information is made available quickly

Efficient backup is introduced

Training can be provided from the different providers of common software for free

Disadvantages
8|Page

It is hard for beginners

Some training may be requested which is expensive for the organization

It may contain errors

II.BESPOKE SOLUTION

It includes the hiring of expert accountants that suits the management for Wiltshire high

school

ADVANTAGES

Results in reduced duplication of effort

Paperwork is reduced since information is stored on the disk

Searching facilities are provided

Reports are easily available

DISADVANTAGES

High possibility of data loss

High chances of the system from suffering from bugs

It is expensive to develop own software

It may contain errors

III JUSTIFICATION OF METHODS OF SOLUTION


9|Page

Tailor made software is the type I will implement of the accounting system for

Wiltshire High the software will be using Microsoft excel and publisher to publish

their transactions this will be used to record transactions made in the school.

o The syntax of Microsoft excel is easier to understand and one can learn fast

o Tutorials are easy to find

Section A: Selection, Investigation And Analysis................................................................2


Problem Definition/Choice of problem area and background analysis........................................2
QUESTIONNAIRE For the Clerk................................................................................ 4
iii. Broad Description of the existing system..............................................................4
iv. Evaluation of existing solution........................................................................... 5
V. Requirements specification........................................................................................ 5
vii. Evidence of research............................................................................................... 6
ISECTION B:DESIGN................................................................................................. 7
i.CONSIDERATION OF ALTERNATIVE METHOD..........................................................7
OF MANUAL RECORDING TRANSACTION OF THE FEES DATABASE............................7
ii.Bespoke solution...................................................................................................... 8
iii JUSTIFICATION OF METHODS OF SOLUTION..........................................................8
iv. INPUT DESIGN..................................................................................................... 9
iii.Data capture form.................................................................................................... 9
iv. OUTPUT DESIGN –............................................................................................. 11
Screen Layouts.................................................................................................... 11
v. Test Plan............................................................................................................. 13
i.)TECHNICAL DOCUMENTATION...........................................................................15
ii. User Documentation............................................................................................... 34
SECTION D: Testing and Evaluation............................................................................. 40
i.USER TESTING..................................................................................................... 40
ii.EVALLUATION OF THE SYSTEM...........................................................................42
o Transactions are easily seen causing a budget for the school

IV. INPUT DESIGN

Below is the input form which is the accounting system form where transactions are

recorded and kept


10 | P a g e

III.DATA CAPTURE FORM

System name: WILTSHIRE ACCOUNTING MANAGEMENT SYSTEM

Designer Name: Delroy T. Rusike form name : Purchase ledger

PURCHASE LEDGER

SYSTEM NAME: WILTSHIRE HIGH ACCOUNTING SYSTEM

Designer name: Delroy Rusike ,Form Name : Sales Ledger


11 | P a g e

IV. OUTPUT DESIGN –

SCREEN LAYOUTS
12 | P a g e

OUTPUT FORM FOR ACCOUNTING SYSTEM

Below is output form that shows reports of the transactions made for Tinashe Kureva . some

of the information contains of the name and the surname and the grace period, date and debt

SALES LEDGER

Below is a sales ledger book which records the transactions made and keeps it in the system

this sales book is used for the income generation coming in from the schools fees paid in

the system

STATEMENT OF FINANCIAL POSITON

This day book reveals the transactions made day by day running costs of the business

expenditure which is capital expenditure


13 | P a g e

V. TEST PLAN

Black box

Black Box testing is whereby the system statement of financial position is regarded as a

black box and is tested according to its specification. No accounts are taken by the analyst of

how the program is written. Different values are to be tested including Standard

(typical/Normal) values, Extreme (borderline) values and values which are Abnormal (Not
14 | P a g e

acceptable). The reasons for use of the black-box testing are that the program is tested

according to its specifications and different values are entered for variables to determine

whether the program can cope with them.

Testing for standard (normal)data

For standard data testing, the data must be accepted and the examples of the data to be tested

will be as follows:

 THE Field Name “Grace Period” was tested for correct value in the Sales Ledger

i.e a value with four alpha-numeric characters. For example “19” which should be

accepted!

 The Field Name. ”Fees Database” was tested for correct value in the fees Database

with the correct range of date/time. For example “28/9/2024” which should be

rejected!

Testing for abnormal Data

 The field Name: ”Fees Debt” Was tested for abnormal data value in the Debt

file i.e a greater value than zero. For example “0.0043” which should be Rejected!
15 | P a g e

 The field Name: ”Grace period” was tested for abnormal data value in the Fees

Database File i.e a value with three alpha-numeric characters .For example:”100”

which should be rejected!

 The Field Name: ”Date” Was tested for abnormal data value in the date file i.e a

value with incorrect range of data/time for example “28/9/2024” which should be

rejected!

I.)TECHNICAL DOCUMENTATION

PSEUDOCODE OF THE Fees Database Module

Start

ENTER Name of Creditors

Enter Surname

Enter Date

Enter Debt

Enter Grace Period

End
16 | P a g e

Else

STOP

PSEUDOCODING OF THE Bad Debts Module

The Pseudo code below shows how the bad Debts are registered for the first time. It

shows the hierarchical stages in which the user must follow to enter the Bad debts

Information

START

Enter Name of Creditors


17 | P a g e

Enter Surname

Enter Date

Enter Debt

Enter Grace Period

End

ELSE

STOP

Flow Chart of The Fees Databse Module


18 | P a g e

Start

Name of
Creditors

Surname

Date

Debt

Grace
Period

AD
D
AE

Stop
19 | P a g e

Code Listing

Login Form Codes

Public Class login_form

Public Class login_form

Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click

If txtpassword.Text = "" And txtusername.Text = "" Then

MsgBox("welcome to Wiltshire High Accounting Management System")

Me.Hide()

main_menu.Show()
20 | P a g e

End If

End Sub

Private Sub txtpassword_TextChanged(sender As Object, e As EventArgs) Handles

txtpassword.TextChanged

End Sub

Private Sub txtusername_TextChanged(sender As Object, e As EventArgs) Handles

txtusername.TextChanged

End Sub

End Class

Main Menu Codes

Public Class main_menu

Private Sub Button5_Click(sender As Object, e As EventArgs) Handles Button5.Click

Me.Hide()

login_form.Show()

End Sub
21 | P a g e

Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click

Me.Hide()

income_statement.Show()

End Sub

Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click

Me.Hide()

stament_of_financial_positio.Show()

End Sub

Private Sub Button3_Click(sender As Object, e As EventArgs) Handles Button3.Click

Me.Hide()

purchases_ledger.Show()

End Sub

Private Sub Button4_Click(sender As Object, e As EventArgs) Handles Button4.Click

Me.Hide()

ledger.Show()
22 | P a g e

End Sub

Private Sub Button6_Click(sender As Object, e As EventArgs) Handles Button6.Click

Me.Close()

End Sub

Private Sub Button7_Click(sender As Object, e As EventArgs) Handles Button7.Click

Me.Hide()

fees_database.Show()

End Sub

Private Sub Button8_Click(sender As Object, e As EventArgs) Handles Button8.Click

Me.Hide()

bad_debts.Show()

End Sub

End Class

Statement of financial position codes

Public Class main_menu

Private Sub Button5_Click(sender As Object, e As EventArgs) Handles Button5.Click


23 | P a g e

Me.Hide()

login_form.Show()

End Sub

Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click

Me.Hide()

income_statement.Show()

End Sub

Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click

Me.Hide()

stament_of_financial_positio.Show()

End Sub

Private Sub Button3_Click(sender As Object, e As EventArgs) Handles Button3.Click

Me.Hide()

purchases_ledger.Show()

End Sub
24 | P a g e

Private Sub Button4_Click(sender As Object, e As EventArgs) Handles Button4.Click

Me.Hide()

ledger.Show()

End Sub

Private Sub Button6_Click(sender As Object, e As EventArgs) Handles Button6.Click

Me.Close()

End Sub

Private Sub Button7_Click(sender As Object, e As EventArgs) Handles Button7.Click

Me.Hide()

fees_database.Show()

End Sub

Private Sub Button8_Click(sender As Object, e As EventArgs) Handles Button8.Click

Me.Hide()

bad_debts.Show()

End Sub

End Class

Fees Database Codes


25 | P a g e

Public Class main_menu

Private Sub Button5_Click(sender As Object, e As EventArgs) Handles Button5.Click

Me.Hide()

login_form.Show()

End Sub

Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click

Me.Hide()

income_statement.Show()

End Sub

Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click

Me.Hide()

stament_of_financial_positio.Show()

End Sub

Private Sub Button3_Click(sender As Object, e As EventArgs) Handles Button3.Click

Me.Hide()
26 | P a g e

purchases_ledger.Show()

End Sub

Private Sub Button4_Click(sender As Object, e As EventArgs) Handles Button4.Click

Me.Hide()

ledger.Show()

End Sub

Private Sub Button6_Click(sender As Object, e As EventArgs) Handles Button6.Click

Me.Close()

End Sub

Private Sub Button7_Click(sender As Object, e As EventArgs) Handles Button7.Click

Me.Hide()

fees_database.Show()

End Sub

Private Sub Button8_Click(sender As Object, e As EventArgs) Handles Button8.Click

Me.Hide()

bad_debts.Show()
27 | P a g e

End Sub

End Class

Dad debts Database Codes

Public Class main_menu

Private Sub Button5_Click(sender As Object, e As EventArgs) Handles Button5.Click

Me.Hide()

login_form.Show()

End Sub

Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click

Me.Hide()

income_statement.Show()

End Sub

Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click

Me.Hide()

stament_of_financial_positio.Show()
28 | P a g e

End Sub

Private Sub Button3_Click(sender As Object, e As EventArgs) Handles Button3.Click

Me.Hide()

purchases_ledger.Show()

End Sub

Private Sub Button4_Click(sender As Object, e As EventArgs) Handles Button4.Click

Me.Hide()

ledger.Show()

End Sub

Private Sub Button6_Click(sender As Object, e As EventArgs) Handles Button6.Click

Me.Close()

End Sub

Private Sub Button7_Click(sender As Object, e As EventArgs) Handles Button7.Click

Me.Hide()

fees_database.Show()

End Sub
29 | P a g e

Private Sub Button8_Click(sender As Object, e As EventArgs) Handles Button8.Click

Me.Hide()

bad_debts.Show()

End Sub

End Class

Fees Database Codes

Public Class fees_database

Private Sub fees_database_Load(sender As Object, e As EventArgs) Handles

MyBase.Load

'TODO: This line of code loads data into the

'Accounting_sysystyemDataSet.bad_debts_form' table. You can move, or remove it, as

needed.

Me.Bad_debts_formTableAdapter.Fill(Me.Accounting_sysystyemDataSet.bad_debts_f

orm)

End Sub
30 | P a g e

Private Sub Bad_debts_formBindingNavigatorSaveItem_Click(sender As Object, e As

EventArgs) Handles Bad_debts_formBindingNavigatorSaveItem.Click

Me.Validate()

Me.Bad_debts_formBindingSource.EndEdit()

Me.TableAdapterManager.UpdateAll(Me.Accounting_sysystyemDataSet)

End Sub

Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click

Me.Bad_debts_formBindingSource.AddNew()

Me.TableAdapterManager.UpdateAll(Me.Accounting_sysystyemDataSet)

MsgBox("new record has been added to the datagridview")

End Sub

Private Sub Button5_Click(sender As Object, e As EventArgs) Handles Button5.Click

Me.Bad_debts_formBindingSource.RemoveCurrent()

Me.TableAdapterManager.UpdateAll(Me.Accounting_sysystyemDataSet)

MsgBox("record has been deleted to the datagridview")

End Sub
31 | P a g e

Private Sub Button4_Click(sender As Object, e As EventArgs) Handles Button4.Click

Me.Bad_debts_formBindingSource.MovePrevious()

Me.TableAdapterManager.UpdateAll(Me.Accounting_sysystyemDataSet)

End Sub

Private Sub Button3_Click(sender As Object, e As EventArgs) Handles Button3.Click

Me.Close()

End Sub

Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click

Me.Hide()

main_menu.Show()

End Sub

End Class

Sales Ledger Codes

Public Class main_menu

Private Sub Button5_Click(sender As Object, e As EventArgs) Handles Button5.Click


32 | P a g e

Me.Hide()

login_form.Show()

End Sub

Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click

Me.Hide()

income_statement.Show()

End Sub

Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click

Me.Hide()

stament_of_financial_positio.Show()

End Sub

Private Sub Button3_Click(sender As Object, e As EventArgs) Handles Button3.Click

Me.Hide()

purchases_ledger.Show()

End Sub
33 | P a g e

Private Sub Button4_Click(sender As Object, e As EventArgs) Handles Button4.Click

Me.Hide()

ledger.Show()

End Sub

Private Sub Button6_Click(sender As Object, e As EventArgs) Handles Button6.Click

Me.Close()

End Sub

Private Sub Button7_Click(sender As Object, e As EventArgs) Handles Button7.Click

Me.Hide()

fees_database.Show()

End Sub

Private Sub Button8_Click(sender As Object, e As EventArgs) Handles Button8.Click

Me.Hide()

bad_debts.Show()

End Sub

End Class
34 | P a g e

II. USER DOCUMENTATION

Installation

Open CD Drive, Click on the system setup. After this, check the existence Microsoft .Net

Framework 4.6 through following the steps below

Click Start then select Control panel form there click Uninstall Program- on the list of the

program check for Microsoft. Net Framework 4.6 If it does not exit then first download on

the Microsoft website. After that, you can now run the setup of the accounting system
35 | P a g e

Click here to install


36 | P a g e

Running the system

The user must open the system by running the application for flight reservation System

The log in form will be dispayed on the screen where he/she enters the user name and

password.
37 | P a g e

USERNAME PASSWORD

Delroy Teekay

After the user enters the password the main menu will appear

If the user clicks the fees database the following will appear
38 | P a g e

If the user clicks back it shows the following


39 | P a g e

NAVIGATION THE SYSTEM

Once the user logs in the system, main menu will be displayed where the user chooses what

to do in the system. The main menu of the system consists of forms that is income statement,

statement of financial position, the fees database, purchases ledger, sales ledger, bad debts

database that consists of choosing an account to transact money in

EXITING THE SYSTEM

On the main menu, the user can click EXIT, to completely exit the system, the user Must

click the button


40 | P a g e

Click here to exit

SECTION D: TESTING AND EVALUATION

I.USER TESTING

STANDARD DATA

It accepts data given in a certain range


41 | P a g e

ERROR MESSAGE

Its when the program/ system rejects

Error 1
42 | P a g e

II.EVALLUATION OF THE SYSTEM

ACHIEVEMENTS

 Development of a system that contains highly secured information

 Fast generations of reports

 Development of a system with proper backup measures

 Reducing working hours

 Fast in terms of recording the information Reduce the paperwork

 Easy to check for the spaces in the plane and the passenger information

 Provide accurate data and information

 Produce printed reports

 To reduce transactional errors


43 | P a g e

 To store data in a cloud computing method

 To ensure quick and reliable retrieval of data

 Show error message when involved or incorrect data is entered

 To have a good interface

 To enable fast data processing

WEAKNESSES

 The system might be expensive to install as they need to hire a system

analyst and set of programmers.

 The bursar needs training to be able to use the system therefore the school

will incur some costs

 The system may require frequent

 Current users might be dismissed due to lack of some skills and

qualifications

 Workers May resist the implementation of the system which leads to the

failure of computerization

 The system may not function well hence a cost to the organization

OPPORTUNITES FUTURE DEVELOPMENTS

 Linking the system with the bank account so that if a customer pays fees

directly in the fees bank account , it will no longer be necessary for the

learner to bring the bank slip to the accounting system because the bank

would have indicated that the customer have paid in the fees database
44 | P a g e

 The system will allow the customer to register their information through

online by entering their details

APPENDIX 1

Interview Guidelines

For The Manager

1) How long have you been working with the company?

ANSWER:

2) How many employees does the company have?

ANSWER:210

3) How long have you been using the current system?

ANSWER:5 YEARS

4) How many customers are served per day?

ANSWER: 140

5) Do customers raise any issues involving the existing system

ANSWER:YES its slow

B)For the clerk

1) Is the system reliable in keeping data?


45 | P a g e

Answer: Yes

2) How Efficient is the system you are using?

You might also like