Object Oriented Analysis and Design (CSF3202)

BACHELOR OF COMPUTER SCIENCE

(SOFTWARE ENGINEERING)
SEM I
SESSION: 2015/2016
SYSTEM DOCUMENTATION
CAFE MENU SYSTEM (CMS)

PREPARED FOR

: DR. NOOR AZLIZA BINTI CHE MAT

PREPARED BY

: SHARIFAH SHARINA BINTI YAHAYA

UK35697

: MUHAMMAD AINUDDIN BIN SAHARUDDIN

UK34308

: NOR ZAFIRAH BINTI MD KAMSOR

UK34865

: NURI ANWAR BIN ZAIDI

UK35293

: NURUL HANAN BINTI BINYAMIN

UK35416

HAND IN DATE

: 13rd DECEMBER 2015

WEIGHTAGE

: TO BE GRADED

Object Oriented System Analysis and Design (CSF3202)

ABSTRACT

This is a study on how the system in the cafe will take place. The goal is to easier the
cafe staff in managing customer order and payment. The management can be done in two
ways either manual or auto method where in manual method, staff takes orders directly from
the customer and in auto, staff will key-in the orders in the system and it will go directly to
the kitchen. This process will help the staff in the cafe in maintaining their works efficiency
and also will contribute to time saving.

Object Oriented System Analysis and Design (CSF3202)

Table of Contents
ABSTRACT ............................................................................................................................................ 2
TABLE OF FIGURES.........................................................................................................................4
1.0 INTRODUCTION.5
1.1 Project Description...5
1.2 Company Background..5
1.3 Business Mission and Vision........6
1.4 Objective of the System........6
1.5 Scope of the System..7
1.6 Problem Definition....7
1.7 Problem Solution......8
1.8 Project Scheduling9
2.0 REQUIREMENTS.9
2.1 Requirements Gathering...9
2.2 Functional Requirement..........10
2.3 Non-Functional Requirement..11
3.0SYSTEM MODELLING..12
3.1 Business Process and Function Modelling.13
3.2 Structural Modelling...19
4.0 SYSTEM DESIGN..24
4.1 Database Design..24
4.1.1 Normalization......24
4.2 Input Design26
4.3 Output Design.....27
4.4 Interface Design..28
5.0 CONCLUSION....28
APPENDIX A - REFERENCES....29
APPENDIX B - REQUIREMENT ANALYSIS (INTERVIEW)..30
APPENDIX C - LOG BOOK31

Object Oriented System Analysis and Design (CSF3202)

Table of Figures
Figure 1 : Use Case....13
Figure 2 : Activity Diagram for Make Order.... 14
Figure 3 : Activity Diagram for Manage Order.....15
Figure 4 : Activity Diagram for Manage Payment............16
Figure 5 : Activity Diagram for Manage Staff...17
Figure 6 : Activity Diagram for Generate Report..........18
Figure 7 : Sequence Diagram for Customer Makes Order....19
Figure 8 : Sequence Diagram for Staff Manages Payment....20
Figure 9 : Sequence Diagram for Manage Staff Information....21
Figure 10 : Caf Menu System Class Diagram..22
Figure 11 : Input for Menus Design...26
Figure 12 : Input for Manage Staff Design....27
Figure 13 : Output for Produce Receipt.27

Object Oriented System Analysis and Design (CSF3202)

1.0 INTRODUCTION
1.1 Project Description

Our system title is Cafe Menu Order System. This system is all about to reduce the
labor and make an ordering progress easier. So what is Caf Menu Order System? This
system is a system that provides the services that a customer can place their order and directly
get the total price of their food(s) and beverage(s) orders. This system will require a device
that is connected to a network which are linked to another device in the kitchen, counter and
for the waiter. Customers will choose their orders based on the menus provided at the
interface of the device but this device only handle by the waiters. The waiters will come to
the customers table to take the order and the order will be link directly to the kitchen and
counter. Then, the kitchen will complete the order while the counter produces the receipt for
the payment.

