Final Ez Srs

Software Requirements
Specification
Contents
1. Introduction …….………………………………………………………………………………………………………….……………………..3
1.1Purpose ……………………………….….………….…………………………….……………………………………………………………3
1.2 Scope .............................................................................................................................. 3

1.3 Overview ......................................................................................................................... 3
1.4 Business Context ........................................................................................................... 3
2. General Descripation ........................................................................................................... 3
2.1 Product Functions .......................................................................................................... 6
2.2 Similar System Information ........................................................................................... 6
2.3 User Characters .............................................................................................................. 6
3. Functional Requirements .................................................................................................... 6
3.1 Login/Sign Up ................................................................................................................. 6
3.2 Search Product ............................................................................................................... 6
3.3 Auction ............................................................................................................................ 6
3.3 Request Product ............................................................................................................. 7
3.4 Shop ................................................................................................................................ 7
3.5 Request Ad ..................................................................................................................... 7
4. Performace Requirements................................................................................................... 7
5. Non-Functional Requirements ............................................................................................ 7
5.1. Security .......................................................................................................................... 7
5.2. Reliability ....................................................................................................................... 8
5.3. Maintainability................................................................................................................ 8
5.4. Portability ....................................................................................................................... 8
5.5. Extensibility ................................................................................................................... 8
5.6. Reusability ..................................................................................................................... 8
5.7. Availability ..................................................................................................................... 8
5.8. Flexibility ........................................................................................................................ 8
5.9. Efficiency ....................................................................................................................... 8
5.10. Application Affinity/Compatibility .............................................................................. 8
5.11. Serviceability ............................................................................................................... 9
5.12. Binary Compatibility .................................................................................................... 9
6. Operational Sceanrios ....................................................................................................... 10
6.2 Use Case Specifications ............................................................................................. 11
6.3 Activity Diagram .......................................................................................................... 18
7. Interface Requirements ..................................................................................................... 18
8. PRELIMINARY OBJECT-ORIENTED DOMAIN ANALYSIS ............................................... 24
8.1 Activity Diagram .......................................................................................................... 24
8.2 Class Description ......................................................................................................... 25
8. PRELIMINARY SCHDULE .................................................................................................. 27
9.1. Project Gantt chart .......................................................................................................... 28
Software Requirements Specification for Ez Mart Page 4
1. Introduction
Ez Mart is an online marketplace that will allow buyer to request a product by uploading image
and Sellers will compete on the basis of user rating to ensure the quality and by full filling buyer’s
request. Additionally, customers can acquire an online shop through our website to start their
own business, thus our platform will not only promote existing e-commerce stores but also help
develop new ones. There will be an auction product option available where buyers can place
bids and highest bidder will won the auction.
1.1 Purpose
This SRS describes the software requirements both functional and non-functional for the
website Ez Mart. This document is intended to be used by the members of the project team that
will implement and verify the correct functioning of the system. All requirements specified here
are unless stated otherwise. This document will be used in all phases of Software Process.
1.2 Scope
Our web solution will entertain all the online store’s holders across Pakistan. Ez Mart will entertain
all the online store’s holders across Pakistan. The shop owners will be able to display
their shop without spending any money, and they will also take advantage of their personal
newsfeed to promote their shops. Interested customers for a new e-shop can also acquire well
designed free ez-shop which can be accessible only through our website. Shop owner can
auction products, which will be sold to the highest bidder.
1.3 Overview
Ez Mart will help buyers and sellers to have a better shopping experience. This is first time
we are introducing bidding system in a marketplace, which is going to benefit both users.
1.4. Business Context
Ez Mart is a local marketplace that serves the needs of people of Pakistan. It provides a lot
of options for online shopping in Pakistan from which you can make the choices that are
right for you. In short, we strive for our customer’s satisfaction and always keep our
customers our top priority.
Here is working flow of platform;

