AZMAN HASHIM

INTERNATIONAL BUSINESS SCHOOL

M
SHAC 3193 (01)
SYSTEM PROPOSAL

PREPARED FOR: MADAM SARIATI BINTI AZMAN

NAME MATRIC NO.

CHAN MAN TENG A16HA0365
RUBBA A/P D. PRAGASH A16HA0208
SARAWANA RAU A/L THARAM RAJU A16HA0211
INTAN SYAHIRAH BINTI RAMZI B17HA0006
NURUL AFIFAH BINTI KAMARULZAMAN B17HA0017
 Table of Contents
Executive Summary ................................................................................................................... 1
1.0 System Problems & Opportunity ......................................................................................... 2
2.0 Goals and Objective of MYUTMFood ................................................................................ 4
3.0 Project Scope ....................................................................................................................... 5
4.0 Anticipated Cost and Benefit ............................................................................................... 6
4.1 Feasibility Analysis .......................................................................................................... 6
4.1.1 Net Present Value ...................................................................................................... 6
4.1.2 Internal Rate of Return .............................................................................................. 7
4.1.3 Payback Period .......................................................................................................... 7
5.0 System Planning................................................................................................................... 8
5.1 Project Timeline ............................................................................................................... 8
6. System Analysis ................................................................................................................... 10
6.1 System Survey ................................................................................................................ 10
6.2 Functional Requirement ................................................................................................. 14
6.3 Software and Hardware Requirements ........................................................................... 15
7.0 Project Design ................................................................................................................... 16
7.1 Conceptual Design ......................................................................................................... 16
7.1.1 Identify and evaluate design alternatives: ............................................................... 16
7.2 Physical Design .............................................................................................................. 17
7.2.1 Activity Diagram ..................................................................................................... 17
7.2.1.1 Activity Diagram for Place Order using Mobile Phone.................................... 17
7.2.1.2 Activity Diagram for Validate Order ................................................................ 18
7.2.1.3 Activity Diagram for Notify Food Status ......................................................... 19
7.2.1.4 Activity Diagram for Cancel Order .................................................................. 20
7.2.1.5 Activity Diagram for Add Menu Info ............................................................... 21
7.2.2 Blue Print Design..................................................................................................... 22
8.0 System Implementations & Testing ................................................................................... 28
8.1 Implementation Issues & Challenges ............................................................................. 28
8.2 Test plan ......................................................................................................................... 29
8.2.1 Unit Testing ............................................................................................................. 29
8.2.2 Functional Testing ................................................................................................... 30
8.2.3 System Testing ........................................................................................................ 31
8.2.4 Acceptance Testing.................................................................................................. 31
9.0 Conclusion ......................................................................................................................... 32
 Executive Summary

In this systems proposal, the Information Systems Analysis Team will present some of
the problems identified and suggest possible solution with descriptions of them organizational,
financial and procedural costs and benefits. We will then offer a recommendation based upon
the analysis of the current system. A summary is included at the end of the proposal, in addition
to an appendix that includes data collection instruments, and other resources used in our
analysis.

Based on the current information system, we are recommending that management move
forward with a solution that to develop MYUTMFood, an online system where the students
can place food order through applications which have facilities like online payment. This
system development is estimated to cost RM 50,620 for complete implementation of the
system.

The above cost will include all of the hardware and software products as well as the
necessary peripheral products needed to get the system up and running. The training for
MYUTMFood is included in this cost. The training product is an ‘in-the-box’ solution and will
be owned by the organization for future use at any time.

A more in-depth breakdown of this solution is provided within this document.

However, the main idea to extract is that this recommendation will help students easy to place
order through online so that they would not be waiting for hours sometimes.

1
1.0 System Problems & Opportunity

Statistics show that there are 15,630 student undergraduates, 8,769 student post-
graduates, 4,256 PhD students and 3,333 international students registered in Universiti
Teknologi Malaysia Johor Bahru (UTMJB). If we assume a total of 16,000 students who live
in a UTM residential college and there are only 10 food courts and cafe available in UTM such
as:

