SRS - HridoyAlam/CSE327projectE-Comercesite GitHub Wiki

Welcome to the CSE327projectE-Comercesite wiki!

Software Requirements Specification (SRS)

for

E-Commerce Web Application (EasyBuy)

Prepared by Raisa Mehjabin Azni (1620216642) ,MD.Mohaimenur (1731268642) ,Jahidul Alam (1621558642),

Electrical and Computer Engineering (ECE)

North South University, Bangladesh

27th July 2020

Chapter 1

Introduction

1.1 Purpose

The e-commerce web application EasyBuy is intended to provide complete solutions for vendors as well as customers through a single gateway using the Internet. Defining and describing the functions and specifications of the E-Commerce System is the primary goal of this Software Requirements Specification (SRS). This Software Requirements Specification actually stands for the usability of the e-commerce site, which will make it easier to surf through the latest products available on the market for the official users. In clear terms, the system’s primarily implements the required functionality as specified by our customers and clients.

1.2 Intended Audience

In this web application, we are focusing on mainly 4 types of moderators.

• The admin panel: The admin panel of this web application will be responsible for managing the products available in the product list, verify the input (required information) taken from the users of the e-commerce web application, arrange the products according to their categories, release time (new or old), and bestseller and maintain the reset and refresh of the application.

• Project developers (Group members): The group members handling the project will have access to the Software Requirement Specification (SRS) document and will manage the front-end and back-end development of this web application project. Each function testing will also be handled by the project development team. A specific development architecture will be followed in designing and building this e-commerce web application such as MVC or MV-VM architecture.

• Instructor: The course instructor of the course CSE327 (Software Engineering), Dr. Md. Musfique Anwar Sir will have access to this Software Requirement Specification (SRS) document. All the required instructions and features suggested by Sir will be implemented in the project.

• Retail store management body: Certain parts of this Software Requirement Specification (SRS) will also be available to the retail store management body, who will responsible for notifying the product list managers about the availability of the most frequently ordered products.

1.3 Intended Use

The intended audience can use this Software Requirement Specification (SRS) document in multiple ways by following the detailed description and criterion of individual functions provided by the moderators and developers of this project.

• Adding new functions: The front-end and back-end developers can efficiently use this document to add new functionalities to the existing system. It is mandatory to follow the detailed functional structure of the existing model. This will allow the developers to maintain the internal connection between different functional elements of the system. the detailed description of unit testing of each feature will also be elaborately described in this document for the test managers to use.

• Updating existing features: As Software Requirement Specification (SRS) document has all the detailed specifications of the features, it is possible to make any trivial changes to the implementation of the features so that they can perform more smoothly and without any failure in real-time.

• Providing suggestion for improvements: The course instructor of this project will be able to see all the functionality details of this e-commerce project and suggest any modification or implementation of any additionally needed features. The scope, further possibilities, detailed user specification will be visible to the instructor.

• Monitoring any product specification change: The retail store management body will be able to monitor and keep track of any trivial product specification change made by the developer or test manager of the product. By following this, they will be able to meet the purchase preferences made by the users of this e-commerce web application. As a result, this web application will reduce the gap between the seller and the customer.

1.4 Product Scope

Benefits:

• This application is different from other online purchase web platforms because of its easy functionality and friendly User interface design from and it will be regularly updated with respect to the user's needs.

• The e-commerce web application will have all the latest products available in the market. the product will be labeled as new or bestseller. Which makes it easier for the user to navigate through the trending products and browse according to the category.

• Because of the easy product detail interface the customer will be able to investigate through the detailed specification of installation and software specification of the products. He/She will be able to add, remove, and increase or decrease the quantity of the product without any complications.

• The payment service and specification is clean and hassle-free for the customer to proceed with the payment process.

• In this web application, discount facility management is also implemented. The customer will be able to browse through the products according to the discounts available on the products. Discounts will be adjusted to the cart.

Objective and Goals:

• The main goal and objective of this project are to present the customers with an easy and comfortable gateway for purchasing their necessary items on a daily basis. The interface is fast and clusters with no unnecessary ads or functionalities.

• In the marketplace, it is estimated that this project will make significant progress as it will have customer demand. The integration of various from other retail management and web store corporation will broaden the horizon of this e-commerce web application.

Chapter 2

Overall Description

2.1 User Classes and Characteristics

The users who will effectively operate this web application are:

1) Registered Members (Primary User):

• Will be able to log in and log out of the system.

• Will see all the products, listed on the homepage with their price and category.

• Will be able to see the detailed specification of each product on the product detail page.

• Will be able to add or remove and choose the product quantity from the product detail page.

• Will be able to see the total number of products added to the cart, total price (with or without discount) in the order summary page/cart.

• Will be able to checkout and proceed with the payment procedure to confirm their purchase for this web application.

2) Guests (Secondary User):

• Will be able to explore the product lists.

• Will be able to sign-up and become a registered member.

• will be able to browse through different functionalities of the web application.

2.2 User Needs

Needs of each user of the e-commerce web application.

1) Registered Members (Primary User):

• Need a clean interface to browse through the latest products available on the market.

• Need specific short documentation of the product they are willing to purchase.

• Need to be sure about their purchase. As a result, several photos of the product are needed to display.

• Need to see all the products on one page to sort out their purchase or control the overall quantity of the products.

• Need to easily delete and add products to the cart.

• Need to navigate between the order summary page, homepage, and checkout page smoothly and efficiently.

• Need to have easy checkout and payment process through stripe functionality.

• Need adjustments in generating the total amount in case of discounts and special offers.

2) Guests (Secondary User):

