COMPUTERIZATION OF PHARMLIGHT HARDWARE SHOP

Pharmlight is a hardware shop introduced in the mid-month of January 2017 by a sole trader
named MrMabvuwe. This shop is located in Zvimba district stand number lancarec 43
marwederd at White House shopping center. Pharmlight hardware receives or gets an average
of 54 customers per day. It started on a small-scale production, supplying building materials
and other hardware equipment to the local people only covering a small proportion of the
market and mainly supplying the goods it produced. This shop is planning to expand in the
future so that it can be recognised countrywide. The shop has 5 employees who were only
employed since the shop was started. Including Mr Mabvuwe and the other 4 employees, are
his family members whom acts as thecashier, accountant, gender and supervisor. Due to the
large sum of paper work, the shop has runs out of space on keeping its records. This shop
mainly sells hardware equipment such building materials and other stuff. Mr Mabvuwe thought
of implementing a computerised based system which wouldsolve some of their problems.

INVESTIGATION OF THE CURRENT SYSTEM

RESEARCH INSTRUMENTS

RECORD INSPECTION

I visited the shop with the aim of inspecting their current records in a bid to carry out my fact-
finding process so as to evaluate whether it`s necessary to get a new system to replace the
existing system because the shop requires a new system which will help the workers and the
manager to operate efficiently and effectively.

OBSERVATION

I observed the shop and to see how the workers work throughout the day. There was a lot of
counter books on the store room. There were also a lot of clients standing to be saved.When
customers buys a lot of materials the cashier would find it hard to calculate fast since the
materials bought will have different cost and also to save a lot of customers waiting in the line.
On every sale they give their clients a receipt and they record on the books which is also quite
hard to record every transaction done in a single day.
 DATA ANALYSIS

Recording in the
Entering
books the goods
Supplier Purchasing products supplier’s details
purchased
in the books Supplier’s Books

Recording the book

Selling products Entering
Customer the products sold
customer’s Customer`s Books
details in the
books

Verification of
data entered
Checking to see if the
details entered are
correct

Counting of Stock’s book

stock to see if
the books are
correct

PROBLEMS OF THE CURRENT SYSTEM

  There is a lot of calculation error, for example a client can be charged a lot of money
when buying a lot of building equipment.
 It is time consuming when finding the important documents or records due large some
of paper work kept in the shop
 There is duplication of data which lead data redundancy as there is double entry of data
which might be contained in other files
 More space is required as it is being used up by the paper documents as there is need to
store the paper files.
 Stationery is now more expensive to buy for this shop since the record keeping books
required in large quantities

FEASIBILITY STUDY

SOCIAL FEASIBILITY STUDY

IT is socially feasible to computerize the existing system because the required system will solve
the problems encountered by the existing system so that it can cope up with the issues. The
system will not affect any of the workers because they all still have to play their roles in the new
system.

ECONOMIC FEASIBILITY STUDY

It is economically feasible because it needs less money to complete the required program for it
to be easy to work with. The system will save money because the system is cheap to buy and
install than keep on buying stationery every time.

OPERATIONAL FEASIBILITY
It is operationally feasible to computerize the system because data will not be lost and there
will be no data duplication (data integrity).There will be data security so that other people
cannot access the system files. It has better security to records and unauthorized access cannot
take place because of the password.

TECHNICAL FEASIBILITY STUDY

The new system is technical feasibility since the organisation can be able to purchase the
hardware requirements like printers, monitors, desktops /lap top and the organisation can also
be able to download software requirements on the internet

LEGAL FEASIBILITY STUDY

The new system is legal feasibility because it does not violet human rights it in accordance with
the laws outlined in the Data Protection Act.

REQUIREMENT SPECIFICATION
USER REQUIREMENTS
The user requires the system to add new records and remove unwanted records by deleting
them from the database. The user wants the system to be able to make calculations of change
and calculate value added tax. The system must be able to amend records when they are
wrongly entered. The user wants the system to be able to implement the use of access levels
when accessing the database and the use of usernames and passwords to protect data and
keep it secure. The system must be able to save and backup data

HARDWARE REQUIREMENTS
QWERTY keyboard-For entering details e.g. customer details, password

