Requirements Gathering and Analysis for Assorted Bakery System

This report focuses on the requirements gathering and analysis for the development of an Australian Assorted Bakery (AAB) system, a family enterprise aiming to improve performance and manage essential information. It outlines both functional and non-functional requirements, detailing aspects such as product information, user registration, login, seat reservation, order placement, delivery, and payment processing. The report includes a use case diagram illustrating interactions between actors (admin and users), along with detailed descriptions of use cases like registration, login, product search, cart management, checkout, and order history. Furthermore, it presents state machine diagrams for selected use cases and sequence diagrams to visualize object interactions within the system, emphasizing the importance of usability, performance, and security in the bakery system's design and development. Desklib provides access to this and other solved assignments for students.

Assessment Item 2 - Requirements
Gathering
1

Contents
INTRODUCTION...........................................................................................................................3
TASK 1............................................................................................................................................4
Functional and Non-Functional requirements for proposed Australian Assorted Bakery System
.....................................................................................................................................................4
TASK 2............................................................................................................................................6
Use case diagram for Assorted Bakery System...........................................................................6
TASK 3..........................................................................................................................................14
Selecting two use cases and develop state machine diagram....................................................14
TASK 4..........................................................................................................................................15
Identify three use cases identified in task 2 and develop Sequence diagram for each use cases.
...................................................................................................................................................15
Sequence Diagram-....................................................................................................................15
CONCLUSION..............................................................................................................................16
REFERENCES..............................................................................................................................17
2

INTRODUCTION
In this report, it is basically focused on the Australian Assorted Bakery (AAB) as family
enterprise that produce a delicious & fresh baked items across Australia. The company will focus
on the improving the performance and keep record all necessary information such as financial
transaction, activities of store, responsibilities of staff members.
This documentation will describe about functional as well as Non-functional requirements
for proposed Australian Assorted Bakery System. Furthermore, it will produce use case
diagrams, identify the involvement of different actors, user interface. Moreover, it will be
selecting two different use cases and then develop state machine diagram. Identify use cases and
also develop sequence diagram for each use cases.
Overview-
The primary aim of this report is to gather, collect, analyse and provide a consistent or
complete description of requirements. Bakery system helps to manage and control all kind of
online transaction in systematic manner. Thus, it is beneficial for both potential consumers and
sellers. On the other hand, it will be developed the Australian Assorted Bakery system or
application. It keep update, maintain all relevant information or data. Usually, this system can
work into two main part:-
Client side- in this part, it has included all features that help user to select as core function of
website. Basically, it involves login, register, view or search product, add into cart, checkout etc.
These are important functionality of bakery system and should be include in the Bakery system
(Irawati and Hin, 2020).
Server Side- in this part, it consists of multiple features to manage and control updated
information within system. Usually, it has performed the different operations such as remove
item, add, search, view order and change status etc.
3

TASK 1
Functional and Non-Functional requirements for proposed Australian Assorted Bakery System
A functional requirement defines a system or its particular component whereas non-
functional requirement defines the entire performance attribute of software system. In Australian
Assorted bakery system, Functional requirements should relate to the different tasks and then
perform database system (Cariou, Brunschwig and Barbier, 2020). Generally, it also established
the form of searching and sorting different queries. Functional requirements are provided the
brief ideas around data that must be held in MySQL.
Functional Requirements
Product information or data-
 To show all menu and price of every items such as cakes, Foods and Beverage. This will
help to access full detailed of different products.
Register or sign up-
 For performed the subscription within specific deadline, archive information or data in
context of shipping.
Login and log out-
 Successful enter personal information into web page and get order, promotion of various
kind of items. User can also exit from order page.
Seat Reservation-
 For purpose of booking, it is important to reserve a seat in advance. But it is depending
on how table is empty.
Order in advance-
 To order food in advance for those people who have already confirmed their booking.
4

Delivery-
 Sometimes, Bakery shop will provide the facility of delivery at home.
Payment-
 Consumer can do payment through credit card.
Check point-
 For different members of shop, it will get an opportunity of good deal.
Contact us-
 For purpose of established a good coordination between consumer and shopper who have
finding the problem, like to know the information.
Non-Functional Requirements
Non-functional requirements are considered as capacity, availability, reliability,
scalability, data integrity and scalability capacity. These are playing an important role to
represent overall performance of Australian Assorted bakery system. Non-functional
requirements play an important role in system design and development (Sugina and Noviyanti,
2020). It server as constraints or restrictions on the design of system across the multiple
backlogs. It ensure that usability and effectiveness of bakery system.
Usability-
 The system must be easy to use by manager and staff members as they do not require an
