Spa Online System (SOS)

(1)

SPA ONLINE SYSTEM

(SOS)

NORAFRA AZMIRA BINTI ADNAN

(2)

BORANG PENGESAHAN STATUS TESIS

JUDUL: SPA ONLINE SYSTEM (SOS) SESI PENGABAN: 2009/20 10

Saya NORAFRA AZMIRA BINTI ADNAN mengaku membenarkan tesis (

P S M-/

) ini disimpan di p e r p u t a h Fakulti Teknologi Maklumat dan Komunikasi dengan sprat-syarat kegunaan seperti di berikut:

1. Tesis dan projek adalah hakmilik Wniversiti Teknikal Malaysia Melaka.

2. Perpustakaan Fakulti Teknologi Maklmat

dan

Komunikasi dibenarkan membuat salinan untuk tujuan pengajian sahaja.

3. Perpustakaan FakuIti Teknologi Maklumat d m Komunikasi dibenarkan membuat salinan tesis ini sebagai bahan pertdamn arntara institusi pengajian tinggi.

4.

**

Sila tandakan

(0

SULIT (Mengandungi &urnat yang berdarjah keselamatan atau kepentingan Malaysia seperti yang termaktub didalam AKTA RAHSIA RASMI 1972)

TERHAD (Mengandungi rnakhmat TERHAD yang telah di tentukan oleh organisasi/badan di mana penyelidikan dijalankan)

TIDAK TERHAD

(TANDATANGAN PENULIS) (TANDATANGAN PENYELIA)

Alamat Tetap: No 171. Lorona Molek

5

PUAN ZAHRIAH BT S A W

Taman Rashibah Indah Sikamat, Nama Penyelia

70400 Seremban. Negeri Sembilan

Tarikh: Tarikh:

(3)

SPA ONLINE SYSTEM

(SOS)

NORAFRA AZMlRA BINTI ADNAN

This report is submitted in partial fulfillment of the requirement for the Bachelor of Computer Science (Sohare Development)

FACULTY OF INFORMATION

AND

COMMUMCATION TECHNOLOGY

XJNIVERSITI TE- MALAYSIA MELAKA

(4)

DECLARATION

I hereby declare that this project report entitled

SPA ONLINE SYSTEM (SO$)

Is written by me and is my own effort and that no part has been plagiarized without citations.

STUDENT:

b@

Date: J r / L / 2 o l 0

SUPERVISOR: Date:

(5)

DEDICATION

To my beloved parents, your m o d support is my greatest d i i inspiration.

To all my beloved friend who have encouraged, guided and inspired me throughout my journey in educakn

(6)

(7)

(8)

(9)

TABLE OF COPlTTENTS

CHAPTER PAGE

DECLARATION DEDICATION

ACKNOWLEDGEMENTS ABSTRACT

ABSTRAK

TABLE OF CONTENTS LIST OF TABLES LIST OF FIGURES

LIST OF ABBREVIATION LIST OF ATTACXIMXNT

CHAPTER I INTRODUCTION

2 . 1 PROJECT BACKGROUND 1.2 PROBLEM STATEMENTS 1.3 OBJECTIVE

1.4 SCOPE

1.5 PROJECT SIGNIFICANCE 1.6 EXPECTED OUTPUT 1.7 CONCLUSION

CHAPTER

IT

LITERATURE

REVIEW AND

PROJECT MErnODQLOGY

2.1 INTRODUCTION 2.2 FACTS

AND

FINDING

2.2.1 Domain

(10)

2.2.2 Existing System 9

2.2.3 Technique 15

2.3 PROJECT METHODOLOGY 16

2.3.1 Object - Oriented Analysis and Design Process 16

2.4 PROJECT REQUIREMENT 18

2.4.1 Software Requirement 18 2.4.2 Hardware Requirement 19

2.4.3 Other Requirement 19

2.5 PROJECT S C H E D W AND MEESTONES 20

2.6 CONCLUSION 21

CHAPTERID ANALYSIS

3.1 INTRODUCTION 3 -2 PROBLEM ANALYSIS

3.2.1 A n d y s i s o f ~ t s y s t e m 3.2.2 Analysis To-Be System 3.3 REQUlREMENT ANALYSIS

3.3.1 Functional Requirement 3.3.2 DataRequirement

3.3.3 Non-Ftudona1 Requirement 3.3.4 OtherRequirement

3.4 CONCLUSION

CHAPTER IV DIESIGN

4.1 IMTRODUCTIOM

4.2 HIGH-LEVEL DESIGN 4.2.1 System Architecture 4.2.2 User Interface Design

(11)

4.2.3 Database design 66 4.2.3.1 Conceptual and Logical Database design 67 4.2.3.1.1 relationship diagram 67 4.2.3.1 -2 Relational Data Model 69

4.3 DETAILED DESIGN 4.3.1 SoRwareDesign

4.3.2 Physical Database Design

4.3.2.1 Data Definition Language @DL) 80

