Scribd
Upload
38 views12 pages

SE Lab Report 3.docx 3

Uploaded by

sifatjahanc213263
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
38 views12 pages

SE Lab Report 3.docx 3

Uploaded by

sifatjahanc213263
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 12

Department of Computer Science

and Engineering

Lab Report-3

Course Code: CSE-3638


Course Title: Software Engineering Lab
Semester: 6th
Section: 6CF
Team Members
Sajia Sultana(C211210)
Sifat Jahan(C213263)
Neshat Tasnim(C221278)
Requirement Specification Report
Online Retail Portal Development

1. Introduction:
This Software Requirement Specification (SRS) document describes the
Online Retail Portal, an e-commerce platform for customers to browse, select,
and buy products online. The portal will provide a complete shopping
experience by allowing users to search for products, add them to a cart, and
securely complete their purchases. This document outlines the features and
requirements needed to develop the portal, helping both developers and
stakeholders understand the project’s goals and expectations.

2. User Requirements Specification:

A User Requirements Specification (URS) is a document that outlines the


expectations and specifications for a system, product, or service from the user's
perspective. It typically defines what the user needs, rather than how those
needs will be fulfilled technically.

2.1 Functional Requirements:

Functional Requirements define the specific behaviors, features, and


capabilities that a system or product must have to meet user needs. These
requirements describe what the system should do, not how it should be
implemented technically.

● User Registration & Login:


Users create accounts and login securely using email and password.
● Product Search and Filtering:
Allows users to search for products by keywords, categories, and apply
filters like price range, ratings, etc.
● Shopping Cart Management:
Users can add products to their cart, view cart details, adjust quantities,
and remove items.
● Checkout and Payment Options:
Provides a secure checkout process and multiple payment options like
credit card, debit card, and digital wallets.
● Order Tracking and History:
Users can track their order status and view previous purchases.
● Logout Functionality:
Users can safely log out after completing their session.

2.2 Non-Functional Requirements:

Non-Functional Requirements (NFRs) define the quality attributes,


performance, and operational constraints that a system or product must meet.
Unlike functional requirements, which specify what a system should do, non-
functional requirements describe how well the system should perform its
functions and focus on the system's quality aspects such as performance,
security, usability, and reliability.

● Security:
Implement secure authentication and encryption for user data protection.
● Reliability:
Ensure minimal downtime and robust error handling for smooth shopping
experiences.
● Usability:
Intuitive and accessible user interface with clear instructions and
navigational ease.
● Scalability:
Designed to handle a growing number of users and an expanding product
catalog.
● Compatibility:
Compatible with multiple devices, browsers, and operating systems.

3. Stakeholders of the System:


● Customers: End-users who browse and purchase products.
● Administrators: Manage product listings, inventory, and customer
service.
● Developers and IT Team: Responsible for development, maintenance,
and upgrades.
● Designers: Work on the website’s visual appeal and user experience.
● Payment Gateway Providers: Handle online payment processing
securely.
● Shipping Partners: Manage logistics and ensure timely product delivery.

4. Use Case Diagram:


Login & view item use case:

Search use case:


Add to cart use case:

Payment use case:


Class Diagram:

Login Diagram:

User

-email: string
-password: string

+login( email : string , password : string) : Boolean

Extends

Customer
-email: string
-password: string

Extends

Admin

-email: string
-username: string
-password: string

+login(username,password): Boolean
+login(isername,password):Boolean
Search diagram:

Online Retail Portal Development

-item: List<item>

+search(keyword : string) : List<item>


+additem(item : Item) : void
+deleteItem(item : Item) : void

Customer
Item
-id: string -customerId : string
-name: string -name : string
-description: string -email : string
-price: double
+getItemId() : string +getCustomerId() : string
+getName() : string +getName() : string
+getDescription() : string +getEmail() : string
+getPrice() : double

Shopping Cart
-item : List<item>
-customer : customer
+addItem(item : Item) : void
+removeItem(item : Item) : void
+checkout() : void

Add to cart diagram:


Shopping Cart
-item : List<item>
+addItem(item : Item) : void
+removeItem(item : Item) : void
+getTotalPrice() : double
+checkout() : order

Item
-productId : int
-name : string
-price : double
+Item(product : int, name : string, price :
double)
+getProduct() : int
+getName () : string
+getPrice() : double

Order
-orderId : int
-items : List<Item>
-totalPrice : double

+order(orderId : int,items:List<item>,totalPrice: double)


+getOrder() : int
+getItem() : List<item>
+getTotalPrice() : double

Payment method diagram:


Payment Method

-paymentId : int
-methodType : string

+paymentMethod(payment : id, methodType : string)


+get paymentId() : int
+getMethodType() : string

Order
-order : int
-items : List<Item>
-totalPrice : double
-paymentMethod : paymentMethod
+order(order : int, items : List<item>, TotalPrice : double , paymentMethod :
paymentmethod
+getOrderId() : int
+getTotalPrice() : double
+getPaymentMethod () : paymentMethod

Sequence Diagram
Login Diagram:

Search Diagram:

Payment Diagram:
Add to cart Diagram:

Conclusion:

You might also like