Software Requirements

Specification

for
Jorsel Inventory Management
System and E-Commerce
Website
Version 1.0 approved

Prepared by:

<organization>

<date created>

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page ii

Table of Contents
Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................2
1.1 Purpose.........................................................................................................................................2
1.2 Document Conventions................................................................................................................2
1.3 Project Scope................................................................................................................................2
2. Overall Description..................................................................................................................2
2.1 Product Perspective......................................................................................................................2
2.2 User Classes and Characteristics..................................................................................................2
2.3 Operating Environment................................................................................................................2
2.4 Design and Implementation Constraints.......................................................................................2
2.5 Assumptions and Dependencies...................................................................................................2
3. System Features.......................................................................................................................2
3.1 System Feature 1..........................................................................................................................2
3.2 System Feature 2 (and so on).......................................................................................................2
4. Data Requirements..................................................................................................................2
4.1 Logical Data Model......................................................................................................................2
4.2 Data Dictionary.............................................................................................................................2
4.3 Reports..........................................................................................................................................2
4.4 Data Acquisition, Integrity, Retention, and Disposal...................................................................2
5. External Interface Requirements...........................................................................................2
5.1 User Interfaces..............................................................................................................................2
5.2 Software Interfaces.......................................................................................................................2
5.3 Hardware Interfaces......................................................................................................................2
5.4 Communications Interfaces..........................................................................................................2
6. Quality Attributes....................................................................................................................2
6.1 Usability........................................................................................................................................2
6.2 Performance..................................................................................................................................2
6.3 Security.........................................................................................................................................2
6.4 Safety............................................................................................................................................2
6.5 [Others as relevant].......................................................................................................................2
7. Internationalization and Localization Requirements...........................................................2
8. Other Requirements................................................................................................................2
Appendix A: Glossary....................................................................................................................2
Appendix B: Analysis Models.......................................................................................................2

Revision History
Name Date Reason For Changes Version

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page 1

1. Introduction
The Software Requirements Specification (SRS) is a document that explains the agreement
between the customer and the developer about what the software should do. Its main purpose is to
provide a clear description of what the user needs, which will guide the development of the
software. The document is divided into sections to make the information easy to find and
understand. It describes the system’s features, how it will interact with other systems, its key
qualities, and any limitations affecting its design. Simple and clear language is used throughout to
avoid confusion.

1.1 Purpose
The main objective of this Software Requirements Specification (SRS) is to outline the features
and requirements of the Jorsel Inventory Management System and E-Commerce Website. This
SRS offers a clear overview of the primary functions of the system as well as the necessary
features that our customer has defined.

This document is meant for our main client, Mr. Jorge Larosa; our instructor, Mr. Amir Ladesma;
the 8 members of our project; and any other stakeholders who might require access to this record.

1.2 Document Conventions

There are several terms in this paper that readers might not be familiar with. Refer to the Appendix
A (Glossary) for a list of these words and their definitions.

1.3 Project Scope

The software being developed is the Jorsel Inventory Management System and E-Commerce
Website, a web application designed to support the online sale of shoes and other items. The
system provides “automation support” for managing shoe listings and facilitating customer
purchases through an intuitive web-bases platform.

The web app is cross-platform, accessible via any modern web browser, and hosted on a central
on a central server. Customers and managers will interact with the system through a responsive
web interface, ensuring accessibility on both desktop and mobile devices.

The Jorsel Inventory Management System and E-Commerce Website enables users to create
accounts and become customers. The system allows users to browse, search, select, and add
items to a cart.

Managers will have access to an admin interface with full Create, Retrieve, Update, and Delete
(CRUD) capabilities for managing the inventory. They can add or edit product listings.

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page 2

2. Overall Description
An overview of the Jorsel Inventory Management System and E-Commerce Website’s features
and limitations is given in this section. It describes the features and capabilities that the system is
intended to provide, identifies particular situations that are purposefully left out, and goes into
depth about the expectations that were made during the development process.

2.1 Product Perspective

The Jorsel Inventory Management System and E-Commerce Website is an entirely new product
developed to address the specific needs of managing and selling shoes and other items through
an online platform. It is made to give customers a simple, easy-to-use interface to browse and buy
items, while also giving the manager the ability to effectively manage inventory.

Although the web app can be used alone, it connects with Firebase as its backend system to
manage the database and authenticate user among other crucial features. This integration
scalability for upcoming improvements and secure data handling.