CHAPTER

V

WIP-AmON

5.1 INTRODUCTION

5.2 SOFTWARE DEVELOPMENT ENVIRONMENT

SETUP 8 5

5.2.1 Software Architecture Setup 85 5.2.2 H a r d w a r e A d i t ~ S e t u p 86 5.3 SOFTWARE CONFTGURATION MANAGEMENT 87

5.3.1 Configuration environment Setup 87 5.3.2 Version Control Procedure

5.4 MPLIZMEGWATION STATUS 5.5 COMCLUSION

CHAPTER

VI

33ZSTmG

6.1 INTRODUCTION 6.2 TESTPLAN

(12)

6.2.2 Test Environment 6.2.3 Test Schedule 6.3 TEST STRATEGY 6.4 TESTDESIGN

6.4.1 Test Description 6.4.2 Test Data

6.5 TEST RESULT

AND

ANALYSIS 6.5.1 Test Summary Report 6.5.2 Test Record

6.5.3 User Satisfaction Level 6.6 CONCLUSION

CHAPTER VII PROJECT CONCLUSION

7.1 OBSERVATION ON WEAKNESSES AND STRENGTH

7.2 PROPOSITION FOR IhdlLpROvEMlWT 7.3 COMTRDBUTION

7.3.1 Contniution to university 7.3.2 Contribution to faculty 7.3.3 Contribution to Spa 7.3.4 Contribution to individual 7.4 CONCLUSION

(13)

TABLE TITLE 2.1 SOS domain

2.2 Comparison three existing +em

2.3 Software Item Compilers and Operating System 2.4 General Tool

2.5 Hardware and Fmwove Item 2.6 Project Milestones

3.1 Data Requirement for SOS

3.2 Software Requirement for d d o p m g SOS 3.3 Hardware Requirement for developing SOS 4.1 Input design for the SOS system

4.2 Data Dictionary of SOS database

5.1 Source Code Version Control

5.2 Implementation !!ht\rs for Each Modttle

6.1 Hardware and Soffware involved in Testing Process 6.2 Test Case for Empty Field (Positive Testing)

6.3 Test Case for Empty Field (Negative Testing) 6.4 Test Case for Unique Staff' ID (Positive Testing) 6.5 Test Case for Unique Staff ID (Negative Testing) 6.6 Test Case for Unique Cusbmer

ID

(Pmitive Testing) 6.7 Test Case for Unique Customer ID (Negative Testing)

(14)

Test Case for Integer Field (Positive Testing) Test Case for Integer Field (Negative Testing)

Test Case for Numeric Fieid (Equivalence ParCitioning) Test Case for identical password (Positive Testing)

Test Case for identical password (Negative Testing) Test Case for Input Field (Positive Testing)