1.2 Company Background

Our company has 5 major roles which are project manager, business analyst, systems
analyst, infrastructure analyst and change management analyst for Cafe Menu Order System.
A project manager is responsible for ensuring that our project is completed on time
and within budget and our system delivers all benefits intended by the project sponsor. The
role of project manager includes managing the team members, developing the project plan,
assigning resources and being the primary point of contact when people outside the team
have questions about the project.
A business analyst focuses on business issues surrounding the system. These issues
include identifying the business value that our system will create, developing ideas and
suggestions for how the business process can be improved and designing the new processes
and policies in conjunction with the system analyst.
A systems analyst focuses on the IS issues surrounding the system also develops ideas
and suggestions for how information technology can improve business processes, designs the
new business processes with help from the business analyst, designs the new information
system and ensure that all IS standards are maintained.

Object Oriented System Analysis and Design (CSF3202)

An infrastructure analyst focuses on technical issues surrounding how the system will
interact with the organizations technical infrastructure. Tasks handled are including ensure
the new information system conforms to organizational standards and identifying
infrastructure changes needed to support the system.
A change management analyst focuses on the people and management issues
surrounding the system installation. The role of this person include ensuring that the adequate
documentation and support are available to users, providing user training on the new system
and developing strategies to overcome resistance to change.

1.3 Business Mission and Vision

1. Mission

Our mission is to make sure the system is fulfil the entire requirement stated
before.

2. Vision

Improve the work quality of the staff and the manager for the cafes operation.

The business runs smoothly.

The system works perfectly.

1.4 Objective of the System

The main objective of this system is to make the ordering process easier. Other
objectives of this system are to reduce labor work and easier payment process. Reducing the
labor work is when the customers make the orders, the waiters did not have to go to the
kitchen to send the orders. They can just input the orders in the system and it will directly
link to the kitchen. So their chefs can complete the orders quickly. The waiters had saved
their times by this process. They can proceed to take another customers orders. This process
lead to another objective that is to improve the time consuming in completing the orders at a
time. For the easier payment process, it is easier because the total payment had been
calculated by the computer or system. Lastly, this system can increase the efficiency of
managers report. The managers can make their monthly report by making this system as the
references instead of make it manually.

Object Oriented System Analysis and Design (CSF3202)

1.5 Scope of the System

1. This system is not limited for the use of a caf. It also can be used for a restaurant
also. This system purposely created to make the easier ordering process and it can
involve the management of orders and customers that comes at the same time.
2. This system only limited to the cash payment type.
3. Meals only can be delivered once the meals are completely ready to be served.
4. Meals and beverages are not available for delivery.

1.6 Problem Definition

Problem is a perceive gap between the existing state and a desired state, or a deviation
from a norm, standard or status quo. Before we decided to build this system, we had made
a survey on the problems that a cafe had faced when they did not use any system for their
cafe. Some of the problems are:
1. Time consuming to complete an order. Without any system, a caf had took a long
time just to complete an order. This is because the waiters need to take the orders
and send it to the kitchen. The chefs at the kitchen need to wait for an order to be
taken and send it to them before they can cook and make the beverages to be
served. This condition had made the customers need to wait for their meals to be
served over than their expectations.
2. Need more paper to take the orders.
3. Missing of workers information and their schedules. Manager need to check the
shift of the workers including the waiters and the chefs manually. The possibilities
that the missing of workers information is high when the information only kept
manually in some pieces of paper.
4. Wrong bills and change. The waiters sometimes forgot the bills and get the wrong
calculations. This may lead to the loss to the cafe.
5. Incorrect orders. Some waiters had send wrong orders to the wrong table. The
customers will not get the meals that they actually want and it will make the
process to complete the customers orders been delay for some minutes or longer
time than it should arrive.

Object Oriented System Analysis and Design (CSF3202)

1.7 Problem Solutions

