Botswana Accountancy College

Computing and Information Systems

Bsc In Applied Business Computing Route Year 3

IProject 3

- Online Bill Payment System –- System Design -

ABC GROUP 4

Tumelo Maripe CIS09-227Mmoloki Kaisara CIS10-189

Itumeleng Mooki CIS11-216

3 Logical Model of the system – Proposed System

An Online Bill Payment System will be an integrated system in which customers will log into a web based system to pay their bills from various suppliers or service providers. It will consist of three servers. Customer’s details will not reside on which the online bill payment system will be resident. Bank Account details,Accounts numbers and Account Balances will reside in the online banking servers; Customer’s bills will reside on the service provider’s servers; Customer’s Login details will be stored on the online bill payment system. The figure below shows a component diagram for our Online Bill Payment System. It consists of three separate components. We may decide, for example, that the BankOnline component resides on the customer’s machine and the remaining components reside on the bank’s servers.

BillPaymentServer

BankOnline

BankServer

Figure 1.0

This system facilitates the customers because they do not have to go to the Service Providers to pay the bills. This system allow the customers to view the bills or pay bills, view transaction history regarding payments.

The goals of this system are:

1. To provide a anytime anyplace service for the customer.2. To promote non cash payments over the internet.3. To increase the profit.4. To minimize the number of staff servicing cash transactions at

the merchant’s premises.

The figure below shows an overview of the whole system.

Figure 2.0

3.0.1 Use Case Description for Customer Log In

Use Case Customer LoginBrief Description This use case allows the

Merchants / Administrator, Customers to sign on to the system.

Actors Administrator, Customer, Merchants / Supplier

Preconditions The Supplier may only sign on

from the administrator system. The Customer will sign on from the interface given by the system.

Main Flow The use case begins when the Supplier, Customer or Administrator need to sign on to the system.They will provide their username and password to the system.For customer that did not register yet, they will provide their username and password and do the registration.

Alternative Flow They enter invalid password.The system will inform about the error and asked to enter it again.

Post Conditions The use case was successful; they will proceed to next step.

3.0.2 Use Case Description for Customer Register

Use Case RegisterBrief Description This use case allows un

registered Customer and suppliers to register into the system

Actors Customer, Merchants / SupplierPreconditions The suppliers and customers may

only get access to the system after successfully registering their user names and passwords.

Main Flow The customers will be able to see a list of registered suppliers or service providers of which the customer will select the one he/she wants to pay.

Alternative Flow They will be notified if they are some errors with registration.

Post Conditions The use case was successful; they will proceed to next step.

3.0.3 Use Case Description for Show Supplier

Use Case Show SupplierBrief Description This use case allows Customer

to view a list of suppliers / service providers registered in the system

Actors Customer, Merchants / SupplierPreconditions The suppliers and customers may

only get access to the system after successfully registering their user names and passwords.

Main Flow The customers will be able to see a list of registered suppliers or service providers of which the customer will select the one he/she wants to pay.

Alternative Flow They will be notified if they are some errors with registration.

Post Conditions The use case was successful; they will proceed to next step.

The figure below show the sequence diagram for Show Supplier Use Case.

Customers / Suppliers

SignOnUI Sign ON Registration

Provide Username()

Provide Password()

Login

Verify Username

Verify Password

Verify Login

Login Accepted

Register()

Decept Registration

Figure 3.0

Sign On UI

-UsernameLabel: Label-PasswordLabel:Label-UsernameTextField:TextField-RegisterButton: ButtonLoginButton:Button

Sign On

-Username-password

-get Username()-get Password()

Supplier / Service Provider

-Supplier Name-Supplier Password

-get Supplier Username()-Get Supplier Password()

Customer

-custUsername-custPassword

Get Customer Username()Get Customer Password()

Class Diagram for User Sign On (Customer / Supplier)

Figure 4.0

3.1 System Architecture

Client layer(combining

presentation, business logic and

data access)

Presentation LayerBusiness Logic LayerData Access Layer

Relational Database

3.2 Interface Design

Interface for User Sign On:

The user who wants to sign on will notify the system whether he/she is a customer or Supplier by click on the radio button. They enter their username and password. Then they click on the Login button. For customer that has not register yet, they will click on the Register hyperlink to register.

Online Bill Payment System (OBPS)

Your Online Trusted Payment Portal

Customer Login

Login Register

Merchant Login

Interface for Customer Registration

Interface for Showing service providers:

The interface is shown after customer login to a list of Service Providers or suppliers registered into the system.

Online Bill Payment System (OBPS)

Your Online Trusted Payment Portal

Create Username and Password for Access to the system

Username:

Password: Retype Password:

Firstname: Lastname:

Address: City:

Email Address:

Submit

Online Bill Payment System (OBPS)

Your Online Trusted Payment Portal

Companies Datagrid View

No Name Address Location1 Botswana Power

CorporationBox 123 Gabs Bus Station

2 Water Utilities3 Mascom Wireless Tsholetsa House

Locate Bill