Systems Analysis and Design Report: Wedding Parties Everything System

This report presents a comprehensive systems analysis and design of a Wedding Parties Everything (WPE) system. It begins by identifying key stakeholders and their interests within the system, followed by a detailed examination of both functional and non-functional requirements. The report utilizes the user goal technique and event decomposition to develop a series of use cases, providing a clear understanding of system interactions. A domain model class diagram is created to visually represent the system's structure, including classes, attributes, associations, and multiplicity, along with association classes and generalizations. A CRUD matrix is used to ensure consistency between the domain model and the use cases. Furthermore, the report includes a fully developed use case description for finding a caterer, an activity diagram illustrating the workflow, a system sequence diagram depicting interactions, and a state machine diagram showing possible states and transitions. Finally, a user acceptance test plan is developed for customers of the WPE system, offering a complete overview of the system's analysis and design.

Systems Analysis and Design

Table of Contents
INTRODUCTION...........................................................................................................................3
Q.1 List the main stakeholders for the wedding parties everything system and describe of their
interest in system..........................................................................................................................3
a).List and briefly describe the main functional requirement .....................................................4
b). non- functional requirements for wedding parties system.....................................................4
Q.3................................................................................................................................................4
a).Use the user goal technique to develop a list of use cases for WPE........................................4
b). Use the event decomposition technique to identify any additional use cases description. . . .7
Q.4 Create a domain model class diagram for the WPE which includes classes, attributes,
association and multiplicity. Show the association classes and generalisation. .........................8
Q.5 Create a CRUID Matrix to check the consistency between the domain model class...........9
Q.6 Create a fully developer use case description for the use case find caterer..........................9
Q.7 Draw an activity diagram to represent the flow of activities for the user cases.................10
Q.8 Draw a system sequence diagram for the use case ............................................................12
Q.9 Draw a state machine diagram to show the possible state and transition for WPE. ..........13
Q.10 Develop a user acceptance test plan for customer of WPE system..................................14
CONCLUSION..............................................................................................................................15
REFERENCES..............................................................................................................................16

INTRODUCTION
System analysis and design is a process or method for collecting and interpreting the
important facts regarding the system design, especially identifying the problem and
decomposition of system. This process is technique to improve the system requirement and also
ensure that every components of the system work in proper manner. This report will discuss
about the list of main stakeholders for the wedding parties event system and explain its interest.
Furthermore, this assignment will describe the list of functional and non-functional requirement
for WPE. It will discuss about the use cases for WPE by using the user goal technique in the
form of table. However, It will describe the event decomposition technique to determine the uses
cases and its an appropriate event types. This documentation will cover the activity diagram,
system sequence diagram and state machine diagram of Wedding, parties and event system.
Q.1 List the main stakeholders for the wedding parties everything system and describe of their
interest in system.
There are some specified main stakeholders in the wedding parties everything system that should
perform the different role in the entire system (Afzal & et.al., 2018). Every stakeholders are
performed different functions to manage the operations and functions. Food service supervisor : The Food service supervisor typically performed the different
role for managing and controlling food preparation or its overall presentation of food. It
is also direct and coordinate with the activities of other people those who prepare food
products. Catering manager : The manager has lead the team of catering assistants and chefs where
they are responsible for running day to day catering operations. It is monitoring the
quality of food and services for wedding parties. Customer : Customers are those who were used the services to the caterers for particular
occasion. They can use the wedding parties event system to register through online
medium and use the many type of services for special occasion. Sponsor : Caterers are the sponsor to provide the food and other services to the consumer.
It can sponsor the different type of food, beverage, decoration and many more.
 Supplier : Supplier has capability to supply the product and service regarding the events,
wedding and parties etc.

Q.2
a).List and briefly describe the main functional requirement
Functional requirements are those which are related to the technical functionality of the
system. This allows the use cases and their activities for identifying the functional requirements
of the project. These are basically the Product features which mainly describes the work that is
performed in use cases diagrams (Levine, 2018). It basically describes the actions about which
whole procedure is concerned. It specify the requirements involved in development of the
product and it also identifies that what the product can be able to do. This can be described by
the users and people of the business who specify the functional requirements of the product in
order to meet the desired design of the product (Li & et.al., 2018). Functional requirements of
the WPE system includes the automatised functions such as payment system, carters
functionality, requirements of customer, credit purchasing etc. all the requirements basically
includes the functionalities of such actions.
b). non- functional requirements for wedding parties system.
These requirements specify the specific criteria Non-functional requirements defines the
system attributes such as security, reliability, performance, maintainability, scalability and
usability. Non-functional requirements mainly ensures the usability and effectiveness of the
entire system. It describes the properties of the product and character of the process involved in
developing a system (Maylawati, Darmalaksana & Ramdhani ,2018). It mainly characterized by
adjectives. These requirements make the significant parts of the specification as the client and
user may may well judge the product on its non-functional properties. A variety of non
functional attributes includes reliability, security, portability and performance efficiency of the
Wedding party event system.
Q.3
a).Use the user goal technique to develop a list of use cases for WPE.
User goal technique is an approach to determine the use cases and also descrinbing their
specific goals by using new or updated system. It typically list all the stakeholders those who are
likely to interact with the system. There are some specific role that need to analyse the existing
system where user can use the WPE system and carry out the uses cases.
Use Case Name: WPE Catering service System
Scenario: Actor wants to take catering services through

