Reng (A)

Module Code : CT056-3-2-REQUIREMENT ENGINEERING
Intake Code : UC2F1905SE
Lecturer Name : LAI CHEW PING
Hand in Date : 5 AUGUST 2019
Tutorial No. : T2/ T3
System Name : Computerized Delivery Tracking System
Student ID Student Name
TP046721 LIM KING WAY
TP050678 TAN FENG QI
TP050399 TAN ZHI XIN
TP050757 TEY WEN YAN

APU Degree - Level 2 Group Assignment Requirements Engineering
Workload Matrix
Criteria Lim King Tan Tan Zhi Tey Wen

Way Feng Qi XIn Yan
Project Introduction: Vision and Goals of new system 50% - 50% -

Project Planning: Gantt Chart
System Analysis: 25% 25% 25% 25%

Problem in Existing System
Requirements Elicitation: 25% 25% 25% 25%

Requirements Sources
Software Requirements Specification: 25% 25% 25% 25%

Functional
Non-Functional
Constraints
Scenario Modelling: 25% 25% 25% 25%

Use Case Diagram
Use Case Specification
Data Modelling: - 50% - 50%

Entity Relationship Diagram
Functional Modelling: 50% - 50% -

DFD Level 0
Behavioral Modelling: 25% 25% 25% 25%

Activity Diagram
Requirements Validation 25% 25% 25% 25%

Requirements Management
Conclusion - 50% - 50%
______________________________________________________________________________
CT056-3-2 Asia Pacific University of Technology and Innovation 2019
1
Table of Content
Workload Matrix…………………………………………………………………………………………. 1
Table of Content…………………………………………………………………………………………... 2
1.0 Introduction………………………………………………………………………………………….... 5
1.1 Organization Background…………………………………………………………………………..5
1.1. Vision and Goals of the new system……………………………………………………………... 6
1.1.1 Vision………………………………………………………………………………………... 6
1.1.2 Goals……………………………………………………………………………………….... 6
12.0 Gantt Chart Project Planning…………………………………………………………………….. 7
3.0 System Analysis………………………………………………………………………………………. 8
3.1 Problems in Existing System……………………………………………………………………... 9
3.1.1 Cannot Upload and Download the latest updates…………………………………………... 9
3.1.2 Communication between customer and owner is not directly……………………………... 10
3.1.3 The manual system need manpower a lot………………………………………………….. 10
3.1.4 In a big organization, it is a time-consuming process…………………………………….... 11
3.1.5 Risk of mismanagement and data when the project is under development………………... 11
4.0 Requirement Elicitation…………………………………………………………………………….. 12
4.1 Requirements Source…………………………………………………………………………….. 12
4.2 Elicitation Techniques……………………………………………………………………………. 13
4.2.1 Interviews………………………………………………………………………………….. 13
4.2.2 Questionnaires……………………………………………………………………………... 14
5.0 Software Requirements Specification…………………………………………………………….... 15
5.1 Functional Requirements…………………………………………………………………………. 15
______________________________________________________________________________
2
5.1.1 System……………………………………………………………………………………... 15
5.1.2 Customer…………………………………………………………………………………... 16
5.1.3 Restaurant…………………………………………………………………………………. 16
5.1.4 Admin……………………………………………………………………………………... 17
5.1.5 Driver…………………………………………………………………………………….... 17
5.1.6 Customer Service………………………………………………………………………….. 17
5.2 Non-functional Requirements……………………………………………………………………. 18
5.2.1 Usability……………………………………………………………………………………. 18
5.2.2 Integrity……………………………………………………………………………………. 18
5.2.3 Availability………………………………………………………………………………….18
5.2.4 Security…………………………………………………………………………………….. 19
5.2.5 Distance constraints………………………………………………………………………... 20
5.2.6 Flexibility………………………………………………………………………………….. 20
5.3 Constraints……………………………………………………………………………………….. 21
6.0 Scenario Modelling…………………………………………………………………………………. 22
6.1 Use Case Diagram……………………………………………………………………………….. 22
6.2 Use Case Specification…………………………………………………………………………... 23
7.0 Data Modelling…………………………………………………………………………………….... 29
7.1 Entity Relationship Diagram…………………………………………………………………….. 29
8.0 Functional Modeling………………………………………………………………………………... 30
8.1 DFD Level 0……………………………………………………………………………………. 30
9.0 Behavioral Modeling………………………………………………………………………………... 31
9.1 Activity Diagram…………………………………………………………………………………. 31
9.1.1 Login……………………………………………………………………………………….. 31
______________________________________________________________________________
3
9.1.2 Place a Call……………………………………………………………………………….... 32
9.1.3 Create Order……………………………………………………………………………….. 33
9.1.4 Make Payment…………………………………………………………………………….. 34
9.1.5 View Orders……………………………………………………………………………….. 35
9.1.6 Confirming Orders……………………………………………………………………….... 36
9.1.7 Check Delivering Status………………………………………………………………….... 37
9.1.8 Accept Incoming Phone Calls……………………………………………………………... 38
9.1.9 Update Menu……………………………………………………………………………….39
9.1.10 Generating Report………………………………………………………………………... 40
9.1.11 Manage Payment………………………………………………………………………….. 41
10.0 Requirements Validation………………………………………………………………………….. 42
10.1 Types of Requirement Validation………………………………………………………………. 42
10.1.1 Walkthroughs…………………………………………………………………………….. 42
10.1.2 Review……………………………………………………………………………………. 42
10.1.3 Prototype………………………………………….. 43
10.2 Requirement Validation for Organization 43
11.0 Requirements Management 45
11.1 Requirements Traceability 46
11.2 Requirements Versioning 47
11.3 Requirements Baseline 47
11.4 Communication of Requirements Changes 48
12.0 Conclusion 50
13.0 References 51
______________________________________________________________________________
4
1.0 Introduction
1.1 Organization Background

