Software Quality Assurance (XI-540)

Final Assessment

Online Shopping Store

Functional Specification Document

Prepared by:

 Fahad Amjad (S2019027001)

 Muhammad Imran Ahmed (S2019027003)

 Muhammad Kamran (S2019027039)

 Muhammad Usama (S2019027016)

Course Instructor: Sir Imran Saleem

School of Professional Advancement

University of Management and Technology

Table of Contents
1. INTRODUCTION.......................................................................................................................................... 6
1.1. PURPOSE.........................................................................................................................................................6
1.2. TARGET GROUPS..............................................................................................................................................6
1.3. SCOPE............................................................................................................................................................6
2. GENERAL DESCRIPTION.............................................................................................................................. 6
2.1. BACKGROUND..................................................................................................................................................6
2.2. OVERVIEW OF THE SYSTEM................................................................................................................................6
2.3. CHARACTERISTICS OF THE USER...........................................................................................................................7
2.3.1. Guest.......................................................................................................................................................7
2.3.2. Registered User.......................................................................................................................................7
2.3.3. Webmaster.............................................................................................................................................7
2.4. THE USER VIEWS OF THE PRODUCTS....................................................................................................................7
2.4.1. Guest.......................................................................................................................................................7
2.4.2. Registered User.......................................................................................................................................7
2.4.3. Webmaster.............................................................................................................................................7
3. FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS...............................................................................8
3.1. FUNCTIONAL....................................................................................................................................................8
3.2. NON-FUNCTIONAL..........................................................................................................................................10
3.3. ASSUMPTIONS................................................................................................................................................10
4. SYSTEM ARCHITECTURE............................................................................................................................ 11
4.1. HIGH LEVEL ARCHITECTURE OF THE SYSTEM........................................................................................................11
4.1.1. User Registration Management...........................................................................................................11
4.1.2. Member Management.........................................................................................................................11
4.1.3. Product Management...........................................................................................................................11
4.1.4. Order Management..............................................................................................................................11
4.2. LOW LEVEL ARCHITECTURE OF THE SYSTEM........................................................................................................12
4.2.1. Log Maintenance..................................................................................................................................12
4.2.2. System Security.....................................................................................................................................12
4.2.3. Notifications.........................................................................................................................................12
4.2.4. System Management............................................................................................................................12
5. USE CASES................................................................................................................................................ 12
5.1. USE CASE # UCS – ECWS01 – LOGGING IN......................................................................................................12
5.1.1 Use Case Name: Logging In..................................................................................................................12
5.1.2 Actor: All Users.....................................................................................................................................12
5.1.3 Pre-Condition:.......................................................................................................................................12
5.1.4 Post-Condition:.....................................................................................................................................12
5.1.5 Basic Flow:............................................................................................................................................12
5.1.6 Alternate Flows:....................................................................................................................................13
5.2. USE CASE # UCS – ECWS02 – LOGGING OUT..................................................................................................13
5.2.1 Use Case Name: Logging Out...............................................................................................................13
5.2.2 Actor: Registered User..........................................................................................................................13
5.2.3 Pre-Condition:.......................................................................................................................................13
5.2.4 Post-Condition:.....................................................................................................................................13
5.2.5 Basic Flow:............................................................................................................................................13
5.3. USE CASE # UCS – ECWS03 – FORGOTTEN PASSWORD.....................................................................................13
5.3.1 Use Case Name: Forgotten Password...................................................................................................13
 5.3.2 Actor: All Users.....................................................................................................................................13
