Online Agriculture products Store Software Requirements Specification Version 1

Online Agriculture products Store

Software Requirements Specification

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

Version 1.0

Group Id: S1802AAD20
Supervisor Name: Miss Nadia Tabassum

Revision History
Date (dd/mm/yyyy) Version Description Author
Current date 1.0 SRS document includes a scope of the project, Functional requirement Non-Functional requirements, Use Case Diagram, Use scenarios, Adopted Methodology, Work Plan/Gantt chart Kashif Javaid Gill
MC170202189

Table of Contents

1. Scope (of the project)
2. Functional Requirements Non Functional requirements
3. Use Case Diagram
4. Usage Scenarios
5. Adopted Methodology
6. Work Plan (Use MS Project to create Schedule/Work Plan)

SRS Document

Scope of Project

The purpose of online agriculture store website is to help farmers to buy agriculture products from their homes. Farmers can buy different agriculture products from the website and connect with business vendor also can share a different type of information and resources as well. Farmers can buy different seeds, pesticides from anywhere through internet connectivity. Customers will get them registered in this application and then will be able to access the website by logging into the system. They can view/search the list of items based on their categories, add the items in their Wish List, also able to update it as per requirement, view the feedbacks and reviews of other customers regarding any product, add the product/item in the Cart and select any of three payment options Cash on delivery, Payment via Credit Card or online transfer, update and conceal the order, view the Sales promotions on web site as well as through SMS.
Admin can log in to the admin panel and will be able to add/delete the list of categories such as seeds, pesticides, fertilizers etc. Admin can add the list of the item of each category based on their names, price and company name and mention their expiry as well. Admin will also add/update/delete information about promotion and sales and also send SMS to regular customers on any promotion or sale. Furthermore, the admin will be able to view customer profile, feedback, reviews generate reports on monthly basis, confirm order over SMS, payment receipt also generated for customer record and as well for admin.

Functional and Non-Functional Requirements:

Functional Requirements:

Administrator Login:

Login process to allow the authentic user to access the admin panel.

Add/Delete List:
Admin will be able to add the list of categories such as seeds, pesticides, fertilizers, and so on. Admin will then add the list of items for each category. Items can be added based on their name, prices, company name, pictures of products. Admin will add manufacturing and expiry date of the product. Admin can also update and delete the categories and items. Admin will be able to add/update/delete information about promotions and sales.

Sales Promotion SMS:
Admin can send SMS to regular customers on any promotion and Sale.

Customer feedback:
Admin will be able to view customer’s profile, feedback, and reviews.

Generate Report:
Admin will be able to generate Sales Report and profit on the monthly basis.

Order Confirmation SMS:
Admin will confirm the order through SMS.

Payment Receipt Generation:
Payment receipt is also generated for customer record as well as for admin.

Customer’s Login:
Customers will get them registered in this application and then will be able to access the website by logging into the system.

View/search items
The Customer can view/search the list of items based on their categories.

Add to Wish List:
The Customer can add the items to their Wish List also able to edit it as per need.

Customer’s Feedback/review:
The Customer can view the feedbacks, and reviews of other customers regarding any product.

Add to Cart /Payment Options:

The Customers can add the product/item in the Cart and select any of three payment options Cash on delivery, Payment via Credit Card or online transfer.

Cancel order:
The Customer can update and conceal the order.

View/SMS Sales and promotion:
The Customer can view the Sales and promotions on web site as well as via SMS.

Non Functional Requirements

Performance Requirement:

The system response to the user must be reasonable.

User-friendly

The Application will have an easy to use interface.

Reliability

The unwavering quality of the general program relies upon the dependability of the different parts. The primary mainstay of unwavering quality of the framework is the reinforcement of the database which is persistently kept up and refreshed to mirror the latest changes. In this way, the general solidness of the framework relies upon the security compartment and its basic working framework.

Availability