Waiters on Wheels is a restaurant with meal-delivery service. Sue and Tom Bickford have started
their restaurant in 1997. Meal-delivery service is a service that allows customers to enjoy food
from a restaurant without leaving their home. At first, they wanted to open their own restaurant,
but due to financial issues, they decided to offer services to both restaurants and customers.
Currently, it uses a system that is able to take orders from customers and track the orders until it
is delivered to them. Customers have to call Waiters on Wheels when they wish to order food.
The staff will then record the customer’s order and pass the order to the respective restaurant.
Then the restaurant will then start preparing the food. Waiters on Wheels will then send one of
their drivers to pick up the order from that restaurant. The drivers sometimes have to pick up
orders from multiple restaurants before delivering it to customers depending on the demand of
that hour. The customers then pay the drivers of Waiters on Wheels the price that was agreed
beforehand. The price that the customers will have to pay includes the cost of the meal, the
service charge, and the tips. The drivers have to inform the restaurant of the completion of
delivery after they have delivered it to the customers. Customers can check the status of their
order through messages that are sent by Waiters on Wheels. Waiters on Wheels will send a
message to the customers whenever the delivery process goes through a step. For example,
customers can call Waiters on Wheels to check that if their order is at the cooking step or the
delivering step.
Customers are allowed to change their orders as long as their orders have not been prepared by
the restaurant yet. At the end of each week, Waiters on Wheels has to calculate how much they
need to pay each restaurant as they are not paid during the delivery process.
______________________________________________________________________________
5
The issues with the current system include using telephone calls to order or check the order
status from the company, it is an inefficient way of communicating. The number of orders the
company can take at a single time is also limited by the number of telephones they have. The
second issue of the system is that the coordination of the drivers are also not efficient as they can
only be reached through phone calls. This is a difficult way of getting information about the
status of each driver and it is an inefficient way of getting information from them. Lastly, staff
has to calculate the earnings and the total price that needs to be paid to each restaurant, might
produce errors as people might calculate the wrong amount.
1.1. Vision and Goals of the new system
1.1.1 Vision
“To deliver the most efficient food delivery service to the community by providing fast delivery
with good customer service to the people.”
1.1.2 Goals
G1 - To deliver food to the customers on time.
G2 - To ensure the food that is delivered to customers.
G3 - To provide excellent customer service to the customers.
G4 - To collect orders from customers efficiently.
G5 - To allow customers to have a variety of food selection.
______________________________________________________________________________
6
2.0 Gantt Chart Project Planning
In order for the project to be a success, a project plan must be needed. Diagram 2.0 at below is
the Gantt chart of project scheduling. This Gantt chart is able to help system developers manage
the time-consuming of every activity in the project.
Diagram 2.0 Gantt Chart of the Project
______________________________________________________________________________
7
3.0 System Analysis

The system analyzes the system observation process for the purposes of troubleshooting or
growth. It is applied to information technology where computer-based systems required defined
analyzes based on their design and makeup. In IT, system analysis may include looking at
end-user execution of a software package or product; looking in-depth at source code to identify
the methodologies used in software construction or taking feasibility studies and other kinds of
research, among other things to promote software product use and manufacturing. Professionals
in the evaluation of systems are often called upon to examine systems critically and to redesign
or suggest modifications as needed. Systems analysts inside and outside the company
environment assist to assess whether a system is feasible or effective in the context of its general
architecture and help to identify the alternatives accessible to the employing company or other
parties. Systems analysts are distinct from system administrators who maintain systems on a
day-to-day basis, and their roles usually require a top-level perspective of a system to determine
its general design-based efficiency. (techopedia, 2019)
______________________________________________________________________________
8
3.1 Problems in Existing System
3.1.1 Cannot Upload and Download the latest updates

Waiters On Wheels Restaurant is a restaurant that serves food delivery to customers. The current
system in this restaurant is unable to update orders for staff, receive orders, arrange for drivers to
pick up meals at a customer-designated restaurant and send them to designated destinations and
bills. All of the above work needs to be done manually by Sue and Bickford of Waiters On
Wheels Restaurant. The system currently does not automatically help them with these tedious
and complex tasks. Sue needs to answer the phone to get the customer's order, and then contact
the customer's designated restaurant to place an order. In addition, she also needs to contact the
driver of the current restaurant to have time to go to the restaurant to take the food ordered by the
customer and send it to the customer's designated location. Bickford needs to settle the bill of the
driver's bill from the restaurant and the driver's charge plus the customer's service fee. When the
driver reports at the end, Bickford needs to add up their money and compare it to his record.
After all, drivers report, he needs to create a bank deposit slip for the total receipt for the day. At
the end of each week, Sue and Bickford calculate the amount they owe to each restaurant at the
agreed wholesale price and then send them a statement and cheque.
______________________________________________________________________________
9
3.1.2 Communication between customer and owner is not directly

