SOFTWARE
ENGINEERING
PROJECT
online shopping system:
1. UML class Diagram
2. Object Diagram
3. Usecase Diagram
4. Activity Diagram
5. Sequance Diagram
T.A Amany Yehya
ID STUDENT NAME
ODD معبدB A L L I M A
212102806 GIN حسين
G Cصبري
محمد O
PROJECT STATUS REPORT
212104021 محمد ربيع يونس عبدهللا
212102797 محمد عالء محمد سعد
محمد عزالدين احمد عبدالسميع 212104089
Uml class diagarm:
1. Class Person:
Attributes: First Name, Last Name, Email, Phone.
2. Class Customer:
Inherits from Person.
Additional Attributes: ID, Password.
Methods: Add Address, Delete Address, Change
Email, Login, Signup, Empty Cart.
3. Class CustomerStatus:
Methods: SetStatus, GetStatus (to show user
status).
4. Class Address:
Attributes: Represents customer addresses.
5. Class Order:
Represents an order made by a customer.
May have associations with Address, Item, and
OrderStatus.
6. Class OrderStatus:
Represents the status of an order.
Methods: SetStatus, GetStatus.
7. Class Item:
Represents an item in an order.
May have associations with Product.
8. Class Product:
Represents a product available for purchase.
9. Class ShoppingCart:
Represents the shopping cart of a customer.
........etc
object Diagram
This class diagram represents the relationships and
structures of the key classes in the Online Shopping
System. Customers, their personal information, addresses,
orders, products, and shopping cart functionalities are
clearly defined. The diagram also captures the associations
between these classes, such as the association between
Customer and Order, Order and Item, and ShoppingCart
and Item. The inclusion of status classes, such as
CustomerStatus and OrderStatus, enhances the system's
ability to manage and track the states of customers and
orders.
usecase diagarm:
The Online Shopping System's use case diagram depicts
various actors and their interactions. The primary actors
include "Web Customer," further categorized as
"Registered Customer" and "New Customer." Inheritance
relationships indicate that both registered and new
customers inherit from the web customer.
Other key actors involved are the "Authentication
Provider," "Identity Provider," "Credit Payment Service,"
and "Admin." The use cases encompass essential
functionalities like "Purchasing" with sub-cases such as
"Checkout Product" and "View Product." Additionally, the
system addresses "Customer Registration," "View Order
History," "Login or Signup," "Manage Product," "Manage
User Account," "Edit System Product," and "Edit Order
System."
These use cases illustrate the comprehensive range of
interactions within the online shopping system, catering
to user registration, product management, order history
viewing, and the purchasing process. The involvement of
authentication and payment services, along with
administrative capabilities, ensures a well-rounded and
secure online shopping experience.
Activity diagarm:
The activity diagram for the Online Shopping System
outlines the sequence of activities performed by a user
during the online shopping process. The activities include
logging in, browsing products, selecting a product, adding
it to the cart, choosing a payment method, and
completing the purchase. The diagram also considers
scenarios such as login verification errors, product
availability, and saving payment information
1. Start:
The process begins when the user starts the online
shopping application.
2. Open Web Page:
The user opens the web page to access the online
shopping platform.
3. Log In:
The user logs in with their credentials (username
and password).
4. Verify Login:
The system verifies the login credentials.
5. If Error:
If there is an error in the login verification process,
the system displays an error message.
6. Else:
If the login is successful, the user proceeds to the
next step.
7. Browse Products:
8. ............etc
sequence diagarm:
A sequence diagram is a visual representation of a series of
steps that explain how an online shopping system works and
how it is used in IT infrastructures. It enables the development
of complex systems by showing how objects interact to
accomplish a task. By showcasing the relationships between
objects, users can gain insight into the workflow of events used
to accomplish a goal. This type of diagram is often used to
analyze and troubleshoot software, pinpoint inefficiencies, and
identify potential problems. Sequence diagrams are a
fundamental element in system architecture and IT
infrastructure planning.