The framework ought to be accessible constantly, which means the client can get to it utilizing a web program, just limited by the downtime of the server on which the framework runs. If there should be an occurrence of an equipment disappointment or database debasement, a substitution page will appear. Additionally, if there should arise an occurrence of an equipment disappointment or database defilement, reinforcements of the database ought to be recovered from the server and spared by the chairman. At that point, the administration will be restarted. It implies 24 X 7 accessibility.

Maintainability

A business database is utilized for keeping up the database and the application server deals with the site. If there should arise an occurrence of a disappointment, a reinstatement of the program will be finished. Likewise, the product configuration is being finished in light of privacy with the goal that practicality should be possible effectively.

Portability

Highlights of the framework, including any equipment stage that is accessible or will be accessible later on.
An end-client is utilized this framework on any OS; it is possible that it is Windows or Linux.
The framework should keep running on PC, Laptops, and PDA as well.

Use case Diagram

Usage Scenarios

1.

Use case Title Login
Use case ID 1
Actions Admin Actions
• Admin request for the sign in page.

• Admin will fill the required fields. System Response
• The System will generate the page.

• The System will check whether the required fields are filled correctly or not.
Description This function Check that only authorized users can access the system. An authorized user is that who has an account in the system.
Pre-conditions Authorized user.
Post-conditions The User has been successfully logged into the system.
Alternative Path • User enter incorrect username and password
• The System will not log in the user.
Authors/Actors Administrator.
Exceptions Username or password is incorrect.

2.

Use case Title Add user
Use case ID 2
Actions Admin Actions
• Admin request for login,
• Admin will select the category to add the new user.
• Fill Add user form details Name, Address etc.
System Response
• The System will confirm login.
• The System will check whether the user already exists or not.
• Store the user information in the database
Description This use case is about adding a new user to the existing system with rights defined at the time of user account creation.
Pre-conditions All must Require information about the new user should be available.
The Database should be available in online mode.

Post-conditions A new user is successfully Added.
Alternative Path • All must require information about the user should be available.
• The Database should be available in online mode.
Authors/Actors Administrator.
Exceptions Admin may abandon the operation anytime.

3.

Use case Title Delete user
Use case ID 3
Actions Admin Actions
• Admin request for login,
• Admin will select the category to delete the user.
• Admin will delete the user.
System Response
• The System will confirm login.
• The System will check whether the user exists.
• Delete the user information from the database.
Description This use case is about deleting a user from the existing system with privileges defined at the time of user account creation.
Pre-conditions • All must require information about the user should be available.
• The Database should be available in online mode.
Post-conditions A user account is successfully deleted.
Alternative Path • The User enters the incorrect username
• The System will not recognize the user.
Authors/Actors Administrator.
Exceptions Admin may abandon the operation anytime.

4.

Use case Title Update user
Use case ID 4
Actions Admin Actions
• Admin request for login.

• Admin will select the category to update the user.

• Admin will update the user.
System Response
• The System will confirm login.
• The System will check whether the user exists.
• Update the user information in the database.
Description This use case is about updating a user to the existing system.
Pre-conditions All must Require information about the user should be available.
The Database should be available in online mode.

Post-conditions A user account is successfully updated.
Alternative Path • The User enters the incorrect username
• The System will not recognize the user.
Authors/Actors Administrator.
Exceptions Admin may abandon the operation anytime.

5.

Use case Title Sales promotion SMS
Use case ID 5
Actions Admin Actions
• Admin request for login,
• Admin will select the category for Sales Promotion SMS.
• Admin will send the sales promotion SMS to selected Customer.
• Admin will send the sales promotion SMS to selected customers.
.
System Response
• The System will confirm login.
• The System Search for users to send sales promotion SMS.
• The System will generate sales promotion SMS.
Description This use case is about sales promotion SMS to customers.
Pre-conditions • All must require information about the user should be available.
• The Database must be accessible in online mode.
Post conditions A sales promotion SMS successfully sent.
Alternative Path None.
Authors/Actors Administrator.
Exceptions Admin may abandon the operation anytime.

6.