5.3.3 Pre-Condition:.......................................................................................................................................13
5.3.4 Post-Condition:.....................................................................................................................................13
5.3.5 Basic Flow:............................................................................................................................................14
5.3.6 Alternate Flows:....................................................................................................................................14
5.4. USE CASE # UCS – ECWS04 – CHANGING THE PASSWORD.................................................................................14
5.4.1 Use Case Name: Changing the Password.............................................................................................14
5.4.2 Actor: All Users.....................................................................................................................................14
5.4.3 Pre-Condition:.......................................................................................................................................14
5.4.4 Post-Condition:.....................................................................................................................................14
5.4.5 Basic Flow:............................................................................................................................................14
5.4.6 Alternate Flows:....................................................................................................................................14
5.5. USE CASE # UCS – ECWS05 – REGISTRATION OF THE USER................................................................................15
5.5.1 Use Case Name: Registration of the User.............................................................................................15
5.5.2 Actor: All Users.....................................................................................................................................15
5.5.3 Pre-Condition:.......................................................................................................................................15
5.5.4 Post-Condition:.....................................................................................................................................15
5.5.5 Basic Flow:............................................................................................................................................15
5.5.6 Alternate Flows:....................................................................................................................................15
5.6. USE CASE # UCS – ECWS06 – MANAGING THE PROFILE....................................................................................15
5.6.1 Use Case Name: Managing the Profile.................................................................................................15
5.6.2 Actor: Registered Users........................................................................................................................15
5.6.3 Pre-Condition:.......................................................................................................................................15
5.6.4 Post-Condition:.....................................................................................................................................15
5.6.5 Basic Flow:............................................................................................................................................15
5.6.6 Alternate Flows:....................................................................................................................................16
5.7. USE CASE # UCS – ECSW07 – SELECTING A PRODUCT.......................................................................................16
5.7.1 Use Case Name: Selecting a Product....................................................................................................16
5.7.2 Actor: Registered Users........................................................................................................................16
5.7.3 Pre-Condition:.......................................................................................................................................16
5.7.4 Post-Condition:.....................................................................................................................................16
5.7.5 Basic Flow:............................................................................................................................................16
5.7.6 Alternate Flows:....................................................................................................................................16
5.8. USE CASE # UCS – ECWS08 – CHECKING OUT..................................................................................................17
5.8.1 Use Case Name: Checking out.............................................................................................................17
5.8.2 Actor: Registered User..........................................................................................................................17
5.8.3 Pre-Condition:.......................................................................................................................................17
5.8.4 Post-Condition:.....................................................................................................................................17
5.8.5 Basic Flow:............................................................................................................................................17
5.8.6 Alternate Flows:....................................................................................................................................17
5.9. USE CASE # UCS – ECWS09 – STATE MAINTENANCE........................................................................................17
5.9.1 Use Case Name: State Maintenance....................................................................................................17
5.9.2 Actor: Registered User..........................................................................................................................17
5.9.3 Pre-Condition:.......................................................................................................................................17
5.9.4 Post-Condition:.....................................................................................................................................17
5.9.5 Basic Flow:............................................................................................................................................17
5.10. USE CASE # UCS – ECWS10 – SHARING PRODUCTS..........................................................................................18
5.10.1 Use Case Name: Sharing Products...................................................................................................18
5.10.2 Actor: All users.................................................................................................................................18
5.10.3 Pre-Condition:..................................................................................................................................18
5.10.4 Post-Condition:................................................................................................................................18
5.10.5 Basic Flow:.......................................................................................................................................18
5.10.6 Alternate Flows:...............................................................................................................................18
5.11. USE CASE # UCS – ECWS11 – ORDERS...........................................................................................................18
5.11.1 Use Case Name: Orders...................................................................................................................18
5.11.2 Actor: Registered Users...................................................................................................................18
5.11.3 Pre-Condition:..................................................................................................................................18
5.11.4 Post-Condition:................................................................................................................................18
5.11.5 Basic Flow:.......................................................................................................................................18
5.12. USE CASE # UCS – ECWS12 – VIEWING PRODUCTS..........................................................................................19
5.12.1 Use Case Name: View Products.......................................................................................................19
5.12.2 Actor: Webmaster............................................................................................................................19
5.12.3 Pre-Condition:..................................................................................................................................19
5.12.4 Post-Condition:................................................................................................................................19
5.12.5 Basic Flow:.......................................................................................................................................19
5.13. USE CASE # UCS – ECWS13 – ADD PRODUCTS IN THE SYSTEM...........................................................................20
5.13.1 Use Case Name: Add Products in the System..................................................................................20
5.13.2 Actor: Webmaster............................................................................................................................20
5.13.3 Pre-Condition:..................................................................................................................................20
5.13.4 Post-Condition:................................................................................................................................20
5.13.5 Basic Flow:.......................................................................................................................................20
5.13.6 Alternate Flow:................................................................................................................................20
5.14. USE CASE # UCS – ECWS14 – REMOVING PRODUCTS FROM THE SYSTEM............................................................20
5.14.1 Use Case Name: Removing Products from the System....................................................................20
5.14.2 Actor: Webmaster............................................................................................................................20
5.14.3 Pre-Condition:..................................................................................................................................20
5.14.4 Post-Condition:................................................................................................................................20
5.14.5 Basic Flow:.......................................................................................................................................20
5.14.6 Alternate Flow:................................................................................................................................21
5.15. USE CASE # UCS – ECWS15 – UPDATING PRODUCTS IN THE SYSTEM..................................................................21
5.15.1 Use Case Name: Updating Products in the System.........................................................................21
5.15.2 Actor: Webmaster............................................................................................................................21
5.15.3 Pre-Condition:..................................................................................................................................21
5.15.4 Post-Condition:................................................................................................................................21
5.15.5 Basic Flow:.......................................................................................................................................21
5.15.6 Alternate Flows:...............................................................................................................................21
5.16. USE CASE # UCS – ECWS16 – CATEGORIZING PRODUCTS IN THE SYSTEM...........................................................21
5.16.1 Use Case Name: Categorizing Products in the System....................................................................21
5.16.2 Actor: Webmaster............................................................................................................................21
5.16.3 Pre-Condition:..................................................................................................................................21
5.16.4 Post-Condition:................................................................................................................................22
5.16.5 Basic Flow:.......................................................................................................................................22
5.16.6 Alternate Flows:...............................................................................................................................22
5.17. USE CASE # UCS – ECWS17 – DE-CATEGORIZING PRODUCTS IN THE SYSTEM........................................................22
5.17.1 Use Case Name: De-Categorizing Products in the System..............................................................22
5.17.2 Actor: Webmaster............................................................................................................................22
5.17.3 Pre-Condition:..................................................................................................................................22
5.17.4 Post-Condition:................................................................................................................................22
5.17.5 Basic Flow:.......................................................................................................................................22
5.17.6 Alternate Flows:...............................................................................................................................22
5.18. USE CASE # UCS – ECWS18 – ADDING A CATEGORY IN THE SYSTEM...................................................................23
5.18.1 Use Case Name: Adding a Category in the System..........................................................................23
5.18.2 Actor: Webmaster............................................................................................................................23
5.18.3 Pre-Condition:..................................................................................................................................23
5.18.4 Post-Condition:................................................................................................................................23
5.18.5 Basic Flow:.......................................................................................................................................23
 5.18.6 Alternate Flows:...............................................................................................................................23
5.19. USE CASE # UCS – ECWS19 – UPDATING A CATEGORY......................................................................................24
5.19.1 Use Case Name: Updating a Category.............................................................................................24
5.19.2 Actor: Webmaster............................................................................................................................24
5.19.3 Pre-Condition:..................................................................................................................................24
5.19.4 Post-Condition:................................................................................................................................24
5.19.5 Basic Flow:.......................................................................................................................................24
5.19.6 Alternate Flows:...............................................................................................................................24
5.20. USE CASE # UCS – ECWS20 – REMOVING A CATEGORY FROM THE SYSTEM..........................................................24
5.20.1 Use Case Name: Removing a Category from the system................................................................24
5.20.2 Actor: Webmaster............................................................................................................................24
5.20.3 Pre-Condition:..................................................................................................................................24
5.20.4 Post-Condition:................................................................................................................................24
5.20.5 Basic Flow:.......................................................................................................................................24
5.20.6 Alternate Flows:...............................................................................................................................25
5.21. USE CASE # UCS – ECWS21 – VIEWING USERS................................................................................................25
5.21.1 Use Case Name: Viewing Users.......................................................................................................25
5.21.2 Actor: Webmaster............................................................................................................................25
5.21.3 Pre-Condition:..................................................................................................................................25
5.21.4 Post-Condition:................................................................................................................................25
5.21.5 Basic Flow:.......................................................................................................................................25
5.22. USE CASE # UCS – ECWS21 – ADDING MEMBERS IN THE SYSTEM......................................................................26
5.22.1 Use Case Name: Adding Members in the System...........................................................................26
5.22.2 Actor: Webmaster............................................................................................................................26
5.22.3 Pre-Condition:..................................................................................................................................26
5.22.4 Post-Condition:................................................................................................................................26
5.22.5 Basic Flow:.......................................................................................................................................26
5.22.6 Alternate Flows:...............................................................................................................................26
5.23. USE CASE # UCS – ECWS23 – DELETING MEMBERS FROM THE SYSTEM..............................................................26
5.23.1 Use Case Name: Deleting Members from the System.....................................................................26
5.23.2 Actor: Webmaster............................................................................................................................26
5.23.3 Pre-Condition:..................................................................................................................................26
5.23.4 Post-Condition:................................................................................................................................26
5.23.5 Basic Flow:.......................................................................................................................................26
5.23.6 Alternate Flows:...............................................................................................................................27
5.24. USE CASE # UCS – ECWS24 – UPDATING MEMBERS IN THE SYSTEM..................................................................27
5.24.1 Use Case Name: Updating Members in the System........................................................................27
5.24.2 Actor: Webmaster............................................................................................................................27
5.24.3 Pre-Condition:..................................................................................................................................27
5.24.4 Post-Condition:................................................................................................................................27
5.24.5 Basic Flow:.......................................................................................................................................27
5.24.6 Alternate Flows:...............................................................................................................................27
5.25. USE CASE # UCS – ECWS25 – VIEWING ORDERS IN THE SYSTEM.......................................................................28
5.25.1 Use Case Name: View Orders in the System....................................................................................28
5.25.2 Actor: Webmaster............................................................................................................................28
5.25.3 Pre-Condition:..................................................................................................................................28
5.25.4 Post-Condition:................................................................................................................................28
5.25.5 Basic Flow:.......................................................................................................................................28
5.26. USE CASE # UCS – ECWS26 – ADDING ORDER(S) IN THE SYSTEM......................................................................28
5.26.1 Use Case Name: Adding Order(s) in the System..............................................................................28
5.26.2 Actor: Webmaster............................................................................................................................28
5.26.3 Pre-Condition:..................................................................................................................................28
5.26.4 Post-Condition:................................................................................................................................28
 5.26.5 Basic Flow:.......................................................................................................................................28