2.2 User Classes and Characteristics

The Jorsel Inventory Management System and E-Commerce Website is designed to support
multiple scenarios for both customers and managers. Each scenario reflects common use cases
that the system will encounter, ensuring it delivers maximum value functionality, user-friendliness,
and reliability.

Potential Scenarios
1. Customer Shopping Experience
o Key Functions:
 Browse and search for shoes by category, size, or price.
 Add items in the cart.
o Requirements:
 Easy-to-use interface for product browsing and filtering.
 Customers can create and access their account securely.
2. Manager Inventory Management
o Key Functions:
 Create, retrieve, update, and delete (CRUD) inventory records.
o Requirements:
 Interface for administrator with advanced inventory management features.

The web app is made to manage several situations at once. While managers change inventory,
customers can continue shopping for products without interfering with the system’s functionality.

2.3 Operating Environment

The Jorsel Inventory Management System along with its E-Commerce Website works through a
central server that is cloud-hosted using the likes of Firebase, which facilitates scalability and
secure data management. It supports a range of client devices encompassing desktops, laptops,
tablets, and smartphones using modern browsers like Chrome, Firefox, Safari, and Edge. The
system remains compatible with many operating systems, specifically Windows, macOS, iOS,

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page 3

Android, and Linux. It is globally accessible, as its data are hosted in distributed data centers for
reliability purposes and to comply with different regional regulations, while the backend integrates
Firebase for database and authentication, and frontend is with responsive design to ensure
seamless experience across different devices. Security is also ensured through encryption and
regular data backups.

2.4 Design and Implementation Constraints

The Jorsel Inventory Management System and E-Commerce website is a constrained
development. There are needs of data protection according to the GDPR and CCPA standards, as
well as secure payment processing that will adhere to the PCI DSS requirements. It will be hosted
in Firebase, which limits databases in size, server resources, and API usage. Access is generally
cross-platform, though devices or browsers older may have slower performance. The security
protocols will include SSL/TLS encryption plus Firebase Authentication by that will ensure the safe
and proper management of users. Such requirements ensure that the system is practical and
meets the laid-down requirements.

2.5 Assumptions and Dependencies

The Jorsel Inventory Management System and E-Commerce Website stand its reliance on
Firebase for reliable backend services, most in authentication as well as management of the
database, and uniform internet access to the use of modern web browsers by various users. It also
relies on third-party payment gateways like PayPal or any online payments for securely handling
transactions, based on the assumption that those services are there and do not change much.
Data protection laws such as GDPR and CCPA are assumed to be followed with the project. Any
kind of disruptions or changes related to these third-party services, Firebase infrastructure related
changes, or any regulatory laws can impede the system's functionality and will need to be adapted
to handle the process smooth operation.

3. System Features
<This template illustrates organizing the functional requirements for the product by system
features, the major services provided by the product. You may prefer to organize this section by
use case, mode of operation, user class, object class, functional hierarchy, stimulus, response, or
combinations of these, whatever makes the most logical sense for your product.>

3.1 System Feature 1

<Don’t really say “System Feature 1.” State the feature name in just a few words.>

3.1.1 Description

<Provide a short description of the feature and indicate whether it is of High, Medium, or
Low priority.>

3.1.2 Stimulus/Response Sequences

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page 4

<List the sequences of user actions and system responses that stimulate the behavior
defined for this feature. These will correspond to the dialog elements associated with use
cases.>

3.1.3 Functional Requirements

<Itemize the specific functional requirements associated with this feature. These are the
software capabilities that must be implemented for the user to carry out the feature's
services or to perform a use case. Describe how the product should respond to anticipated
error conditions. Use “TBD” as a placeholder to indicate when necessary information is not
yet available.>

3.2 System Feature 2 (and so on)

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page 5

4. External Interface Requirements

4.1 User Interface
4.1.1 Login Screen

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page 6

 For users who already used the app and for first time users
 Prompts the user to enter their email and password to log in
 Clickable “Click here” link for users who forgot their password and redirected to a password
recovery process
 For first time users a “Sign up here” link is provided to create an account and Login

4.1.2 Sign-up Page

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page 7

 For first time users to register and create an account

 Prompt user to input their Name, Email, Contact Number and Password
 Prompt error message in every field if user incorrectly filled the textfields
 “Create account” button to finalizes the registration process once all fields are filled