Test Case for Input F i d ('Negative Testing) Test Data for Empty Field

Test Data for Uniqae SMZD Test Data for Unique Customer ID Test Data for Integer Field

Test Data for Identical Password Test Data for Input field length Test Data for Login

Test Data for Add

New

User

Test Data for Add new treatment module Test Data for Cheek Availability

Test Data for Make Appomtment

Test Data for Update payment statns 112

(15)

xii

DIAGRAM TITLE PAGE

Online booking of web A View list of Web A treatment Menu interface of web B Booking of Web B

View list of Web C treatment

Select date and time of appointment Web C Add Service and search availability of Web C List of treatment that available on the date choose Login of Web C

Create account of Web C Software development process Use case diagram of manual system Activity diagram for check avmiabifity

Activity diagram for fill form for appointment Activity diagram for payment

Use case diagram of SOS system Activity diagram for sign tip Activity diagram for login Activity diagram for logout

(16)

Activity diagram for make appointment Activity diagram for make payment Activity diagram for view appointment Activity diagram for view s Mdetails JavaServer Faces Implementation of

lWVC

MVC

class structure Navigation for SOS

Customer Login main page screen design Invalid username and password

Change Password

Add customer screen design

Add, delete, and update staff screen design Appointment screen design

Staff Login main page screen design View appointment list screen design

Cheek

Availability screen design Check AvailabiIity Message Available

Check Availability Message Not Avmible Save appointment with dik button 'Done' Delete Treatment screen design

(17)

The sequence of Enstabtion T d s for SOS system Test Schedule for Unit Testing

Test Schedule for System Testing

Graphical view of partition for Numeric Field Test Script for Login

Test Script for Add New User

(18)

DBMS

DDL

ERD

H.TML JSF

OOADM

RUP SDLC

sos

SSADM

SQL

UML

UTeM

Database Management System

Data Definition Language

Entity Relation Diagram Hypertext Markup Language

JavaServer Faces

Object Oriented Analysis and Design Model

Rational Unified Process

Software Development Life Cycle

Spa Online System

Data Flow Diagram

Structured Query Language

Unified Modeling Language

(19)

xvi

ATTACEMEMT 1.1 Gantt Chart 1.2 Proposal form 1.3 Log Book 1.4 User Manud 1.5 Testing SOS

(20)

CHAPTER I

INTRODUCTION

1.1 PROJECT BACKGROUND

(21)

1.2 PROBLEM STATEMENTS

1.2.1 Time Consuming

Customer who was on travelling also cannot make an appointment. So the processing time of booking consume time.

1.2.2 High cost of transportation

E

the spa is far fiom customer house, it

w

i

l

give a problem to customer to come and make an appoidment and payment.

1.2.3 Phone d l cost

Customer has to make more than one =Us to mdkm the booking which ended up in a high cost of phone calls

1.2.4 Increase paper work load

This cause problem when keeping a lot of paper

1.3 PROJECT OBJECTIVE

1.3.1 To develop a computerized spa system

To improve the current m u a i system (paper work system) that is using by the spa organization by having an online web base system which can be accessed anywhere by spa customers

1.3.2 To make an effective and efficient spa system

(22)

1.3 SCOPE

Basically, in this web base system, the target users are customer, staff and admin. This system will help spa owner to solve the problem that faced by spa customer and spa staff.

1.3.3 Customer Module

1.3.3.1 Login - To give security for an data, this system provide a login module. Customer must enter username and password before use the system.

1.3.3.2 Add new user

I

Register - These &les for customer add p e r s o d Information and update their personal information.

1.3.3.3 Change Password -

These

module for customer to change password

1.3.3.4 Check Availability - This module is for customer to check availability for particular date, time and staff.

1.3.3.5 Appointment

-

This module is for user choose treatment name, appointment date, apointment time and sta£F

1.3.3.6 View treatment list -

This

module for customer to see what

(23)

1.3.4 Staff Module

1.3.4.1 Login - To give security for all data, this system provide a login module. Admii must enter usemame and password before use the system.

1.3.4.2 View Appointment fist - This module is for staff to view customer appointment.

1.3.4.3 View customer list -This module for staffview customer details.

1.3.4.4 View Payment and Update Payment Status - This module is for staff to view and update customer payment status

1.3.5 Admin Modules

1.3.5.1 Login - To give security for a11 data, this system provide a login module- Admin must enter usenrame and password before use the system.

1.3.5.2 Add, Update, Delete - These modules fur admin add staff detail and delete staff.

(24)

1.4 PROJECT SIGNlFICANCE

1.4.3 Users

The target users of this buoking system are spa's customer which can perform reservation through online system Other than that, staff also can use this system to view customer appointment and update payment status.

1.4.4 Save time and cost

With this system, it can helps users to save their time by not going out twice which is to make an appointment and payment. This indirectly has

saved up the cost of - t r a n s p t & o n fee

d

phone call.

1.4.5 Reduce workload

._

With this system, it will reduce the works of staff on duty and allow them to more concentrate on

ather

.arorks in spa In this way, less staff will be hired purpose to reduce cost.

1.6 EXPECTED OUTPUT