Mouse -Selecting and clicking options and buttons e.g. selecting and clicking the buttons after
amending data or after entering new data

LaserJet Printer -For printing receipts, quotations, report e.g. customer

Hard disk 240G -Storing files e.g. customer files and vehicle registration Files

Processor 2GHz Intel core -For processing data about customers and vehicles e.g. validating
records

SOFTWARE REQUIREMENTS
 Visual basic 2010: for designing and programming the system that will enable the
system to run and execute.
 Microsoft access 2013: for creating the database, queries and reports
 Microsoft Word 2013: for creating the documentation
 Microsoft windows 7, 8, 10 and the other latest versions which are 32bit OS orany
latest.
 Printing utility programs must also be installed for the System to print queries.

AIM AND OBJECTIVES

Aims
The aims of the new system are:
 To reduce the uses of paper work i.e. use of manual paper receipts and file to store data
for example customer records and reports.
 To be more efficient and essential
 To be user friendly.
 To stop records from getting lost.

Objectives
The objectives of the new system are:
 To be able to add, delete, amend, search, sort records in the system.
 To reduce and avoid the arithmetic errors made by the humans.
 To be able to sort data in the order that the user needs in a very short period of time
 To be able to automatically generate ad hoc reports for the user
 To be able to print out records in form of reports and queries.
 To ensure the security by use of usernames and passwords.

EVIDENCE FOR THE RESAERCH IS CARRIED OUT IN THE APPENDIX

SECTION B: DESIGN
CONSIDERATION OF ALTERNATIVES
ALTERNATIVES METHODS

OFF THE SHELF PACKAGE

 This is a system that exists, it has already been created. The system can be purchased
from the creator or manufactures.

Advantages
 It is cheap as it is mass produced so the cost is spread.
 There are few errors within the system since the developers test and justify the system.
 The system saves time since it is bought and installed, rather than waiting for
developments of the system.

Disadvantages
 It may not perfectly match to the manual system since the system can contain
additional features that cannot be used in Pharmlight Hardware.
 Users of the system at Pharmlight hardware can take a lot of time to adopt the system.
CUSTOMIZED PACKAGE
 Pharmlight Hardware can buy an of the shelf package and modify some parts of the
package adding orremoving some parts of the package which are not necessary for the
system making it suitable and compatible with the objectives of the system.

Advantages
 Unnecessary features can be removed or deleted making the package simpler and
suitable for the system.
 Customising a package is much easier and faster than starting a new project since some
codes have been already coded by the manufacturer.
 Errors are reduced as some tested modules in the original package are reused.
 This is much cheaper than hiring programmers to make a new package.

Disadvantages
 In buying the software to be customized will pay for more than they want as off the
shelf packages are usually integrated or general purpose.
 It is not always easy to maintain software written by another programmer since it has
many errors.

JUSTIFICATION OF THE CHOSEN METHOD

MICROSOFT VISUAL STUDIO

 The final choice I have made is to use purpose built software.

The software will be built using Microsoft Visual Studioand Microsoft Access.

 Visual basic will be used to create the interface whilst Microsoft access will be used to
create the database.
 I have chosen it because of its advantages as compared to other alternative solutions.

ADVANTAGES OF JUSTIFIED SOLUTION OVER OTHERS

 Visual basic is easy to debug and to test.
 The software developed is not machine dependent as the compiled code can be stored
on disk and run on any computer without considering make of the hardware.
  The programmers can come and make changes on the system when needed whereas
on off the shelf you have no specific person to ask on problems of the system.
 Visual basic is problem oriented which reduces time taken to know the features of the
package.The system is made for the specific use of the shop; there will be no extra
unwanted features.
 Pharmlight Hardware Shop pays for only what they want as it is tailor-made.
 Microsoft Access is easy to create relationships with the table, create queries and print
out reports.

INPUT DESIGN
SUPPLIER FORM

SALES FORM
STOCK FORM
CUSTOMER FORM
 DATA STRUCTURES/FILE DESIGN OR OBJECT ORIENTED

