BACHELOR OF SCIENCE IN INFORMATION

TECHNOLOGY.

PROJECT: BIT 3205A

AN ON DEMAND SERVICES WEB APPLICATION

FOR HOUSEHOLDS

SYSTEM DESIGN SPECIFICATION

MOSES KORIR

17/04006

0741836118

1
TABLE OF CONTENTS

5.1. INTRODUCTION…………………………………………………………………..…………….3

5.2. SYSTEM OVERVIEW……………………………………………………………..…….………3

5.3 SYSTEM ARCHITECTURE……………………………………………………….……..………… 4

5.4 PROGRAM DESIGN………………………………………………………..…………………………7-13

5.5 BUSINESS PROCESSES……………………………………………………………………………..14

5.6 DATABASE DESIGN…………………………………………………………….……………………16-17

5.7 USER INTERFACE DESIGN…………………………………………………..……………………19-21

5.8 REFERENCES………………………………………………………….………………………………..22

2
 CHAPTER FIVE

SYSTEM DESIGN SPECIFICATION

5.1. INTRODUCTION

This document describes how the house hold web application will be designed and also
how it functions. It defines the architecture modules, Interfaces and data for the
system to satisfy the required specification.
5.2. SYSTEM OVERVIEW

It encompasses the base outline design of the house hold web application and the features
identified in the system requirements specification document. This document entails the
purpose of the system, the intended audience and reading suggestion. It will use the Data Flow
diagrams to show the interaction between different objects and how data is used by the system.

5.2.1. Level o-data flow diagram

It shows a single process that illustrate and describe the entire system.

Household owner
(customer) Administrator

House hold web

application

Service provider Database

3
The system constitute of the web application, database, administrator, service provider and the
customer who is the household owner.

5.2.2. Level one Data flow diagram

It reveals the general process and data stores.

4
l Admin sign in 1 Google ac details D1 Ggl ac
Admin
Sign in with google
account

Customer sign in D2Houseowner

2

Customer Validate sign in details of

(household the admin and customer
owner) Admin can add/remove service providers

Customer checks the service providers available

Add/remove service providers

3

Check service providers

available
Addition/removal of service providers

Select appropriate service

provider
Selection of the service provider

D3 Service provider details

Generates report from db

Generate report

5
 5.3 SYSTEM ARCHITECTURE

It is a conceptual representation of the components that reflects the behavior of a system and
how it is structured. The web browser makes request to the server. The information is processed
and the results are sent back to the client web browser. The web browser serves the files from
the web pages to users in response to their requests. The server will be the intermediary
between the client’s side and the database. The client may use the desktop, computer or a
mobile phone to access the system.

The diagrammatic representation of the system;

6
5.4 PROGRAM DESIGN

Program design is a process that transform user requirement into some suitable form, which
helps the developer when writing the source code. I will use flowcharts and pseudocode to
illustrate the different modules of the library system. A flowchart is a diagrammatic
representation of an algorithm, a step-by-step approach to solving a task while pseudocode is a
methodology that allows the programmer to implement the implementation of the algorithm.

a. Sign in flowchart

START

Input username
and password

No
Is username and
password
correct?

Yes

Display the home page

STOP
 a. sign in pseudocode
1. START
2. Enter username and password eg. gmail and password
3. IF username and password is correct
3.1 Display home page

4. ELSE

4.1 Display invalid username and password

5. STOP

b. Update sign in credentials flowchart

START

Input current username

and password

NO
Validate current Invalid username and
username and password
password
YES

Update user name,

password and profile

8
STOP
b. pseudocode for updating sign in credentials
1. START
2. Input current username and password
3. IF username and password is valid
3.1 Update username and password
3.2 Update profile information
4. ELSE
4.1 Display invalid username and password
5. STOP

c. Add or delete service providers flowchart(Admin)

START

Click update or delete

service providers button
(Admin)

NO
Is the
service
provider
available?

YES

Delete the service provider Add the service provider

c. Add or delete service provider’s pseudocode (Admin)

STOP 9
 1. START
2. Click add or delete service providers
3. IF
3.1 Service provider is available
3.1.1 Delete the service provider
4. ELSE
4.1 Add the service provider
5. STOP

d. Check service providers flowchart

START

Click the “check service

provider’s button”

Display the service

providers available

STOP

10
 d. Pseudocode for checking the service providers available
1. START
2. Click the check service providers button
3. Display the service providers available
4. STOP

e. Pseudocode for selecting service providers

1. START
2. Click the service provider needed
3. View the qualifications of the service provider
4. IF customer is interested
4.1 Select the one
4.2 Generate report
5. ELSE
5.1 Choose another service provider
6. STOP