1. Arked Lestari K9 & K10

2. Arked Cengal L53
3. Arked Meranti H32
4. Pak Lah Scholar Inn
5. The Sino Perdana
6. Arked KDSE WA5
7. Street Café N24
8. Angkasa
9. Pak Lah KTC
10. Mak Ngah KTDI

The limited number of food courts cannot accommodate the number of students and
arise troublesome in ordering food especially during the peak hours such as lunch time and
dinner time. The current ordering system been used in all these food courts is still in traditional
method which is the students need to queue to write their order and wait for food to be ready.
This method has caused problems for the students while they are in the food court such as:

P1: Due to the nature and the type of operation that food court has adopted, they have
become overcrowded especially during peak hour and one cannot expect such place to be a
peaceful dining out solution for the students.

P2: Students are required to place an order at the payment counter and this causes
congestion at the counter. Because of the narrow place and there is only one counter. This poses
congestion to students who want to make payments and make orders.

P3: The students need to wait for another long time for their food to be ready. For
example, they already take 10 minutes for the queue and need to wait for another 20 to 30
minutes for their food to be ready. So, they wasted around 40 minutes just for the food.

2
 P4: Proper display menu are not available on most of the food court and student have
to stand and decide their order from the common menu that is displayed near the ordering
counter. This makes them feel uncomfortable with the process.

P5: The student stands in a long queue in the food court, and then when their turn to
place order, they discovered that the food item that they want to order is not available. This
leads to lots of frustration in the student and their valuable time and energy is just wasted. If
they want to think about the new order, it will take time for them to make a decision. So, it will
give impact to the other students which are they need to wait for a longer time in a longer
queue.

P6: Due to the limited sitting area, the seats are always congested and the design or the
sitting arrangement in the food court is not customer friendly at all. Besides, the seats usually
full with the students who are waiting for their food to be ready and people who have food in
hand does not have a place to sit.

The opportunity that we see from these problems are we can develop an online system
where the students can place food order through the application that have online payment
facilities. This system is called MYUTMFood. The advantage of this system is that students
can manage and plan their meal times more efficient and systematic. The students do not have
to waste their time by queuing to order and waiting for food ready in the food court. But, they
only need to use the MYUTMFood app to place food orders and the application will display
the amount of time allocated to food ready. So, students can use their wasted time to do the
other benefit things like group discussion, revision and assignment.

Moreover, by using this application, students will not miss and skip their meal time
because they are too busy and do not have time to go and buy food at the food court. Besides,
this application also helps the student to know the food courts that operate on that day and the
available menus. Therefore, the student can decide and choose the food that they want easy and
quickly.

Additionally, this application can also reduce congestion at the food court and make
them more organized. Students can choose whether to eat there or take away according to the
food courts conditions and seat availability. Furthermore, an effective and convenient
application can attract more customers to UTM food court.

3
2.0 Goals and Objective of MYUTMFood

Goals are general guidelines that explain what you want to achieve in a community. They are
usually long-term and represent global visions.

Objectives are defined strategies or implementation steps to attain the identified goals. Unlike
goals, objectives are specific, measurable, and have a defined completion date. They are more
specific and outline the “who, what, when, where and how” of reaching the goals.

The goals and objectives of MYUTMFood are:

1. Reduce the time students spend on waiting for their ordered food.

This system will allow students to not waste their valuable time for waiting for the food that
they ordered. It will allow the students to enjoy their meals within a short period of time.
Therefore, the system will eliminate the minor section of order processing time.

2. Inform students on the availability of the menu.

This system will allow the students to explore various menus according to their preferences
before they order their food. This will reduce the possibility of the students from ordering the
food just because it is available. It will also allow the students to make comparisons between
the prices and the variations of the menus.

3. Reduce the number of students who wait for empty seats to have their meals.

This system will allow students to not find for empty seats to have their meals. Sometimes,
students will not get satisfied while enjoying their meals because there will be other students
who are waiting with their meals behind their seats. Thus, by enabling this system which allow
online ordering, this will improve their satisfaction apart from reducing their time for waiting
for empty seats.