5.26.6 Alternate Flows:...............................................................................................................................28
5.27. USE CASE # UCS – ECWS27 – REMOVING ORDERS FROM THE SYSTEM..............................................................29
5.27.1 Use Case Name: Removing Orders from the System.......................................................................29
5.27.2 Actor: Webmaster............................................................................................................................29
5.27.3 Pre-Condition:..................................................................................................................................29
5.27.4 Post-Condition:................................................................................................................................29
5.27.5 Basic Flow:.......................................................................................................................................29
5.27.6 Alternate Flows:...............................................................................................................................29
5.28. USE CASE # UCS – ECWS28 – UPDATING ORDERS IN THE SYSTEM.....................................................................29
5.28.1 Use Case Name: Updating Orders in the System.............................................................................29
5.28.2 Actor: Webmaster............................................................................................................................29
5.28.3 Pre-Condition:..................................................................................................................................29
5.28.4 Post-Condition:................................................................................................................................29
5.28.5 Basic Flow:.......................................................................................................................................29
5.24.6 Alternate Flows:...............................................................................................................................30
6. GRAPHICAL USER INTERFACES.................................................................................................................. 30
6.1. HOME SCREEN...............................................................................................................................................30
6.1.1. Description............................................................................................................................................30
6.1.2. User Actions..........................................................................................................................................31
6.2. LOGIN SCREEN...............................................................................................................................................31
6.2.1. Description............................................................................................................................................31
6.2.2. User Actions..........................................................................................................................................32
6.3. USER GUI FLOW............................................................................................................................................32
6.4. SHOPPING CART.............................................................................................................................................32
6.4.1. Description............................................................................................................................................33
6.4.2. User Actions..........................................................................................................................................33
7. DATABASE DESIGN................................................................................................................................... 33
A. LOGICAL MODEL.................................................................................................................................................33
B. DATA DICTIONARY...............................................................................................................................................33
8. RISK ANALYSIS......................................................................................................................................... 37
A. PROJECT RISKS....................................................................................................................................................37
B. TECHNICAL RISKS.................................................................................................................................................37
9. SYSTEM REQUIREMENTS.......................................................................................................................... 37
A. SERVER REQUIREMENTS.......................................................................................................................................37
i. Hardware Requirements...........................................................................................................................37
ii. Software Requirements.............................................................................................................................37
B. DEVELOPMENT REQUIREMENTS.............................................................................................................................37
iii. Hardware Requirements...........................................................................................................................37
iv. Software Requirements.............................................................................................................................38
10. VERSION HISTORY.................................................................................................................................... 38
1. Introduction
1.1.Purpose
This draft gives a complete overview of an Online Shopping Store Project. The overall
layout of the Project is discussed in detail. The expected requirements have been
elaborated. This will be a reference for all proceeding development activities.

1.2.Target Groups
This documentation has been drafted for the:
 Client – The expected requirements of the client have been listed. Models and
approaches have been proposed to deliver the best possible solution that caters the
needs of the client.
 Team – The document serves as the full and final requirements for the development
activities to be carried out.

1.3.Scope
The architecture, data definitions, models, work flows and usage scenarios for an
Online Shopping Store are covered in this document.

2. General Description
The final website created as a result of this project will allow the online processing and
selling of products.

2.1.Background
With the global expansion and increasing bandwidth of Internet Services, the legacy
business models have been transformed to allow their customers to shop online as
they find it easy and convenient. New businesses have also emerged that only have
online presence and at the same time are successfully generating hefty revenues and
profits.

This website will allow the customers to shop online.

2.2.Overview of the System

Users will visit the Online Shopping Store Website. They will select the products of their
choice from a list of categories. The Search feature can be used to get a list of similar
products. The selected products will be added to the Shopping Cart. The user can add
further products.
The user will proceed to checkout when no more products are to be added. The user will
be prompted to login by entering a username and password. Users shopping for the first
time would be directed to the registration page.
 After registration or login, the user will be required to confirm their shipping details.
Lastly the user will select from one of the listed payment options. In case of online
payment, the user will be directed to the payment gateway.

2.3.Characteristics of the User

The Online Shopping Store would comprise of the following users:

2.3.1. Guest
A user surfing the website without going through the formal registration process
and even if already registered, still has not successfully logged into the website
using the correct credentials.

2.3.2. Registered User

A user, successfully undergone through the registration process, and has logged
into the website, by supplying the correct credentials.

2.3.3. Webmaster
A user, with administrative privileges and is responsible for the smooth running of
the website by monitoring the ongoing processes, and ensuring timely
maintenance activities.
The user can add, update, modify and delete categories and/or their products. The
user can exercise the powers for adding, removing and updating the ordinary
registered users of the site.
The user also has access to the dashboard and real time analytics.

2.4.The User Views of the Products

2.4.1. Guest
This user is restricted to just view the products displayed publicly. The user can
select products, add them to cart and proceed to checkout but cannot complete
the order.

