Specification
Contents
1. Introduction …….………………………………………………………………………………………………………….……………………..3
1.1Purpose ……………………………….….………….…………………………….……………………………………………………………3
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.
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.
2. General Description
1- People can request for the product if the product is not available in marketplace, we
have simplified this process by “Upload Product Image”.
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.
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.
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.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.
Software Requirements Specification for Ez Mart Page 7
3.4 Shop
3.5 Request Ad
4. Performance Requirements
Since Ez Mart is going to web application, it does require a powerful machine. Machine
should have an internet access.
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.
Software Requirements Specification for Ez Mart Page 8
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
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.
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.
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
Sign Up
Log In
Use Case ID: EZMART-UC-1.2
Includes: N/A
Assumptions: 1. User must have internet access.
Notes and Issues: N/A
View Profile
Use Case ID: EZMART-UC-1.3
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.
Edit Profile
Use Case ID: EZMART-UC-1.4
Request Shop
Use Case ID: EZMART-UC-2.1
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.
2. Internet availability must be ensured.
Software Requirements Specification for Ez Mart Page 14
Auction
Postconditions: 1. System will review and add the product in auction list.
Exceptions: N/A
Includes: N/A
Assumptions: 1. User must have internet access.
Software Requirements Specification for Ez Mart Page 15
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
Assumptions: 1. User must have internet access.
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
Assumptions: 1. User must have internet access.
Track order
Use Case ID: EZMART-UC-5.0
Exceptions: N/A
Includes: N/A
Assumptions: 1. User must have internet access.
Notes and Issues: N/A
Software Requirements Specification for Ez Mart Page 17
Register Complaint
View Feed
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”.
7. Interface Requirements
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 Panel
Create Ad
Manage Ad
Admin Banner Ad Management Panel
Banner Ad request Panel
Enable/Disable/Delete Banner Ad
4. Shop Advertisement
Software Requirements Specification for Ez Mart Page 26
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
9. PRELIMINARY SCHEDULE
11. REFERENCES
www.ebay.com
www.amazon.com
www.daraz.com