e. Flowchart for selecting the service providers

11
START
 Search or click the specific
service provider needed

View the qualifications for

the service provider chosen

Did the NO
customer found Choose another
or interested?

YES

Choose the appropriate one

Generate report

f. Sign out pseudocode

STOP
1. START

12
 2. Click setting icon
3. Select sign out
4. Confirm sign out option
g. Sign out flowchart

START

Click setting icon

Select sign out options

Confirm sign out options

5.5 BUSINESS PROCESSES

STOP

13
It defines how the system operates and works. I will use a flow chart to illustrate how the web
application will be functioning.

14
15
5.6 DATABASE DESIGN

A database is a structured organization of data stored in such a way that there is minimum
duplication of data to provide consistency of the data and provide access for many users.

The Database will store all the systems data, where all the tables will be linked together. This
ensures there is no repetition of attributes in the database unless it’s a foreign key for
relationships purposes.

The web application will use MySQL database to store the information about the system. It will
have four tables;

-Admin table which stores the administrator details.

-Customer table which stores the details about the customer

-Service provider table stores the details of the individuals that provides the services to the
customers.

-Selection table stores the items that the customer has selected.

5.6.1 Conceptual and logical design

Defines how data is organized and how the relations among them are associated.

16
 House hold web
application

User ID

Username

Customer Selected item Service provider Admin

(Owner of the
household) Selected item Service provider Pin
ID ID
Customer ID
Admin ID
Username Username
Username
Address
Date Category
Password

17
 5.6.2 Physical design

Normalization

Normalization is a logical process that structures a relational database in order to reduce data
redundancy and improve data integrity.

UNF 1NF 2NF 3NF

Customer ID Customer ID Customer ID(PK) Customer ID(PK)
Username Selected item ID Username Username
Password Service provider ID Password Password
Address Admin ID Address Address
Selected item ID Username Selected item ID(PK) Selected item ID(PK)
Date Password Date Date
Service provider ID Address Experience Experience
Experience Date Cost Cost
Price Experience Service provider Service provider ID(FK)
description
Password Price Service provider ID(PK) Service provider ID(PK)
Address Password Category Category
Admin ID Category Experience Experience
Service provider Address Password Password
description
Category Service provider Admin ID(PK) Admin ID(PK)
description
Pin Pin
Username Username

Data dictionary

Customer table

FIELD NAME DATA TYPE LENGTH DESCRIPTION

Admin ID Varchar 10 Primary key

Username Varchar 20 Descriptor

Password Varchar 15 Descriptor

18
 Address Varchar 10 Descriptor

Selected item table

FIELD NAME DATA TYPE LENGTH DESCRIPTION

Selected item ID Varchar 15 Primary key

Date Date 8 Descriptor

Experience Varchar 8 Descriptor

Cost Number 6 Descriptor

Service provider Varchar 15 Descriptor

ID(FK)

Service provider table

FIELD NAME DATA TYPE LENGTH DESCRIPTION

Service provider Varchar 10 Primary key

ID

Category Varchar 20 Descriptor

Experience Varchar 15 Descriptor

Password Varchar 18 Descriptor

Category Varchar 25 Descriptor

Admin table

19
 FIELD NAME DATA TYPE LENGTH DESCRIPTION

Admin ID Varchar 30 Primary key

Pin Number 15 Descriptor

Username Varchar 20 Descriptor

5.7 USER INTERFACE DESIGN

It describes the user interface where the user will be interacting with the system.

5.7.1 Log in web page

USERNAME

PASSWORD

CANCEL SIGN IN FORGOTE PASSWORD

5.7.2 Home page

WELCOME TO BISMART HOUSEHOLD SERVICE PROVIDERS

20
 SELECT SEARCH

ELECTRICIANS

ABOUT US CONTACT US EXIT

(The background color is the image of the different service providers)

5.6.2 Admin page for updating the service providers

SELECT

ADD DELETE

SAVE EXIT

5.6.3 Qualifications of the service provider chosen

;MKKNM
SELECT THE BEST SERVICE PROVIDER OF YOUR CHOICE

PLUMPERS 21 ELECTRICIANS

CHOOSE EXIT
 REFERENCES

1. Levin,Mark Sh.Modular system design and evaluation.Springer,2015.

2. Development of an object-oriented DBMS;Portland,Oregon,United
States;Page 475;1986;ISBN 0-89791-204-7.
3. Kothari, C.R. (2005). Research Methodology. New Age International (P)
Limited Publishers, New Dehli

22