2.4.2. Registered User

This user can view the available and exclusive products, add them to cart, proceed
to checkout, select a payment option and incase of online payments, directed to
the payment gateway. The user can also review and make request to update the
registration information. The user can further view and track the orders.

2.4.3. Webmaster
This user can view the Admin Panel of the website, and the associated database.
3. Functional and Non-Functional Requirements
3.1.Functional
No. Requirement Description
Func.Req.1 Registering for the first time
A new user would be required to input the
following data, when registering for the first time:
 Full Name
 Valid Email Address
 Proposed Password
 Mobile Number
 Complete Postal Address.
Func.Req.2 Login The registered user should enter the following:
 Email Address used at the time of sign up.
 Password set at the time of sign up.
Func.Req.3 Resetting the Password The registered user has to enter either:
 Email Address used at the time of sign up.
 Mobile Number provided at the time of
sign up.
Func.Req.4 Adding a Product to Cart A product can be added to the cart if:
 It is in stock
 It is not exceeding the allowed quantity.
 It has not been restricted by webmaster.
Func.Req.5 Removing a Product from A product can be removed from the cart if:
the Cart  It already exists in the cart.
Func.Req.6 Proceeding to Check Out A user can proceed to check out if:
 A valid login session exists.
 The shopping cart is not empty.
 No more products are to be added or
removed.
Func.Req.7 Proceeding to the Payment A user can proceed to the payment gateway:
Gateway  A valid login session exists
 The shopping cart is not empty
 No more products are to be added or
removed.
 A complete postal address exists in the
system.
 A valid phone number is present in the
system.
 Online payment mode is selected.
Func.Req.8 Placing the order An order would be placed if:
 A valid login session exists
 The shopping cart is not empty

Func.Req.9 View Orders
Func.Req.1 Adding a new product to
0 the online shopping store
Func.Req.1 Updating a product in the
1 Online Shopping Store
Func.Req.1 Deleting a product from the
2 Online Shopping Store
Func.Req.1 Adding a new category to
3 the online shopping store
Func.Req.1 Updating a category in the
4 Online Shopping Store
Func.Req.1 Deleting a category from
5 the Online Shopping Store
 No more products are to be added or
removed.
 A complete postal address exists in the
system.
 A valid phone number is present in the
system.
 Payment has been successfully processed.
The orders can be viewed if:
 A valid login session exists.
 Payment carried out successfully.
To add a new product in the online shopping
store, the following conditions are necessary:
 A valid login session with administrative
privileges.
 The product identification number should
not exist in the system before.
 A category should be assigned.
To update a product in the online shopping store,
the following conditions are necessary:
 A valid login session with administrative
privileges.
 The product to be updated should exist in
the system.
To delete a product in the online shopping store, it
is necessary to have:
 A valid login session with administrative
privileges.
 The product to be deleted should exist in
the system.
To add a category into the system, it is necessary
to have:
 A valid login session with administrative
privileges.
 The category name should not exist in the
system before.
To update a category, it is necessary to have:
 A valid login session with administrative
privileges.
 The category to be updated should exist in
the system.
To delete a category, it is necessary to have:
 A valid login session with administrative
privileges.
 
The category to be deleted should exist in
the system.
Func.Req.1 Adding a user to the online To add a user into the system, it is necessary to
6 shopping store have:
 A valid login session with administrative
privileges.
 The email address should not exist in the
system before.
Func.Req.1 Updating a user in the To update a user, it is necessary to have:
7 online shopping store  A valid login session with administrative
privileges.
 The user to be updated should exist in the
system.
Func.Req.1 Deleting a user from the To delete a user, it is necessary to have:
8 online shopping store  A valid login session with administrative
privileges.
 The user to be deleted should exist in the
system.

3.2.Non-Functional
No Requirement Description
Non.Func.Req. UI (User Interface)  Responsive Website
1
Non.Func.Req. Security  Login required if proceeding to checkout
2 and routing to the payment gateway.
 Login with administrative privileges
required if products and/or categories
are to be added, updated or deleted.
 The same is required to view the dash
board.
Non.Func.Req. Independent of a Specific  Cross Platform
3 Platform
Non.Func.Req. Performance  The website should be able to serve
4 2,000 to 3,000 users at a specific
instance of time.

3.3.Assumptions
No Assumption
Assump. The email address is the unique identifier in the registration and/or login process.
1
Assump. Ordered Products are neither returnable nor refundable.
2
Assump. A user without administrative privileges cannot access the order of other users.
3

4. System Architecture
It is made of business and framework service layer.
 Business service layer houses the system components related to logic of the
application from the perspective of a business.
 Framework service layer is caters to the needs of business service layer.

4.1.High Level Architecture of the System

Overall system architecture consists of the user registration, members, orders,
performance and product management units.

4.1.1. User Registration Management

It deals with the first time registration of the new users.

4.1.2. Member Management

The user with administrative privileges can add, delete or update other users.

4.1.3. Product Management

The users with administrative privileges can add, delete and update products
and/or categories.

4.1.4. Order Management

The users with administrative privileges can view the order information of other
users.
 4.2.Low Level Architecture of the System
4.2.1. Log Maintenance
A complete log of all the events occurring would be maintained by this component.

4.2.2. System Security

This component will be responsible for all the matters related to the security.

4.2.3. Notifications
The notification component will be used for all generating all kinds of alerts to the
users.

4.2.4. System Management

The users of the system will be managed by this component.

5. Use Cases

5.1.Use Case # UCS – ECWS01 – Logging In

5.1.1 Use Case Name: Logging In

5.1.2 Actor: All Users

5.1.3 Pre-Condition:
The Website Login Page has to be opened by the User.

5.1.4 Post-Condition:
After successful login, the user is displayed the dashboard, customized as per the
user category/status.

5.1.5 Basic Flow:

1. The User inputs the email address.
2. The User enters the password.
3. The User then has to click on the Login button.
 4. The System looks for the typed email address. (E-1)
5. The Typed email address and password are matched with the database. (E-2)
6. The User is displayed the dashboard with clickable buttons to perform the tasks.

5.1.6 Alternate Flows:

The User can choose not to login, by not clicking on the login button or closing
the login page.
E-1: If the System cannot find the typed email address, the user will be directed
to the registration page.
E-2: In case the email address and passwords do not match, a message is
displayed to the user instructing, to again enter the email address and/or
password.

5.2.Use Case # UCS – ECWS02 – Logging Out

5.2.1 Use Case Name: Logging Out

5.2.2 Actor: Registered User