Use case Title Order Confirmation SMS
Use case ID 6
Actions Admin Actions
• Admin request for login.
• Admin will select the category for order confirmation SMS.
• Admin will send order confirmation SMS to customers.
.
System Response
• The System will confirm login.
• The System Search for users to send order confirmation SMS.
• The System will generate order confirmation SMS
Description This use case is about Order Confirmation SMS.

Pre-conditions • All must require information about the user should be available.
• The Database should be available in online mode.
Post-conditions Order Confirmation SMS is successfully sent.
Alternative Path None.
Authors/Actors Administrator.
Exceptions Admin may abandon the operation anytime.

7.

Use case Title Payment Receipt Generate
Use case ID 7
Actions Admin Actions
• Admin request for login.
• Admin will select the category for payment receipt generation.
• Admin will generate payment receipt.
System Response
• The System will confirm login.
• Search for users to generate payment receipt.
• The System will generate payment receipt.
Description This use case is about Payment receipt Generation.
Pre-conditions • All must require information about the user should be available.
• The Database must be accessible in online mode.
Post conditions Payment receipt generate successfully.
Alternative Path None.
Authors/Actors Administrator.
Exceptions Admin may abandon the operation anytime.

8.

Use case Title Sign up/Costumer Login
Use case ID 8
Actions Admin Actions
• Customer request for sign up page.

• Customer will fill the required fields.

• Customer submits the form. System Response
• The System will generate the page.

• The System will check whether the required fields are filled correctly or not.

• The System store the information in the database.
Description This function Check that only authorized users can access the system. An authorized user is that who has an account in the system.
Pre-conditions • Internet Connection is working.
• The Server is not down.
Post-conditions The customer has been successfully signed up.
Alternative Path • The user fills unformatted information.
• The Server is down and can’t reach to the database server.
Authors/Actors Customer.
Exceptions Username or password is incorrect.

9.

Use case Title View/Search list
Use case ID 9
Actions Admin Actions
• Customer search for the required item.

• Customer search the product in categories.
System Response
• The Search will be a call to get the required product.

• The System will check whether the required product available or not.
Description This use case is about searching the available products.

Pre-conditions Log in to the system.

Post-conditions The product is found.
Alternative Path • Required product not found.
• Searched product Price is high.
Authors/Actors Customer.
Exceptions Customer may abandon the operation anytime.

10.

Use case Title Add to Wish List
Use case ID 10
Actions Admin Actions
• Customer search the required item.
• Customer will select the item.
System Response
• The Search will be a call to get the required product.
• The System adds the item to the Wish List.

Description This use case is used to add the item to Wish List.
Pre-conditions Log in to the system.
Post-conditions The Product is added to Wish List.
Alternative Path • Required item not found
• The Product is already on the Wish List.
Authors/Actors Customer.
Exceptions Customer may abandon the operation anytime.

11.

Use case Title Add to Cart
Use case ID 11
Actions Admin Actions
• Customer search the required item.
• Customer will select the item.
System Response
• The Search will be a call to get the required product.
• The System adds the item to the cart.

Description This use case is used to add the item to the cart
Pre-conditions Log in to the system
Post-conditions Item is added to the cart.
Alternative Path • Require item not found
• Item is already in the cart.
Authors/Actors Customer.
Exceptions Customer may abandon the operation anytime.

12.

Use case Title Delete from Cart
Use case ID 12
Actions Admin Actions
• Customer searches the required item from the cart.
• Customer will select the item to be deleted.
System Response
• The Search will be a call to get the required product.
• The System deletes the item from the cart.

Description This use case is used to delete the item from the cart.
Pre-conditions Log in to the system
Post-conditions Item is deleted from the cart.
Alternative Path Required item not in the cart

Authors/Actors Customer.
Exceptions Customer may abandon the operation anytime.

13.

Use case Title Payment
Use case ID 13
Actions Admin Actions
• The Customer selects the payment option.
• Customer will select the payment method (cash on delivery, credit card, bank transfer).
• Customer confirms the payment method. System Response
• The System will generate the page.
• The System will generate the page for payment methods.
• The System will check whether the payment method and proceed further.
Description This use case is about payment.
Pre-conditions
• The customer has added credit card number (payment via credit card).
• The customer has added bank account number (payment via bank transfer)
• The Database should be available in online mode.