DATA STRUCTURES
SUPPLIER FORM
DATA DATA TYPE SIZE VALIDATION EXAMPLE
Supplier Id Text 2char Should have a letter and a number S2
Supplier name Text 5char Supplier names should not be numeric ClivetChikafu
supplier’s contacts number 9char Supplier contacts should only numeric 7734567856
values only
Company name Text 10char Should only contain text only not Rancho
numerical values
Product id number char Should only contain numerical values 2
only
Quantity number 2char Should only contain numerical value 23
only
Date of purchase Date and time 10char The date must be of the current years 23/07/2019
and the past not the future
Amount paid currency 2char Monetary should only be recorded $500
 CUSTOMER FORM
Data Data type Size Validation Example
Customer id Number char Only numerical values required 3
Customer name Text 5char Customer name should be in text Ryan chimbanje
Customer’s contacts Number 9char Numerical values is only required 786596394
Product id Number char Should only contain numerical values 1
only
Quantity Number 2char Should only contain numerical value 38
only
Date of sale Date and time 10char The date must be of the current
years and the past not the future

RELATIONSHIPS FORM
 OVERAL PLAN

PHARMLIGHT HARDWARE SHOP

SYSTEM

WELCOME FORM

PASSWORD

MAIN MENU

EXITING FORM

No Go to Menu
CUSTOMER DETAILS MANAGERIAL FORM
Yes
Go to PASSWORD
SALES SECTION
PASSWORD FORM

EXIT
MANAGER MENU

STOCK SECTION SUPPLIER SECTION CUSTOMER SECTION

OUTPUT DESIGN
SUPPLIER FORM
CUSTOMER FORM

SALES FORM
STOCK FORM
 INTERFACE DESIGN
This can be viewed from above forms and in the user documentation section

TEST STRATEGY/TEST PLAN

TEST PLAN

BLACK-BOX TESTING
Some errors cannot be found by the programmer therefore black-box testing will be used to
recognise errors in the system that cannot be found by programmer. During this testing the
actual code is not required to be known.

Justification of Black Box Testing

Black box testing strategy has been chosen over white box because of its advantages as
compared to white box testing strategy and other testing strategies which include the
following;

 Black box testing does not require knowledge of the code as needed to perform white
box testing, so any one can perform the testing to see if the system is working, this will
save time since there is time limit.
 Black box testing tests the functionality of the system not the structure of the system
 Ease to use Because the testers do not have to concern themselves with the inner
workings of an application, it is easier to create test cases by simply working through the
application, as would an end user i.e. the managers and sales reps.
SECTION C

TECHNICAL DOCUMENTATION
ALGORITHMS

PSEUDO CODES

PASSWORD FORM
Start

Select Option

If Option Selected Is Exit Then System Close

If Option Selected Is Enter Then

Enter Name And Password

If Password Is Incorrect Then

Display Message Box” Error & Access Denied”

Display Message Box “Exiting The System & Error”

Elseif Password Is Correct Then

Display Messagebox” Welcome & Name & Access Granted”

Display Main Menu Form

End
MAIN MENU
Start
Select Option
If Option Selected Is Sales Form Then Display Sales Form
If Option Selected Is Managerial Section Then Display Managerial Password
End

Managerial Password
Start

Select Option

If Option Selected Is Exit Then Display Main Menu Form

If Option Selected Is Enter The

Enter Name And Password

If Password Is Incorrect Then

Display Message Box” Error & Access Denied”

Display message box “goodbye”

Display Main Menu Form

Elseif Password Is Correct Then

Display Messagebox” Welcome & Name & Access Granted”

Display Manager Menu Form

End select

End

Manager Menu
Start
Select Option
If Option Selected Is Customer Section The Display Customer Form
If Option Selected Is Stock Section Then Display Stock Form
If Option Selected Is Supplier Section Then Display Supplier Form
If Option Selected Is Lock Then Display Managerial Password Form
If Option Selected Is Exit Then Display Password Form
End select
 End

Customer Form
Start
Select Option
If Selected Option Is Add Then Show Blank Customer Form
If Selected Option Is Delete Then Delete Current Record Of The Customer Form
If Selected Option Is Print Then Print Current Record In The Customer Form
If Selected Option Is Save Then Save Current Record In The Customer Form
If Selected Option Is Next Then Navigate To The Next Record In Customer Form
If Selected Option Is Previous Then Navigate To The Previous Record In Customer Form
If Selected Option Is Back Then Navigate To The Manager Menu Form

