sistem pengurusan makanan rjngan (spmr ... - umpir.ump.edu.my

24
SISTEM PENGURUSAN MAKANAN RJNGAN (SPMR) (Rosly Masum SDN BHD) NUR SYAMJMI SALMA BINTI ABDILLAH A THESIS SUBMITTED IN FULFILMENT OF THE REQUIREMENTS FOR THE AWARD OF THE DEGREE OF BACHELOR OF COMPUTER SCIENCE (SOFTWARE ENGINEERING) FACULTY OF COMPUTER SYSTEMS & SOFTWARE ENGINEERING UNIVERSITI MALAYSIA PAHANG

Upload: others

Post on 02-Feb-2022

2 views

Category:

Documents


0 download

TRANSCRIPT

SISTEM PENGURUSAN MAKANAN RJNGAN (SPMR)

(Rosly Masum SDN BHD)

NUR SYAMJMI SALMA BINTI ABDILLAH

A THESIS SUBMITTED IN FULFILMENT OF THE

REQUIREMENTS FOR THE AWARD OF THE DEGREE OF

BACHELOR OF COMPUTER SCIENCE (SOFTWARE ENGINEERING)

FACULTY OF COMPUTER SYSTEMS & SOFTWARE ENGINEERING

UNIVERSITI MALAYSIA PAHANG

ABSTRACT

/ Snack food industry is not less important in daily life. This is because many

people involved in this field, especially the indigenous people. This industry is very

lucrative returns. For example are food industry and rosly Azhar masum sdn bhd.

although the industry is increasingly popular but the major problem in this industry in

terms of management. Management in the industry takes it easy while many things have

to be dealt with in the management of this industry. For example, food order, manage

reservations, generate profit and soon. The very significant problem is during the festive

season has received many orders. This project highlights the problems faced by Rosly

Masum SDN BED is one of the companies involved in this field. Among the problems

faced by Rosly Masum SDN BHD is the business done manually. Manual management

has no security features to manage all information about customers and information

about the products. This can cause all information is lost. In addition, to develop this

system requires the allocation of Rosly Masum SDN BIRD. so , one way is needed to

meet the requirement. The solutions proposed in the development of this system are to

computerize the manual management and implement the document Software

Development Plan (SDP), SRS (Software Requirement Specification) and the Software

Design Document.

V

TABLE OF CONTENTS

CHAPTER

TITLE

PAGE

vi'

TITLE PAGE

SUPERVISOR'S DECLARATION

DECLARATION

DEDICATION

ACKNOWLEDGEMENT

ABSTRACT

ABSTRAK

TABLE OF CONTENTS

LIST OF TABLES

LIST OF FIGURES

LIST OF APPENDICES

1

INTRODUCTION

1.1 Introduction

1.2 Problem Statement

1.3 Project Objective

1.4 Project Scopes

1.5 Thesis Organization

2 LITERATURE REVIEW

2.1 Introduction

2.2 Manual System

2.3 Existing System (Pluisliner Sdn Bhd)

1

11

111

Iv

V

VI'

ix

X

Xi

1

1

2

3

4

5

6

6

7

9

viii

3

2.4 Overview of the purpose system 12

2.5 Study on Journal (Database Management) 14

2.6 Software Approach 16

2.6.1 Study on Software 16

2.6.2 Study on Database 18

2.6.3 Study on Methodology 20

METHODOLOGY 25

/

3.1 introduction 25

3.2 Selected Project Method 25

3.2.1 Exploration phase 27

3.2.2 Planning phase 28

3.2.3 Iteration phase 29

3.2.4 Productionizing 36

3.2.5 Maintenance 42

3.3 Development Tools 42

3.3.1 Hardware Requirement 43

3.3.2 Software Requirement 44

3.4 Conclusion 45

4 IMPLEMENTATION 46

4.1 Introduction 46

4.2 Interface and coding 47

ix

5 RESULT AND DISCUSSION 66

5.1 Introduction 66

5.2 Result of System 68

5.3 Result and Analysis of User Feedback 69

5.4 System Module 73

5.5 Discussion 82

5.6 Advantages 82

5.7 Disadvantages 83

5.8 Assumption 83

5.9 Future Development 84

6 CONCLUSION 85

6.1 Introduction 85

6.2 Lesson Learnt 86

6.2.1 Project Planning 86

6.2.2 Time Management 86

6.2.3 Skills 87

REFERENCES 88

Appendices A-F 90-105

LIST OF TABLES

TABLE NO TITLE PAGE

3.1 Software Requirements 43

3.2 Hardware Requirements 44

x

LIST OF FIGURES

FIGURE NO TITLE PAGE

2.1 Manual System Flow (order) 8

2.2 Main Form of Existing System 10 2.3 Booking form of Existing Sistem 11 2.4 Flowchart ,6f Manual System 13

2.5 Components of Database 15

3.1 Extreme Programming LifeCycle 26

3.2 Use Case Diagram for SMPR 30

3.3 Sequence Diagram for Registration 31

3.4 Sequence Diagram for Order 32

3.5 Sequence Diagram for Payment 33

3.6 Sequence Diagram for Manage Product 34

3.7 Sequence Diagram for Produce Report 35

3.8 System testing for Registration without data 37

3.9 System testing for Registration with wrong data 38

3.10 System testing without enter password 39

3.11 System testing for Order Form 40

3.12 System testing for Confirm Order 41

4.1 Registration Form 48

4.2 Login Form 50

4.3 Order Form 52

4.4 Confirmation Order Form 54

4.5 Update Profile From 56

4.6 Manage Order Form 58

4.7 Add Product Form 60

4.8 Edit Product Form 62

xi

4.9 Confirmation Edit Product Form 64

5.1 Result for survey question number 1 69

5.2 Result for survey question number 2 70

5.3 Result for survey question number 3 70

5.4 Result for survey question number 4 71

5.5 Result for survey question number 5 71

5.6 Result for survey question number 6 72

5.7 Result for survey question number 7 72

xii

//

xlii

LIST OF APPENDICES

APPENDIX TITLE PAGE

A Gantt Chat 90

B Data Material 92

C Database Design 95

D User Manual 99

E Entity Relationship Design 105

F Questionnaire 107

CHAPTER 1

INTl DUCTION

1.1 Introduction

This chapter will introduce the 'Sistem Pengurusan Makanan Ringan' in few

aspects; highlight the problem will current practice using manual system. The objective

for this system and the scope covered of this system. 'Sistem Pengurusan Makanan

Ringan' is developing to manage a Rosly Masum Sdn Bhd order record, calculate stocks

of the product and generate payment report. It also to implement Software Development

Plan (SDP), Software Requirement Specification (SRS) and Software Design Document

(SDD) to fulfill all the requirement of the Rosly Masum Sdn Bhd.

1.1 Problem Statement

These problems are identified based on Rosly Masum Sdn Bhd. The current

problem in Rosly Masum Sdn Bhd is did not have systematic data to manage customer

order, payment report, and stocks of the product. Currently, staff that work at Rosly

Masum Sdn Bhd requires to manually manage all information that has been recorded in

files. The manual system is not providing the security of the customer booking, salary of

the staff and stocks of the product. Other problem that can be happen is hard to search

and update the order, stocks of the product and generate payment report. Below is the

specific problems statement that occurs by using manually system

i. The manual system is not providing the security to manage all

information about the customer order and stocks of the product

information that might be lost and other unexpected problem if it

occurs.

ii. To fulfill the requirement of the Rosly Masüm Sdn Bhd is very

difficult and need one way to solve it.

3

1.2 Objectives

The objectives of this system are:

i. To provide computerize 'Sistem Pengurusan Makanan Ringan'

via online to manage customer orders, stocks of the product and

generate report so that the data is more secure.

/

ii. To implement Software Development Plan (SDP), Software

Requirement Specification (SRS), Software Design Document

(SDD).

"In managing the projects, it is crucially important to select and

use the most effective management methods. When changes

occur, they should be dealt with as soon as possible. At the initial

stages of a project, gross development value, land cost,

construction cost, time and profit are the main concerns of the

client. When the economic environment changes, then the

developer may change the plan or strategy so as to reduce or

eliminate the negative impacts of any change that is incurred."

[1]

4

1.3 Scope

This system will be developing based on Rosly Masum Sdn Bhd requirement.

This system will cater on individual personal order at Johor only and focusing on

recording Rosly Masum Sdn Bhd customer order, stocks of the product information,

payment and generate profit report. There will be three users who will use this system

which is Manager, Service person and Customer. This system has five main modules,

namely registration, ordering, payment, manage stocks of the product and produce

report. Customer can make an order via pnline and can edit, update, view and delete the

profile and order. Service person is responsible for manage customer order, record

stocks of the product. Manager also has same optional with the Service person but

manager has additional option which is managed payment and generate report. This is a

web-based system.

5

1.4 Thesis Organization

In chapter two, it will discuss about research for the project that has been chosen.

The researches divide in two that current system or case study and research for technique

that will be used to develop current system

For chapter three will be discuss on approach and overall work load to develop

this system. This content consist of technique for implementation the projects

While chapter four will be exp1ining on documentation about all process that

required in develop the system. If system develop use database, the technique of

database need to be explain and the timetable that has been create need to insert via SQL

instruction.

Chapter five will be discuss on result that has been received and all data analysis.

The content that must have in this chapter consists of analysis of result, difficulty of

projects and improvement of project.

Chapter six will be discuss on summary of the project that has been developed.

CHAPTER 2

LITERATURE REVIEW

/

2.1 Introduction

"Sistem Pengurusan Makanan Ringan (SPMR) is a computerized system

for Rosly Masum Sdn Bhd usage. This system will developed to replace current

booking and data storage problem. This system is to computerize 'Sistem

Pengurusan Makanan Ringan' via online to manage customer, staff salary and

stocks of the product so that the data is more secure. This system is developed

via online.

7

2.2 Manual system

In order to develop the new system, important parts that must be considered

are study and analysis the current system. For that, the current system had been study

and analysis by interview to staff of Rosly Masum Sdn Bhd. From the interview,

flow management can be referring in Figure 2.1.

In the manual system, the order is done using the phone. Customers need to call

Rosly Masum Sdn Bhd to make an order/Employee will record all the customer's details

and also the order are made in the booking form manually. This led to the use of a long

time to deal.

The payment will be done manually. Staff needs to calculate payment manually

to determine total cost that need to pay by the customers. To make a payment, customer

can pay during they get their order. In that case, status payment will be record in the

payment book. Customer will receive a receipt after they made a successful payment.

For update the products quantity, the entire product lists have been recorded by

jot-down in white board with the quantity. For the return stocks not be calculate and

record.

To report gains of Rosly Masum Sdn Bhd, a manager will calculate manually.

This causes a lot of time on the need and benefits can not be counted cause correctly.

Begin( ,)

F7Vew Customers Booking

Staff fills the booking form from customer order

Customer receive the orders

te

Record in receipt/log book

End

Figure 2.1: Manual System Flow (order)

Figure 2.1 show the flow of the manual system for Rosly Masum Sdn Bhd. There

are many problems using manual system. There is not providing security for orders and

payment process. The order information can be misplaced or record the wrong order

8

because staffs only record the customer order in the paper. For the payment, there is no

deposit payment so customer can cancel the order anytime.

2.3 Plusliner Sdn Bhd

The Plusliner Online Ticketing System [2] - both implemented at the

sales counters, and this system was developed in house by the owner of Systems

Engineering Unit. This grants the great flexibility in making enhancements as

and when required. If using the plusliner.com , you only need to visit this system

once - which is on the date of departure. Furthermore, plusliner.com offers a

membership Loyalty Programmed which rewards passengers with attractive

discounts and coming soon - other gifts for redemption.

The Plusliner Online Ticketing was designed specifically to suit the

operational requirements of Plusliner Sdn. Bhd., for Plusliner and NiCE express

coach services. It is therefore not a "generic" ticketing system that can be

applied directly to other operators, of which their operational requirements may

be very different from ours. This can only be achieved through customization,

which is gladly willing to discuss with other operators and service providers.

10

Interface Design

- --

ITh1 fr I JI (cJj4

rat Av Tic ket Delivery

fig

- - - - -- - , yjoe to check coach Click to check for sat Hassle free availability One Day Delivery

PenangLoyalty Program

Visitus atTuüuiujMaiiiia, -ev Route For NICE 8A Pmgkahvi Weld.

1po - Kuala Lumpur daily at i, FAX: 6042501112

12:OOPM and 7!30PM Want to get moveClick for more

Children fare: RM20/S$i5

benefit^? Come

and i

as a IMICE member

Figure 2.2: Main Page

Figure 2.2 show the main page of Plusliner Sdn Bhd. In this main page it

has the new information and announcement about Plusliner so the customer can

know the latest update about the Plusliner Sdn Bhd. This page also contain the

login session.

Junior - age 12 & below (Fr) Nice - above aqe 12 (RM1OjSDpryr Platinum renew with 10,000 pint in a/c

WeW4it FoligwingInfQrmMfl.; .

FIe.e efli, le PT b![tI p TI) P to NV IAil, iioh

Trt! p Mr.

Full TTme-.

Single

L!a l _._J_j - umufrav

nuary

L

2000

w 1c pl -

Figure 2.3: Booking Interface

,Figure.2.3 show the booking form. After login, the customer can fill all

the information in the booking form to book the ticket and check seat

availability.

I

12

2.4 Proposed System

The system will be covering : all the disadvantages or weakness of the current

system. For make the system is more security, the password will be require. For the

order, the customers need to register. System will provide form that contains the

important information to customer need to fill it. During make a ordering, system will

record the identity number of the customer. The identity number will be used in a

long term. By using the Identity number, system can search profile, search status

order and edit profile. Flow management can be referring in figure 2.4.

/

Process for booking, customers can choose the product that they want in the

list along with the quantity of product required. System will display the unit price for

each product and also the total price of the product was selected based on quantity.

After that, the customer should verify all information order made is correct.

Customers also need to confirm details such as address themselves to the delivery of

goods, name and phone number.

For a payment process, customer needs to pay first before get the order.

Customers can choose to make payment of fees provided in this system. Customers can

only choose one type of payment only. After that, customers need to transfer the

payment from their account to the company account. They can also see the delivery

status in their profile.

System also will count number of stocks. The staff need to edit product using the

series number and can add total of that product.

For the report, administrator can view the profit every month. After that,

administrator can print the report.

Begin D Online Booking

Register

Order Process

Confirm No Order

Yts

Yes

Payment No Yes

Yes

Print invoice

C nd :E t

13

Figure 2.4: Flowchart of propose system for "Sistem Pengurusan Makanan Ringan"

Figure 2.4 shows the flowchart of propose system for "Sistem Pengurusan

Makanan Ringan". Customers must order via online. Before that, they must register to

make order process. After done the order process, they must confirm their order and

have two options whether want to continue order process or cancel it. For the payment

process, it will continue after customers confirm their order. They need to choose

payment type that contain in the interface.

2.5 Database Management

When discussing about database, it cannot escape from discussing about data.

Decisions that are made without reference to neither any accurate data nor information

would normally result in disastrous circumstances. Data and information are important

basic in the decision making process and data also is an asset to an organization.

Information resulted from the data that has been analyses and synthesized.

Data must be stored and manage properly because it is a valuable asset to an

organization. A huge data compilation which is stored in a data repository is known

database. Database is a compilation of related data that are shared together by various

categories of user to cater the information need of an organization.

Although data and information are considered as an asset to an organization, but

large repository data will become a burden if they are not managed efficiently. Data

access and maintenance involves high costs, thus an organized data and information

management system is required. This system is known as Database Management System

(DBMS). DBMS is a software system which allows users to interpret, creates, update,

arrange, manages and maintain database. DBMS also controls data access in the

14

15

database. DBMS simplifies data and information management that required by

organization. DBMS acts as an interface between users and database. Refer figure 2.5.

IDatabase

DBMSN//W

I Application I

/

Figure 2.5: Components of Database System

Database application is an application program which maybe written in one

programming language such as C and C++ to execute certain tasks by accessing

database.

The use of database management systems (DBMS) to replace conventionalfile

processing systems has dramatically increased in the past years. Although the use of

DBMSs overcomes many of the limitations offile processing systems, many important

applications require access to and integration of information among several and often

incompatible DBMSs. allows users and applications to access and manipulate data

across several heterogeneous databases while maintaining their autonomy. We discuss

the requirements and objectives of a federated database management system, and

outline the major issues and challenges for building and using such a system [3].