The Waiters On Wheels Restaurant is a restaurant that serves food delivery to customers. The
customer places an order with the restaurant by phone and contacts the designated restaurant
through the restaurant's staff to make the meal they have designated, and then the driver arranged
by the Waiters On Wheels Restaurant sends the customer's designated destination. In the process,
the customer has no way to communicate directly with the staff of the designated restaurant. If
the customer wants to make changes or cancel the order after placing the order, the Waiters On
Wheels Restaurant staff will be required to inform the restaurant. Occasionally, the Waiters On
Wheels Restaurant staff may place the wrong order, or forget to place an order. After the
customer has waited for a long time, they have not received the meal or received the wrong meal.
They also need to call Sue to ask for a meal. If this happens, it will have a big impact on the
reputation of the Waiters On Wheels Restaurant. If this restaurant has a complete ordering
system, it will reduce many of these mistakes for Sue and Bickford.
3.1.3 The manual system need manpower a lot
The Waiters On Wheels Restaurant staff need to take a lot of work every day. They need to
personally answer the customer's phone number and personal call the customer's designated
restaurant to give them the meal they have designated. After the meal is done, they also need to
personally contact the driver who has time to go to the restaurant to take the customer's meal and
send it to the destination specified by the customer. In addition, they also need to settle the bills
that need to be returned to the restaurant after the day ends. These are complex and cumbersome
tasks that need to be done manually by Sue and Bickford. They also need a large number of
drivers to help them complete the meal delivery service.
______________________________________________________________________________
10
3.1.4 In a big organization, it is a time-consuming process
Due to the growing customer base of Waiters On Wheels Restaurant, the scale of Sue and
Bickford's restaurants is growing. With the increasing number of customers, they can no longer
do things like they used to, but they need to rely on a complete system to help them reduce their
workload. If they do all the work without relying on the system, it will cause them to slow down
their delivery speed and may spend a lot of time doing the work that the system can do easily.
3.1.5 Risk of mismanagement and data when the project is under development
As the customer base of Waiters On Wheels Restaurant grows, there is a risk that staff may make
mistakes or make records in the accounts and record customer orders. If you use the system,
these problems will not occur and the system will automatically update and record all accounts
and customer orders at any time. Compared to writing on paper, the system's records are
relatively safe to keep these records.
______________________________________________________________________________
11
4.0 Requirement Elicitation
Requirements elicitation is a stage that requires the developers to discovering, searching and
collecting the requirements from the source of the company such as the stakeholders
(Modernanalyst, n.d.). In this stage, requirement sources and requirement techniques are the
major source which enable the users and developers to collaborate and to gather the data.
4.1 Requirements Source

Requirement source is the most important part source of the requirement elicitation. Requirement
source is the main source that the requirements need to be collected. In waiters on wheels, there
will be two sources which are stakeholders and existing system. Stakeholders are the people that
involve in within the activities in the company such as customers, chairman, suppliers,
employees and other stakeholders, hence their are the one who affect the environment of the
company. The second source is the existing system. Existing system is the system that currently
existing and still applying in the company, so we did some research and collect the information
from the current system and analyze the problems and issues to find out the requirements of the
current system.
______________________________________________________________________________
12
4.2 Elicitation Techniques

Elicitation techniques is a type of technique that is used to collect the information from the
surrounding environment or other sources and to gather and analyze the information and
knowledge from the people (Visual-paradigm.com, n.d.). In order to support the business
operation, we have applied elicitation techniques that could help us in collecting information
from Waiters on Wheels’ stakeholders such as customers, admin, employees, suppliers, drivers,
and other stakeholders. By using these methods, we are able to identify the domain problem and
propose a new solution to the current system where we will be using two techniques - interview
and questionnaires.
4.2.1 Interviews
The first elicitation techniques are the interview. Interview is a formal meeting that involves
face-to-face conversation in which one or more people will be asked a list of questions and to
collect the information whether the information is accurate or not (Modernanalyst.com, n.d.).
The reason we have chosen this method is because the interview is the most efficient ways to
collect data because the interviewee is able to provide a wide range of answers and in more detail
ways, unlike questionnaire, however, the target of stakeholders to interview will be the chairman
of Waiters on Wheels, hence he is the one who runs the company. Yet, the employee will then
report all the activities in the company where he could determine and analyze the existing
problems in the current system. As a result, we have sent an invitation to the chairman of the
company to invite him to attend the interview section and during the interview, we have collected
and recorded the fundamental system that still used in the current system.
______________________________________________________________________________
13
4.2.2 Questionnaires
The next elicitation techniques are Questionnaires. Questionnaires are a type of survey that
consists of a listed of the question with a choice of an answer for researchers to collect
information in a formed of statistic (Modernanalyst.com, n.d.). Questionnaires are the simplest
method to collect information from customers, because it does not take too much time on
answering the question where the answers are provided, and the user just need to choose between
the given answers, and so we have used google platform - google form to create a questionnaire
template, therefore, the main target user will be customers, workers and suppliers where they are
the stakeholders to this company. To collect the data, we have created a list of questions for the
customer when the customer collects the items from the driver, the customer will receive a
message that required them to answer the questionnaire. As for the worker and supplier, a link
will be sent to them where when they click on the link, they could directly access to the google
form to answer all the questions.
______________________________________________________________________________
14
5.0 Software Requirements Specification