WPE system for particular occasion.
Triggering Event:
Brief Description: WPE is the fastest growing online business that
can link together with the customer those who
need a caterer for the events. This system has
fulfilled the need, locations in proper manner.
It is based on the two sided system of caterers
and consumers.
Actors:  Customer
 Caterers
Stakeholders:  Supplier
 consumer
 Sponsor
Preconditions: The credit has expired in three month and
system will notify the caterers for added more
credits.
Postconditions: In case, System has required for purchased
more credits.
Flow of activities: Actor System
Caterers Caterers can use
WPE and register to
mention all the
description about
their business name,
services, location and
website link. The
verifier caterer has
own ABN, logo and

Proof.
Customer Customer make an
account on the WPE
system to choose the
best caterers for
event management.
They also submit
their requirement
through online form.
Expectation conditions: The Expectation conditional occurs when
customer cannot found the exact location of
caterers and not meet an appropriate
requirement. It has chances to increase the lack
of management system.
Table : 1

b). Use the event decomposition technique to identify any additional use cases description.
Event decomposition technique is starting for identifying all the enterprises events that
will cause the WPE system to response and each event lead to use cases. Starting with the events
help to analyse the accurate details. The level of details for determine the use cases which mainly
focused on the WPE system. In this system, caterers are performed task to mention about the
overall details of business, logos, service provider.
Event Event type Use case name Description
Catering Load () Caterers Caterer has performed
different functions to
load the details in the
WPE system.
Payment On click () Caterers Caterer can use the
payment option by
using PayPal method.
Credit Click () Customer Caterer has purchased
more credits to
maintain their
information and details
on the WPE system.
Quotes String () Customer Customer can use the
Quotes regarding the
services.
Feedback String () Caterers Caterer has checked
the review related the
customer feedback.
Table : 2

Q.4 Create a domain model class diagram for the WPE which includes classes, attributes,
association and multiplicity. Show the association classes and generalisation.
Domain model class diagram is based on the conceptual model that incorporates the both
behaviour and data (Oinas-Kukkonen & Harjumaa, 2018). It the formal ways to represent the
knowledge domain with the concepts individuals, data types and description logics. According to
scenario, it has created a domain class diagram of wedding parties and events.
Illustration 1

Q.5 Create a CRUID Matrix to check the consistency between the domain model class
A CRUD matrix is developed using the information provided in previous step. SQL is
consists of 4 statements which are sometimes referred as CRUD. It can be defined as Create,
insert, update, delete (Possieri & Sassano, 2018). It mainly used in understanding the basic
operations of data. However, these operations are changed according to the user requirements
and needs.
Data Entity CRUD Resulting the use case
Caterers Create
Update
Check
Read and record
insert
Add details
Find the consumer
Generate customer list
update the business details
update services
Customer Login
check
insert
Read
Report
Take new services
find the food items
update the information
contacted
Table : 3
Q.6 Create a fully developer use case description for the use case find caterer
Use case name caterers
Use case description Caterer can use the advertise medium on the
basis of on time Guarantee which provide on
time service to customers.
Check the previous review to satisfied the
customer through services.
Caterer pay to use the WPE system to register
on the system and purchase more credits
through PayPal payment method.

Table : 4

Q.7 Draw an activity diagram to represent the flow of activities for the user cases.

In unified language (UML), An Activity Diagram is considered as a graphical representation of
the executive set of procedural system activities which consists of the actions which are aimed at
performing a particular task. It represents the workflows and stepwise activities which supports
users choice, concurrency and iteration. It basically represents the flow of activities with the use
of the arrows which determines the work flow of the system (Rajaraman, 2018). According to
the case study of implementing the Wedding party Everything system, Actions in this diagram
are Catering services, Credit details, Event organiser and waiters etc. Here the activities are
Paypal, Registration, Purchase more credits etc. Present activity diagram helps in managing the
process flow of the WPE system.