Figure 1.1 Overview of Ez Mart
2. General Description
2.1 Product Functions
The main functionality of the system are:
1- People can request for the product if the product is not available in marketplace, we
have simplified this process by “Upload Product Image”.
2- Auction will benefit both parties.
3- A special team will manage the complaint cell, which will solve dispute problems.
4- There will be payment gateway, which can support local payment method such as
easy paisa.
5- Ez Mart contains improved rating system which is going to rank users according
their reputation.
2.2 Similar System Information

Similar platform like Daraz.pk, Olx.com, Kamyu.com are available in Pakistan but none
of these are have Auction. As we are under developed country we need to build a
stand-alone system for our people of Pakistan.
2.3 User Characteristics
Proposed project should satisfy to the following user classes:

Developer: The role of a developer is to design and maintain the website.
Client: Clients are divided into 2 categories.
1- Buyer
2- Seller (Primary User)
Primary User: It defines a user who works at and provide the services to their
customers.
Visitors: People can visit the website and can search for the products in marketplace.
3. Functional Requirements
3.1 Login/Sign Up
Description All users must be Login/Sign Up before shopping. Visitors can explore the
marketplace but can’t purchase/sell anything if they are not register.
Priority This is the First and highest rank requirement.
Restrictions and Risks Malicious attacks to misuse the system.
Dependencies User must be connected to the internet.
3.2 Search Product
Description All User can search in mart.

Priority This is the second highest rank requirement.
Restrictions and Risks The possible risk is that the user is looking for a product and it is not
available in marketplace.
Dependencies Seller notifications panel.
3.3 Auction
Description Seller can auction the product if they want to sell it fast.
Priority This is the Third highest rank requirement.
Restrictions and Risks There is no restrictions and risks
Dependencies No dependencies.
3.3 Request Product
Description Buyer can request the product.

Priority This is the Fourth highest rank requirement.
Restrictions and Risks If none of the seller, respond back to buyer’s request. System will delete
the request after a set time.
Dependencies User must have registered as buyer.
3.4 Shop
Description Seller can request for the shop.

Priority This is the Fifth highest rank requirement.
Restrictions and Risks No Risk.
Dependencies Seller can only have one shop at a time.
3.5 Request Ad
Description Seller can request the ad of his shop.

Priority This is the Sixth highest rank requirement.
Restrictions and Risks No Risk.
Dependencies No Dependency.
4. Performance Requirements
Since Ez Mart is going to web application, it does require a powerful machine. Machine
should have an internet access.
5. Other Non-Functional Attributes
In this section, non-functional requirements will be explained in detail. The Requirements

Specification captures system requirements for the following areas: security, reliability,
maintainability, portability, extensibility, reusability, availability, flexibility, efficiency etc.
5.1. Security
Product should be able to protect privacy of user data using SSL. Workspace of the technical
user should only be accessed through user own credentials and any other user should not be
able to access to the user private data. Since execution will also be done in the machine, user
should be restricted in terms of user rights. Also rights of the user should be restricted so that
user can not harm to system by the programs they run or by the commands they run on
terminal.
5.2. Reliability
The system has to be reliable due to the importance of data and the damages that can be
caused by incorrect or incomplete data.
5.3. Maintainability
Changes must be verified on the behalf of system act. The system should provide
automatically notification to developer by e-mail about failure overdue, reservation results
etc.
5.4. Portability
The system is fully portable and any system using any web browser should be able to use
the features of the system, including any hardware platform that is available or will be
available in the future. An end-user is use this system on any OS; either it is Windows. The
system shall run on PC, Laptops etc.
5.5. Extensibility
The system can be extended later with other functionalities required.
5.6. Reusability
If other company need the data relating to the legal information. It can be used as a
foundation for any upcoming subpages or a future overhaul of the website.
5.7. Availability
The System is available 100% for the user and it could be use 24 hrs. The system shall be
operational 24 hours a day and 7 days a week.
5.8. Flexibility
Flexible service will be highly desirable for future extension. Non-Functional Requirements
define system properties and constraints.
5.9. Efficiency
Mean Time to Repair (MTTR). Even if the system fails, the system will be recovered back up
within a day or less.
5.10. Application Affinity/Compatibility