correctly
 A “Login Here” link that redirects users after creating and users with existing accounts to
the login page

4.1.3 Landing Page

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page 8

 Search bar at the top to allows users to find specific items by entering key words.
 User enable to filter their browsing by selecting “category” drop-down such as Men,
Women, Kids, Bags, Accessories etc.
 Display containing image, name and price of a product is shown for user to easily scan the
overall description of the product.
 Cart logo navigation on top right that provides easy access of user to view their cart
 3 stacked lines menu button navigation next to the cart logo to provide additional pages and
options

4.1.4 Product Selection

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page 9

 After users selecting a product an image, name, category and price of the product are
displayed for quick identification of users.
 A size selector allows user to select all available sizes to their preferred option with ease
 A quantity selector allows user to adjust the quantity of the product before adding items to
their cart

4.1.5 Add to Cart and View Page

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page 10

 This prompt will show after the user click the “add to cart” button will be able to view their
cart after clicking “View cart” button otherwise dismiss for “back” button
 The user can remove the product by clicking the “remove” button or the “checkout” button if
the user want to checkout their orders.

4.1.6 Edit Profile Page

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page 11

 Allows user to update their information such as profile picture, name contact number and
email
 The “Update Profile” button allows the user to finalize the updated changes in their account.

4.1.7 Admin Page

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page 12

 For admin only

 Shows all the product in the inventory, admin can edit, remove and add new products and
view orders after a user or customer checks out.

4.1.8 Add item prompt

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page 13

 Admin can add products after clicking the “add new product” button.
 Prompt admin to upload image input name, description, price and quantity of the product,
select categories and select sizes
 Clicking the “Add” button after the admin finalizes the descriptions of the product

4.1.9 View Orders prompt

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page 14

 Admin can view the product descriptions of the checkout orders of the users/customers
 Prompt the admin to accept or reject the checkout orders of the users/customers

4.2 Hardware Interfaces

The shoe application is designed as a mobile application compatible with both iOS and android
platforms, ensures the accessibility across modern devices. The shoe app relies on a central
server to process and synchronize all message, updates and transactions across user devices in
real-time interactivity while maintaining data integrity and security.

The shoe app supports devices running android 7.0 (Nougat) and higher similar to iOS 11 and
newer versions. Push notifications are implement in order to deliver product updates, and alerts
using firebase cloud for android and push notification service for iOS. All communication regarding
the application and the server is conducted using TCP/IP protocol in to secure HTTPS connection.

4.3 Software Interfaces

The shoe application is developed using FlutterFlow, a visual development tool and Firebase as its
primary database and backend service provider.

4.3.1 Outgoing and Incoming Items

 Outgoing data include users login credentials, registration information, shopping cart
details, and preferences, these information are sent from the app to Firebase for storage
and processing. Moreover when a user updates their shopping cart the data is transmitted
to Firebase.
 Incoming data includes product details such as prices, descriptions, sizes and images
stores into the firebase’s firestore database. The app also receives updates on availability
of products, order status and user authentication.

4.3.2 Services and Communications

 The shoe app will rely on Firebase’s real-time cloud services to provide smooth
communication from the mobile application and the server.
o Whenever a user creates an account and logs in

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page 15

o Everytime the user interact with the app (searching, browsing, viewing details etc.)
o Whenever there are changes on one device it will reflect immediately on other
devices with the same user account.

4.4 Communication Interfaces

The shoe application will use the cloud-based server architecture powered by Firebase, that can
handle a real-time data synchronization. Firebase Cloud Firestore will store all the product, user
profile and inventory data. Whenever the user interacts with the app data will be fetched from the
firebase. For example the user logs in the app will send data to Firebase through HTTPS protocols
that will stored in real-time. This communication will run seamlessly and ensures the users have
the access to the current information across all devices.

5. Other Non-functional Requirements

5.1 Performance Requirements
Performance should not be an issue, as the shoe app is designed to ensure the interaction of
users is efficient. Product and checkout screen load will take within 1.5 seconds on an average 4g
connection, ensures responsive experience for users. The UI animations such as scrolling through
the product option or moving through checkout process, will run at 60 frames per second for
smooth and seamless user interactions. The animation in this application is carefully selected to
ensure optimization for its performance.

5.2 Reliability and Availability