A Software Requirements Specification can also know as a System Requirements Specification.
It is a set of documentation that is used to describe the features of a software application or a
system. It includes a variety of elements that attempts to meet the functionality required by the
client to satisfy their different kind of users such as the driver, the manager, the customer and
other. There are a few of the functional and non-functional requirements required by clients in
this Computerized delivery tracking system and those constraints that the system will face:
5.1 Functional Requirements
5.1.1 System
F1: This system must be able to accept orders either via telephone or via the company website.
F2: This system should be able to inform the specific restaurants to prepare the meals that
customers ordered.
F3: This system shall be able to accept payment from customers.
F3.1: The payment can be online banking, credit card or debit card or cash.
F4: This system can able to calculate the salary of drivers based on the number of orders they
take.
F5: This system must be able to identify the user to restrict access in the system.
F5.1: Every employee on Waiters on Wheels restaurant has their own restrictions in the
a system such as only the financial officer can review the financial of the restaurant.
F6: This system could be able to collect all the information and report to the top manager.
F6.1: By using this system, employees can get the information and manage them into a
report easily. For example, this system will display the hottest picked meals of
customers. The report can allow the top manager to make a better decision.
______________________________________________________________________________
15
F7: The system must show the delivery status to the customer and employee.
F8: The system is able to calculate the cost of orders.
F8.1: The cost of the order shall be included with wholesale price, retail price, service
charge and tips.
F9: The scheme will enable the customer to add to the order in additional remarks.
F10: The system shall be able to calculate the estimated delivery time.
F11: The system shall be able to assign orders to drivers.
F11.1: The system will automatically assign an order to a driver depending on their
Availability.
5.1.2 Customer
F12: Customer shall be able to make a phone call to customer services.
F12.1: Customers are able to make a phone call to their driver after placing an order.
F13: Customer must enter username and passwords in order to login to the account on the
website.
F14: A customer shall only be able to register one account per user.
F14.1: Every single account must be linked to a customer’s phone number and email.
F15: A customer shall only select a restaurant to make an order.
F16: Customer shall be able to trace every single order with a given unique number.
F16.1: The given unique number shall be able to track the location of the driver who has
taken his/her order.
5.1.3 Restaurant
F17: When the customer made an order, the restaurant shall receive a notification to confirm the
order.
F18: Restaurant shall able to manage the food and beverage on the menu on the website.
______________________________________________________________________________
16
F18.1: Restaurant shall able to update, add, or remove the items on the menu.
F19: After the delivery is completed, the restaurant shall be able to receive a payment based on
the customer’s order.
5.1.4 Admin
F20: Admin shall be able to receive payment and produce sales report and deposit slip.
F21: Admin shall be able to make a refund if there is a need.
F21.1 The refund needs to be approved by the admin before refunding to the customer.
F22: Admin shall be able to manage the users and menu on the website.
F22.1 The menu must be updated according to the restaurant’s menu.
5.1.5 Driver
F23: Driver shall able to send a private message and call the customer to ask for additional
Information.
F24: When the customer made an order, the driver shall receive a notification to confirm the
Ride.
5.1.6 Customer Service

F25: Customer service shall able to check the delivery status of the order such as confirmation
from driver and restaurant.
F26: Customer Service shall able trace the current activities such as order status and delivery
status.
F27: The scheme allows the customer to cancel the order that occurs erroneously or in
extraordinary cases.
F28: The scheme will allow the customer to place a consumer order.
F29: The system will prompt the user to check the order placed.
______________________________________________________________________________
17
F30: The system will collect associated data from the database and produce a report to the
customer.
5.2 Non-functional Requirements
5.2.1 Usability
NF1: This system must handle a large number of users using this software application at the
same time.
NF1.1: This system will not crash while 1000 customers are taking orders and 10
employees of Waiters on Wheels company managing product information behind
the system.
NF2: The system should display the specific image of the meals while customers are selecting
the meal such as nasi lemak, fried rice, and others.
5.2.2 Integrity
NF3: The system must ensure the customer enters the phone number incorrect formats, such as
international standard (+60)12-3456789 or (+14)12-3456780.
NF4: The system shall be able to round with 5, on hundredths decimal place if the payment is
between RM0.05 - RM0.09.
NF5: The system must allow the customer to send a maximum of 200 messages to the driver.
5.2.3 Availability
NF6: This system must limit and all the restaurant that the time on preparing and delivering
meals.
______________________________________________________________________________
18
NF6.1: All the meals will arrive at the customer place within 45 minutes at
lunchtime(12:00 p.m. until 3:00 p.m.) and dinner time(6:00 p.m. until 9:00 p.m.).
NF7: This system needs to send a mail to inform a specific restaurant within 2 minutes while a
customer has taken down an order.
NF8: The system will allow the customer to change their order for 10 minutes.
NF8.1: After 10 minutes, the customer will not be able to change their order.
NF9: The system can only allow the customer to make a phone call for not more than 10
Minutes.
5.2.4 Security
NF10: The system will allow one user account login only on one device.
NF10.1: If the system detected there have multiple logins using the same account, the
system will force the account to log out and notice the account there has multiple
logins.
NF11: The customer shall enter the credit card information within 15 minutes, if not the system
will terminate the payment process.
NF 12: A tablet login waiter password must have at least 64 bits of bit strength.
NF13: It is necessary to change the password used for wireless communication every three
months.
NF14: To monitor tablet operating status, the system shall use regular 30-second keep-alive
emails between devices and the server.
NF15:The system must log each surface computer, tablet and display state and state shift to
provide recovery from system failure.
______________________________________________________________________________
19
5.2.5 Distance constraints