The web presence shall be compatible with all modern web browsers (IE 6+, Chrome,
Firefox, Safari, etc.).
5.11. Serviceability
It will provide the administrators an easy-to-use interface with capabilities to maintain the
website. This paired with abundant documentation should provide a smooth and error free
way to service their web presence.
5.12. Binary Compatibility
The website will be operational with any operating system that can use modern browsers
that support HTML 4.01 and partial support of CSS.
6. OPERATIONAL SCENARIOS
6.1 Use Case Diagram
Admin use case
Figure 6.1 Admin use case

Buyer use case
Figure 6.2 Buyer Use case
Seller use case
Figure 6.3 Seller Use case

6.2 Use Case Specifications
Sign Up
Use Case ID: EZMART-UC-1

Use Case Name: Sign Up
Actors: End user(Primary)
Description: In this use case, the end user gets himself/herself registered to the EzMart. For
that purpose, he/she has to provide detailed information inquired by the system on
signup page. In result, end user would be able to avail services provided by EzMart.
Trigger: After clicking the “Sign Up” button by the user.

Preconditions: 1. End user should be on the home page of the web application.
2. Internet must be available.
Post conditions: 1. End user account successfully created.
2. An email confirmation is sent to the user.
Normal Flow: 1. End user opens the “ EzMart” web application on their desktop.
2. System displays the home page of application.
3. End user clicks the “Signup” button.
4. System displays the signup page to the end user.
5. End user enters the information in the fields which shows on the page. i.e.
• Name
• Email
• Password
• Re-enter Password
• Cell Number
6. End user clicks on the register button.
7. An email confirmation is sent to the end user confirming the registration.
Alternative Flows: N/A
Exceptions: N/A
Includes: N/A
Assumptions: 1.User must have internet access.
Notes and Issues: N/A
Log In
Use Case ID: EZMART-UC-1.2
Use Case Name: Login
Actors: End User (Primary)

Description:
Buyer clicks the “Registered” button.
System displays the popup message “Successfully signup into the system”.
Trigger: After clicking on the “Login” button by the user.

Preconditions: 1. System has the user already signed up to the system,
2. Internet availability must be ensured.
Postconditions: 1. System has user successfully logged into it

Normal Flow: 1. User opens the “EzMart application” on their desktop.

2. System displays the home page of application.
3. User clicks the “Login” button.
4. System displays the login page to the user.
5. User enters the email id in the “Email Id” field and password in
the “Password” field
6. User presses the “Ok” button.
7. System verifies the email id and password.
8. System displays the message “Successfully Log in to the Account”.
9. System displays the main page of the application to the user.

Exceptions: 5a. In step 5 of the normal flow, if the user enters the email id which
doesn’t exist in the system data base.
1. System displays the message “No User Account Exists Against This
Email Id”
2. User re-enters the correct email id in the “Email Id” field.
3. Resume to step 5 of the normal flow.
5b. In step 5 of the normal flow, if the password enters by the user
mismatch against the email Id.
1. System displays the message “Wrong Password”.
2. Password field become empty.
3. User re-enters the correct password in the “Password” field.
4. Resume to step 7 of the normal flow.
Includes: N/A
Assumptions: 1. User must have internet access.
View Profile
Use Case Name: View Profile
Actors: Buyer (Primary) End User (Primary)

Description: In this use case, the user would be able to view his/her personal profile. For
that purpose, he has to click on account button As a result, he would be able
to view his profile, so he could edit his information if he wants to change it.
Trigger: After clicking the “Account” icon.

Preconditions: 1. System has user already logged into it.
2. System already has some user’s profile information,
3. Internet availability must be ensured,
Postconditions: 1. System can allow editing to the user once he views the profile.
Normal Flow: 1. User clicks the “Account” icon.
2. System displays the dropdown list of all the profile functions.
3. User click the “View Profile” button.
4. System displays the profile page to the user.

