Software Requirement Specification

For

Ecommerce Food Products Sales Forecasting

System

Version 1.0

Prepared By
(Adil Khan, Prakhar Gupta, Allauddin Ali)

Table of Contents
1. Executive Summary ……………………………………………………………….3
1.1 Project Overview …………………………………………………………..3
1.2 Purpose and Scope of this Specification …………………………………………………….3

2. Purpose and Scope of this Specification ………………………………………..3

2.1 User Characteristics ……………………………………………………….3
2.2 Assumptions ………………………………………………………………………………………………..3
2.3 Dependencies ………………………………………………………………………………………………3
3. Requirements ………………………………………………………………………4
3.1 Functional Requirements ………………………………………………….5
3.2 User Interface Requirements ……………………………………………………………………….6
3.3 Usability ……………………………………………………………………………………………………….7
3.4 Performance ………………………………………………………………………………………………..7
 3.4.1 Capacity ……………………………………………………………7
3.4.2 Availability ……………………………………………………………………………………….7
3.4.3 Latency ……………………………………………………………………………………………..8
3.5 Manageability/Maintainability ……………………………………………………………………..8
3.5.1 Monitoring ……………………………………………………………8
3.5.2 Maintenance …………………………………………………………………………………....8
3.6 System Interface/Integration ………………………………………………………………………..8
3.7 Security …………………………………………………………………………………………………………8
3.7.1 Protection …………………………………………………………….9
3.7.2 Authorization and Authentication ……………………………………………………..9
3.8 Data Management …………………………………………………………………………………………9

4. User Scenarios/Use Cases …………………………………………………………9

5. Deleted OR Deferred Requirements ……………………………………………..10
5.1 Hardware Interface …………………………………………………………10
5.2 Software interface ……………………………………………………………………………………….11
1. Executive Summary

1.1 Project Overview

Ecommerce Food Products Sales Forecasting System buying and selling of foods product like
carrot, potato, chicken, tomato etc. The application gives detailed information about sales
amount of consumption in last month and current and trying to predict future Sales. And it
also gives suggestion that which product is more in demand and which product is less demand
and gives suggestion to the user that upcoming festivals and seasonal foods.

1.2 Purpose and Scope of this Specification

1. Future Forecasting.
2. Seasonal Product peak.
3. Sales Measurement.
The specification documents is useful on all stages of the production process, on the suppliers
and producer sides as well as on the buying company side which can use this document as a
quality standard required at the delivery.

2. Product/Service Description
Product Demand is definately one the reason that cause product misbehave and affect the
requirement of the product.

2.1 User characteristics

.Student/faculty/staff/other -> user can buy the product and can also Feedback
suggestion and category-vise products
.technical expertise -> manage all the products availability and payment options
 .other general characteristics that may influence the product -> add to Cart, payment
options, view order history, categorial product measurement, sales behaviour.
2.2 Assumptions

. Android Sdk 18 or above and android operating system and

. internet Connectivity(Required to load data From Database).
. availability of RAM and Hardisk for storing application cache.
2.3 Dependencies

. Glide Image Loading library (for image loading in the application).

. AndroidX library for designing the layout in androidX format.
. Firebase Library for Database Connectivity and analytics.
. Okhttp3 for loading the resources from internet with version-3 security.

3. Requirements
. Android Studio IDE(Integrated Development Environment)

For writing code and layout design and all the things are developing in this IDE and database
Connectivity and all other stuffs SDK integration and api integration and modular coding and
layouting coding is done in xml and functionalities is done in python.

. Python Programming Language

Language used to give the functionality to the application and making it working perfectly and
the modular coding technique is used in this and all the modules are worked together and
making the app functioning.

. XML (Extensible Markup Language)

This is basically used for the purpose of layout and making the interactive design in the
application and giving animation effects and manyother things which gives application a better
user interface.

. Firebase for Database Storage and Retreival

For Database Connectivity Storage and faster retrieval of information with SSL and store the
data in tree structure or using the concept of firestore which gives the more easiness
rading the data from the application.

Simple Navigation -> Make it easy for customers to find products and information with
clear menus, filters, colorful buttons, and simple page titles. Don’t give them any reason to
become frustrated and click away. Clear navigation options are also crucial for Core Web Vital
metrics.Correct
Unambiguous -> (all statements have exactly one interpretation)

Complete -> (where TBDs are absolutely necessary, document why the information is
unknown, who is responsible for resolution, and the deadline) Consistent Ranked for
importance and/or stability

Verifiable -> (avoid soft descriptions like “works well”, “is user friendly”; use concrete terms
and specify measurable quantities)

Modifiable -> (evolve the Requirements Specification only via a formal change process,
preserving a complete audit trail of changes)Does not specify any particular design Traceable
(cross-reference with source doc)

3.1 Functional Requirements

Requirements analysis in systems engineering and software engineering, encompasses those

tasks that go into determining the needs or conditions to meet for a new or altered product,
taking account of the possibly conflicting requirements of the various stakeholders, such as
beneficiaries or users. It is an early stage in the more general activity of requirements
engineering which encompasses all activities concerned with eliciting, analyzing, documenting,
validating and managing software or system requirements.

Requirements analysis is critical to the success of a systems or software project. The

requirements should be documented, actionable, measurable, testable, traceable, related to
identified business needs or opportunities, and defined to a level of detail sufficient for system
design.

Conceptually, requirements analysis includes three types of

activities:

. Eliciting requirements: The task of identifying the various types of requirements from
various sources including project documentation, (e.g. the project charter or definition),
business process documentation, and stakeholder interviews. This is sometimes also called
requirements gathering.