5.2.3 Pre-Condition:
The Registered User has an active login session.

5.2.4 Post-Condition:
The Active Login Session will end and the registered user will be redirected to
the System Login Page.

5.2.5 Basic Flow:

1. The Registered User navigates to the log out option.
2. The Registered User clicks on the log out button.
3. The System ends the Active Login Session of the User.

5.3.Use Case # UCS – ECWS03 – Forgotten Password

5.3.1 Use Case Name: Forgotten Password

5.3.2 Actor: All Users

5.3.3 Pre-Condition:
The System Login Page has to be opened by the User.

5.3.4 Post-Condition:
The password of the user is reset and the user is directed to the Dashboard.
 5.3.5 Basic Flow:
1. The User clicks on the Forgot Password button.
2. The User inputs his/her email address used at the time of sign-up.
3. The System matches the typed email address with the database. (E-1)
4. The User will receive a password reset link on the registered email address.
5. The System directs to the Password Change Page.

5.3.6 Alternate Flows:

The User can choose not to carry on with the Forgot Password process by not
clicking the Change Password button.
E-1: If the email address entered by the user does not match, a message is
displayed by the System to the User that the email address does not match and
needs to be entered again.

5.4.Use Case # UCS – ECWS04 – Changing the Password

5.4.1 Use Case Name: Changing the Password

5.4.2 Actor: All Users

5.4.3 Pre-Condition:
The User should have an active login session.

5.4.4 Post-Condition:
The Password for logging into the system is changed and the user is notified of
the change. The Dashboard is displayed.

5.4.5 Basic Flow:

1. The User clicks on the Password Change button.
2. The System directs to the Password Change Page.
3. The User inputs the Password that he/she wishes to keep.
4. The User inputs the Same Password in the Confirmed Password space.
5. The User then has to click on the Change Password button.
6. The Passwords entered, twice by the user, are matched by the system. (E-1)
7. A message regarding the successful change of password is displayed to the user.
8. The User is redirected to the Dashboard.

5.4.6 Alternate Flows:

The User can click on the Log Out button whenever he/she wishes to, and the
session would be ended.
E-1: If the newly entered passwords by the user do not match, a message is
displayed by the System to the User that the passwords do not match and need
to be entered again.
5.5.Use Case # UCS – ECWS05 – Registration of the User
5.5.1 Use Case Name: Registration of the User

5.5.2 Actor: All Users

5.5.3 Pre-Condition:
The User Registration Page has to be opened by the User.

5.5.4 Post-Condition:
The User is Registered and directed to the Dashboard.

5.5.5 Basic Flow:

1. The User enters the Name.
2. The User enters the Email Address. (E-1)
3. The User enters the Password.
4. The User clicks on the sign up button.
5. The System will send an email to the user, with a Confirmation Link.
6. The User will click on the Confirmation Link.
7. The User will be directed to the Dashboard.

5.5.6 Alternate Flows:

The user can choose not to register just by closing the browser tab.
E-1: If the email address already exists in the Database, the user will be directed
to the System Login Page.

5.6.Use Case # UCS – ECWS06 – Managing the Profile

5.6.1 Use Case Name: Managing the Profile

5.6.2 Actor: Registered Users

5.6.3 Pre-Condition:
The System Login Page has to be opened by the User.

5.6.4 Post-Condition:
The Profile of the User is updated and the user is notified of the changes.

5.6.5 Basic Flow:

1. The User can enter a new name.
2. The User can enter a new email address. (E-1)
3. The User can enter a new password.
4. The User can select a new or no address.
5. The User clicks on the update button.
 5.6.6 Alternate Flows:
The User can choose not to make any changes to their existing profile, by not clicking on
the update button.
E-1: If the email address already exists in the System Database, the user will be directed
to enter another email address that has not been previously used for registering into the
system.

5.7.Use Case # UCS – ECSW07 – Selecting a Product

5.7.1 Use Case Name: Selecting a Product

5.7.2 Actor: Registered Users

5.7.3 Pre-Condition:
The Registered User has an Active Web Session.

5.7.4 Post-Condition:
The Product is added to the cart of the registered user.

5.7.5 Basic Flow:

1. The Registered User clicks on a Product. (E-1)
2. The Registered User clicks on the add button.
3. The Registered User is notified that the Product has been added.

5.7.6 Alternate Flows:

The registered user can choose not to add a product by not clicking the add
button.
E-1: If the registered user is not allowed to click on a product, the user can try
selecting another product.
5.8.Use Case # UCS – ECWS08 – Checking out
5.8.1 Use Case Name: Checking out

5.8.2 Actor: Registered User

5.8.3 Pre-Condition:
The Registered User has an active login session and the products are added by
the Registered User.

5.8.4 Post-Condition:
The Registered User will have the Products available in the account.

5.8.5 Basic Flow:

1. The Registered User clicks on check out.
2. The System ensures that the registered user is logged in. (E-1)
3. The Registered User is directed to the Payment Gateway.
4. The Payment is successfully processed. (E-2)
5. The product is available to the User.

5.8.6 Alternate Flows:

The Registered User can choose not to check out by not clicking the check out
button.
E-1: If the Registered User does not have an active log in session, he/she will be
directed to the login page.
E-2: If the payment is not successfully carried out, the registered user is again
directed to the Payment Gateway.

5.9.Use Case # UCS – ECWS09 – State Maintenance

5.9.1 Use Case Name: State Maintenance

5.9.2 Actor: Registered User

5.9.3 Pre-Condition:
The Registered User has added the products in the cart and clicks on the
Checkout button.

5.9.4 Post-Condition:
The Registered User will be directed to the Checkout Page.

5.9.5 Basic Flow:

1. The Registered User clicks on the Check Out button.
2. The System directs the Registered User to the Login Page.
5.10. Use Case # UCS – ECWS10 – Sharing Products
5.10.1 Use Case Name: Sharing Products

5.10.2 Actor: All users

5.10.3 Pre-Condition:
The Users have an active login session.

5.10.4 Post-Condition:
The product will be shared with the recipients.

5.10.5 Basic Flow:

1. The User clicks on the share product button.
2. The User enters the Email Address of the recipients. (E-1)

5.10.6 Alternate Flows:

The user can choose not to share a product by not clicking on the share product button.
E-1: In case the entered email address does not conform to a standard email address
format, a message is displayed to the user instructing him/her, to again enter the email
address as per standard email format.

5.11. Use Case # UCS – ECWS11 – Orders

5.11.1 Use Case Name: Orders

5.11.2 Actor: Registered Users