1. This is how we do to overcome the time consuming problem. With this system, a
waiter can take the orders for the customers and the orders will be directly to the chefs
and to the counter section. Chefs and cashier can directly linked to order so the chefs
can complete the orders quickly while the cashier can prepare for next step which is
payment.
2. A waiter will take an order with a device that has been installed with this system.
3. The workers information and their schedules are being kept in this system. But it can
be only access by the managers while for the other workers, they only can update their
information.
4. In this system, when the receipt is ready, the total and amount of food and beverages
are being calculated and recorded. So the customers know what they are paying for.
5. The receipt printed also included the number of each table for each order. So the order
will be ready for the appropriate table.

Object Oriented System Analysis and Design (CSF3202)

1.8 Project Scheduling

TOPIC
INTRODUCTION
REQUIREMENT
Requirement Gathering
Functional Requirement
Nonfunctional Requirement
SYSTEM MODELING
Business Process and
Functional Modeling (Use
Case Diagram & Activity
Diagram)
Structural Modeling (Class
Diagram & Sequence
Diagram)
SYSTEM DESIGN
Database Design
Input Design (use HTML
/Dreamweaver/Flash/Pencil)
Output Design (use
HTML/Dreamweaver
/Flash/Pencil)
Interface Design
CONCLUSION
APPENDIX
REFERENCE

WEEK1

WEEK2

WEEK3

WEEK4

WEEK5

WEEK6

WEEK7

2.0 SYSTEM REQUIREMENTS

2.1 Requirements Gathering
1. Interviewing the user or stakeholder. The most common technique for gathering
requirements is to sit down with the clients and ask them what they need. The process
include:

The interviewee was selected and the interview session included with the
questions that was planned out based on the requirement that was discussed.

Open-ended, close-ended and probing were the approach or question types

used in order to prepare the question for the interviews session.

Unstructured interview was implemented that avoid closed-ended question

because this type of question types will give yes and no answers.

The interview was conducted with bottom-up technique.

Object Oriented System Analysis and Design (CSF3202)

2. Observation.

An observation was conducted by watching users, a process flow and

opportunities can be determined by an analyst for improvement.

3. Use Cases.

Use cases is definitely were use in order to make analysis for this system. The
stories include people (actors) and describe how the solution works from a
user perspective. Use cases may be easier for the users to articulate, although
the use cases may need to be distilled later into the more specific detailed
requirements.

4. Brainstorming.

In this project, simple brainstorming may be the starting point. After all the
ideas are generated, we prioritize the ones that we think are the best. The
resulting consensus of best ideas is used for the initial requirements.

2.2 Functional Requirement

1. Data for each menu were entered before a request can be approved.
2. The data were included:

List of price of each menu so the payment can be proceed.

Id of the staff that must be entered first before the payment process.

The data of the operations in a day for the transaction made must be saved
either by the staffs or manager then a record can be generated for the purpose
and view of the manager.

The total transaction must be key-in according to the menu so that the total
payment and the receipt can be printed.

The menu that entered either by staff or manager will link to the kitchen and
chef will process the order.

3. All the staff using the system will be trained how to use the system.
4. Staff and manager also can add and delete the menu based on customer request.
5. Process that included in this system:

(Actor) Customer: Customers will only make order, and then will make the
payment after eating.

(Actor) Waiter: Waiter manages the order by take the order from the customer
by explain or showing the list of menu to the customer. Then he key in the

10

Object Oriented System Analysis and Design (CSF3202)

order to the system so the order will link to the kitchen. Lastly, waiter act as
the cashier.

(Actor) Manager: Manager generates record. Manager creates the ID for the
staff so the staff can access the system. Next, manager also takes the order
from customer, key-in the order in the system then the order will link to the
kitchen. Lastly, manager also acts as the cashier.

(Actor) Chef: Prepare and cook the order made from the customer and ask the
waiter to serve / send the food for the customer.

2.3 Non-Functional Requirement

1. Security

Staff can enter the request but cannot approve or delete request. For example,
staff in charge for the cashier, he just can enter the amount of the total bill or
he can enter the list of menu that customer asked only but never can change
the price of the menu.

