“Requirement Specification Plan for ShopEZ”

Assessment 02

TECH 1300: - Information System in Business

SUBJECT COORDINATOR AND FACILITATOR:

Silva Wei

&

Kiran Kaur

PREPARED BY:

Mr MohammadSoyeb Mansuri

1812918

September 2023
 TABLE OF CONTENTS
Sr No Description Page
No
1 Summary
1
2 Company Overview
1
3 Case Study and Models used to develop Requirement Specification Plan.
1
4 Taxonomy of Requirement Engineering 2
5 Requirement Gathering Techniques Used
3
6 Business Requirement by Agile Methodology
4
7 Use Case Diagram
5
8 Class Diagram
6
9 Sequence Diagram 7
10 Identification of Stake Holders 7
11 References 9

LIST OF FIGURES
Sr No Description Page
No
Fig1.1 Use Case Diagram
5
Fig1.2 Class Diagram
6
Fig1.3 Sequence Diagram between User and Bank
7
Fig1.4 Sequence Diagram between User and DB Server
8
Information System in Business Tech1300_Assessment 02

Requirement Specification Plan for Shop EZ

Summary:
This report specifies requirements for ShopEZ, a new online shopping platform. It uses
Agile techniques like user stories and use cases gather requirements from a customer
perspective. User stories are captured and needed features while use cases model
customer-system interactions are studied. UML diagrams including use case, class, and
sequence diagrams visualize the functional design. These models provide the
development team clear specifications to build ShopEZ effectively per the timeline.
Requirements are also communicated to the project sponsor and customers for approval
and feedback. Overall, this report leverages Agile methodologies to analyze and specify
ShopEZ's requirements using a customer-centric approach. This ensures the platform is
designed to meet end-user needs.

Company Overview:
ShopEZ is a new e-commerce startup building an online shopping platform that provides
a smooth customer experience. The goal is to create a user-friendly website and apps
where customers can easily discover, evaluate, purchase and track products. ShopEZ
will offer a wide product catalog across categories like electronics, fashion, beauty etc.
Customers can securely pay with integrated gateways and track deliveries. The backend
will manage the product catalog, inventory, logistics and order fulfillment. User data will
enable personalized recommendations. Overall, ShopEZ aims to differentiate itself
through strong UI/UX design, broad product selection, and fast delivery.

Case Study and M odels used to develop Requirement Specification

Plan.
This case study involves developing requirements and specifications for ShopEZ, a new
online shopping platform that will allow customers to browse, select and purchase
products over the internet. ShopEZ aims to build an e-commerce website and backend
infrastructure to manage the product catalog, inventory, orders and payments. The goal
is to provide a smooth online shopping experience for customers.

1
Information System in Business Tech1300_Assessment 02

As a consultant, I have been hired to design the IT requirements for ShopEZ using Agile
techniques. Requirements will be gathered from a customer perspective through user
stories, use cases and interviews.

These requirements will then be analyzed, modeled using UML diagrams, and
communicated to the development team and other stakeholders like the project sponsor.
The objective is to provide the development team with clear, visual models and
specifications so they can build the system efficiently within schedule.

Taxonomy of Requirement Engineering

A process in which customer demand is analyzed along with its feasibility which can be
further transformed into operational system is generally known as requirement
engineering.

(Jogannagari Malla Reddy, 2016)explained the structural layout of Requirement

engineering which merely focuses on User Requirements and System Requirements.
(Jogannagari Malla Reddy, 2016) states that those requirements which serves as a
contract between system buyer and software developer which gives the information of
detailed system services and constraints are said to be System Requirements.

Further in the literature (Jogannagari Malla Reddy, 2016)states that those requirements
which are directly delivered by the client to the user are said to be User Requirement.
System Requirement can be Functional as well as Non-Functional. Thorough
classification for the same is expressed below.

Functional Requirements: It includes the functions provided by the system and how the
system should respond as per the inputs given by the users.

2
Information System in Business Tech1300_Assessment 02

For Example, Functional Requirement of ShopEZ

includes: Login process with username and Password
by the customer, Browsing the required product, User
Requirement
Adding the product in cart and Wishlist, Changes to be
made in cart such as Quantity, Add or Remove
products, Payment of the purchase through third-party
System
payment gateway and reverting back for successful Requirement
payment.

Non-Functional Requirement includes: Performance,

Memory, Reliability of the system developed. It also Non
Functional
Functional
includes design methodology, legislative factors etc.
which therefore affects the operational criteria of
system working.

Requirement Gathering Techniques Used.

These techniques involve some basic methodology for gathering the data of requirement
so that it can be clearly identified how the system should perform [2]. It generally includes
some of the basic techniques such as

• Interviews: Structured and Unstructured interviews can help to gather information.

• Questionnaires and Feedback.
• Brainstorming.
• Storyboard.
• Prototyping: Sample preparation can lead to give basic ideas about the
consequences of failure
• Use cases Modeling / User Model (Further to be used for preparation of plan)