4
3.0 Project Scope

The project aimed is to developing a food application system that can be used by the UTM
students to order food through the apps which can help to reduce waiting time to get food
especially during peak hour and congestion at the food court.

The food apps develop in smartphone based because nowadays smartphone are necessity
for everyone. The system is developed to let students to view the available menu on that
particular day and able students place an order via the system. Besides that, the system also
developed to reduce time of students stand in a long queue in the food court and waiting
for the empty spaces to having their dinner. The most important function is to allow
students place an order at anywhere they are.

The food apps will provide benefit to students such as save time and energy. Because of
this system, students can save their time to do other things instead of to stand in long queue
for having dinner. Furthermore, students also can in advance know the available menu for
the particular to avoid the food that they want to order is not available.

Food Ordering Module

This module will be developed that let students use their own smartphone to viewing the
food menu information and place an order through the smartphone apps.

Menu Management Module

In this module, students can review the latest and updated food menu information through
the apps.

Billing Module

This module will collect all the order information and calculate the total bill for the students.
Students can pay through online banking to pay the bills. This module also will print the
billing statement for students for their reference.

5
4.0 Anticipated Cost and Benefit

4.1 Feasibility Analysis

4.1.1 Net Present Value

CASH FLOW YEAR

0 1 2 3 4 5
(RM) (RM) (RM) (RM) (RM) (RM)
Initial Outlay cost
Hardware (Computer and
server) (40,000)
Software (programming ) (2,500)
Training (5,600)
Initial System Design (1,750)
Documentation (770)
Total Initial cost (50,620)

Recurring cost
System maintenance (1,100) (1,100) (1,100) (1,100) (1,100)
Overhead (1,800) (1,800) (1,800) (1,800) (1,800)
Software update (2,000) (2,000) (4,000) (2,000) (2,000)
Total cost (4,900) (4,900) (6,900) (4,900) (4,900)
Savings
Profit from sales increase 11,000 13,200 14,520 15,972 17,569.2
In app advertising profit 6,000 6,000 6,000 6,000 6,000

Net Cash flow (50,620) 12,100 14,300 13,620 17,072 18,669.2

Present value factor
1 0.9009 0.8116 0.7312 0.6587 0.5935
(Cost of capital 11%)
Present value of Cash
flow (50,620) 10,900.89 11,605.88 9,958.94 11,245.33 11,080.17
Net present value 4,171.21

⸫ NPV is higher than 0 which is RM4,171 so the project should be accepted.

6
 4.1.2 Internal Rate of Return

CASH FLOW YEAR

0 1 2 3 4 5
(RM) (RM) (RM) (RM) (RM) (RM)
Net Cash flow (50,620) 12,100 14,300 13,620 17,072 18,669.2
Present value factor
1 0.8696 0.7561 0.6575 0.5718 0.419
(Interest rate 15%)
Present value of Cash flow (50,620) 10,522.16 10,812.23 8,955.15 9,761.77 7,822.39
Net present value (2,746.30)

11% NPV 4,171

i NPV 0
15% NPV -2,746

4,171 −0
IRR= 0.11 + [(4,171+2,746)(0.15 − 0.11)]

IRR= 0.134
IRR= 13.4%

⸫ IRR is higher than cost of capital (11%) which is 13.4% so the project should be
accepted.

4.1.3 Payback Period

Payback Period (without discount) Payback Period (discount)

Year Cash flow Accumulated Year Cash flow Accumulated

0 (50,620) (50,620) 0 (50,620) (50,620)
1 12,100 (38,520) 1 10,901 (39,719)
2 14,300 (24,220) 2 11,606 (28,113)
3 13,620 (10,600) 3 9,959 (18,154)
4 17,072 6,472 4 11,245 (6,909)
5 18,669.2 25,141.2 5 11,080 4,171

Payback Period = 3 + 10600 / 17072 Payback Period = 4 + 6909 / 11080

= 3.62 years = 4.62 years
⸫ Payback period is within 5 years so the project should be accepted
- Since all the analysis shows that the project is feasible so the project should be
accepted and implemented.