5.11.3 Pre-Condition:
The registered user has an active login session.

5.11.4 Post-Condition:
The registered user can view the entire ordered products.

5.11.5 Basic Flow:

1. The registered user clicks on the Order button.
2. The System displays the orders to the registered users.
5.12. Use Case # UCS – ECWS12 – Viewing Products
5.12.1 Use Case Name: View Products

5.12.2 Actor: Webmaster

5.12.3 Pre-Condition:
An Active Login Session with administrative privileges.

5.12.4 Post-Condition:
The user with administrative privileges can view the products in the system.

5.12.5 Basic Flow:

1. The User with administrative privileges clicks on the Product Management.
2. The User with administrative privileges clicks on View Products.
5.13. Use Case # UCS – ECWS13 – Add Products in the System
5.13.1 Use Case Name: Add Products in the System

5.13.2 Actor: Webmaster

5.13.3 Pre-Condition:
An Active Login Session with administrative privileges.

5.13.4 Post-Condition:
The User with administrative privileges can add products in the system.

5.13.5 Basic Flow:

1. The User with administrative privileges clicks on Product Management.
2. The User with administrative privileges clicks on Add Product.
3. The User with administrative privileges selects a product.
4. The User with administrative privileges inputs a name. (E-1)
5. The User with administrative privileges clicks Add.
6. The Product is added.

5.13.6 Alternate Flow:

The User with administrative privileges can choose not to add a product by not
clicking on the Add button.
E-1: If the name already exists, the user will be directed to enter another name
that does not currently exist.

5.14. Use Case # UCS – ECWS14 – Removing Products from the

System
5.14.1 Use Case Name: Removing Products from the System

5.14.2 Actor: Webmaster

5.14.3 Pre-Condition:
An Active Login Session with administrative privileges.

5.14.4 Post-Condition:
The User with administrative privileges can remove Products from the system.

5.14.5 Basic Flow:

1. The User with administrative privileges clicks on Product Management.
2. The User with administrative privileges clicks on Remove a Product.
3. The User with administrative privileges selects a product.
4. The User with administrative privileges clicks Remove.
 5. The Product is removed.

5.14.6 Alternate Flow:

The User with administrative privileges can choose not to remove a product by
not clicking on the Remove button.

5.15. Use Case # UCS – ECWS15 – Updating Products in the

System
5.15.1 Use Case Name: Updating Products in the System

5.15.2 Actor: Webmaster

5.15.3 Pre-Condition:
An Active Login Session with administrative privileges.

5.15.4 Post-Condition:
The User with administrative privileges can update products in the system.

5.15.5 Basic Flow:

1. The User with administrative privileges clicks on Product Management.
2. The User with administrative privileges clicks on Update Product.
3. The User with administrative privileges selects a Product.
4. The User with administrative privileges clicks Edit.
5. The User with administrative privileges enters a name. (E-1)
6. The Product is updated.

5.15.6 Alternate Flows:

The User with administrative privileges can choose not to update a product by
not clicking on the Update button.
E-1: If the name already exists, the user with administrative privileges will be
directed to enter another name that does not currently exist in the system.

5.16. Use Case # UCS – ECWS16 – Categorizing Products in

the System
5.16.1 Use Case Name: Categorizing Products in the System

5.16.2 Actor: Webmaster

5.16.3 Pre-Condition:
An Active Login Session with administrative privileges.
 5.16.4 Post-Condition:
The User with administrative privileges can categorize products in the system.

5.16.5 Basic Flow:

1. The User with administrative privileges clicks on Product Management.
2. The User with administrative privileges clicks on Categorize Product.
3. The User with administrative privileges selects a Product.
4. The User with administrative privileges clicks Add.
5. The Product is added into a category in the system.

5.16.6 Alternate Flows:

The User can choose not to categorize a Product by not clicking on the Add button.

5.17. Use Case # UCS – ECWS17 – De-Categorizing Products in the

System
5.17.1 Use Case Name: De-Categorizing Products in the System

5.17.2 Actor: Webmaster

5.17.3 Pre-Condition:
An Active Login Session with administrative privileges.

5.17.4 Post-Condition:
The User with administrative privileges can de-categorize products in the system.

5.17.5 Basic Flow:

1. The User with administrative privileges clicks on Product Management.
2. The User with administrative privileges clicks on Categorize Product.
3. The User with administrative privileges selects a product.
4. The User with administrative privileges clicks Remove.
5. The Product is removed from a category in the system.

5.17.6 Alternate Flows:

The User can choose not to de-categorize a product in the system, by not clicking
on the Remove button.
5.18. Use Case # UCS – ECWS18 – Adding a Category in the
system
5.18.1 Use Case Name: Adding a Category in the System

5.18.2 Actor: Webmaster

5.18.3 Pre-Condition:
An Active Login Session with administrative privileges.

5.18.4 Post-Condition:
The User with administrative privileges can add a new category into the system.

5.18.5 Basic Flow:

1. The User with administrative privileges clicks on Product Management.
2. The User with administrative privileges clicks on Categorize Products.
3. The User with administrative privileges clicks on Categories.
4. The User with administrative privileges clicks Add New Category.
5. The User with administrative privileges enters a Name. (E-1)
6. The Product Category is added into the system.

5.18.6 Alternate Flows:

The User with administrative privileges can choose not to add a category by not
entering anything.
E-1: If the name already exists, the user with administrative privileges will be
directed to enter another name that does not currently exist.
5.19. Use Case # UCS – ECWS19 – Updating a Category
5.19.1 Use Case Name: Updating a Category

5.19.2 Actor: Webmaster

5.19.3 Pre-Condition:
An Active Login Session with administrative privileges.

5.19.4 Post-Condition:
The User with administrative privileges can update a category of the system.

5.19.5 Basic Flow:

1. The User with administrative privileges clicks on Product Management.
2. The User with administrative privileges clicks on Categorize Products.
3. The User with administrative privileges clicks on Categories.
4. The User with administrative privileges selects a Category.
5. The User with administrative privileges clicks on Updating.
6. The User with administrative privileges enters a new Name. (E-1)
7. The Product Category is edited in the system.

5.19.6 Alternate Flows:

The User with administrative privileges can choose not to update a category by
not entering anything.
E-1: If the name already exists, the user with administrative privileges will be
directed to enter another name that does not currently exist.

5.20. Use Case # UCS – ECWS20 – Removing a Category from the

system
5.20.1 Use Case Name: Removing a Category from the system

5.20.2 Actor: Webmaster