(Mushtaq, 2016) showed that Use case Modelling and UML are the most effective ways
for requirement gathering process where

3
Information System in Business Tech1300_Assessment 02

Business Requirement by Agile M ethodology

1. User Story: Customer wants to register an account so that he can save his
information for faster checkout.
• Acceptance Criteria: Customers can create an account with email and
password
2. User Story : Customer wants to browse products so that he can find items that
he wants to purchase.
• Acceptance Criteria: Customer can search for products by name or category
sorted by price, ratings etc.
3. User Story: Customer want to view product details so he can learn more before
purchasing.
• Acceptance Criteria: Product details like description, price, images are
displayed
4. User Story: Customer wants to add products to a cart so he can purchase
multiple items together.
• Acceptance Criteria: Products can be added to cart with desired quantity
5. User Story: Customer wants to apply discounts on purchases
• Acceptance Criteria: Valid Promo codes and Discounts reflected.
6. User Story: Customer wants multiple payment options
• Acceptance Criteria: Customers can pay by Credit card, Debit card, Net-
banking, UPI
7. User Story: Customer wants to track order status
• Acceptance Criteria: Customers can track order by order id and view My
Orders section.
8. User Story: Customer wants to return/exchange items
• Acceptance Criteria: Customers can return original item as it is and get refund
as per policy to original payment method or customer can exchange if applicable
and replace with new one.

4
Information System in Business Tech1300_Assessment 02

Use Case Diagram: The three most fundamental use instances are search items,
make purchasing and patron sign in process. This use case might be blanketed within the
make Buy use case. The checkout use case is a buying procedure,now not a stand by
myself use case. (Mule, 2015)

Fig 1.1: Use case Diagram

5
Information System in Business Tech1300_Assessment 02

Class Diagram: A class diagram is a type of static structural diagram in Unified

Modeling Language (UML) used for general conceptual modeling of the structure of a
system. It models the static view of an application by showing the system's classes, their
attributes, operations (or methods), and the relationships among objects. Relationship
between Product and Customer, Customer and Transactions etc are shown. (Waykar,
2014)

Fig 1.2: Class Diagram

6
Information System in Business Tech1300_Assessment 02

Sequence Diagrams: It is a visual representation of a number of steps that shows

how an online shipping system is functioning. It enables developing of intricate systems
by showing how several components work together to perform the goal. (Song, 2001). A
reply message from the Shop EZ or Bank is indicated by dotted lines and the forward
approaches are indicated by dark solid line followed by arrows.This is a sequence
diagram which enables the procedure from login till ordering the product.

Fig 1.3: Sequence Diagram between User and Bank

7
Information System in Business Tech1300_Assessment 02

Fig 1.4: Sequence Diagram between User and DB Server

Identification of Stake Holders

• Customers • Product Owner
• Development Team (Approve Requirement)
• Project Managers • Operational Team
(Approve/signoff requirement) • Marketing Team

8
Information System in Business Tech1300_Assessment 02

Customers: The end users who will purchase on ShopEZ. Requirements will be gathered
from them via interviews, surveys, user testing etc.

Development team - They will build ShopEZ based on the requirements. Requirements
will be communicated through user stories, use cases and UML diagrams.

Project manager - The project manager oversees development and can approve
requirements. Requirements will be communicated through specification documents and
status updates.

Product owner - The product owner defines the product vision and roadmap. They will
provide feedback on requirements through Agile ceremonies like sprint planning.

Operations team - Responsible for order fulfillment and delivery. Requirements will be
communicated through workshops and documentation.

Marketing team – This team will Handle promotional activities. Requirements will be
communicated through emails, meetings focused on marketing needs.

Finance team – They will Manage budgets and costs. Financial requirements will be
communicated via emails and meetings.

9
Information System in Business Tech1300_Assessment 02

References
Bahl, R. K. (2014). Requirements Anlysis, Refinement and Unambiguationsing using
Requirements gathering and project managment tools. International Journal of
Innovative Science, Engineering & Technology, 1(4).
Jogannagari Malla Reddy, S. P. (2016). REQUIREMENT ENGINEERING: AN
ARCHETYPAL APPROACH FOR THE DEVELOPMENT OF QUALITY
SOFTWARE. INTERNATIONAL JOURNAL OF ENGINEERING SCIENCES &
RESEARCH TECHNOLOGY, 5(12).
Mule, S. S. (2015). Role of Use case diagram in S/w Development. International Journal
of Management and Economics.
Mushtaq, J. (2016). Different Requirements Gathering Techniques and Issues.
INTERNATIONAL JOURNAL OF SCIENTIFIC & ENGINEERING RESEARCH ,
7(9).
Song, I.-Y. (2001). Developing Sequence Diagrams in UML. Conference Paper.
Waykar, M. Y. (2014). Significance of Class Diagram in S/W Development. Conference:
MANAGELIZATIONAt: OSMANABAD.

10