6 chapter 4

7/27/2019 6 Chapter 4

1/25

CHAPTER 4

ANALYSIS AND DESIGN

4.1 Overview

This chapter, will describes the analysis and design for Mohamad Long ChineseMuslim Restaurant Reservation System (MRRS) which will includes the

determination of system requirements. System requirement is divided into two which

are user requirement and system requirement based on the user and system scope

where all these requirements are very important to ensure the functionalities of the

system meet the user requests. Flow chart, Data Flow Figure (DFD) and Entity

Relationship Figure (ERD) are used to analyze the system that will be developed.

System design involves two types which are database and interface design. Database

design to be determines types of data that will be stored. Whereas, the interface design

is enable users to input the data and return, display the data to users after the input is

successfully processed.

4.2 Requirement Analysis

Mohamad Long Chinese Muslim Restaurant Reservation (MRRS)allowed user that is

customer able to reserve table and book reservation online after they have been login

successfully to the system. Below shows the analysis of system requirements based on

each of the module :

1. Login module Only authorized users are allowed to use the system. Awarning message will pop up if the user system is not valid. A warning also

will be given if the user input a wrong password.

7/27/2019 6 Chapter 4

2/25

18

2. Registration module Customer able to fill up the registration details online.Applicants also are able to view their name and other information also after

the registration. If applicants try to input unnecessary details in the database,

an alert will pop up to alert user that the information is invalid. Once the

registration form is completed, customer can submit the form to the admin to

be stored in the database.

3. Manage Module In this module, admin can view how many reservationmade on that day by searching the calendar.

4. List Customer Module Admin can view how many user registered and canalso update information on the customer and also delete the user.

5. Reservation module Customer can pick the desired table and booked thetime needed. After click the booking button, customer will receive

confirmation booking via sms.

6. Customer Status Module customer can also view their status on the date thatthey booked. They can also update their reservation and cancel the reservation

if they want to.

7/27/2019 6 Chapter 4

3/25

19

4.2.1 Flow Chart

Figure 5: Main Flowchart of the system

7/27/2019 6 Chapter 4

4/25

20

Figure 6 : Customer registers information subroutine

7/27/2019 6 Chapter 4

5/25

21

Figure 7 : View and cancel subroutine

7/27/2019 6 Chapter 4

6/25

22

Figure 8 : Table reservation subroutine

7/27/2019 6 Chapter 4

7/25

23

Figure 9 : View and update reservation status subroutine

7/27/2019 6 Chapter 4

8/25

24

Figure 10 : SMS confirmation subroutine

7/27/2019 6 Chapter 4

9/25

25

4.2.2 DFD

Figure 11: Context Diagram

7/27/2019 6 Chapter 4

10/25

26

Figure 12: Data Flow Figure (DFD) Level 0

7/27/2019 6 Chapter 4

11/25

27


Process : Customer login validation

Figure 14 : Data Flow Figure (DFD) Level 1

Process: Deciding Table

7/27/2019 6 Chapter 4

12/25

28


Process: Filling Reservation form


Process : Updating reservation

7/27/2019 6 Chapter 4

13/25

29


Process : Administrative Login

7/27/2019 6 Chapter 4

14/25

30


Process : Checking Reservation Status

7/27/2019 6 Chapter 4

15/25

31


Process: Approving reservation

7/27/2019 6 Chapter 4

16/25

32


Process: Confirming Reservation

7/27/2019 6 Chapter 4

17/25

33


Process: Cancelling Reservation

7/27/2019 6 Chapter 4

18/25

34

4.2.3 ERD

Figure 22: Entity Relationship Figure (ERD)

7/27/2019 6 Chapter 4

19/25

35

4.3 System Design

System design is an important part which gives conception about input that will be

inserted and output that will be displayed. System design will determine the interface

that will be developed in the future.

Figure 23: Design Sketch for Admin and User Interface

Figure 24: Design Sketch for Registration User Interface

7/27/2019 6 Chapter 4

20/25

36

Figure 25: Design Sketch for user and admin forgotten interface

Figure 26: Design Sketch for list of customer interface for admin interface

7/27/2019 6 Chapter 4

21/25

37

Figure 27: Design Sketch for user information for admin interface

Figure 28: Design Sketch for edit and delete user (customer) information interface

7/27/2019 6 Chapter 4

22/25

38

Figure 29: Design Sketch for search date in admin interface

Figure 30: Select table reservation for user (customer) interface

7/27/2019 6 Chapter 4

23/25

39

Figure 31: Design Sketch for reservation list interface

Figure 32: Design Sketch for update reservation interface

7/27/2019 6 Chapter 4

24/25

40

4.4 Data Dictionary

Table 2 : User Data Dictionary

No Attribute Data Type Explanation

1 fullname Varchar(20) Users fullname.

2 username Varchar (10) Primary key, also represent as the ID

for system users.

3 password Varchar(20) Password for users and admin to login.

4 usertype Varchar(10) Admin or User.

5 email Varchar(20) Users email address.

6 phone Varchar(20) Users contact number.

7 regdate date Date registry.

Table 3 : Book Table Data Dictionary

No Attribute Data Type Explanation

1 Ref_no Int (11) Primary key for table request, as

reference number for access it.

2 Table_no text Number table for user to book.

3 fullname Text Users fullname.

4 No_person Int (11) Number of person reserve for a table.

5 Time time Time the user start start their reservation

6 Time2 time Time the user finish their reservation.

7/27/2019 6 Chapter 4

25/25

41

4.5 Conclusion

System Analysis that is done properly can produce system requirement accurately.

Accurate requirement specification is very important to ensure that a system can be

developed smoothly. Analysis and design phase are very important as it will give

impact to the system implementation and testing phase.

6 chapter 4

Documents