NF16: The system will assign orders to drivers that are within 10km to the restaurant that has an
order.
NF16.1: If there is no driver within 10km, it will assign the nearest driver to collect the
order.
NF17: The system will calculate the estimated time which is the sum of the purchasing time and
delivery time.
5.2.6 Flexibility
NF18: When the order is made from a phone call, the system shall be able to record the
information of the customers such as customer’s name, address, phone number, and order
history on the first order.
NF19: The system shall be able to record the conversation between customer service and
customer in 266-320kbps, MP3 within 10 minutes.
NF20: The system shall store the information of the customer while ordering the food.
NF20.1: Using this information, managers will know the most-picked food in the system.
______________________________________________________________________________
20
5.3 Constraints
C1: This system will only allow halal restaurants to use their services.
C1.1: In Malaysia, Waiters on Wheels organization needs to respect for culture such as
Muslim cannot eat pork.
C2: The system has to restrict the total price of meals.
C2.1: The restaurant has set a rule of delivery, that is a customer has ordered a meal
within RM20, this customer needs to pay the delivery fees otherwise the restaurant
offers free delivery on that order.
C3: The system will only show a restaurant that is in range.
C3.1: Restaurants that are further than 20km from Waiters on Wheels.
C4: The system will only be able to receive a limited amount of orders from the customers.
C4.1: The system can only accept one thousand orders at any given time.
C5: The system will only deliver orders to customers in a certain range.
C5.1: The system will only accept orders from customers that are within 20km from
Waiters on Wheels.
C6: The system will only allow customers to order meals in limited menu choices.
C6.1: Other restaurants have to do the registration from Waiters on Wheels restaurant to
add a new menu in the system.
C7: The system only allows one cell phone number can only register one account.
C8: The system shall not accept two or more promo code used in a single order.
C9: The customer shall not be able to place an order from two different restaurants.
C10: The ordering system will only operate on business hours from 10 am to 10 pm.
______________________________________________________________________________
21
6.0 Scenario Modelling
6.1 Use Case Diagram

In this use case diagram, the food ordering system can be ordered via telephone or via online.
Diagram 6.1 shows the use case diagram of Waiters on Wheels' Food Ordering System
______________________________________________________________________________
22
6.2 Use Case Specification
Use case Login
Brief Description Allows the user to access to the system
Actors Customers
Preconditions The user must have an existing account
Basic Flow 1) Access to the website

2) Login into the account
3) Enter username and password
4) Login successful
5) Make order
Alternative Flows 2.1) Register an account

3.1) Invalid username and password
Use case Place a call
Brief Description Allows customer to call for the delivery
Actors Customer
Preconditions The user must have a mobile phone
Basic Flow 1) View menu

2) Make call
3) Select Restaurant
4) Make orders
Alternative Flows 2.1) Call rejected

2.2) Call is unavailable
______________________________________________________________________________
23
Use case Create order
Brief Description Allows the customer to create a new order
Actors Customer
Preconditions The user must login into personal account
Basic Flow 1) Select restaurant

2) View menu
3) Add items to carts
4) Complete order
5) Select payment
6) Select address
7) Confirm order
Alternative Flows -
Use case Make Payment
Brief Description Allows admin to receive the payment from the customer
Actors Customer
Preconditions Customer must make an order
Basic Flow 1) Select payment option

2) Enter cash in slot
3) Driver collect cash
4) Return change
5)Payment verification
6) Receive bill
Alternative Flows 1.1) Card payment

1.1.1) Prompt to enter card number
1.1.2) Enter pin and verify
______________________________________________________________________________
24
Use case View orders
Brief Description Enable user to view the recent order
Actors Customer
Preconditions User must create an order
Basic Flow 1) Access website

2) Login
3) View order status
4) Check the order
Alternative Flows 4.1) Edit order details

4.1.1) Give new details
Use case Confirming orders
Brief Description Allows the admin to confirm the item and driver are still available
Actors Driver and restaurant employee
Preconditions Admin must send the order details
Basic Flow 1) Receive order

2) Select Restaurant
3) Send order
4) Check availability
5) Confirm order
6) Notify Customer
Alternative Flows 4.1) Restaurant in busy

4,2) No driver in the area
______________________________________________________________________________
25
Use case Check to deliver status
Brief Description Allows admin to confirm the order is in available
Actors Admin
Preconditions Customer must make an order via website or via telephone
Basic Flow 1) Access to the website

2) Click on the track my order
3) Enter the tracking number
4) Check delivering status
Alternative Flows 3.1) Tracking number enter wrongly

3.2) Tracking number does not exist
Use case Accept Incoming Calls
Brief Description Allows the customer service to provide service in the call
Actors Customer Service
Preconditions User must have a mobile devices
Basic Flow 1) Wait for calls

2) Get customer details
3) Check for order
5) End call
Alternative Flows 3.1) Create a new order
______________________________________________________________________________
26
Use case Update Menu
Brief Description Allows admin to add, remove or edit the items in the menu
Actors Admin
Preconditions Admin must login with admin account
Basic Flow 1) Login to the system

2) Enter password
3) Save Menu
4) Update Menu
5) Log out
Alternative Flows 2.1) Password Invalid

2.2) Change Password
Use case Generating Report
Brief Description Allows admin to view the monthly profit
Actors Admin
Preconditions System must have sales and orders data
Basic Flow 1) Order details

2) Generate sales report
3) Generate orders report
4) View report
Alternative Flows -
______________________________________________________________________________
27
Use case Manage payment
Brief Description Allows the admin to manage the transaction in an order
Actors Admin
Preconditions Payment must receive on online or in cash
Basic Flow 1) Collect Sales money

2) Collect payment for restaurant and driver
3) Calculate income
4) Pay for expenses and deposits
5) Make Payment
Alternative Flows -
______________________________________________________________________________
28
7.0 Data Modelling

The data models that will be shown in the latter part of this project will be the ERD, activity
diagram and DFD.
7.1 Entity Relationship Diagram

An ERD is a data modeling technique that graphically shows relationships between entities in an
information system.
Diagram 7.1 Waiters on Wheels of Delivering Food System
______________________________________________________________________________
29
8.0 Functional Modeling

Functional modeling is a structured representation of functions (i.e. activities, actions, processes,
operations) within the system.
8.1 DFD Level 0