The shoe application ensures the user data such as cart and profile information is consistently
synchronized across device. Any changes to the cart or profile will be reflected immediately on all
devices within 5 seconds, allowing the users to switch between different devices of their own
without delay or discrepancy regarding on their data. The app is designed to handle network
interruption effectively such as retrying data sync when a connection is restored, guaranteeing no
information is lost.

5.3 Security Requirements

The application implements user authentication through Firebase Authentication that supports
email and social media logins to secure the sign in options of users and allows that he/she can
only have an access to his account or device. This enhance the security using the two-factor
authentication (2FA) enabled to ensure the user account is protected. Access to admin
functionalities will be restricted based on the user roles this will help unauthorized access to
sensitive data and maintaining the integrity and confidentiality of the app.

5.4 Usability Requirements

The shoe app will prioritize usability based on Material Design guidelines to provide intuitive,
mobile-first interface for user to easily navigate through the app. This will provide consistent

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page 16

smooth interaction for user experience across all devices. For new users, the app will include flow
that guides them through different features helping them to become familiar using the application’s
layout and functionality such as browse product, cart managing etc. to improve overall user
satisfaction.

5.5 Compatibility Requirements

The shoe app will ensure the compatibility across both iOS and Android platforms via maintaining
visual design and functional performance. Optimizing the user experience regardless of their
operating system, having the same features, interface, layout, interaction etc. on both platforms.
These include testing on various devices and screen sizes for it to perform smoothly across
supported devices.

6. Quality Attributes
6.1 Usability
<Specify any requirements regarding characteristics that will make the software appear to be
“user-friendly.” Usability encompasses ease of use, ease of learning; memorability; error
avoidance, handling, and recovery; efficiency of interactions; accessibility; and ergonomics.
Sometimes these can conflict with each other, as with ease of use over ease of learning. Indicate
any user interface design standards or guidelines to which the application must conform.>

6.2 Performance
<State specific performance requirements for various system operations. If different functional
requirements or features have different performance requirements, it's appropriate to specify those
performance goals right with the corresponding functional requirements, rather than collecting
them in this section.>

6.3 Security
<Specify any requirements regarding security or privacy issues that restrict access to or use of the
product. These could refer to physical, data, or software security. Security requirements often
originate in business rules, so identify any security or privacy policies or regulations to which the
product must conform. If these are documented in a business rules repository, just refer to them.>

6.4 Safety
<Specify requirements that are concerned with possible loss, damage, or harm that could result
from use of the product. Define any safeguards or actions that must be taken, as well as potentially
dangerous actions that must be prevented. Identify any safety certifications, policies, or regulations
to which the product must conform.>

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Jorsel Inventory Management System and E-Commerce Website Page 17

6.5 [Others as relevant]

<Create a separate section in the SRS for each additional product quality attribute to describe
characteristics that will be important to either customers or developers. Possibilities include
availability, efficiency, installability, integrity, interoperability, modifiability, portability, reliability,
reusability, robustness, scalability, and verifiability. Write these to be specific, quantitative, and
verifiable. Clarify the relative priorities for various attributes, such as security over performance.>

7. Internationalization and Localization Requirements

<Internationalization and localization requirements ensure that the product will be suitable for use
in nations, cultures, and geographic locations other than those in which it was created. Such
requirements might address differences in: currency; formatting of dates, numbers, addresses, and
telephone numbers; language, including national spelling conventions within the same language
(such as American versus British English), symbols used, and character sets; given name and
family name order; time zones; international regulations and laws; cultural and political issues;
paper sizes used; weights and measures; electrical voltages and plug shapes; and many others.>

8. Other Requirements
<Examples are: legal, regulatory or financial compliance, and standards requirements;
requirements for product installation, configuration, startup, and shutdown; and logging, monitoring
and audit trail requirements. Instead of just combining these all under "Other," add any new
sections to the template that are pertinent to your project. Omit this section if all your requirements
are accommodated in other sections. >

Appendix A: Glossary
<Define any specialized terms that a reader needs to know to understand the SRS, including
acronyms and abbreviations. Spell out each acronym and provide its definition. Consider building a
reusable enterprise-level glossary that spans multiple projects and incorporating by reference any
terms that pertain to this project.>

Appendix B: Analysis Models

<This optional section includes or points to pertinent analysis models such as data flow diagrams,
feature trees, state-transition diagrams, or entity-relationship diagrams. You might prefer to insert
certain models into the relevant sections of the specification instead of collecting them at the end.>

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.