Software
Engineering
2024/2025
Software Engineering project
BENI SUEF NATIONAL UNIVERSITY
Table of Contents
Team Information............................................................................................................................. 2
Project proposal ................................................................................................................................ 3
Project Idea ................................................................................................................................... 3
Project scope ................................................................................................................................ 3
Main functionalities ...................................................................................................................... 3
Development platform.................................................................................................................. 3
Stakeholders ................................................................................................................................. 3
Similar applications in the market ................................................................................................ 3
SRS (Software requirement specification) ....................................................................................... 4
Functional Requirements.............................................................................................................. 4
Non-Functional Requirements...................................................................................................... 4
Software Design ............................................................................................................................... 5
Activity Diagram .......................................................................................................................... 5
Use Case ....................................................................................................................................... 5
Use cases Description............................................................................................................... 5
Use case Diagram ..................................................................................................................... 5
Class Diagram .............................................................................................................................. 5
Team Information: (typed not handwritten, except for the attendance signature):
ID Full Name Attendance Final
Grade
[Ordered by ID] [In Arabic] [Handwritten
Signature]
1 230100133 محمد مختار زكريا
2 230100237 احمد عصام رؤف
3 230100292 كيرلس مرقس صبري
4
5
6
7
Project proposal:
Project Idea: The idea project is to develop an online shopping
application that allow user to browse product, add them to the cart, and
place orders.
Project scope:
The project covers the following:
1- user registration and login
2- Browsing product categories
3- Product search and filtering
4- Shopping cart and checkout
5- Order management for user
Main functionalities:
1- user registration/login
2- Product browsing and search
3- checkout and place orders
4- Order history and tracking
5- Admin:Add/edit/delete product
Development platform:
1- [Link]
2- [Link]/PHP
Stakeholders:
1- User(Shoppers)
2- Store admins
3- System developers
Similar applications in the market:
1- Amazon
2-Noon
3-Jumia
SRS (Software requirement specification)
Functional Requirements
User requirements System requirements
Req1 1- Users shall be able to 1- The system shall store user data securely
register and log into System
2- The system shall maintain a database of products
2- Usersshall be able to and their details
browse available products by
category 3- The system shall update the product quantity after
each purchase
3- Users shall be able to
search for products using 4- The system shall send a confirmation message after
keywords successful order placement
4- Users shall be able to add
products to a shopping carts
Non-Functional Requirements
System requirements User requirements
Req1 1- The system shall support at 1- The system shall be easy to use with a user-friendly
least 100 concurrent users interface
2- The system shall respond 2- The application shall load within 3second on
to product search queries in standard devices
less than 3 second
3- The system shall be available 24/7
3- the system shall be secured
using HTTPS and encrypted
passwords
Activity diagram
Use Case
Use Case 1 - Search product
Field Description
Goal in Context Allow users to search for products using various
filters (e.g., category, price range, brand).
Preconditions Product data is available in the database.
Success End Condition Relevant products are displayed based on user filters
Failed End Condition No products are ret Relevant urned or a system error
occurs.
Primary Actor Customer/User
Secondary Actors Product Database, Web Server
Trigger User enters a search query or applies filters and hits
search
1. User opens the online store.
Description Steps:
2. Enters search keywords or applies filters
(e.g., price, category).
3. System queries the product database.
4. System displays matching products.
If no products match, system shows a "No results found"
Extensions or Variations: message
Use Case 2 - Admin Login
Field Description
Goal in Context Allow administrators to securely log into the admin
dashboard.
Preconditions Admin account exists.
Success End Condition Admin is redirected to the dashboard.
Failed End Condition Login fails due to incorrect credentials.
Primary Actor System Administrator
Secondary Actors Authentication server
Trigger Admin enters username and password and clicks
login
1. Admin accesses the login page.
Description Steps: 2. Enters valid credentials.
3. Clicks login.
4. System authenticates credentials.
5. System redirects to the admin dashboard.
If credentials are incorrect, show 'Invalid login' message.
Extensions or Variations:
Use Case 3 - Delete product
Field Description
Goal in Context Allow admin to remove a product from the catalog
Preconditions product member exists and admin is logged in.
Success End Condition product record is removed from the system.
Failed End Condition Deletion fails or is cancelled.
Primary Actor Admin
Secondary Actors Database
Trigger Admin selects a product and clicks delete
Description Steps:
1. Admin selects the product to delete.
2. Clicks "Delete" option.
3. System asks for confirmation.
4. Admin confirms.
If deletion is cancelled, no changes occur.
Extensions or Variations:
Use case Diagram:
Class Diagram:
Object diagram
Sequence diagram
Communication diagram