extensive amount of manuals.
 The Bakery system must be quickly accessible by both manager and staff members.
 Menu of Bakery Shop must be easily navigable by users with clicks on the button.
Therefore, it can easily develop more understanding towards system.
Performance-
 The system will be stored all information because of staff members, they do not have
down time to wait for particular action.
 It keep update the databases, adding ingredient, vendor and occasion successfully every
time on the bass of requests.
5

 All functionality of system can be handled and used by users every time.
Security-
 It assess that secure or protect the security of system and maintain user’s confidential data
or information.
 Maintainability- it can be used the better coding conventions, follow-up documents for
purpose of maintenance activities.
TASK 2
Use case diagram for Assorted Bakery System
A use case diagram is based on the graphical depiction of user’s possible interaction with
system. The importance of use case diagram which means that represent as various use cases,
types of users in system (Jbara, Bibliowicz and Dori, 2020). It often be accomplished by other
kind of process but it will be representing in the form of graphical manner.
A use case diagram is the best option that help to show a dynamic behaviour of entire
system. It means that encapsulates the system’s functionality by incorporating a use cases, actors
and their relationships. It may be considered as model of tasks, services and functions required
by Australian Assorted bakery system of an application.
6

Figure 1 Use Case Diagram
In Figure-1, it has represented the use case diagram of Assorted Bakery System and identify two
actors such as Admin and user. Both are establishing an interaction between each other. User can
consumers, staff members and admin can handle the entire processing of bakery system, keep
update, maintain information within system.
7

Use Case-1 registered
Use Case Name Registration process
Actor User
Description User can access system to register a new
account and get access functions of Bakery
system.
Precondition User can enter the website
Post Condition A new user is also created their account and
saved information within database
Workflow  User lick on the login option
 Display a login form where user can
enter details.
 User fill the form and confirm process
of registration
 Successfully created a new account
Alternative Flow N/A
Exception The information is either incomplete or invalid
point. It prompt the error to user and go back
initial step.
Table: 1
8

Use Case-2 Login account
Use Case Name Login account
Actor User
Description User can access system to login account by
using username, password and get access
functions of Bakery system.
Precondition User needs to do register account on the
system
Post Condition A new user is login the account and saved
information within database
Workflow  User lick on the login option
 Display a login form where user can
enter details.
 Enter user name and password
 Submit details
 Successfully login their own account
Alternative Flow N/A
Exception The information is either incomplete or invalid
point. It prompt the error to user and go back
initial step.
Table: 2
9

Use Case-3 search, Add product to Cart
Use Case Name Search and add product to cart
Actor User
Description User can login account by using username,
password and then search, add bakery item in
their cart.
Precondition User needs to login the account on the system
Post Condition User can identify the desired product according
to the interest, preferences of client.
Workflow  User click on the search option
 Display a variety of product lists and
their full information detailed.
 User can easily select item and add into
cart
Alternative Flow N/A
Exception The information is either incomplete or invalid
point. It prompt the error to user and go back
initial step.
Table: 3
10

Use Case-4
Use Case Name Change the quantity of product in cart
Actor User
Description User can change the quantity of selected item
in cart
Precondition User needs to login the account on the system
Add the one or more bakery item in cart
Post Condition It keep update that quantity of selected item in
cart is change according to demand of user’s.
Workflow  User click on cart
 Display a variety of product lists and
their full information detailed.
 User can easily select another item and
add into cart
Alternative Flow N/A
Exception The information is either incomplete or invalid
point. It prompt the error to user and go back
initial step.
Table: 4
11

Use Case-5
Use Case Name Check out process
Actor User
Description User can confirm their item and further move
towards check out process
Precondition User needs to login the account on the system
Add the one or more bakery item in cart.
User move towards shipping address and
update their phone number.
Post Condition It keep update that quantity of selected item in
cart is change. Sending all updated information
to the system server
Workflow  User click on cart
 Display a variety of product lists and
their full information detailed.
 Select and confirm order
 Sent detailed of order to server
Alternative Flow N/A
Exception The information is either incomplete or invalid
point. It prompt the error to user and go back
initial step.
Table: 5
12