Exceptions: 1. Unable to connect to the server.
Includes: N/A

Edit Profile
Use Case Name: Edit Profile
Actors: Buyer(primary) End user (primary)

Description: In this use case, user would be able to edit his/her profile. In result, if user
wants to make changes to his/her profile, he would be able to do that by
providing new information. As a result, email is sent to the user to indicate
that his/her profile has been edited.
Trigger: After clicking the “Account” icon.
Preconditions: 1. System has the user already signed up to the system,
Postconditions: 1. System ensures the necessary changes as made by the user.
2. An email confirmation is sent to the user indicating the change.
Normal Flow: 1. User clicks the “Account” icon.

2. System displays the dropdown list.
3. User clicks the “Edit Profile” button.
4. System displays the profile page in which some entries are editable.
5. User edits his/her profile.
6. User clicks the “Submit” button.
7. System displays the message “Profile successfully edited”.
Includes: N/A
Request Shop
Use Case Name: Request Shop
Actors: Buyer
Description: In this use case, Buyer can send Request Shop to place his ad on the front
advertisement banner. For that purpose, Buyer has to provide details about
the ad, and as a result, the Buyer would be able to promote his, her shop if
admin approves.
Trigger: After clicking the “Request Shop” button
Preconditions: 1. Buyer’s shop should be registered in the mall.
Postconditions: 1. System will send respective ad to the admin for approval.
Normal Flow: 1. User clicks the “Request Shop” button.

2. System takes the user to another page for details.
3. System displays a textbox for user to enter the details of ad and a
button “Upload picture” to upload picture for the ad.
4. User gives the details about the shop, and uploads the picture
5. User clicks the “Send Request” button.
6. System displays the message “Request successfully made”.

Exceptions: 3a. In the step 3 of the normal flow, if the user exceeds the word limits
of the textbox
1. System displays the message “Give details in the given word limit”
2. Buyer re-enters the details.
3. Resume step 3 from the normal flow.
3b. In the step 3 of normal flow, if the user forgets to upload picture
before clicking “send request button”
1. Systems requests the user to upload the picture.
2. User uploads the picture
3. Resume from step 3 of normal flow.
Includes: N/A
Assumptions: 1. Buyer must have internet access.
Auction
Use CaseID: EZMART-UC-2.2

Use Case Name: Comment
Actors: End UserBuyer

Description: In this use case, the user would be able to the product. As a result, the
system will display that product in auction list. Product will be at the auction
list according to the user instructions.
Trigger: After clicking on the shop.

Preconditions: 1. System should have user registered to it
3. There should be a product in the store.
Postconditions: 1. System will review and add the product in auction list.
Normal Flow: 1. User clicks on the Auction.

2. System displays all the product in the auction.
3. User can place bid.
4. Product will be sold to higher bidder when the time ends.
Exceptions: N/A
Includes: N/A

Rate the shop
Use Case Name: Rate the shop
Actors: End User

Description: In this use case, the user would be able to review the shop by clicking on the
stars for rating purposes. As a result, the system will provide a review based
scheme to the new users to help them make shopping related decisions.
Trigger: After clicking on the shop.
Postconditions: 1. System will have a record of user’s reviews.
Normal Flow: 1. User clicks on the respective shop.

2. User rates the shop by clicking on the stars
3. User presses “submit” button.
Alternative Flows: 2a. In the step 2 of the normal flow, if user has already rated the shop
before
1. User will press the button “edit rating”.
2. Resume from step 2 of the normal flow,
Exceptions: N/A
Includes: N/A

Place order
Use Case Name: Place Order
Actors: End User