5.20.3 Pre-Condition:
An Active Login Session with administrative privileges.

5.20.4 Post-Condition:
The User with administrative privileges can remove a category from the system.

5.20.5 Basic Flow:

1. The User with administrative privileges clicks on Products Management.
2. The User with administrative privileges clicks on Categorize Products.
3. The User with administrative privileges clicks on Categories.
 4. The User with administrative privileges selects a Category.
5. The User with administrative privileges selects Remove.
6. The User with administrative privileges confirms it.
7. The Product Category is removed from the system.

5.20.6 Alternate Flows:

The User with administrative privileges can choose not to edit a category by not
confirming the removal.

5.21. Use Case # UCS – ECWS21 – Viewing Users

5.21.1 Use Case Name: Viewing Users

5.21.2 Actor: Webmaster

5.21.3 Pre-Condition:
An Active Login Session with administrative privileges.

5.21.4 Post-Condition:
The User with administrative privileges can view the registered users of the
system.

5.21.5 Basic Flow:

1. The User with administrative privileges clicks on Members Management.
2. The User with administrative privileges clicks on View Users.
3. The System displays the Registered Users to the User with administrative
privileges.
5.22. Use Case # UCS – ECWS21 – Adding Members in the System
5.22.1 Use Case Name: Adding Members in the System

5.22.2 Actor: Webmaster

5.22.3 Pre-Condition:
An Active Login Session with administrative privileges.

5.22.4 Post-Condition:
The Users with administrative privileges can add members to the system.

5.22.5 Basic Flow:

1. The User with administrative privileges clicks on Members Management.
2. The User with administrative privileges clicks on Add Members.
3. The User with administrative privileges enters the name. (E-1)
4. The New User is added.

5.22.6 Alternate Flows:

The User with administrative privileges can choose not to add a member by not
entering anything.
E-1: If the name already exists, the user with administrative privileges will be
directed to enter another name that does not currently exist.

5.23. Use Case # UCS – ECWS23 – Deleting Members from the System
5.23.1 Use Case Name: Deleting Members from the System

5.23.2 Actor: Webmaster

5.23.3 Pre-Condition:
An Active Login Session with administrative privileges.

5.23.4 Post-Condition:
The User with administrative privileges can delete the members from the
system.

5.23.5 Basic Flow:

1. The User with administrative privileges clicks on Members Management.
2. The User with administrative privileges clicks on Delete Members.
3. The User with administrative privileges selects a name.
4. The User with administrative privileges confirms the deletion.
5. The User is deleted.
 5.23.6 Alternate Flows:
The User with administrative privileges can choose not to delete a member by not
confirming the removal.

5.24. Use Case # UCS – ECWS24 – Updating Members in the

System
5.24.1 Use Case Name: Updating Members in the System

5.24.2 Actor: Webmaster

5.24.3 Pre-Condition:
An Active Login Session with administrative privileges.

5.24.4 Post-Condition:
The User with administrative privileges can update the members of the system.

5.24.5 Basic Flow:

1. The User with administrative privileges clicks on Members Management.
2. The User with administrative privileges clicks on Update Members.
3. The User with administrative privileges selects a name. (E-1)
4. The User with administrative privileges clicks on edit.
5. The User with administrative privileges edits the profile.
6. The User profile is edited.

5.24.6 Alternate Flows:

The User with administrative privileges can choose not to edit a member by not
typing anything new.
E-1: If the name already exists, the user with administrative privileges will be
directed to enter another name that does not currently exist.
5.25. Use Case # UCS – ECWS25 – Viewing Orders in the System
5.25.1 Use Case Name: View Orders in the System

5.25.2 Actor: Webmaster

5.25.3 Pre-Condition:
An Active Login Session with administrative privileges.

5.25.4 Post-Condition:
The User with administrative privileges can view the orders of the system.

5.25.5 Basic Flow:

1. The User with administrative privileges clicks on Orders Management.
2. The User with administrative privileges clicks on View Orders.
3. The System displays the Orders to the User with administrative privileges.

5.26. Use Case # UCS – ECWS26 – Adding Order(s) in the System

5.26.1 Use Case Name: Adding Order(s) in the System

5.26.2 Actor: Webmaster

5.26.3 Pre-Condition:
An Active Login Session with administrative privileges.

5.26.4 Post-Condition:
The User with administrative privileges can add orders in the system.

5.26.5 Basic Flow:

1. The User with administrative privileges clicks on Orders Management.
2. The User with administrative privileges clicks on Add Orders.
3. The User with administrative privileges enters the Order Number. (E-1)
4. The User with administrative privileges selects Products
5. The New Order is created in the System.

5.26.6 Alternate Flows:

The User with administrative privileges can choose not to add an order by not entering
any Order Number.
E-1: If the Order Number already exists, the user will be directed to enter another
Order Number that does not currently exist.
5.27. Use Case # UCS – ECWS27 – Removing Orders from the
System
5.27.1 Use Case Name: Removing Orders from the System

5.27.2 Actor: Webmaster

5.27.3 Pre-Condition:
An Active Login Session with administrative privileges.

5.27.4 Post-Condition:
The User with administrative privileges can delete orders from the system.

5.27.5 Basic Flow:

1. The User with administrative privileges clicks on Orders Management.
2. The User with administrative privileges clicks on Remove Orders.
3. The User with administrative privileges selects an Order Number.
4. The User with administrative privileges confirms the deletion.
5. The Order is deleted from the System.

5.27.6 Alternate Flows:

The User with administrative privileges can choose not to delete an order by not
confirming the removal.

5.28. Use Case # UCS – ECWS28 – Updating Orders in the System

5.28.1 Use Case Name: Updating Orders in the System

5.28.2 Actor: Webmaster

5.28.3 Pre-Condition:
An Active Login Session with administrative privileges.

5.28.4 Post-Condition:
The User with administrative privileges can update orders in the system.

5.28.5 Basic Flow:

1. The User with administrative privileges clicks on Orders Management.
2. The User with administrative privileges clicks on Update Orders.
3. The User with administrative privileges selects an Order Number.
4. The User with administrative privileges clicks on update.
5. The User with administrative privileges adds or removes the Order.
6. The User with administrative privileges confirms it.
7. The Order is updated in the System.
 5.24.6 Alternate Flows:
The User can choose not to update an order by negating the confirmation to
update.

6. Graphical User Interfaces

6.1.Home Screen

6.1.1. Description
1. A search bar with text field.
2. A clickable search button.
3. A home icon button in the top left corner of the webpage.
4. Login link in the top right corner of the website.
5. Shopping cart also present at the top right corner of the page and continuously
displaying the amount of products present in the shopping cart.
6. Products categories and brands listed on the left margin of the webpage.