Only the manager can view the record of the whole transaction and operation
of the cafe.

Only the manager or owner of the cafe can changed the menu or the list of the
price of the menu.

Every staff and the manager have their own unique ID number.

Manager has an authority to create ID for staff.

The limitation to enter id number and password was set to prevent any
unauthorized user.

2. Performance

Any interaction between the user and the system should not exceed 3 seconds.

The list of the menu and prices can be updated if needed.

The system should receive updated inventory information every 15 minutes, if

the system is break down the record is still saved.

3. Operational

The system will start when the staff or the manager open the system to start
the operation of the caf every day.

When the staff or the managers close the system it means that the system is
close for that day.
11

Object Oriented System Analysis and Design (CSF3202)

When the system is start, the day and time is recorded so that the manager can
know when the operation is start.

It is also when the system is closed, the day and time is recorded so the
manager can know when the operation is start.

The list of the menu are showed according to the categories:

-

The list of menu can sort from A to Z.

The list of the menu also can sort from the price of each dish.

The search tools also provide to search the menu instead of search one by one.

4. Cultural & political

The system is for Malaysia currency.

The system is included GST (Goods and Service Tax) that was established by
the government.

3.0 SYSTEM MODELLING

3.1 Business Process and Function Modelling (Use Case and Activity Diagram)
This subsection extends upon the functional requirements given in Section 2.0
through the presentation of detailed use cases. To facilitate an unambiguous and clear view of
how the end-users interact with the subject CMS, the actors (end-users) involved in the use
cases, a use case diagram and detailed use case descriptions are provided. The use cases that
find representation are Make Order, Make Payment, Manage Staff, Manage Order and
Generate Report and there are four actors in the CMS which are Customer, Waiter, Chef and
Manager.

12

Object Oriented System Analysis and Design (CSF3202)

3.1.1 Use Case

Figure 1 presents a use case diagram for the subject CMS. They key interactions between the
end-users of the system and the systems itself are depicted.

Use Case for Cafe Menu Order

System

13

Object Oriented System Analysis and Design (CSF3202)

3.1.1 Activity Diagram

Figure 2 presents the Make Order activity diagram to provide graphical representation of the
customer make order.

Activity Diagram
for Make Order

Select food and

beverage

Put quantity

Check price

Sum up total

Make order

14

Object Oriented System Analysis and Design (CSF3202)

Figure 3 presents the Manage Order activity diagram to provide graphical representation
when staff manages order.

Activity Diagram for

Manage Order

Customer makes order

Customer wait

Key in order in the system

Produce

Order link

receipt

to the
kitchen

Alert waiter

Waiter serve
menu

Mark item
delivered

15

Object Oriented System Analysis and Design (CSF3202)

Figure 4 presents the Manage Payment activity diagram to provide graphical representation
when staff manages payment.

Activity Diagram for Manage

Payment

Customer

View bill

Waiter/Manager

Check payment/
transaction

Make purchase

16

Object Oriented System Analysis and Design (CSF3202)

Figure 5 presents the Manage Staff activity diagram to provide graphical representation when
manager manages staff.

Activity Diagram for Manage Staff

Get Staff info

Assign department

Waiter

Create

Update

Chef

Delete

View

Create

Update

Delete

Print

17

Object Oriented System Analysis and Design (CSF3202)

Figure 6 presents the Generate Report activity diagram to provide graphical representation
when manager generate daily, weekly and monthly report.
Activity Diagram for Generate Report

Closing

Pay out

Count float
Not tally

Tally
Type of report

Daily

Monthly

Weekly

Print

Print

Print

End of generate report

18

Object Oriented System Analysis and Design (CSF3202)

3.2 Structural Modelling

3.2.1 Sequence Diagram

Figure 7 presents the sequence diagram for customer makes order.

19

Object Oriented System Analysis and Design (CSF3202)

Figure 8 presents the sequence diagram for staff manages payment.