End Select
End

Supplier Form
Start
Select Option
If Selected Option Is Add Then Show Blank Supplier Form
If Selected Option Is Delete Then Delete Current Record Of The Supplier Form
If Selected Option Is Edit Then Edit Current Record In The Supplier Form
If Selected Option Is Save Then Save Current Record In The Supplier Form
If Selected Option Is Next Then Navigate To The Next Record In Supplier Form
If Selected Option Is Previous Then Navigate To The Previous Record In Supplier Form
If Selected Option Is Back Then Navigate To The Manager Menu Form
End Select
End

Stock Form
Start
Select Option
If Selected Option Is Add Then Show Blank Stock Form
If Selected Option Is Delete Then Delete Current Record Of The Stock Form
If Selected Option Is Print Then Print Current Record In The Stock Form
If Selected Option Is Save Then Save Current Record In The Stock Form
If Selected Option Is Next Then Navigate To The Next Record In Stock Form
If Selected Option Is Previous Then Navigate To The Previous Record In Stock Form
If Selected Option Is Back Then Navigate To The Manager Menu Form

End Select
End
 Sales Form
Start
Select Option
If Selected Option Is Add Then Show Blank Sales Form
If Selected Option Is Delete Then Delete Current Record Of The Sales Form
If Selected Option Is Print Then Print Current Record In The Sales Form
If Selected Option Is Save Then Save Current Record In The Sales Form
If Selected Option Is Next Then Navigate To The Next Record In Sales Form
If Selected Option Is Previous Then Navigate To The Previous Record In Sales Form
If Selected Option Is Back Then Navigate To The Main Menu Form
If Selected Option Is Total Price Then Calculate The Total Price In Sales Form
If Selected Option Is Change Then Calculate The Change Paid In Sales Form

End Select
End

FLOW CHARTS
CUSTOMER SECTION
 Start
Select From Options

ADD NEW No

Yes DELETE
No
BLANK FORM NEXT
Yes No
DELETE RECORD PREVIOUS
Yes No No
NEXT RECORD
SAVE
Yes
PREVIOUS RECORD PRINT No
Yes
BACK
SAVE RECORD Yes
PRINT RECORD
Yes

BACK

SUPPLIER SECTION
 Start
Select From Options

ADD NEW
No
DELETE
Yes No
NEXT
BLANK FORM
Yes No
PREVIOUS
DELETE RECORD
Yes No No
SAVE
NEXT RECORD
Yes
PRINT
PREVIOUS RECORD
No
Yes BACK

SAVE RECORD Yes

PRINT RECORD
Yes

BACK

STOCK SECTION
 Start
Select From Options

ADD NEW
No
DELETE
Yes No
NEXT
BLANK FORM
Yes No
PREVIOUS
DELETE RECORD
Yes No No
SAVE
NEXT RECORD
Yes
PRINT
PREVIOUS RECORD
No
Yes BACK

SAVE RECORD Yes

PRINT RECORD
Yes

BACK

Exit System:

Start

Select Exit

Return to password
Exit form No

Stop
Yes
Exit System
PROGRAMMING CODES
PASSWORD FORM
PublicClassForm1

PrivateSub Button1_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button1.Click
Dim password AsString
Dim username AsString
Dim COUNT AsInteger = 4

MessageBox.Show("Access Granted", "WELCOME "& TextBox1.Text)

TextBox2.Text = ""
MAIN_MENU.Show()

Me.Hide()
Else
MessageBox.Show("Access Denied", "Error")
MessageBox.Show("GOODBYE")
password = ""
Me.Close()
EndIf

EndSub

PrivateSub Button2_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button2.Click
Me.Close()
EndSub
EndClass

MAIN MENU FORM

PublicClassMAIN_MENU

PrivateSub Button1_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button1.Click
MANAGER_PASSWORD.Show()
Me.Hide()
EndSub

PrivateSub Button4_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button4.Click
SALES_SECTION.Show()
Me.Hide()
EndSub

PrivateSub Button5_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button5.Click
Form1.Show()
Me.Hide()
EndSub
EndClass
SALES SECTION
PublicClassSALES_SECTION