7
 5.0 System Planning
5.1 Project Timeline
24 31- 7- 14- 21- 28- 5- 12- 19- 26- 2- 9- 16- 23- 30- 7- 14-
Task name Mar Mar Apr Apr Apr Apr May May May May Jun Jun Jun Jun Jun July July
System Planning
Select Title
Project Inspiration
Project Background
Information
Project Scope
Project Objective
Project Impact and
Contribution
Schedule and Budget Planning
System Analysis
Research for Existing System
Survey towards Students
Requirement of System
System Design
Conceptual Design
Identify and Evaluate
Design Alternatives
Physical Design
General Work Procedure
Design
Database Design
Blue Print Design

8
 Task name 19- 26- 2- 9- 16- 23- 30- 7- 14- 21- 28- 4- 11- 18- 25-
May May Jun Jun Jun Jun Jun July July July July Aug Aug Aug Aug
System Implementation
Implementation
Testing
Unit Testing
Functional Testing
System Testing
Acceptance Testing

Figure 1 Gantt Chart of MYUTMFood

9
6. System Analysis

6.1 System Survey

Pak Mak
Arked Arked Arked PakLah Arked Street
Bil D’Sino Angkasa Lah Ngah
Lestari Cengal Meranti Café KDSE Cafe
Problem KTC KTDI
Nature and type of operation food 220 230 250 200 215 230 210 200 230 230
1
court
Congestion at counter for place an 100 60 90 75 90 110 85 65 90 95
2
order and make payment
3 80 40 0 75 75 50 80 45 40 0
Display menu are not available
4 80 70 40 150 60 90 0 200 45 80
limited sitting area
Stands in long queue and waiting 430 490 500 500 420 440 460 450 500 470
5
long time for food
6 0 80 90 0 100 60 100 0 70 70
Appear a lot of cat
Smoky & smelly around the food 90 30 30 0 40 20 65 40 25 55
7
court

The surveys are done with 500 students who are having their meals at the food court and café in UTM. The results are showed that the problem
most students faced are stands in long queue and waiting long time for food.

10
 Problem Faced by The Students UTM While Having Their Meal in Food Court and Cafe in UTM
600

Nature and type of operation food

500 court

Congestion at counter for place an

order and make payment
400
Personalize menu are not available

300
limited sitting area

200 Stands in long queue and waiting long

time for food

Appear a lot of cat

100

Smoky smell around the food court

0
Arked Lestari Arked Cengal Arked PakLah Café D’Sino Arked KDSE Street Cafe Angkasa Pak Lah KTC Mak Ngah
Meranti KTDI

Figure 2 is Problem Faced by The Students UTM While Having Their Meal in Food Court and Cafe in UTM

11
 Reaction of
Application Food
Bil Apps KP K9&10 KTC KTHO KRP KTR KTDI KTF KDSE KDOJ
1 Strong Disagree
2 Disagree
3 Neutral
4 Agree
5 Strongly Agree

Total Number
Bil Reaction of Application Food Apps of Students
1 Strong Disagree 0
2 Disagree 0
3 Neutral 11
4 Agree 39
5 Strongly Agree 450

The surveys are done with 500 students who are having their meals at the food court and café in UTM. The result showed that most of the
students are strongly agree to implement food apps (MYUTMFood) in UTM.

12
Reaction UTM Students Towards Food Apps

0%
2% 8%
Strong Disagree
Disagree
Neutral
Agree
Strongly Agree
90%

Figure 3 Reaction UTM Students towards Food Apps

13
6.2 Functional Requirement

Order and Billing Management

User able to place an order for their consumers.
The system shall prompt and ask user to verify the order that have been placed.
User able to add in extra remark regarding the order.
User able to void the order that mistakenly placed or exceptional case occur.
User able to choose the payment channel that they wish to use

Security Requirements
The system should validate the username and password in order to login and make
changes to the system.
The system should request the current password of the user in order to let them
change to a new password

Usability Requirement
The system should have an easy understandable graphic user interface.
The system should be easy to understand the functionality of each module.