Description: In this use case, the user would able to place the order for the products he
added to the cart. For that purpose, he clicks on the cart icon. As a result, he
would be redirected to the page containing all the information about the
products that were in the cart.
Trigger: After clicking on the “cart” icon.
Preconditions: 1. Availability of the product must be ensured.
Postconditions: 1. Email shall be sent to the customer for the confirmation.
Normal Flow: 1. User clicks on the cart on the top left corner of the screen,
2. The system displays the Place Order Screen for that product.
3. The system displays the name and address of the person
associated with the profile, user is logged in.
4. The user verifies the information by clicking on “Confirm” button.
5. For each product ordered, the system add price to the total.
6. The system will verify the customer information, and then save the
order as pending.
7. The order is marked confirmed, an order id is returned to the
customer.
8. A confirmation email shall be sent to the user.
Alternative Flows: 4a. In the step 4 of the use case, if user wants to edit his/her
information
1. The user clicks on “edit information” button’.
2. Systems displays two textboxes with labels “name” and
“address”
Exceptions: N/A
Includes: N/A
Track order
Use Case Name: Track Order
Actors: End User

Description: In this use case, the user would able to track the order he placed. For that
purpose, he has to press on “track order” tab. As a result, he would be
redirected to the “Find order” screen where he shall track his/her order.
Trigger: After clicking on the “track order” icon.

Preconditions: 1. User has ordered something from our website.
Postconditions: 1. Email shall be sent to the customer for the confirmation.

Normal Flow: 1. User clicks on the track order icon.
2. The system displays the Find order screen.
3. The user enters an order id or name and address.
4. The user selects search.
5. The system returns information with the order id, and the use case
ends.
Alternative Flows: 3a. If the user entered a name and address
1. The system will display a list of orders for that customer with all
details.
2. The user will select one order.
Exceptions: N/A
Includes: N/A
Register Complaint
Use Case Name: Register Complaint
Actors: End User

Description: In this use case, the user would able to register a complaint if he/she
encounters any problem. For that purpose, the user has to fill a form
regarding the type of the problem he has encountered. In result, a detailed
complaint with a distinct number is created and an email is sent to the user
to ensure help.
Trigger: After clicking on the “Register Complain” icon.
Post conditions: 1. An email confirmation shall be sent to the customer for
confirmation
Normal Flow: 1. User clicks on the “register complaint” icon.
2. System asks the user to choose from the dropdown menu of shops
that are currently present in the EzMart.
3. System further asks the user to write about the nature of problem
and the people involved in the text box as to further clarify the
details.
4. Supportive image should be provided as an evidence to support the
claim.
5. User enter all the details and press the button “submit”.
6. System assigns a random electronically generated number to the
complaint to easily manage it.
7. System will send an email confirmation the user if everything goes
right.
Exceptions: N/A
Includes: N/A
View Feed
Use Case Name: View Feed
Actors: End user

Description: In this use case, the end user would be able to view the feed, where Seller he
has posted about his products earlier. For that purpose, end user has to click
view feed tab. As a result, the user is directed to his newsfeed.
Trigger: After pressing on newsfeed his tab.

Preconditions: N/A
Postconditions: N/A
Normal Flow: 1. User clicks on newsfeed.
2. System redirects the user to newsfeed.
3. System shows all the posts by different Sellers.
4. The user enters on a post to buy something.
5. The use case ends.
Alternative Flows: 4a. In step 4 of the normal flow, if there are no posts to shows to the
end user.
1. System displays the message “No posts to show”.

Includes: N/A
6.3 Activity Diagram
Auction Module Activity

7. Interface Requirements
Figure 7.1 Sign Up
Figure 7.2 Sign In

Figure 7.3 Main Screen
Figure 7.4 Feed

Figure 7.5 Ad Panel
Figure 7.6 Advertisement Banner
Figure 7.7 Shop Panel

Figure 7.8 Recommended Shop panel
Figure 7.9 Disabled shops

Figure 7.10 Auction

8. PRELIMINARY OBJECT-ORIENTED DOMAIN ANALYSIS
8.1 Activity Diagram
Figure 8.1 Class Diagram

8.2 Class Description
Following are the main activities of the proposed web application.
1. Profile management
  Seller
  Create Profile
  Manage Profile
  Manage Shop
 Auction a product


  Buyer
  Create Profile
  Manage Profile
  Place bid
  Request Product