PrivateSubSALES_SECTIONBindingNavigatorSaveItem_Click(ByVal sender
AsSystem.Object, ByVal e AsSystem.EventArgs)
HandlesSALES_SECTIONBindingNavigatorSaveItem.Click
Me.Validate()
Me.SALES_SECTIONBindingSource.EndEdit()
Me.TableAdapterManager.UpdateAll(Me.PHARMLIGHT_HARDWAREDataSet)

EndSub

PrivateSubSALES_SECTION_Load(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) HandlesMyBase.Load
'TODO: This line of code loads data into the
'PHARMLIGHT_HARDWAREDataSet.SALES_SECTION' table. You can move, or remove it, as
needed.
Me.SALES_SECTIONTableAdapter.Fill(Me.PHARMLIGHT_HARDWAREDataSet.SALES_SECTION)

EndSub

PrivateSub Button8_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button8.Click
Me.Validate()
Me.SALES_SECTIONTableAdapter.Update(PHARMLIGHT_HARDWAREDataSet)
Me.SALES_SECTIONBindingSource.EndEdit()
EndSub

PrivateSub Button1_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button1.Click
SALES_SECTIONBindingSource.AddNew()
EndSub

PrivateSub Button2_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button2.Click
SALES_SECTIONBindingSource.RemoveCurrent()
EndSub

PrivateSub Button3_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button3.Click
SALES_SECTIONBindingSource.MoveNext()
EndSub

PrivateSub Button4_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button4.Click
SALES_SECTIONBindingSource.MovePrevious()
EndSub

PrivateSub Button5_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button5.Click
CHANGETextBox.Text = TOTAL_PRICETextBox.Text - AMOUNT_PAIDTextBox.Text
EndSub

PrivateSub Button6_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button6.Click
TOTAL_PRICETextBox.Text = QUANTITYTextBox.Text * PRICETextBox.Text
EndSub

PrivateSub Button7_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button7.Click
MAIN_MENU.Show()
Me.Hide()
EndSub

PrivateSub Button9_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button9.Click

EndSub

MANAGERIAL PASSWORD
PublicClassMANAGER_PASSWORD

PrivateSub Button1_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button1.Click
Dim password AsString
Dim username AsString
username = TextBox1.Text
password = TextBox2.Text
If username = TextBox1.Text And password = "ASTRO"Then
MessageBox.Show("Access Granted ", " WELCOME "& TextBox1.Text)
password = ""
MANAGER_MENU.Show()

Me.Hide()
Else
MessageBox.Show("Access Denied", "Error")
password = ""
MAIN_MENU.Show()
Me.Hide()

EndIf
EndSub

PrivateSub Button2_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button2.Click
MAIN_MENU.Show()
Me.Hide()
EndSub
EndClass

MANAGERIAL MENU
PublicClassMANAGER_MENU

PrivateSub Button4_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button4.Click
MANAGER_PASSWORD.Show()
Me.Hide()

EndSub
PrivateSub Button5_Click(ByVal sender AsSystem.Object, ByVal e
AsSystem.EventArgs) Handles Button5.Click
Form1.Show()
Me.Hide()
EndSub

PrivateSub Button1_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button1.Click
STOCK_SECTION.Show()
Me.Hide()
EndSub

PrivateSub Button2_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button2.Click
SUPPLIER_SECTION.Show()
Me.Hide()
EndSub

PrivateSub Button3_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button3.Click
CUSTOMER_SECTION.Show()
Me.Hide()
EndSub
EndClass

SUPPLIER SECTION
PublicClassSUPPLIER_SECTION

PrivateSubSUPPLIER_SECTIONBindingNavigatorSaveItem_Click(ByVal sender
AsSystem.Object, ByVal e AsSystem.EventArgs)
HandlesSUPPLIER_SECTIONBindingNavigatorSaveItem.Click
Me.Validate()
Me.SUPPLIER_SECTIONBindingSource.EndEdit()
Me.TableAdapterManager.UpdateAll(Me.PHARMLIGHT_HARDWAREDataSet)

EndSub