A level 0 data flow diagram (DFD) shows a data system and how the data is flowing within the
system. The arrows in the diagram show the direction to which the data is going. This DFD level
0 based on diagram8.1.1 shows how such a system might function within Waiters On Wheels.
Diagram 8.1.1 Waiters on Wheels of Delivering Food System
______________________________________________________________________________
30
9.0 Behavioral Modeling

Behavior Modeling is a component of the Social Learning Theory. It is guiding the employee
how to do something like showing them the standard modeled behavior.
9.1 Activity Diagram

Activity Diagrams describe how activities are coordinated to provide a service which can be at
different levels of abstraction.
9.1.1 Login
Diagram 9.1.1 Activity Diagram for Login
______________________________________________________________________________
31
9.1.2 Place a Call
Diagram 9.1.2 Activity Diagram for Place a Call
______________________________________________________________________________
32
9.1.3 Create Order
Diagram 9.1.3 Activity Diagram for Create Order
______________________________________________________________________________
33
9.1.4 Make Payment
Diagram 9.1.4 Activity Diagram for Make Payment
______________________________________________________________________________
34
9.1.5 View Orders
Diagram 9.1.5 Activity Diagram for View Orders
______________________________________________________________________________
35
9.1.6 Confirming Orders
Diagram 9.1.6 Activity Diagram for Confirming Orders
______________________________________________________________________________
36
9.1.7 Check Delivering Status
Diagram 9.1.7 Activity Diagram for Check Delivering Status
______________________________________________________________________________
37
9.1.8 Accept Incoming Phone Calls
Diagram 9.1.8 Activity Diagram for Accept Incoming Phone Calls
______________________________________________________________________________
38
9.1.9 Update Menu
Diagram 9.1.9 Activity Diagram for Update Menu
______________________________________________________________________________
39
9.1.10 Generating Report
Diagram 9.1.10 Activity Diagram for Generating Report
______________________________________________________________________________
40
9.1.11 Manage Payment
Diagram 9.1.11 Activity Diagram for Manage Payment
______________________________________________________________________________
41
10.0 Requirements Validation

Requirements validation is a process of checking the requirement definitions reflect all the needs
of customers. System consultants need to perform requirements validation to check issues on any
requirements and also use requirement validation to analysis the error in the initial phase of
project development. If system consultants did not detect the error in the initial phase, the error
may cause a huge problem and increase rework. To perform requirement validation, system
consultants have to decide which validation to perform. There a few types of requirement
validation and there are walkthroughs, review, prototyping and others. (WORDPRESS, 2019)
10.1 Types of Requirement Validation
10.1.1 Walkthroughs
Walkthroughs is a way to valid requirements. It can check the ideas of system consultant in
deciding which requirements are feasible to implement in the project early with the stakeholder
of Waiters on Wheels company. In this way, system consultant can achieve some opinions and
suggestions from stakeholders. Walkthroughs can also use to check what has been approved by
stakeholders while implementing requirements for reaching the agreement. (skc161931, 2019)
10.1.2 Review
Besides, system consultants will provide the requirements review that requires from managers --
Sue and Tom Bickfords, and the review team of the Waiters on Wheels organization. The review
team consists of systematic analyzers, software engineering, and managers to examine the
document and ensure the problem of requirement associated with omissions and errors have
detected and corrected by system consultant. (DINESH, T., 2019)
______________________________________________________________________________
42
10.1.3 Prototype
Moreover, system consultant will provide the prototype of the system for the Waiters on Wheels
organization to determine whether the system meets their requirements. This action will help
system consultants to collect feedback about the requirement of clients and modify the system
before presents it to end-user. (DINESH, T., 2019)
10.2 Requirement Validation for Organization

System consultants have chosen those three ways to validate the requirement in the system. By
using the way of walkthroughs, it is used to discuss the idea of system consultant in developing
the requirements with the stakeholders of Waiters on Wheels company. System consultants need
to walkthroughs with stakeholders because the system will have many functions while system
consultant implementing it. To avoid rework on the system, system consultants need to
walkthrough with stakeholders to know the needs of stakeholders in more detail.
Furthermore, system consultants also have decided to provide reviews for a review team of
Waiters on Wheels organization. Providing the reviews is very important because system
consultant might neglect some small problems in the system and it will cause the whole system
paralyzed. In this case, the review team is an important team to detect the problem in the system
and inform system consultants to correct the problem.
In addition, providing a prototype of the system for Waiters on Wheels organization to check
whether the system has included the requirement of the stakeholders such as the function, the
graphics, the design, and others. If system consultants did not provide the prototype of the
system to the clients. After the system has fully implemented but the system did not meet the
needs of clients. So, system consultants need to take time to redo the whole system or modify it.
______________________________________________________________________________
43
To put all in a nutshell, these techniques of requirement validation are very important for
checking the system has met the needs of clients or not. Without validating the requirement,
system consultants may create a system that did not satisfy clients’ needs.
______________________________________________________________________________
44
11.0 Requirements Management