20

Object Oriented System Analysis and Design (CSF3202)

Figure 9 presents the sequence diagram for manager manages staff information.

21

Object Oriented System Analysis and Design (CSF3202)

3.2.2 Class Diagram

The following subsection presents descriptions for the classes identified for the subject CMS.
Order
This class represents a collection of items requirement. It is part of a single meal and
maintains information about whether it has been placed or approved. An order can be in
either the placed, cancelled or the approved state. An order wills typically de deleted shortly
before key-in in the system.
Payment
This class represents a payment to be made to the cafe using cash method. A payment
maintains its total value and the seat of the paying customer.
Meal
This class represents a collection of all items ordered by a single customer. It is part of a
single account and maintains the seat number related to the meal. The total price of a meal is
also maintained.
Staff
This class represents as an actor to manage while customer makes order until they make
payment. The staff can be a manager, waiter and chef.
Customer
This class represents as an actor as they can make order and payment.

22

Object Oriented System Analysis and Design (CSF3202)

Figure 10 represents Cafe Menu System Class Diagram

23

Object Oriented System Analysis and Design (CSF3202)

4.0 SYSTEM DESIGN

4.1 Database
Database normalization is the process of organizing the columns (attributes) and
tables (relations) of a relation database to minimize data redundancy.
Un-Normalized Form (UNF)
Order system
-Order number: unsigned long
-Date: Date
-Time: Time
-Table number: unsigned long
-Staff id: String
-Staff name: String
-Payment number
-Meal id: String
-Meal name: String
-Meal price: Double
-Quantity: unsigned long
-Amount: Double
-Tax: float
-Total: Double
-Change: Double
First Normal Form (1NF)
Order table
-Order number: unsigned long
-Date: Date
-Time: Time
-Table number: unsigned long
-Staff id: String
-Payment number
-Meal id: String
-Meal name: String
-Meal price: Double
-Quantity : unsigned long
-Amount: Double
-Tax: float
-Total: Double
-Change: Double

Staff table
-Staff id: String
-Staff name: String

24

Object Oriented System Analysis and Design (CSF3202)

Second Normal Form (2NF)

Order table
-Order number: unsigned long
-Date: Date
-Time: Time
-Table number: unsigned long
-Staff id: String
-Meal id: String
-Meal name: String
-Meal price: Double
-Quantity: unsigned long
-Payment number: unsigned long

Payment Table
-Payment number: unsigned
long
-Amount: unsigned long
-Tax: Float
-Total: Double
-Change: Double

Staff table
-Staff id: String
-Staff name: String

Third Normal Form (3NF)

Order table

Customer table

Payment Table

Staff table

-Order number: unsigned

long

-Order number:
unsigned long

-Staff id: String

-Date: Date

-Payment number:
unsigned long
-Table number:
unsigned long

-Payment
number:
unsigned long
-Amount:
unsigned long
-Tax: Float

-Time: Time
-Staff id: String
-Meal id: String

-Staff name: String

-Total: Double
-Change: Double

-Meal name: String

-Meal price: Double
-Quantity: unsigned long

25

Object Oriented System Analysis and Design (CSF3202)

Fourth Normal Form (4NF)

Order table
-Order number:
unsigned long

Meal table
-Meal id:
String

Customer table
-Order number:
unsigned long

-Date: Date

-Meal name:
String

-Time: Time

-Meal price:
Double

-Payment
number:
unsigned long
-Table number:
unsigned long

-Staff id: String

-Meal id: String

Payment Table
-Payment
number:
unsigned long
-Amount:
Double

Staff table
-Staff id String

-Staff name:
String

-Tax: float
-Total: Double
-Change:
Double

-Quantity:
unsigned long
-Payment
number:
unsigned long

4.2 Input Design

Figure 11 represents Menu Design. This design shows the selection menus to choose.

26

Object Oriented System Analysis and Design (CSF3202)

Figure 12 represents Manage Staff Design. This design shows the manager can perform
process delete, update and create staff ID.