PrivateSubSUPPLIER_SECTION_Load(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) HandlesMyBase.Load
'TODO: This line of code loads data into the
'PHARMLIGHT_HARDWAREDataSet.SUPPLIER_SECTION' table. You can move, or remove it,
as needed.
Me.SUPPLIER_SECTIONTableAdapter.Fill(Me.PHARMLIGHT_HARDWAREDataSet.SUPPLIER_SECTI
ON)

EndSub

PrivateSub Button6_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button6.Click
Me.Validate()
Me.SUPPLIER_SECTIONBindingSource.EndEdit()
Me.SUPPLIER_SECTIONTableAdapter.Update(PHARMLIGHT_HARDWAREDataSet)
EndSub
PrivateSub Button1_Click(ByVal sender AsSystem.Object, ByVal e
AsSystem.EventArgs) Handles Button1.Click
SUPPLIER_SECTIONBindingSource.AddNew()
EndSub

PrivateSub Button2_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button2.Click
SUPPLIER_SECTIONBindingSource.RemoveCurrent()
EndSub

PrivateSub Button3_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button3.Click
SUPPLIER_SECTIONBindingSource.MoveNext()
EndSub

PrivateSub Button4_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button4.Click
SUPPLIER_SECTIONBindingSource.MovePrevious()
EndSub

PrivateSub Button7_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button7.Click
MANAGER_MENU.Show()
Me.Hide()
EndSub
EndClass
STOCK SECTION
PublicClassSTOCK_SECTION

PrivateSubSTOCK_SECTIONBindingNavigatorSaveItem_Click(ByVal sender
AsSystem.Object, ByVal e AsSystem.EventArgs)
HandlesSTOCK_SECTIONBindingNavigatorSaveItem.Click
Me.Validate()
Me.STOCK_SECTIONBindingSource.EndEdit()
Me.TableAdapterManager.UpdateAll(Me.PHARMLIGHT_HARDWAREDataSet)

EndSub

PrivateSubSTOCK_SECTION_Load(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) HandlesMyBase.Load
'TODO: This line of code loads data into the
'PHARMLIGHT_HARDWAREDataSet.STOCK_SECTION' table. You can move, or remove it, as
needed.
Me.STOCK_SECTIONTableAdapter.Fill(Me.PHARMLIGHT_HARDWAREDataSet.STOCK_SECTION)

EndSub

PrivateSub Button6_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button6.Click
Me.Validate()
Me.STOCK_SECTIONBindingSource.EndEdit()
Me.STOCK_SECTIONTableAdapter.Update(PHARMLIGHT_HARDWAREDataSet)
EndSub
PrivateSub Button4_Click(ByVal sender AsSystem.Object, ByVal e
AsSystem.EventArgs) Handles Button4.Click
STOCK_SECTIONBindingSource.MovePrevious()
EndSub

PrivateSub Button1_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button1.Click
STOCK_SECTIONBindingSource.AddNew()
EndSub

PrivateSub Button2_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button2.Click
STOCK_SECTIONBindingSource.RemoveCurrent()
EndSub

PrivateSub Button3_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button3.Click
STOCK_SECTIONBindingSource.MoveNext()
EndSub

PrivateSub Button7_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button7.Click
MANAGER_MENU.Show()
Me.Hide()
EndSub
EndClass
CUSTOMER SECTION
PublicClassCUSTOMER_SECTION

PrivateSubCUSTOMER_SECTIONBindingNavigatorSaveItem_Click(ByVal sender
AsSystem.Object, ByVal e AsSystem.EventArgs)
HandlesCUSTOMER_SECTIONBindingNavigatorSaveItem.Click
Me.Validate()
Me.CUSTOMER_SECTIONBindingSource.EndEdit()
Me.TableAdapterManager.UpdateAll(Me.PHARMLIGHT_HARDWAREDataSet)

EndSub

PrivateSubCUSTOMER_SECTION_Load(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) HandlesMyBase.Load
'TODO: This line of code loads data into the
'PHARMLIGHT_HARDWAREDataSet.CUSTOMER_SECTION' table. You can move, or remove it,
as needed.
Me.CUSTOMER_SECTIONTableAdapter.Fill(Me.PHARMLIGHT_HARDWAREDataSet.CUSTOMER_SECTI
ON)

EndSub