14
 6.3 Software and Hardware Requirements

In this project, a computer with sufficient processing power is needed. The computer is required
for the developer to have project development such as coding for the mobile application,
database creation and modification. For the complete system to work, several hardware
requirements must be met. First, it requires an android based smartphone to deploy the software
application and this smartphone is required to connect to the wireless access point to perform
request and respond processes that access to the database. Next, database is a must for the entire
system to store and retrieve the necessary data. Furthermore, a laptop or desktop is required to
host the database and manipulate the entire system.

Requirement for the staff computer

Description Minimum Requirements

Processor 1.6GHz or faster processor
RAM 512MB or more
Hard Disk 5GB of disk space available or more
Windows Operating System Windows 7 or above

Requirement for smartphone

Description Minimum Requirements

Processor 1.1 GHz or higher
RAM 512 MB or more
Storage 1GB free or more
Wireless Connection YES
Mobile Operating System Android 5.0 or above for android phones
IOS 9 or above for iPhone

15
7.0 Project Design

7.1 Conceptual Design

7.1.1 Identify and evaluate design alternatives:

We have identified and evaluate three alternatives in order to build food ordering
Apps (MYUTMFood) which are:
a. Purchasing the software

Advantages:
Less development times since it is already available in market.
Lower cost because the product is sold to many companies

Disadvantages:
Does not meet the organization needs since it is designed for wide audiences.
The functions cannot fully utilize.

b. Developing the System In-House

Advantages:
Can customize the system based on the organization’s need.
Lower cost because the system is developed by phase.
Any confidential information or ideas are kept within the organization.
Fewer training requirement.

Disadvantage:
Significant amount of time required for development process.

c. Outsourcing the System:

Advantages:
Involve less development time.
Minimizing the labor costs.
Reduce error.

Disadvantages:
External party will not have a throughout understanding of the system.
Obligated to buy license for upgrade therefore will induce higher cost in long run.

16
 After evaluating all the pros and cons of design alternatives, we decide to do in
house development of MYUTMFood since we have a great team with a lot of expertise in
this field. Therefore, we can avoid from dealing with the technician who may not
understand our unique situation. Not only that, by customize the system we can meet the
exact specifications and cover every aspect without unnecessary extras. Besides, having
customized software also makes the system’s interface more familiar and user friendly.
Lastly, we can have the ownership and control the system as we wish.

7.2 Physical Design

7.2.1 Activity Diagram
7.2.1.1 Activity Diagram for Place Order using Mobile Phone

Customer Food Court’s Staff System

Choose Food Court

View Menu

Place Order

Submit Order Update to Database

Wait Staff to Verify Order

Figure 4 Activity Diagram for Place Order using Mobile Phone

17
 7.2.1.2 Activity Diagram for Validate Order

Customer Food Court’s Staff System

Notify Staff to Verify

Order
Check Order

[Have Unknown Issue] [No Unknown Issue]

Clarify with Customer

Verify Order Update Order Queue

Figure 5 Activity Diagram for Validate Order

18
 7.2.1.3 Activity Diagram for Notify Food Status

Customer Food Court’s Staff System

Preparing Order
Queue

Food Ready Update Food Status

Customer Get
Notification to
Pick Up Order

Figure 6 Activity Diagram for Notify Food Status

19
 7.2.1.4 Activity Diagram for Cancel Order

Customer Food Court’s Staff System

Request to Cancel Check Food Queue

Order Void Order
Status

Notify User Food [Food is preparing] [Food Haven Prepare]

is Preparing

Inform Customer Cancel

Food is Preparing The Order

Update Order
Queue

Figure 7 Activity Diagram for Cancel Order

20
7.2.1.5 Activity Diagram for Add Menu Info

Customer Food Court’s Staff System

Log in MyUTMFood
Apps

Request to Add
Menu Info

Input All Require and

Necessary Details

Submit the Menu Info Validate the require

field
[Any Require Field [All Required Field
Notify User is Blank] is Filed Up]

Require Field is
Blank

Save The
Record

Figure 8 Activity Diagram for Add Menu Info

