Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Software Engineering
Submitted To
Submitted By
Section C
Due Date
1 Introduction:
Introduction
Our system is a client-based project.
Our client wants to develop an easy to use online store which will fulfill his needs.
This online shopping store which will facilitate its customers to buy products of any
category they want.
It will display all the products of all categories like
fashion & beauty,
home appliances,
kitchen products,
sports & wear etc.
Users can buy products by making payment online as well as cash on delivery.
They can create their Wishlist for future.
While the administration can check the weekly, monthly and yearly progress report
which will help them to improve their business in future.
Organizational Chart
We are three members in our group. We are not much experienced that one of us lead us
towards the project tasks. We are working together in all tasks like managing the timetable,
gathering requirements, making design documents, completing documentations and
developing the system. So, we all are managers, requirement engineers, designers,
developers and testers at the same time.
At the same time, we have to learn how the organizational works go. So, our organizational
chart is as follows:
This application provides a facility to a customer to search about a product they need and can
order products of daily life. The customer will have the ability to create their wish list of desired
products. The key goals of this project are to boost the eStore business globally, to facilitate the
online customers, to generate more revenue, to keep record of sales and to maintain the record
of customers.
Perform Refinement:
After over specifying the entities, we must refine them on the basis of our Business Logic.
For example, we found the following entities more related to our Business Logic;
User Online Payment
Subscription Alerts Add to Cart & Wishlist
Chat Group User Authentication
Order
3.0 Our system “shall” provide an interface to user to edit quantity in his/her Shopping
Cart.
4.0 Our system “shall” provide a simple interface to user to buy a product i.e. proceed to
checkout.
4.0 Our system “shall” provide an interface to users to buy product via credit or debit
card payment.
4.0 Whenever someone place an order. Our system “shall” send a unique order number
to his/her email id.
4.0 Our system “shall” allow the customers to track their order via an order number.
5.0 Our system “shall” provide Chat facility to the customers with admin.
5.0 Our system “shall” provide an interface to the user to claim Refund.
5.0 Our system “shall” provide an interface to admin to approve refund request.
5.0 Our system “shall” provide facility of Email Subscription.
5.0 Our system “shall” provide an interface to users to give feedback about product after
purchasing.
5.0 Our system “shall” provide an interface to admin to manage feedback of user’s.
6.0 Our system “shall” provide an interface to admin to manage customers’ account.
7.0 Our system “shall” provide an interface to admin to manage discounts and
promotions.
7.0 Our system “shall” provide an interface only to the admin to generate sales report.
Registration
UC ID 1
Use Case Name UC_Register
Primary Actor User
Preconditions User have to visit our website.
1. System will ask the user to register himself.
2. User will provide the required info as email address,
Basic Flow
password, Username etc.
3. System will evaluate the given info and register the user.
Post conditions Registration successful.
Special Requirements Nil
If the user does not provide required information, then system will
Alternative Flow
user to provide the all required information.
Login
UC ID 2
Use Case Name UC_Login
Primary Actor User
Preconditions User must be registered.
1. System will ask the user for email and password.
2. User will provide the required info.
Basic Flow
3. System will evaluate the info.
4. If the info is authentic, system will log in the user.
Post conditions Login Successful.
Special Requirements Nil
1. If the given email and password are wrong, then system will
ask the user to check his/her email and password or re- enter.
2. User will provide the required info.
Alternative Flow 3. System will evaluate the info.
4. If the info is not authentic, system will not log in the user,
and suggest recovering account,
Forgot Password
UC ID 3
Use Case Name UC_Forgot_Password
Primary Actor User
Preconditions A user must have a registered account.
1. User will request for forgot password.
2. System will confirm his email address.
3. User will provide the info.
Basic Flow 4. System will send a recovery code on that email.
5. User will enter that code to the system.
6. If the recovery code matches, then system will ask the user
for new password.
Post conditions Account Recovered.
Special Requirements Nil
Account will not be recovered in case of wrong recovery code or
Alternative Flow
invalid email address.
Add to Cart
UC ID 6
Use Case Name UC_Add_to_Cart
Primary Actor User
Preconditions A User must login to system.
1. User clicks on desired product.
Basic Flow 2. User clicks on Add to Cart button.
3. System will add the Product to user’s shopping cart.
Post conditions Product added successfully.
Special Requirements Nil
1. If an unregistered user clicks on add to Cart, then system
Alternative Flow
will ask to please login to system or create account.
View Cart
UC ID 7
Use Case Name UC_View _Cart
Primary Actor User
Preconditions User must visit our website.
1. User clicks on view cart.
2. System show his/her shopping cart.
Basic Flow
3. User click on delete product from cart.
4. System delete the product.
Post conditions User is redirected to home page.
Special Requirements Nil
1. System will check that if there are only 10 minutes
Alternative Flow remaining before a particular class or not.
2. If not, system will not send any notification to the user.
Search Catalog
UC ID 9
Use Case Name UC_Search_by_ProductName
Primary Actor User
Preconditions User must visit our website.
1. User will click on search button.
2. System ask to enter product name.
Basic Flow 3. User provide product name and click search button.
4. System will check if the product exists or not.
5. If yes, system will show a particular product to user.
Post conditions Product found Successfully.
Assumption User login to system
Special Requirements Nil
1. User will click on search button.
2. System ask to enter product name.
3. User provide product name and click search button.
Alternative Flow
4. System will check if the product exists or not.
5. If not, then system show a message that product does not
exist, please enter right spelling or search another product.
Search Catalog
UC ID 10
Use Case Name UC_ Search_by_CategoryName
Primary Actor User
Preconditions User must visit our website.
Assumption User in logged into the system.
1. User will click on search button.
2. System ask to enter category name.
Basic Flow 3. User provide information and click search button.
4. System will check if the searched category exists or not.
5. If yes, system will show a particular category to user.
Post conditions Result found.
Special Requirements Nil
1. User will click on search button.
2.System ask to enter category name.
3.User provide required information and click search button.
Alternative Flow 4.System will check if the category exists or not.
5.If not, then system show a message that searched category does
not exist, please enter right spelling or search another category
of product.
Browse Product
UC ID 11
Use Case Name UC_Browse_Product
Primary Actor User
Preconditions User visit our website.
Assumption User logged into the system.
1. User visit our site.
2. System will show him products
Basic Flow
3. User will click on next page.
4. System will open the next page and so on.
Post conditions Show a pop up message to user to login or create account.
Special Requirements Nil
Alternative Flow
View Product
UC ID 12
Use Case Name UC_View_Product
Primary Actor User
Preconditions User visit our website.
Assumption User logged into the system.
5. User will click on the product.
6. System will open a page showing detail of product like
picture, price quantity color and description etc.
Basic Flow
7. User can zoom in and zoom out the product picture, select
color, quantity or can read product description, can add to
Cart, add to Wishlist or can buy the product.
Post conditions User prompt to home page.
Special Requirements Nil
Alternative Flow 1. .
Add to Wishlist
UC ID 13
Use Case Name UC_Add_to_Wishlist
Primary Actor User
Preconditions Quiz must login to the system.
1. User will click on the product.
Basic Flow 2. User will click on add to Wishlist button.
3. System will add the product to Wishlist of user.
Post conditions Product added to Wishlist successfully.
Special Requirements Nil
1. If the unregistered user clicks on add to Wishlist, then
Alternative Flow
system will ask to please login to system or create account.
Buy Product
UC ID 14
Use Case Name UC_CheckOut
Primary Actor User
Preconditions A user maybe registered or unregistered.
1. User clicks on buy button.
2. System will open a new interface asking for login or to
create account.
3. User will create account or will login to system.
4. System will ask for delivery information.
5. User will enter his/her information like, phone#, email,
Basic Flow
address.
6. System will authenticate the information.
7. Then system will ask to payment method either cash on
delivery or via a credit card.
8. User will choose his/her desired payment method and click
on place order.
Post conditions Order placed successfully.
Special Requirements Nil
1. If the user does not provide all required detail, then system
Alternative Flow
will ask to fill all fields.
Feedback
UC ID 18
Use Case Name UC_Give_feedback
Primary Actor User
Preconditions User login to system.
1. User click on leave feedback button.
2. System will ask user to enter his/her feedback.
Basic Flow
3. User will enter feedback in feedback section.
4. System will store the feedback of customer.
Post conditions System will prompt the user to home screen.
Special Requirements Nil
1. If the user the user feedback section empty and click on submit
Alternative Flow feedback button, then system will ask user to please enter
feedback.
Track order
UC ID 29
Use Case Name UC_Track_Order
Primary Actor User
Preconditions User must login to system.
1. User click on track order button.
2. System will ask to enter order number.
Basic Flow 3. User will enter order number.
4. System will check order number, if yes then system will
show the order status like shipped, pending or delivered.
Post conditions Prompt user to back screen.
Special Requirements Nil
1. System will order number if No then system ask to enter
correct order number.
Alternative Flow
2. Order status will not be shown unless user provide correct
order number.
Generate Reports
UC ID 21
Use Case Name UC_Generate_Reports
Primary Actor Admin
Preconditions Admin must login to system.
1. Admin click on generate report.
2. System will show him an option to generate report daily,
Basic Flow weekly, monthly, annually.
3. User click on one from above report types.
4. System will generate the particular report.
Post conditions Report generated.
Special Requirements Nil
Alternative Flow .
Manage Customer Account
UC ID 22
Use Case Name UC_Manage_Customer
Primary Actor Admin
Preconditions Admin must be login to system.
1. User will click on manage customer button.
2. System shows multiple options like delete customer’s
account, approve customer account, reset password
Basic Flow 3. Admin click on delete customer account
4. System asks to enter customer email.
5. Admin will enter customer email and press delete button.
6. System will delete customer account.
Post conditions Customer account deleted successfully.
Special Requirements Nil
If the entered email do not exist in the system, system will show
Alternative Flow
an error message and asks for a valid email.
Manage Feedbacks
UC ID 23
Use Case Name UC_Manage_Feedback
Primary Actor admin
Preconditions Admin must be logged into the system.
1. Admin click on manage feedback.
2. System shows him the feedback of user.
Basic Flow
3. Admin click on delete feedback.
4. System delete the feedback of user.
Post conditions Deleted successfully.
Special Requirements Nil
Alternative Flow 1. .
Manage Sales
UC ID 24
Use Case Name UC_Manage_Sales
Primary Actor Admin
Preconditions Admin must login to system.
1. Member will type a message and send that message in chat
group.
2. Every member including admin will receive that message.
Basic Flow OR
1. Admin will type a message and send that message in chat
group.
2. Every member will receive that message.
Post conditions Message Sent.
Special Requirements Nil
Alternative Flow -
Manage orders
UC ID 25
Use Case Name UC_Manage_Orders
Primary Actor Admin
Preconditions Admin must login to system.
1. Admin will click on manage orders.
2. System will show him multiple option like total order,
pending order, shipped orders, check availability, cancelled
Basic Flow ordered, and completed order.
3. Admin click on one of them.
4. System will show the detail of orders.
5. Same as above admin can check all of options.
Post conditions System prompt admin to back screen.
Special Requirements Nil
Alternative Flow .
Claim refund
UC ID 26
Use Case Name UC_Claim_Refund
Primary Actor User
Preconditions User must login to system
1. User goes to his/her order and clicks on refund.
2. System will ask him reason of refund.
3. User will enter reason and submit it.
Basic Flow
4. Request will be added to system.
5. Admin will refund if it is according to terms and
conditions of website.
Post conditions Request have been successfully added.
Special Requirements Nil
1. Admin will request to add a member in the group.
2. System will ask admin for the user name.
Alternative Flow 3. Admin will provide the required info.
4. System will check if that user exist is the system or not.
5. If not, system will not add that user in chat group.
Approve Refund
UC ID 27
Use Case Name UC_Approve_Refund
Primary Actor admin
Preconditions admin must login to system
1. Admin will receive refund request.
2. System will check if customer is authentic via an order
number.
Basic Flow 3. system will check if the request is made within 7 days are
not.
4. If yes admin will approve the refund request and will
contact the user for refund.
Post conditions Prompt admin to back screen.
Special Requirements Nil
If the request made after 7 days, then system will not
Alternative Flow
approve the request. And inform the user.
Add product
UC ID 28
Use Case Name UC_Add_Product
Primary Actor admin
Preconditions Admin must login to system.
1. Admin clicks on add product.
2. System ask admin to select product.
3. Admin select the product he/she want to upload.
4. System provide him fields to enter price, color and
Basic Flow
description of product.
5. Admin enter the required information and click on add
product.
6. System will add the product.
Post conditions Product added successfully.
Special Requirements Nil
1. Admin click on select picture of product.
2. If the selected product has large size or have different format,
then system will show a message to check product size or
Alternative Flow format.
3. Admin write product price, color and description.
4. If the entered price, color and description is not according
to data type then system ask to correct information.
Delete Product
UC ID 29
Use Case Name UC_Delete_Product
Primary Actor Admin
Preconditions Admin must login to system.
1. Admin clicks on delete product.
2. System will ask the admin for product name.
Basic Flow 3. User will provide the required info.
4. System will check if the product exists or not.
5. If yes, system will delete the product from the system.
Post conditions Product Deleted Successfully.
Special Requirements Nil
1. Admin will request to delete a product.
2. System will ask the admin for the product name.
3. Admin will provide the required info.
Alternative Flow 4. System will check if the assignment already exists or not.
5. If not, system will send a message to the user that the
particular product does not exist in the system so can’t be
deleted.
Search product
UC ID 30
Use Case Name UC_ Search_Product
Primary Actor Admin
Preconditions Admin must login to system.
1. User will click on search button.
2. System ask to enter product name.
Basic Flow 3. User provide product name and click search button.
4. System will check if the product exists or not.
5. If yes, system will show a particular product to user.
Post conditions Product found.
Special Requirements Nil
1. Admin will click on search button.
2. System ask to enter product name.
3. Admin provide product name and click search button.
Alternative Flow
4. System will check if the product exists or not.
If not, then system show a message that product does not
exist, please enter right spelling or search another product
Update Product
UC ID 31
UC_ Update_Product
Use Case Name
Primary Actor Admin
Preconditions User must login to system.
1. Admin click on edit product detail.
2. System will ask admin to enter product name whom do u
want to edit.
3. Admin enter the product name.
Basic Flow 4. System check if the desired product exists or not.
5. If yes, then system will ask to enter product detail which
you want to edit.
6. Admin enter the product detail.
7. System update the product detail.
Post conditions Product detail updated successfully.
Special Requirements Nil
1. System will check if the particular product exists or not.
2. If No, then system show a message that product does not
exist, please enter correct name.
Alternative Flow
3. If the admin leaves some required while updating product
info and click on update button, then system ask him to enter
all fields.
Send Email
UC ID 32
Use Case Name UC_Send_Email
Primary Actor Admin
Preconditions Admin must login to system.
1. Admin will click on send emails button.
2. System ask to enter message.
Basic Flow
3. Admin will enter message and click on send.
4. System will send messages to all store email in database.
Post conditions Email sent successfully.
Special Requirements Nil
Alternative Flow
Change Password
UC ID 33
Use Case Name UC_Change_Password
Primary Actor User
Preconditions User must login to system.
5. User click on change password button.
6. System will ask to enter previous password
7. User will enter password.
Basic Flow 8. System will authenticate the password.
9. If matches, then system ask to enter new password.
10. User will enter new password and confirm the password.
11. System will update the password.
Post conditions Password change successfully.
Special Requirements Nil
3. If previous password not matches, then system ask to enter
correct password.
Alternative Flow 4. If the new password and confirm password does not match
then system tell that password and new password does not
match, enter same password again.
Bundle of thanks