PrivateSub Button6_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button6.Click
Me.Validate()
Me.CUSTOMER_SECTIONBindingSource.EndEdit()
Me.CUSTOMER_SECTIONTableAdapter.Update(Me.PHARMLIGHT_HARDWAREDataSet)
EndSub
PrivateSub Button1_Click(ByVal sender AsSystem.Object, ByVal e
AsSystem.EventArgs) Handles Button1.Click
CUSTOMER_SECTIONBindingSource.AddNew()
EndSub

PrivateSub Button2_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button2.Click
CUSTOMER_SECTIONBindingSource.RemoveCurrent()
EndSub

PrivateSub Button3_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button3.Click
CUSTOMER_SECTIONBindingSource.MoveNext()
EndSub

PrivateSub Button4_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button4.Click
CUSTOMER_SECTIONBindingSource.MovePrevious()
EndSub

PrivateSub Button7_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button7.Click
MAIN_MENU.Show()
Me.Hide()

EndSub

PrivateSub Button5_Click(ByVal sender AsSystem.Object, ByVal e

AsSystem.EventArgs) Handles Button5.Click

EndSub
EndClass
USER DOCUMENTATION
Installations
Click the start button on task bar as shown below. (Click on start button and a pop up will appear)

Click file
explorer
Insert the CD with the package into your computer disk drive (CD/DVD ROM) and select the (CD/DVD)
drive icon, right click and click on open.

Copy the document on your laptop

After copying the package in the computer the install following the instructions provided
 STARTING THE SYSTEM
Click on the task bar the program called PHARMLIGHT HARDWARE and this form will display.

By clicking on the login

button you are given the
right to enter into the
system

By clicking on the login button the password form is displayed

 By entering the correct password a
message box is displayed. The user is also
given the access to enter in the program.

NAVIGATION OF THE SYSTEM

 This button gives the user to access to enter in the
manager section

The sales button allows the user to sell goods

to a customer by entering in the sales form

The lock button allows the user to lock the

system after use so that only authorised users
can get access
  Click on any form of your choice for example the supplier form
 Buttons will be there for you to do anything you want to do like
 Add new button is for adding new record/s.
 Save button is for saving the current record.
 Delete button is for deleting the current record.
 Next button is for moving to next record.
 Previous button is for moving to previous record.
 Print button is for printing to the current record.
 Back button is for returning to main menu.
 Exit button is for closing the whole system.
 If you click exit the following message will appear.

EXITING THE SYSTEM

To exit the system we use system exit button.On clicking the system exit button on the main menu a message
for you to confirm if you really want to exit the system, this form will appear on your screen.

If you select YES the message displayed above will appear as show, but if you select NO it will enable the
password form again.

SECTION D
TESTING AND EVALUATION
TEST PLAN

BLACK-BOX TESTING
Some errors cannot be found by the programmer therefore black-box testing will be used to recognise
errors in the system that cannot be found by programmer. During this testing the actual code is not
required to be known.

JUSTIFICATION OF BLACK BOX TESTING

Black box testing strategy has been chosen over white box because of its advantages as compared to
white box testing strategy and other testing strategies which include the following;
  Black box testing does not require knowledge of the code as needed to perform white box
testing, so any one can perform the testing to see if the system is working, this will save time
since there is time limit.
 Black box testing tests the functionality of the system not the structure of the system
 Ease to use Because the testers do not have to concern themselves with the inner workings of
an application, it is easier to create test cases by simply working through the application, as
would an end user i.e. the managers and sales reps.

TESTING FOR NORMAL DATA

FORM/FILE TEST FIELD TEST DATA EXPECTED RESULTS

CUSTOMER CUSTOMER ID 76544 ACCEPTED

FORM

CUSTOMER NAME NIGEL ACCEPTED

HANGAIKA

CUSTOMER’S 776654873 ACCEPTED

NUMBER

PRODUCT ID 2 ACCEPTED
QUANTITY 30 ACCEPTED
DATE OF SALE 17/09/2020 ACCEPTED

FORM/FILE TEST FIELD TEST DATA RESULTS