21
7.2.2 Blue Print Design

The interface displays the

MYUTMFood logo in mobile user.

Figure 9 MYUTMFood Apps Logo

22
 This is the first interface that will
display while students and vendors run
the MYUTMFood application.

Figure 10 MYUTMFood First Interface

As for students, they need to use their

acid ID and password. As for the
vendor, they can create their own user
ID and password.

Figure 11 MYUTMFood Log In

23
 This interface will show up after the
student’s log in. Its allow user to know
what the famous menu of the day. And
the students can choose the nearby café
according to the map and the café list.

Figure 12 MYUTMFood Student’s Interface

There will be list of café under the café

list. The students may choose any arked
or café that they want to eat and if
student click on that café, it will give
the direction to go to that café.

Figure 13 MYUTMFood Café List

24
 Aside from directing the direction of
the café, the students also can get
updated menu of the café.

Figure 14 Menu’s Available

This interface will display the

information of the food and the user can
enter the number of order quantity and
add the order list. After that, the student
can submit the order to the vendors by
clicking the “make an order” button.

Figure 15 Student’s Order Interface

25
 This figure shows that if student want
to cancel the order, they can go to
history and click the “cancel order”
button. This will notify the vendor that
the student want to cancel the order.

Figure 16 Student’s Cancel Order

This interface is for the vendors. It will

show the menu that the student has
selected and the vendor will tick in the
box and verify the order of their
customers. Once food ready, the vendor
just need to click “food ready” button to
inform food status to their customers.

Figure 17 Vendor Verify Order

26
“
This interface available the vendor to
update their menu to let their customer
get the latest menu of the day. So, if the
vendor wants to update their menu, they
just need to click on the “+” and put
food details that they want to update.

Figure 18 Vendor Interface

This is how the notification will appear

to the customer once the vendor clicks
the “food ready” button.

Figure 19 Food Notification

27
8.0 System Implementations & Testing

At the end of the project design, it is the beginning for system implementation, which is the
actual coding to develop the proposed project. During development phase, the table structure
of the database will be first built in order to provide a suitable data types that suit the system
back end development, system connection and data transfer. Next, the computer side client
program will be developed and follow by will be the web services that allow mobile phone
client program to communicate with the server and lastly mobile phone side client program
will be developed. In testing phase, several test cases will be carry out to test the system in
order to determine the system reliability and system accuracy. According to the test cases, a
system testing report will be generated for further review to figure out the system weaknesses
and made improvement accordingly. In the deployment phase, several training will be
provided for the particular restaurant staff such as how to operate the system, the procedure of
handling different events and several instructions that need to be follow when operating the
system.

8.1 Implementation Issues & Challenges

During the implementation phase, there are several challenges because it involves the end users
to test the production system in different situations. Following are possible challenges that may
be faced:

i. Required Internet network to access the food apps.

The users are required to connect with WIFI or mobile data to access the MYUTMFood apps.
Without Internet connection, the user cannot make an order and even update the menu info. All
the transaction or activities in this apps required user to have internet network.

ii. Server performance

During real time system implementation, there would be a huge number of clients that access
to the server at the same time. Therefore, it may slow down the connection and performances
of the system and even cause the server down if the issue goes beyond the level of acceptance.

28
 8.2 Test plan

After the system has been developed, next is system testing phase. In testing phase, the
developed system will be installed on appropriate devices for testing purposes. After the
completion of installation, the system testing tasks will be performed by different users. The
purpose of system testing is to identify and determine the degree of system stability and
efficiency. At the same time, it will give an opportunity for the developers to identify the system
errors that has not been identified during the system development phase. These errors during
the system testing will be solved. Each and every part of the system is actually being tested by
the system developer itself before system testing phase. Therefore, there would be bias towards
the testing due to the system developer have knowledge about the system software logic and
lead the result to be inappropriate. There are four types of testing that will be used to test the
developed system which includes unit testing, integration testing, system testing and
acceptance testing.

8.2.1 Unit Testing

Objective: To ensure user can login into system correctly with valid ID and password.