2. Shop management
  Seller Shop Management Panel

  Manage Shop
  Edit Information
  Create Newsfeed
 Create Advertisement


  Admin Shop Management Panel
  Shop request Panel
 Enable/Disable Shop


3. Banner Advertisement
  Seller Panel
  Create Ad
 Manage Ad

  Admin Banner Ad Management Panel
  Banner Ad request Panel
 Enable/Disable/Delete Banner Ad
4. Shop Advertisement
  Seller Panel
  Create Ad
 Manage Ad

  Admin Shop Ad Management Panel
  Shop Ad request Panel
  Enable/Disable/Delete Shop Ad
5. Need a shop
  Shop Development
1. Add Product
2. Cart
3. Order Management
4. Sales
5. Automation of Shop Creation
6. Rating And Reviews
  Top Rated Shops
  Rate Now
7. News Feed
  Create Feed
  User Manage Feed
  Admin Manage Feed

8. Complaint Cell
  Create Complaint
 Manage Complaint
Admin Manage Complaint

9. PRELIMINARY SCHEDULE
Figure 9.1 Schedule

9.1. Project Gantt chart
Figure 9.2 Gantt chart
10. DEFINITIONS, ACRONYMS, ABBREVIATIONS
  SRS- Software Requirement Specification

  PHP- PHP Hypertext Processor
  MTTR- Mean Time to Repair
  IE- Internet Explorer
  HTML- Hyper-Text Markup Language
 CSS- Cascading Style Sheets
11. REFERENCES
www.ebay.com
www.amazon.com
www.daraz.com

Final Ez Srs

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Final Ez Srs

Загружено:

Авторское право:

Доступные форматы

Software Requirements

1.2 Scope .............................................................................................................................. 3

1.4. Business Context

Here is working flow of platform;

Figure 1.1 Overview of Ez Mart

2.1 Product Functions

The main functionality of the system are:

2- Auction will benefit both parties.

2.2 Similar System Information

2.3 User Characteristics

Proposed project should satisfy to the following user classes:

3.2 Search Product

Description All User can search in mart.

3.3 Request Product

Description Buyer can request the product.

Description Seller can request for the shop.

Description Seller can request the ad of his shop.

5. Other Non-Functional Attributes

In this section, non-functional requirements will be explained in detail. The Requirements

The system can be extended later with other functionalities required.

5.10. Application Affinity/Compatibility

5.12. Binary Compatibility

6.1 Use Case Diagram

Admin use case

Figure 6.1 Admin use case

Buyer use case

Figure 6.2 Buyer Use case

Seller use case

Figure 6.3 Seller Use case

6.2 Use Case Specifications

Use Case ID: EZMART-UC-1

Trigger: After clicking the “Sign Up” button by the user.

Use Case Name: Login

Actors: End User (Primary)

Trigger: After clicking on the “Login” button by the user.

Postconditions: 1. System has user successfully logged into it

Normal Flow: 1. User opens the “EzMart application” on their desktop.

Alternative Flows: N/A

Use Case Name: View Profile

Actors: Buyer (Primary) End User (Primary)

Trigger: After clicking the “Account” icon.

Alternative Flows: N/A

Assumptions: 1. User must have internet access.

Use Case Name: Edit Profile

Actors: Buyer(primary) End user (primary)

Normal Flow: 1. User clicks the “Account” icon.

Notes and Issues: N/A

Use Case Name: Request Shop

Postconditions: 1. System will send respective ad to the admin for approval.

Normal Flow: 1. User clicks the “Request Shop” button.

Alternative Flows: N/A

Notes and Issues: N/A

Use CaseID: EZMART-UC-2.2

Actors: End UserBuyer

Trigger: After clicking on the shop.

Normal Flow: 1. User clicks on the Auction.

Notes and Issues: N/A

Use Case ID: EZMART-UC-3.0

Use Case Name: Rate the shop

Actors: End User

Normal Flow: 1. User clicks on the respective shop.

Notes and Issues: N/A

Use Case Name: Place Order