Elicitation Document
for
Ordering App
Version 1.0 approved
Prepared by
26/05/2021
Elicitation Document for Ordering App Page ii
Table of Contents
Table of Contents................................................................................................................ii
Revision History..................................................................................................................ii
1. Introduction....................................................................................................................1
2. Domain description........................................................................................................1
2.1. Glossary (terms and acronyms)..............................................................................1
2.2. General knowledge about the domain (including competing systems)..................1
2.3. Environment and context........................................................................................1
3. Initial description of the problem..................................................................................1
3.1. Description of stakeholders and their goals...........................................................1
3.2. Description of the system scope.............................................................................1
3.3. Main Features/Functionalities................................................................................1
3.4. Preliminary requirements.......................................................................................1
3.5. Constraints..............................................................................................................1
3.6. Risks.......................................................................................................................1
4. Aspects needing clarifications.......................................................................................1
5. Business Context...........................................................................................................1
5.1. Stakeholder Profiles...............................................................................................1
5.2. Project Priorities.....................................................................................................2
5.3. Operating Environment..........................................................................................3
5.4. Description of team and roles.................................................................................3
6. Appendix A....................................................................................................................3
Revision History
Name Date Reason For Changes Version
26/05/2021 Initial draft 1.0 draft 1
29/05/2021 baseline following changes after inspection 1.0 approved
Elicitation Document for Ordering App Page 1
1. Introduction
In the advanced technology world, it is extremely difficult to start a new small-scale
business and live-through the competition from the well-established and settled owners.
In the fast-paced time of today, when everyone is squeezed for time, the majority of
people are finicky when it comes to placing a food order. The customers of today are not
only attracted because placing an order online is very convenient but also because they
have visibility into the items offered, price and extremely simplified navigation for the
order.
The Ordering App system that I am creating here, greatly simplified the process of
ordering for both customers and vendors. This system presents an interactive and up-to-
date menu with all available options in an easy way to use.
2. Domain description
2.1. Glossary (terms and acronyms)
Acronyms Description
Ordering App (O/A) This app allows users to place food items on
app.
Cart Where customers can put all the temporary
items that they’ve chosen.
GUI Graphical User Interface
Front End
BE Back End Server side
RI Business Risk
MC Main Constraint
FE Main Features
2.2. General knowledge about the domain (including competing systems)
The Ordering App system allows customers choose one or more items to place an order
which will land in the Cart. Customers can view all the order details in the Cart before
checking out. In addition to this, the customers can easy to remove or add more the items
in the Cart. At the end, customers will get the order confirmation details. Once the order
is placed successfully, the system will send a notification to them.
There are some competing systems such as Now, Baemin, etc, which also apply those
functions to their app. However, the Ordering App (O/A) system will slightly different
with those app, O/A system allows customers to view all the menu without login. Until
the users want to make payment to all the items that are stored in their Cart, they will
have 2 options, one is fill up the information form, and another is to create an account.
That will provide more flexibility ways for customers to use our O/A system.
Elicitation Document for Ordering App Page 2
2.3. Environment and context
The Ordering App system Front End GUI will be built on Flutter programing language,
that GUI will contain some basic layout at the first release such as login form, register
form, menu items, those can be interacted for the users to experience the app.
The Ordering App system will be connected with server-side Back End which is based on
NodeJs and ExpressJs to create some non-functional like security, authentication, routers,
authorization, etc. We will use the MongoDB database to store the vendors data, menu,
user’s data etc.
For those restaurants which are using traditional method for food ordering processes, this
is a problem that can’t be eliminated. The main goal of this Ordering App system is to
solve the problems of going directly to the restaurants to order food items. This Ordering
App system will greatly simplify the process of ordering for both customers and
restaurants.
3. Initial description of the problem
3.1. Description of stakeholders and their goals
1. Platform Owners:
Description: The main responsibility of a product owner is to ensure that
the product brings value to its customers and users, and to the company.
Roles: Develop the Product Vision, Manage the product Backlog, Define
acceptance criteria, Prioritize the needs of products, Manage development
stages, Monitor progress, Anticipate client needs.
2. Vendor Partners:
Description: The owner of stores who register on the app, list their
offerings and serve the foods once demanded.
Roles: Responsibility to provide the database of menu items to store in the
app.
3. Delivery Partners
Description: This could be the shippers of restaurants or integrate with
third-party such as Gojek, Grab, etc.
Roles: Who gets the food delivered from the restaurant to the consumer.
4. Customers:
Description: Who compare and choose food items from multiple available
sources and then place the order.
Roles: Choosing food items and placing orders.
Elicitation Document for Ordering App Page 3
3.2. Description of the system scope and Preliminary requirements
The Ordering App system will be divided into 2 parts:
For vendors part who register on the app to sell their products. Ordering App system
will allow vendors to access as a admin, on the admin vendor dashboard, they will have
the rights to add, update, delete and view the food categories, food items and price to
their menu, they can also update the additional information (description of store, photo,
etc.) for given food items and their store.
For the buyers who will use the Ordering App for shopping online purposes. They can
browse the app without having account, they can pick items from the different stores on
the app and put them into the Cart. Then they can view, delete, update, add more items in
their Cart. If they are happy with those chosen items, they can make a payment for those,
in this step, if they’ve had account already, the app will redirect them to confirmation
notification, unless the app will ask them for filling up the confirmation form to move to
the next step.
3.3. Main Features/Functionalities
Entry main functionalities web ordering system
FE-1: Create an account.
FE-2: Manage their account.
FE-3: Log in to the system.
FE-4: Navigate the category of app.
FE-5: Classify the type of products on the navigation.
FE-6: Select items from the category
FE-7: Add more items to current customers’ orders.
FE-8: Review their current cart order.
FE-9: Remove a single selected item/ remove all selected items from their current orders.
FE-10: Provide payment details.
FE-11: Place an order.
FE-12: Receive confirmation in the form of an order number.
FE-13: View order placed.
FE-14: Keep tracking the status of orders.
FE-15: Keep tracking the situation of shipper on the app on the Ordering App system.
FE-16: Integrate chat bot.
FE-17: Customize options by filtering the search engine.
FE-18: Search products.
FE-19: Write review for purchased products.
Admin dashboard main functionality web ordering system
FE-1: Add new/update/delete vendor from the app.
Elicitation Document for Ordering App Page 4
FE-2: Add new/update/delete products from the app.
FE-3: Add/new/update/delete price for a given items.
FE-4: Update additional information (description, photo, etc.) for a given product detail.
FE-5: Integrate with chat bot on social medial to response the request.
3.4. Constraints
MC-1: Not be able to compare the products among vendors on the ordering app system.
MC-2: Only shipping for the address in Vietnam.
MC-3: Not allow buyers to ask more options for the food products (example: more ice,
more sugar, etc.).
MC-4: Not provide the function of filtering by price.
3.5. Risks
RI-1: Lack of accepting for the new ordering system on market at first. (Probability =0.3;
Impact= 9)
RI-2: Not enough support capital backing to maintain the app. (Probability =0.1;
Impact = 9)
RI-3: Difficult to ensure the quality of products from vendors. (Probability =0.8; Impact
= 5)
RI-4: Unable to meet the customer needs. (Probability =0.2; Impact= 8)
RF-5: Can’t protect the privacy customers. (Probability =0.5; Impact= 3)
RF-6: Can’t control the website traffic which may causes to crash the app. (Probability
=0.3; Impact= 9)
Elicitation Document for Ordering App Page 5
4. Business Context and Aspects needing clarifications
4.1. Stakeholder Profiles
Major Value
Stakeholder Attitudes Major Interests Constraints
executives increased see product as avenue richer feature set than maximum budget
revenue to 25% increase in competitors; time to = $1.4M
market share market
Vendors Increased highly receptive, but Ease of use must run on low-
sales on the expect high usability end workstations
Ordering App
Consumers Going Highly expecting Ease of use, saving time; no budget for
shopping reduced rework retraining
online by using
Ordering App
Delivery system Shipping the highly receptive, but Having enough must run on low-
products that expect high usability information of buyers, end workstations
customers Ease of contact
placed orders
Elicitation Document for Ordering App Page 6
4.2. Project Priorities
Dimension Driver Constraint Degree of Freedom
(state objective) (state limits) (state allowable range)
Schedule release 1.0 to be overrun of up to 3 weeks
available by acceptable without sponsor
30/10/2021, release review
1.1 by 03/06/2022
Features 70-80% of high priority
features must be included in
release 1.0
Quality 95% of user 90-95% of user acceptance
acceptance tests must tests must pass for release
pass; all security tests 1.0, 95-98% for release 1.1
must pass; compliance
with corporate security
standards must be
demonstrated for all
secure transactions
Staff maximum team size is
6 developers + 4
testers, 2 BA, 2 Project
Manager, 1 Product
Owner.
Cost budget overrun up to 15%
acceptable without executive
review
4.3. Operating Environment
Hardwar Interface:
Pentium Processor
60MB of free hard-drive space
128MB of RAM
Software Interface
Operating system: Windows (Vista/7 or above)
Web Browser: IE 10 or above, Mozilla FF 31 or above, Google Chrome, Coc Coc, Safari
version 11.1 or above.
Elicitation Document for Ordering App Page 7
Drivers: V8 JavaScript Engine.
Integrated Development Environment: VS code, Visual Studio 2012 or above, VIM.
Programing Languages: JavaScript, Flutter, Nodejs.
Database: MongoDB.
4.4. Description of team and roles
Team member name Role Work Percentages of the work
done
Nguyen Minh Doan Leader Contact with 100%
partner, assign
work and role to
team members,
collect the
requirements.
Ngo Quoc Tuan Team Member collect the 100%
requirements, find
the information
about app ordering.
Nguyen Phuc Hau Team Member collect the 100%
requirements, find
the issue of app
may have
5. Appendix A
Details of questions, answers
https://docs.google.com/document/d/
1UU1KS4b4sb7TtycJs06P2fDx3lp7_Mv2vWdYHBrGEBU/edit?usp=sharing
Interview video Youtube link and Interview notes
https://drive.google.com/drive/folders/1UBHFqMQp0OUVLzFh3oBkY2ptWXE64pet?
usp=sharing