. Analysing requirements: Determining whether the stated requirements are clear,

complete, consistent and unambiguous, and resolving any apparent conflicts.

. Recording requirements: Requirements may be documented in various forms, usually

including a summary list and may include natural-language documents, use cases or process
specifications.
 3.2 user Interface Requirements

. Register/Login -> to getting entered in the application and to view all other prouducts and
things.

. View Product -> is to show the user all the products are ongoing and are most indemand.

. View Detail -> user address and details about the account and all the related information
regarding the account.

. Categorial Product -> helps the user to sort the products and filter the product.
. Rating View -> gives the rating to the product and show these rating to the other user so
that it can get the info about the quality of the product.

• Design and Implementation

User

Login Register

User Details

View Product View Details Categorial Rating View

Product
3.3 Usability

#1 Simple & Uncluttered Interface

Be it a website design or mobile app, a simple and uncluttered interface always fetch more
sales.The rule of thumb is to avoid the confusion among your users. Provide them with limited
options with a high level of simplicity to use the app.

#2 Prominent Buttons
Displaying important buttons like “Add to Cart” & “Checkout” on the prominent positions of
the app screen is perhaps the most crucial step you can take toward increasing your sales. Not
only displaying these buttons in the prominent buttons will make a difference, but you can
also ensure that:

#3 Show Progress Bar

If your ecommerce store requires the user to fill out a checkout form that has several fields
(although a short & concise checkout form is always advised), you must ask your app
developer to display a progress bar on the top of the form so that your users are always
informed about their current step and remaining steps to complete the form.

3.4 Performance
Specify static and dynamic numerical requirements placed on the system or on human
interaction with the system:

Static numerical requirements may include the number of terminals to be supported, the
number of simultaneous users to be supported, and the amount and type of information to be
handled.Dynamic numerical requirements may include the number of transactions and tasks
and the amount of data to be processed within certain time period for both normal and peak
workload conditions.

All of these requirements should be stated in measurable form. For example, "95% of the
transactions shall be processed in less than 1 second" rather than “an operator shall not have
to wait for the transaction to complete”.

3.4.1 Capacity
Include measurable capacity requirements (e.g., the number of simultaneous users to be
supported, the maximum simultaneous user load, per-user memory requirements, expected
application throughput)
3.4.2 Availability
Include specific and measurable requirements for:
. 24/7 working of the product.
. always availability no downtime because online database
. Covere all the world

. Impact of downtime on users and business operations

. Impact of scheduled and unscheduled maintenance on uptime and maintenance
communications procedures.

. reliability (e.g., acceptable mean time between failures (MTBF), or the maximum permitted
number of failures per hour).

3.4.3 Latency
Include explicit latency requirements, e.g., the maximum acceptable time (or average time) for
a service request.

3.5 Manageability/Maintainability

3.5.1 Monitoring
Cloud Service is used in this so that the monitoring is observed in firebase and making the
application well maintained and clearly bug observation.

3.5.2 Maintenance
A commercial database is used for maintaining the database and the application server takes
care of the site.

• In case of a failure, a re-initialization of the program will be done.

Also the software design is being done with modularity in mind so that maintainability can be
done efficiently

3.6 System Interface/Integration

User Interface Layer: The section of the assignment referring to what the user interacts with
directly.Application Logic Layer: The section of the assignment referring to the web server.
This is where all computations are completed.

Data Storage Level: The section of the assignment referring to where all data is recorded.
Use Case: A broad level diagram of the project showing a basic overview.
Class diagram: It is a type of static structure diagram that describes the structure of a system
by showing the system's cases,their attributes, and the relationships between the classes.
Interface: Something used to communicate across different mediums.
Unique Key: Used to differentiate entries in a database.
3.7 Security

3.7.1 Protection Specify the factors that will protect the system from malicious or
accidental access, modification, disclosure, destruction, or misuse. For example:
. encryption
. activity logging, historical data sets
. restrictions on intermodule communications
. data integrity checks
3.7.2 Authorization and Authentication
. Multi Factor Authentication . Consider using standard tools such as PubCookie.

3.8 Data Management-> Types of information used by various functions

1. No any Frequency
2. Any user can read data from DB only
3. data entities and relationships
4. constantly changing data
5. data retention
6. valid range, accuracy, and/or tolerance
7. All quantity are in rupees
8. Encryption Data Format

4. User Scenarios/Use Cases

4.1. Product recommendation: One of the key use cases where machine learning has been
used is to provide product recommendations for ecommerce websites

4.2. Pricing recommendation: Pricing is an important aspect of eCommerce and machine

learning can be used to recommend the best prices for products.

4.3. Personalized shopping experience based on customer segmentation: eCommerce

businesses can use machine learning to identify different customer segments and then
personalize the shopping experience for them.

4.4. Demand forecasting: eCommerce businesses like e-commerce marketplaces face the
challenge of accurately forecasting demand for their products.

4.5. Product comparisons: Product comparison engines are a special case of a product
recommendation system, in which a product detail page displays alternative choices in a table
containing informative product specifications.

4.6. Product search: eCommerce businesses rely on product search engines to help their
customers find the products they are looking for
4.7. Customer lifetime value (LTV) prediction: Measuring customer future purchases and
lifetime value is an important performance indicator for marketing management and
budgeting.
5. Deleted or Deferred Requirements.
5.1 Hardware Interfaces
.Operating system: windows
.Hard disk :40 GB D RAM: 512MB.
.Processor: Pentium(R) Dual-core CPU
5.2 Software Interfaces
.XAMPP
.Notepad++
.MySQL server