• Need to explore the web application signing up to the system. they need to get a general idea about the features and offers this e-commerce plate form will offer to them as a registered user.

• Need to sign up in the system in order to become registered members. This will give them the ability to make a purchase and explore more through the available products.

2.3 Operating Environment

The operating system needed to access this e-commerce web application is windows 8 and above, 32-bit or 64-bit, and macOS. As it is a browser-based web application, it will operate in all the famous browsers, as a model we are taking Google chrome versions 16.0.1 and opera browser latest. Internet connection is needed for successful access to the platform as it is web-based.

2.4 Constraints

• The deadline for the project is within two and a half months.

• Because of the quarantine due to Covid-19, work from home has significantly limited the scope of group work.

• Working and communicating with project development members have become quite challenging due to constantly failing internet connection.

• Lack of high configured processor or device, it is difficult to execute important tasks, codes, emulators on usual devices available at hand.

• Lack of payment verification and testing the payment process with a real visa card is not safe and ethically unproven.

• If internet access is not familiar than it will be tough to use this web application.

• Due to the lack of internet in the remote areas, finding resources regarding the assembly of the product has been significantly hampered.

• Proper query commands for such complex functions.

• product being out of stock.

• Users may face unwanted cart added or unwanted amounts in their cart.

• Wait for payment confirmation notification.

• Users sometimes have to provide their information more than one times.

2.5 Assumptions

The Assumptions needed to be considered while building the e-commerce web application system:

• It is assumed that the users of this web application have good command over the English language.

• The users are 10 years old and above.

• The users have verified email ID and password for sign-up

• The user will provide honest and valid information in the system while sign-up and making payments.

• The user accustomed to operating the internet. And has a secure internet connection.

• The users are used to using Chrome or any frequently accessed browser.

• The user has a general idea of online shopping and making a purchase.

• The user operates Android or iOS mobile phones.

Chapter 3

Requirements

3.1 Functional Requirements

1. Product List:

As a user

I want to see all the latest products available on the e-commerce home page.

So that, I can find my desired product efficiently and also can browse through the product list.

Confirmation/Acceptance:

•	There will be four products in a row on the home page.

•       There will be at least 2 or 3 rows containing the products on each page.

•	There will be arrows on both sides to navigate through the products.

•	Each product on the home page will have an image, price, product description, quick view, and add to cart option.

•	Users will be able to see the total amount of product he/she has selected for purchase on the home page.

2. Adding items to a cart (Product View/Detail):

As a User

I want to add the product from its item detail page to the cart.

So that, I can see the description of my desired product and add it to the cart.

Confirmation/Acceptance:

•       Users will be able to see a detailed picture of the selected product.
                
•	Users will be able to see a detailed description of the functionality of the product.

•	Users will be able to directly buy the product to the cart from the product detail page through buy now option.
      
•	Users will be able to add and remove the product to the cart from the product detail page.
      
•	Users will be able to check whether the product is in the cart. If not then he/she can add the product

3. Creating an order summary:

As a registered member

I want to see an order product summary

So that, can see all of my selected products on one page and confirm my overall purchase.

Confirmation/Acceptance:

•       Registered members will be able to see all his/her selected product on one page in a chronological order

•	Registered members will be able to increase or decrease the quantity of the products.

•	Registered members will be able to delete individual products for the order summary page.

•	There will be a table containing item title, price, quantity, and total item price.

•	If there are discounts available on multiple products, they will be applied while calculating the total amount. It will show the total price and total final price.

•	Registered members will be able to continue their shopping or will be able to proceed to checkout.

4. The checkout process and payment:

As a registered member

I want to I need to check out.

So that, I can confirm my purchase and go to the payment page.

Confirmation/Acceptance:

•       Registered members will have to provide their address, country name. zip code etc

•	They have to check that they are going to the shipping address is the same as my billing address.

•	Registered members will be able to get a notification after their successful persuasion.

•	Registered members can save their VISA card numbers for the next purchase if they want.

•	After payment they will get an email notification.

5. Keeping track:

As a user

I want to track the movement of my product

So that, I can monitor whether my ordered product is arriving or canceled.

Confirmation/Acceptance:

•	Customer has to provide his/her order number (which one he/she received after successful purchased) and email address which one he/she used during order time.

•	If they provide all correct required information they will be able to see the details

3.2 Non Functional Requirements

Safety and Security:-

    • The latest and most popular products will be available on the e-commerce site.

    • More payment gateways if possible.

    • The response time should be less.

    • All the products will be distinctively separated so that it’s easy to navigate and search among them.

    • Make Data security more powerful and secure.

    • The payment method should be kept with high-security.

    • The latest and most popular products will be available on the e-commerce site.

    • Products will be available from a reliable and verified retail source.

    • The sign-up, log-in, and log-out function will efficiently verify the registered members given information by fetching from the database.

    • The guests will have to input verified and original information while doing sign-up and becoming a registered member.

    • An effective rating and comment system can be applied to each available product.

    • There will be a fixed amount of product in the stock. If it’s not available out of stock message will be shown.

    • A pop-up notification will be displayed while adding and removing a product in the cart.

    • Navigation between the home page, checkout page, and product detail page will be carefully designated to make the page flow more well-organized for the members.

    • If the system fails to add the product in the cart or generate the order summary, the system needs to reboot and refresh for member execution and provide spontaneous customer service.

    • Multiple pictures can be added on the product detailed page.

    • Users have to check the details by their own responsibility.

    • Users have to provide their personal information by their own responsibility.

Quality:-

    • The UI of the application should be user friendly so that anyone can use it.

    • Each and every product must arrange in their own category.