6.1.2. User Actions

1. Search Bar: Allows the user to enter text in the search bar followed by either
the enter key or by clicking on the magnifying glass button.
 2. Search Button: Submits the text query entered in the search bar to the search
engine.
3. Home Icon: Navigates the User back to the Home Page.
4. Login link: When clicked, displays the space for entering email address and
password.
5. Shopping Cart: The user can click on the cart icon to see details of the items
present in the cart
6. Left Side Icons: The user can click on either a product or a brand or a category
to see multiple offerings.

6.2.Login Screen

6.2.1. Description
1. A text field to input email address.
2. Another text field to input password.
3. A button for submitting credentials.
4. A link for forgotten password recovery.
 6.2.2. User Actions
1. Email Address Text field: Accepts email address in the form of alphabets, numerals and
symbols and then displays the same as output for the user to identify any error during
the typing process.
2. Password Text field: Also accepts password in the form of alphabets, numerals and
symbols but only displays dots for privacy and security concerns.
3. Submit Button: Sends the entered email address and password to the server for further
instructions.
4. Password Recovery Link: Guides the user to the password recovery procedure page.

6.3.User GUI Flow

6.4.Shopping Cart

6.4.1. Description
1. The Shopping Cart button on the navigation bar.
2. An edit button in the Shopping Cart sliding window.
 6.4.2. User Actions
1. Shopping Cart Button: When clicked, opens a small sliding window on the same screen.
2. Edit Button in Shopping Cart: Allows the removal or reduction in the quantity of the
products present in the cart.

7. Database Design
a. Logical Model

b. Data Dictionary

Table Name: Brands

Table Definition: This table stores the information about brands.
Column Column Is PK Is FK Column Data Null Option
Name Definition Type
brand_id Unique Yes No Number NOT NULL
Identifier of
the brand
brand_title Brand’s No No Varchar NOT NULL
name (255)

Table Name: Cart

Table Definition: This table stores the information of carts that contain product
Column Column Is PK Is FK Column Data Null Option
Name Definition Type
cat_id Unique Yes No Number NOT NULL
Identifier of
 the cart
p_id Unique No No Number NOT NULL
Identifier of
the product
which the
customer
added in cart
user_id Unique No No Number NOT NULL
Identifier of
the user
Qty Shows the No No Number NOT NULL
number of
items the
customer
purchased

Table Name: Categories

Table Definition: This table stores the information about categories.
Column Column Is PK Is FK Column Data Null Option
Name Definition Type
cat_Id Unique Yes No Number NOT NULL
Identifier of
the category
cat_title Describes the No No Varchar NOT NULL
category title (255)

Table Name: Order

Table Definition: This table stores the information of orders made by customers.
Column Column Is PK Is FK Column Data Null Option
Name Definition Type
order_Id Unique Yes No Number NOT NULL
Identifier of
the order
user_id Unique No Yes Number NOT NULL
Identifier of
the user
product_id Unique No Yes Number NOT NULL
Identifier of
the product
Qty Stores the No No Number NOT NULL
information
regarding
 quantity of
order
Trx_id Unique No NO Number NOT NULL
Identifier of
transaction
number
p-status Shows NO NO Varchar(50) NOT NULL
whether the
order has
been
completed or
not

Table Name: Products

Table Definition: This table stores the information of products.
Column Name Column Is PK Is FK Column Data Null Option
Definition Type
product_Id Unique Yes No Number NOT NULL
Identifier of a
product
product_cat Unique No Yes Number NOT NULL
Identifier of
the category
of product
product_brand Unique No Yes Number NOT NULL
Identifier of
brand of the
product
Product_title Stores the No No Varchar(150) NOT NULL
information
regarding
title of
product
product_price Stores the No NO Number NOT NULL
info about
the price of a
product
product- Store some NO NO Text NOT NULL
description description
about
product
product_image Store images NO NO Text NOT NULL
of products
 product_keyword Store some NO NO Text NOT NULL
s extra
description
about
production

Table Name: user-info

Table Definition: This table stores the information of users.
Column Column Is PK Is FK Column Data Null Option
Name Definition Type
user_id Unique Yes No Varchar(150) NOT NULL
Identifier of a
user
first_name Store the first No NO Varchar(150) NOT NULL
name of users
last_name Store the No NO Varchar(150) NOT NULL
second name
of users
email Stores the e- No No Varchar(150) NOT NULL
mail address
of users
password Stores the No NO Password NOT NULL
personal
password of
users
mobile Stores the NO NO Varchar(150) NOT NULL
mobile
number of
users
address1 Store the NO NO Varchar(150) NOT NULL
address
(house ,
street and
block) of the
users
address2 Store the NO NO Varchar(150) NOT NULL
address (city
& town) of
the users
8. Risk Analysis
a. Project Risks
 Increased time for completion.
 Increased costs.
 Requirements not correctly comprehended.

b. Technical Risks
 No agility during the course of developmental activities.
 Lack of professional approach before and during the development.
 Competitors employing cutting edge technologies.

9. System Requirements
a. Server Requirements
i. Hardware Requirements
The following hardware equipment would be required:
For Database Server Deployment:
 Intel Xeon Processors
 32GB RAM
 240GB HDD
For Application Server Deployment:
 Intel Xeon Processors
 32GB RAM
 120GB HDD

ii. Software Requirements

The following software would be required for the deployment of this website:
 CentOS or Microsoft Windows Server
 Database client (Microsoft SQL Server)
 Apache Tomcat

b. Development Requirements
iii. Hardware Requirements
The following hardware would be needed:
 Intel Core Processor
 16GB RAM
 160GB HDD

iv. Software Requirements

The following software would be required for the development of this website:
  Windows/Linux/Mac OS
 Apache Server
 MySQL
 Notepad++ or Sublime

10. Version History

Version Date Description Author
1.0 05/06/2020 Requirements Mr. Fahad Amjad
Gathering
1.1 06/06/2020 Architecture of Mr. Fahad Amjad
System
1.2 07/06/2020 Use Case Scenarios Mr. Muhammad
Kamran
1.3 08/06/2020 Graphical User Mr. Imran Ahmed
Interface
1.4 09/06/2020 Logical Model & Data Mr. Imran Ahmed
Dictionary
1.5 10/06/2020 Editing Mr. Muhammad
Usama
1.6 12/06/2020 Publishing Mr. Muhammad
Usama