4.3 Output Design

Figure 13 represents Receipt Output Design. This receipt design can be print or just keep it in
the system to save the paper.

27

Object Oriented System Analysis and Design (CSF3202)

4.4 Interface Design

4.4.1 Hierarchical Chart

Start

Use as manager

Use as staff

Menu

Manage staff

Receipt

End

5.0 CONCLUSION
This system has been able to come to a successful end of a journey that we go through
ups and down, hills and valley that even seemed impossible to climb. We hope that our
system has accomplished according to the requirements of the manager that we got during an
interview.

28

Object Oriented System Analysis and Design (CSF3202)

APPENDIX A
REFERENCES

David Tegarden, A. D. (n.d.). System Analysis and Design with UML (4th Edition ed.).
Wiley. Retrieved December, 2015
EPF. (2012, May 3). Requirement Techniques. Retrieved 12 10, 2015 from Guidelines:
http://epf.eclipse.org/wikis/openup/core.tech.common.extend_supp/guidances/guideli
nes/req_gathering_techniques_8CB8E44C.html
B. (2015, January 17). Requirement Gathering Techniques. Retrieved October 10, 2015 from
REQUIREMENT GATHERING: http://business-analysisexcellence.com/requirement-gathering/
Sommerville. (2011). Software Engineering (International Edition ed.). Pearson. Retrieved
December 10, 2015

29

Object Oriented System Analysis and Design (CSF3202)

APPENDIX B
REQUIREMENT ANALYSIS (INTERVIEW)

1. When is the operation time of this caf?

2. Did all of the staff know how to use a computer?
3. What is your duty as a manager?
4. What is your duty as a waiter or chef?
5. Can you tell us the average of customers that you receive every day?
6. Is this caf using a system same just like we are going to build?
7. As a manager, can you explain some of the problem with the current system and give
an example?
8. Can you tell us, what kind of improvement that you wish in this system?
9. How the ordering system in this caf? Did the waiter comes to the tables or the
customers came to the counter?
10. How long does it takes to complete an order?
11. What are your solutions to avoid the error in the order such as wrong beverages send
to a table?

30

Object Oriented System Analysis and Design (CSF3202)

APPENDIX C
LOG BOOK

Bil.

Tarikh/Masa

1.

30/10/2015
(10am1pm)

Perkara
-

Perjumpaan pertama bersama ahli

kumpulan.
Perbincangan mengenai tugasan yang
diberikan.
Membuat analisa mengenai tugasan
kami (fasa analisis)

Catatan
-

2.

10/11/2015
(8pm-12pm)

Membicangkan mengenai tugasan yang

telah diberikan.
Membuat design sistem (fasa design)

Setiap ahli
kumpulan
hadir.
Tugasan juga
telah
diagihkan
Setiap ahli
kumpulan
hadir.
Tugasan juga
telah
diagihkan
Setiap ahli
kumpulan
hadir

Berbincang dan mengumpul tugasan

masing masing

25/11/2015
(2pm-3pm)

Meneruskan tugasan yang dirancang

dan perjumpaan di buat untuk
berbincang mengenai tugasan yang
sedang dibuat

Setiap ahli
kumpulan
hadir

5.

30/11/2015
(4pm5.30pm)

Mengumpul tugasan yang telah siap dan

mengubah suai bahagian yang salah
sekiranya tidak menepati syarat
tugasan.

Setiap ahli
kumpulan
hadir

6.

9/11/2015
(11pm12.30pm)

Perjumpaaan diadakan untuk mengemas

kini tugasan dan memperbaiki
kesalahan setelah berjumpa Puan
Azliza.

Setiap ahli
kumpulan
hadir

7.

12/11/2015
(1pm-2pm)

Perjumpaan terakhir untuk tugasan dan

mengumpul setiap tugasan yang diberi
berasingan daripada ahli kumpulan.

Setiap ahli
kumpulan
hadir

3.

20/11/2015
(9pm11.pm)

4.

31