i. Event: Verify that ID and password that enter by user and match the data in the database
when user click “OK” button on the login prompt

ii. Attributes and values: Login ID: validID & Password: validPassword

iii. Expected Results: Login successful

iv. Results: Pass

Objective: To ensure new user can be created properly.

i. Event: Create a new system user

ii. Attributes and values: System user information.

iii. Expected Results: Prompt new user has been created successfully message

iv. Results: Pass

29
 Objective: Add new food category to the menu

i. Event: Vendor enters the category name and click “OK” button.
ii. Attributes and values: Food Category Name: Dinner
iii. Expected Results: The entered category name is store into the database and refreshes the
food category panel with the new added category
iv. Results: Pass

8.2.2 Functional Testing

Objective: To ensure user with different role login according to restricted system
features.
i. Event: Login as “Vendor”
ii. Attributes and values: Login with Vendor ID
iii. Expected Results: Successfully login
iv. Results: Pass

Objective: To ensure order place by customer is stored to the system and work
properly.

i. Event: Place order according to what customer request

ii. Attributes and values: Food Quantity and extra remark for that particular food
iii. Expected Results: Order details submitted successfully and store into the database system
iv. Results: Pass

Objective: To ensure the cancel order by customer is stored to the system and work
properly

I Event: Cancel order by customer

II Attributes and values: Food can be cancel if the food are not yet prepare

III Expected Results: Each and every order details will be display, taxes amount and grand
total amount will be calculated correctly.

IV Results: Pass

30
 8.2.3 System Testing

System testing, which is known as software and hardware testing, is a testing conducted on a
system which is completed and integrated. System testing is a critical testing procedure that
must be conducted by software developer before the system is available to the end users.
System testing is to evaluate the system’s compliance with its specified requirements according
to the system design. Furthermore, several testing activities in system testing are carried out on
the design of the system to identify the behavior and the believed expectations from the
customers. In addition, various complex test cases are used on testing according to the business
process requirements which are collected from the users. Meanwhile, errors that detected
during the testing phase is required by software developer to look into it from the initial step
of the business process to the end of the process to ensure that the system provide the expected
result in order to solve the errors to determine the degree of system stability and efficiency.

8.2.4 Acceptance Testing

Last but not lease, acceptance testing, which is also known as user acceptance testing would be
the final testing procedure that performed to test the developed software system. In acceptance
testing, the testing activities are different compared to the testing activities that mentioned
previously because the individual that tests the system will be the end user who do not have
any knowledge about the system. If the end users identify any errors while using the system,
the system developers are required to maintain the system as soon as possible and release a
new patch for the existing system to recover the error. Meanwhile, final user will use the system
that visualized as to support their real business routine operation, therefore software support
team are required to stand by to provide technical support while final user need any help or
support that regarding the system. If there is no errors detected by the final user while using
the system for a long period, the development job of developer is consider as complete and the
system will be a final system product.

31
 9.0 Conclusion

MYUTMfood can reduce and replace the human manpower task, reduce the time consumption
for each transaction and generate report for further management purpose by fully utilizing the
system. This system will help to improve the productivity in delivering the food to the students.
In addition, there will be less costs incurred because the system will carry out almost all the
business process itself and there will be less manpower required. In term of portability, this
system provides convenience, accessibility, and it is easy to communicate. In nutshell, this
system is user friendly and it will provide many benefits to the users.

There are some additional features that has been recommended by the development team. The
system can further add a feature which is real time notification from the mobile phone
application to the service desk. This feature will enable the customers to request customer
service through using the mobile application rather than verbally call restaurant staff to
approach them. In addition, the mobile application also can add a feature that allow customer
to update the food serve status. For example, customers fine dining at the restaurant they can
request the food to be serve through using the mobile application and if the customer finish the
main course and feeling full, the customer may request do not serve the following food through
using the mobile application. Last but not least, the mobile application may implement some
mini game that is able to entertain customers while they are waiting for the food to be served.
As this system has been approved to be implemented, the development team will work on these
recommendations to enhance the productivity of this system.

32