STOCK FORM PRODUCT ID 2 REJECTED
PRODUCT NAME PUTY REJECTED
QUANTITY 30000 REJECTED
SUPPLIER ID S2344 REJECTED
SUPPLIER’S 78790878 REJECTED
NUMBER
DATE OF 09/06/2019 REJECTED
PURCHASE
TESTING FOR ABNORMAL DATA
FORM/FILE TEST FIELD TEST DATA RESULTS
STOCK FORM PRODUCT ID FGFGH REJECTED
PRODUCT NAME PUTY38586 REJECTED
QUANTITY RJEDS REJECTED
SUPPLIER ID EJ REJN REJECTED
SUPPLIER’S 78790878FN REJECTED
NUMBER
DATE OF 99/78/2020 REJECTED
PURCHASE

FORM/FILE TEST FIELD TEST DATA EXPECTED RESULTS

CUSTOMER CUSTOMER ID HJNGHDF REJECTED

FORM

CUSTOMER NAME 439485923 REJECTED

CUSTOMER’S DJSK48658 REJECTED

NUMBER

PRODUCT ID F4 REJECTED
QUANTITY FMNDS REJECTED
DATE OF SALE 17/09/KDFJS REJECTED
TESTING FOR EXTREME DATA

THE AMOUNT ENTERED IS OUT OF

RANGE BUT ACCEPTABLE

FORM/FILE TEST FIELD TEST DATA RESULTS

STOCK FORM PRODUCT ID 245768 ACCEPTED
PRODUCT NAME PUTY86679 ACCEPTED
QUANTITY 4000000000 ACCEPTED
SUPPLIER ID S3454F65485 ACCEPTED
SUPPLIER’S 78790878876607 ACCEPTED
NUMBER
DATE OF 06/04/2030 ACCEPTED
PURCHASE

FORM/FILE TEST FIELD TEST DATA EXPECTED RESULTS

CUSTOMER CUSTOMER ID 76544457 ACCEPTED

FORM

CUSTOMER NAME NIGEL ACCEPTED

HANGAIKA #4

CUSTOMER’S 7766548739495 ACCEPTED

NUMBER

PRODUCT ID 2334 ACCEPTED

QUANTITY 30023456 ACCEPTED
DATE OF SALE 17/09/2040 ACCEPTED
SAMPLE RUNS
ERROR MESSAGES
 THE AMOUNT ENTERED WAS
OUT OF RANGE

BENEFITS
 The system is able to add, delete, search, print and modify records.
 The system has reduced paperwork for PHARMLIGHT HARDAWRE which led to less stationery
expenses.
 Privacy was improved for the data held by the company, this is made possible by use of
password and user name to gain access to data stored, and these passwords have different
access levels which restricts access to other forms to anyone without administrative powers in
the system of PHARMLIGHT HARDAWRE.
 The system was able to reduce errors made by humans for example, logic errors and
grammatical errors. This led to less mistakes in the organisation as the system is now used to do
most of the calculations i.e. sales revenue, expenses and change at the point of sale
 Data consistency was also a success for the new system as the whole system is now stored in a
linked database.

LIMITATIONS
 The system does not perform automatic stock control.
 The system does not automatically backup data.
 The system is not linked to a network.
 The system was not able to meet the objective of automatically keying in data by use of bar code
readers.
DUE TO HARDWARE AND TIME
The system due to factors like time and lack of some hardware resources was not able to complete
some of the specifications and some of what I as the analyst had in mind. The lack of hardware
resources as barcode readers and the other hardware needed to implement the use of swipe cards in
the library was a great limitation. The cost of some of the hardware resources was also a limitation to
the system developed. Time is one great limitation to the system developed as the time span given to
complete the system was not enough even thou I worked under pressure.

OPPORTUNITIES FOR FURTHER DEVELOPMENT

 The system may also be improved by use of bar code readers to automatically input information
about the hardware equipment into the system. This will improve on operational speed and
efficiency of the system.
 This was not done due to constraints on the hardware resources available at the school. This
improvement if possible should be done within the next year since the computers are dynamic.
 The system can be made such that customer’s information is automatically fed into the
database by use of a bank cards, this will improve on security and accuracy on keying in data.
This was also not done due to constraints on hardware available at the school.
 The system can be improved that the data entered by the sales person can be save but cannot
be edited and only the manager can edit the form.