Post conditions Payment made successfully.
Alternative Path
None.
Authors/Actors Customer.
Exceptions Customer may terminate the operation anytime.

14.

Use case Title Give Feedback
Use case ID 14
Actions Admin Actions
• The Customer selects the Feedback option.
• Customer will select the category for feedback.
• Customer submits feedback. System Response
• The System will generate the page.
• The System will check whether the format is correct or not.
• The System will generate feedback.
Description This use case is about a feedback by the customer.
Pre-conditions Customer login to the system.
Post-conditions Feedback is given successfully.
Alternative Path None.
Authors/Actors Customer.
Exceptions Customer may abandon the operation anytime.

15.

Use case Title View Sales promotion
Use case ID 15
Actions Admin Actions
• The Customer selects the sales promotion.
• Customer will select the category sales promotion.
System Response
• The System will generate the page.
• The System will generate sales promotion page.

Description This use case is about viewing the sales promotion.
Pre-conditions
The Database should be available in online mode.

Post-conditions Sales Promotion viewed successfully.
Alternative Path None.

Authors/Actors Customer
Exceptions Customer may abandon the operation anytime.

16.

Use case Title Update/Cancel order before Shipping
Use case ID 16
Actions Admin Actions
• The Customer selects the shipping order.
• The Customer selects cancel /update the shipping.
• Customer confirms to cancel
/update shipping order. System Response
• The System will generate the page.
• The System will cancel/ update shipping order.
• The System will cancel/update shipping order.
Description This use case is about update /Cancel order before Shipping
Pre-conditions • Order for shipping placed
• The Database should be available in online mode.
Post-conditions The Order updated/canceled successfully.
Alternative Path • The Order didn’t cancel/update successfully.
• The Server is down.
Authors/Actors Customer.
Exceptions Customer may abandon the operation anytime.

Adopted Methodology

It is the technique to utilize advancement of the task. We have embraced the VU Process Model which is the blend of Waterfall procedure and Spiral philosophy. VU Process Model will join the advantages of Waterfall and Spiral approach.

The Waterfall model

Waterfall display is a consecutive outline process utilized as a part of programming advancement process in this model advance is viewed as streaming relentlessly downwards (like the waterfall) through the periods of Conception, Initiation, Analysis, Design, Construction, Implementation and Maintenance.

The Spiral Model

The Spiral model otherwise called Spiral Lifecycle Model is a System Development Method (SDM) utilized as a part of information technology (IT). This model joins the highlights of prototyping model and the System Development Life Cycle (SDLC).

VU Process Model

It is chosen to choose VU process Model that is a Combination of Water Fall model and Spiral Model.

Purposes of Choosing VU process Model.

1. The fundamental plan to pick is to get the advantages of both these models.

2. It is the consecutive model within reverse redundancy.

3. We need to accomplish the straight idea of the Waterfall and iterative in addition to chance decrease nature of the Spiral model.

4. In VU process show we will be work in stages to finish the given undertaking.

5. All the exercises are performed in an arrangement in VU Process Model.

On the off chance that we need to do rectification or improvement at any stage and reiteration at whatever point fundamental then we can pick VU process model

Work Plan (Use MS Project to create Schedule/Work Plan)

The work design is a record that counseling firms use to sort out a task. It plots the arrangement by which the organization intends to finish a quality task inside a given measure of time and in the agreement with a set budget.

Gantt outlines are helpful instruments for arranging and booking ventures. They enable you to evaluate to what extent a venture should take, decide the assets required, and lay out the request in which undertakings should be done. They are helpful in dealing with the conditions between undertakings

At the point when an undertaking is underway, Gantt outlines are helpful for observing it’s encouraging. You can instantly observe what ought to have been accomplished at a point in time, and can thusly make a healing move to bring the undertaking back on course. This can be basic for the fruitful and productive use of the task.