Requirements management is the method by which product requirements are collected, analyzed,
refined and prioritized and then planned for shipment. Requirements management is intended to
guarantee that the organization validates and meets its customers' and external and internal
stakeholders ' needs. Management of demands includes communication between project team
members and stakeholders and adjustment throughout the course of the project to modifications
in demands. Constant communication between development team members is critical to
preventing one class of demands from overriding another. Management of requirements does not
end with the release of the item. From that stage on, the information about the acceptability of
the application will be collected and fed into the next generation or release investigation stage.
This is how the method starts again.
A requirement is a specified capacity that should fulfill the outcomes of some job (in this case
software development). It is a continuous process throughout a product's life cycle and many
stakeholders can generate requirements including customers, partners, sales, support,
management, engineering, operations, and, of course, product management. There is clear and
coherent communication between the product team and engineering members when
specifications are correctly curated and managed and any necessary modifications are widely
communicated with all stakeholders. （Aha!, 2019)
______________________________________________________________________________
45
11.1 Requirements Traceability
Diagram 11.1 Requirements Traceability
Traceability is one of the most significant parts of requirement leadership. Tracing enables us to
know why there is a necessity, the effect of change if the set of demands is full, and helps
prioritize demands. Diagram 11.1 demonstrates how traceability begins with the
outcomes/benefits and traces of the company demands through stakeholder demands, solution
requirements, additional / non-functional requirements, and down into test scenarios and test
cases. Tracing complexity could be very easy or quite comprehensive. It really relies on the
organization's maturity and the organizations with which you work. You can see the quantity of
high-level demands is quite low, but as you go down, you go down to a reduced granularity level
where the quantity will grow. However, understanding how they connect back to the top is
critically crucial.
______________________________________________________________________________
46
11.2 Requirements Versioning
Requirements versioning is the process by which all changes to a specific requirement are
documented and maintained. The main aim of versioning a specific requirement is to assist
guarantee that the project team works from exactly the same necessity. To increase modifications
to a necessity, versioning is essential. This is probably something you won't do on an ongoing
basis unless you use a requirements management tool. Important demands can alter several
times-10, 20, 50 times, and this can happen throughout the project's entire lifecycle. It is essential
to monitor which version of the requirement and the specifics of the modifications to the
requirement. This enables you to connect it to the proprietor who made the shift.
Other versioning objectives include:
● Enable the project team to determine how and why over time a requirement has shifted.
● Help guarantee that the proper version of the specifications is reviewed and not an old
version
11.3 Requirements Baseline

A baseline is a foundation for comparison over a period of time between demands (all or
sub-set); it is a "snapshot" of demands (not a one-time event). Each project should define a
baseline strategy involving the definition of the baseline in terms of creation, frequency, content,
and publication. A baseline is a vehicle for communicating changes in the details of requirements
to interested parties. Baselining is a system at a specific stage in time to package a set of
demands and pass it on to the next group in the project team. Specifying when to establish a
baseline and how often they will be linked to official project milestones is essential in the
requirement management plan. It is also necessary to specify the content of the baseline and how
it will be released.
______________________________________________________________________________
47
The significant thing is that this upfront planning is the requirements management plan. We're
trying to make sure we've planned these activities and as we move through the project's
application lifecycle, we don't want these choices to be made as we get to critical distribution
points. A baseline can be formal or informal.
● Formal – A prescribed project milestone with formal recognition of demands (all
requirement characteristics must be filled in and specifications validated as full,
unambiguous and verifiable)
● Informal – Agreement between project team members that specifications are right at the
moment (minimum set of required characteristics must be filled in)
Balance the baseline amount with the size of the project. Once the official baseline has been
developed, any modifications to any of these criteria must be addressed by the change
management procedure of the project.
11.4 Communication of Requirements Changes
A change control method should be associated with the communication strategy for
modifications to demands.
● Processes in waterfalls treat evolving demands as an exception
● Iterative and agile processes adapt to changing demands
A solid communications approach will make it easier for inner and external organizations to
audit demands to assist guarantee that the solution supplied correctly reflects demands. If you
work in a complicated setting with many inner stakeholders and external stakeholders, a
successful communications approach is particularly crucial. Your communication strategy
requires to be some kind of plan around a technique of communication, and it needs to be a
process that can be repeated. It has to be formalized in the plan. This will assist to make sure it
______________________________________________________________________________
48
can be repeated. It will be quite complicated on big projects. It'll be fairly simple on bigger
projects, but it's essential to think about it. Change requirements, as it is inevitable as
requirements are validated and verified. Control, however, changes closely in order to manage it.
______________________________________________________________________________
49
12.0 Conclusion
In this system, there is still need lots of improvement such as optimization the interface, makes
the system more user-friendly, and others but all of these improvements have to meet
requirements of the company. This system has the basic function of an online delivery system.
However, these basic functions cannot attract a huge number of people to use this system. The
system must have additional functions such as reward customers that ordered meals for numbers
of time, play minigame of the system to win rewards or others. In this way, the online delivery
system will be more interesting and attract more people to use it. By adding additional features,
system consultants have to ask for permission or option of the idea that system consultants
before the additional features implemented.
In this assignment, system consultants will know the requirements of the client are very
important before designing a system because the client will define the system that has been
developed is a useful or useless system. The basic function of the system, according to the
client’s needs in the system. For example, system consultant has developed an online delivery
tracking system but this system does not have the cancel order function that client needed.
Therefore, system consultants need to modify the system. In this case, if the system missed a part
of the required function, system consultants can modify it but if the system missed all
requirements of the client, system consultant will need to redo the whole system. So, the
requirement of the client can make changes to the whole system.
To put all in a nutshell, system consultants have to understand all the needs of the client before
implementing a system.
______________________________________________________________________________
50
13.0 References
Aha!. (2019) Introduction to Requirements Management. [Online] Available at:
https://www.aha.io/roadmapping/guide/requirements-management [Accessed Date: 3 August
2019].
DINESH, T. (2019) Requirements Validation in Software Engineering. [Online] Available at:

http://ecomputernotes.com/software-engineering/requirementsvalid/ [Accessed: 17 July 2019].
OfniSystems. (2019) Functional Requirements. [Online] Available at:

