1.

Requirement Elicitation
1.1. Requirement Sources
1.1.1. Human
To begin with, the developer team need to collect the requirement from the
client, in this case is Tom and Sue as the owner of Waiter on Wheels Restaurant.
However, they are not the only one who will suggest for the requirement, employees
and the customers also need to be involved in this requirement gathering because their
opinion and suggestion are important for developing the system. Developer do not
want to create the system that only prefer for one side only, they need to develop the
system that suitable for all the users so, it can maintain the relationship between the
customer and the restaurant itself. For example, the UI for each user is different,
because it depends on the function for each type of user.

1.1.2. Existing System

Determined the requirement from the existing system is also important. The
existing system function can be the foundation for developing the next system. If the
user still comfortable with some of the function from the current system, developer
team might consider using or improve the functions for example, adding more
function to it or even update the UI. Moreover, using the same function from the
current system may reduce the workload for the development team and finish the
project on time or even faster than the current due date.

1.1.3. Document
Every system has their own documentation. Documentation of system provide
every detail of the current system that have been implemented, such as the
functionality, features and tools for developing the system. Using a document as a
source is important for determining the suitable requirement. The reason is document
can provide more detail information compared to the user such as customer, staff and
owner because some of them did not understand in term of technical of the system.

1.1.4. Forms
Using form as a requirement resource is also one of the choice. For instance,
Tom and Sue as an owner already proposed the requirement to the developer but that
requirement itself might not enough. The developer team can collect some
 requirement by analysing the customer or staff answer in a form that already
distributed.

1.2. Elicitation Technique

1.2.1. Document Analysis
Analysing the document is one way of elicitation technique. Every system must
have their own documentation that consist of features and functionalities of the
system. It describes the act of reviewing and existing documentation of systems or
business processes to find information for a current project (Chris Adams, 2010).
Using the documentation of the old system that currently use by Waiters on
Wheels and analysing every functions and features. The developer team will take
notes every function and feature that used in the current system and discussed it with
the owner and other user. By discussing it with the user, the developer team will know
which functions and features that unused, needed or need to improve.

1.2.2. Surveys/Questionnaire
Surveys or questionnaire is one of the method to collecting requirement from
the users by creating some questions. It preferable for large number of stakeholder or
the interviewees are having a different activity and cannot be gathered in one place at
the same time (modernanalyst,2013). Besides, conducting questionnaires can
minimize the survey cost for organization which is recommended for this restaurant.
To implementing this technique, developer team can use QR code that available
on the driver of restaurant and shared by the driver and make sure it scanned by every
user. The QR code will redirect the user into a questionnaire page. Another way is
using a shareable link and share it to the stakeholder, such as customer, staff and the
owner itself. Using this method, collecting the requirement will be fast because every
user can access it right away.
Example of survey questions:
1. How satisfied is today service? (Scale measuring from 1 to 5)
2. Does the rider send the food at accurate timing? (Scale measuring from
1 to 5)
1.2.3. Brainstorming
Brainstorming is also popular method of elicit requirements. Brainstorming is
an exceptional method of eliciting that producing a different new idea and solution
from a certain problem (AnAr Corporate, 2018). Basically, there are several ways for
conducting this method. Some of the organisations used an individual brainstorming,
which is each person need to think a solution or idea by themselves that not represent
for a team. In the end, all person has their own idea and solution which is when it
gathered together, they have many ideas to be considered as an option. The other way
is group brainstorming. In this session, people will be gathered in a group and think
for several innovative ideas. The different between individual brainstorming is this
group session might produce fewer ideas compared to individual because every person
might not need to give one idea to be discussed. However, it faster to conclude which
idea that will be implemented and which one is not because everyone in the group or
team can express their thought directly and discussed it right away.
In this case, the developer team can manage an appointment with Tom and Sue
as a stakeholder. In this meeting, Tom and Sue can express their dissatisfaction about
the current system. From this feedback, the developer team produce the solutions for
the problem.

Example of topic that discussed:

 Payment method
- Which one is preferable, wait for driver to pick up the food until it
arrived then pay it or pay online after finish with ordering the food or
drink? why?
- If this system using an online payment, then what kind of payment that
will be acceptable? Is it using the e-money that need to be recharge or
top-up first if there is no balance or using directly a credit card or master
card for every ordering? and is there any way to make sure the online
payment is safety? How?
- If the system is using a manual payment, imagine if you guys are the
driver. What will you do if you guys don’t have a change
  Tracking System
- why tracking system is important? give advantage and disadvantage for
each function.
- Is this system important for the whole system or is this just a waste?
why is it beneficial? how to maintain it?

Adams, Chris (2010). What is Document Analysis? [online] Available at:

https://www.modernanalyst.com/Careers/InterviewQuestions/tabid/128/ID/1610/What-is-
Document-Analysis.aspx [Accessed 4 December 2019].

modernanalyst (2013). 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-Requirements-Elicitation-Methods.aspx [Accessed 4 December 2019]

AnAr Corporate (2018). Top 5 Requirements Elicitation Techniques. [online] Available at:
http://www.anarsolutions.com/top-5-requirements-elicitation-techniques/ [Accessed 4
December 2019]