http://www.ofnisystems.com/services/validation/functional-requirements/
[Accessed: 14 July 2019].
PMI. (2019) Requirements management- planning for success. [Online] Available at:
https://www.pmi.org/learning/library/requirements-management-planning-for-success-9669
[Accessed Date: 3 August 2019].
Masters, M. (2019) The Top Five Go-To Requirements Elicitation Methods. [Online] Available
at:
https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/2483/The-Top-Five-Go-To-Re
quirements-Elicitation-Methods.aspx [Accessed: 21 July 2019].
Modernanalyst. (n.d.). An Overview of Requirements Elicitation > Business Analyst Community

& Resources | Modern Analyst. [online] Available at:
https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/1427/An-Overview-of-Require
ments-Elicitation.aspx [Accessed 5 Aug. 2019].
skc161931. (2019) Software Engineering | Requirements Validation Techniques. [Online]

Available at:
https://www.geeksforgeeks.org/software-engineering-requirements-validation-techniques/
[Accessed: 17 July 2019].
______________________________________________________________________________
51
Techopedia. (2019) System Analysis. [Online] Available at:

https://www.techopedia.com/definition/9611/systems-analysis [Accessed Date: 3 August 2019]
UKESSAYS. (2019) The Problem In Existing System Information Technology Essay. [Online]
Available at:
https://www.ukessays.com/essays/information-technology/the-problem-in-existing-system-infor
mation-technology-essay.php [Accessed Date: 3 August 2019].
Visual-paradigm.com. (n.d.). Requirement Analysis Techniques. [online] Available at:

https://www.visual-paradigm.com/guide/requirements-gathering/requirement-analysis-techniques
/ [Accessed 5 Aug. 2019].
WORDPRESS. (2019) VALIDATION. [Online] Available at:

https://requirementstechniques.wordpress.com/validation/ [Accessed: 17 July 2019].
______________________________________________________________________________
52

Reng (A)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Reng (A)

Uploaded by

Copyright:

Available Formats

Module Code : CT056-3-2-REQUIREMENT ENGINEERING

Intake Code : UC2F1905SE

Lecturer Name : LAI CHEW PING

Hand in Date : 5 AUGUST 2019

Tutorial No. : T2/ T3

System Name : Computerized Delivery Tracking System

Student ID Student Name

TP046721 LIM KING WAY

TP050678 TAN FENG QI

TP050399 TAN ZHI XIN

TP050757 TEY WEN YAN

Criteria Lim King Tan Tan Zhi Tey Wen

Project Introduction: Vision and Goals of new system 50% - 50% -

System Analysis: 25% 25% 25% 25%

Requirements Elicitation: 25% 25% 25% 25%

Software Requirements Specification: 25% 25% 25% 25%

Scenario Modelling: 25% 25% 25% 25%

Data Modelling: - 50% - 50%

Functional Modelling: 50% - 50% -

Behavioral Modelling: 25% 25% 25% 25%

Requirements Validation 25% 25% 25% 25%

Conclusion - 50% - 50%

1.1 Organization Background…………………………………………………………………………..5

1.1. Vision and Goals of the new system……………………………………………………………... 6

12.0 Gantt Chart Project Planning…………………………………………………………………….. 7

3.0 System Analysis………………………………………………………………………………………. 8

3.1 Problems in Existing System……………………………………………………………………... 9

3.1.1 Cannot Upload and Download the latest updates…………………………………………... 9

3.1.2 Communication between customer and owner is not directly……………………………... 10

3.1.3 The manual system need manpower a lot………………………………………………….. 10

3.1.4 In a big organization, it is a time-consuming process…………………………………….... 11

4.0 Requirement Elicitation…………………………………………………………………………….. 12

4.1 Requirements Source…………………………………………………………………………….. 12

4.2 Elicitation Techniques……………………………………………………………………………. 13

5.0 Software Requirements Specification…………………………………………………………….... 15

5.1 Functional Requirements…………………………………………………………………………. 15

5.1.6 Customer Service………………………………………………………………………….. 17

5.2 Non-functional Requirements……………………………………………………………………. 18

5.2.5 Distance constraints………………………………………………………………………... 20

6.0 Scenario Modelling…………………………………………………………………………………. 22

6.1 Use Case Diagram……………………………………………………………………………….. 22

6.2 Use Case Specification…………………………………………………………………………... 23

7.0 Data Modelling…………………………………………………………………………………….... 29

7.1 Entity Relationship Diagram…………………………………………………………………….. 29

8.0 Functional Modeling………………………………………………………………………………... 30

8.1 DFD Level 0……………………………………………………………………………………. 30

9.0 Behavioral Modeling………………………………………………………………………………... 31

9.1 Activity Diagram…………………………………………………………………………………. 31

9.1.2 Place a Call……………………………………………………………………………….... 32

9.1.3 Create Order……………………………………………………………………………….. 33

9.1.4 Make Payment…………………………………………………………………………….. 34

9.1.5 View Orders……………………………………………………………………………….. 35

9.1.6 Confirming Orders……………………………………………………………………….... 36

9.1.7 Check Delivering Status………………………………………………………………….... 37

9.1.8 Accept Incoming Phone Calls……………………………………………………………... 38

9.1.9 Update Menu……………………………………………………………………………….39

9.1.10 Generating Report………………………………………………………………………... 40

9.1.11 Manage Payment………………………………………………………………………….. 41

10.0 Requirements Validation………………………………………………………………………….. 42

10.1 Types of Requirement Validation………………………………………………………………. 42

10.2 Requirement Validation for Organization 43

11.0 Requirements Management 45