SRS Lifco Ver 1.0 (May'19)

Software Requirements Specification
INTEGRATED ECOMMERCE PLATFORM

DEVELOPMENT (WEBSITE & NATIVE MOBILE
APP - ANDROID & IOS)
For
ON BOARD EXPRESS
Sharjah, UAE
Project Code: NAV/INT/0004
Version No.: 1.0
Table of Contents
Sharjah/UAE/D/SRS Page 1 of 70
Software Requirements Specification Navigators Software Pvt. Ltd.
A. Document Release History 5

B. Circulation Details................................................................................................................6
C. List of Amendments Made on the Previous Version:...........................................................7
1.0 Introduction....................................................................................................................8
1.1 Purpose of this document...................................................................................................8
1.2 Scope...................................................................................................................................8
1.3 Organization Profile.............................................................................................................9
1.4 Assumptions........................................................................................................................9
1.5 Constraints.........................................................................................................................10
1.6 Dependencies....................................................................................................................11
2.0 Overall Descriptions......................................................................................................12
2.1 Product Perspective...........................................................................................................12
2.2 Product Functions..............................................................................................................13
2.3 Operating Environment.....................................................................................................16
2.4 User Characteristics...........................................................................................................16
3.0 Detailed Functional Requirements................................................................................18
3.1 STORE-FRONT FEATURES (WEB & MOBILE APP)................................................................18
3.2 GRN APP FEATURES...........................................................................................................28
3.3 LAST MILE DELIVERY APP...................................................................................................34
3.4 INTELLIGENT ORDER PROCESSING LOGIC..........................................................................42
3.5 BACKEND ADMIN PANEL FEATURES...................................................................................50
4.0 System Requirements....................................................................................................57
4.1 Software Requirements.....................................................................................................57
4.1.1 SOFTWARE FUNCTIONALITY......................................................................................................57
4.1.2 SOFTWARE CHARACTERISTICS....................................................................................................58
4.2 Hardware Requirements....................................................................................................58
4.2.1 HARDWARE FUNCTIONALITY.....................................................................................................59
4.2.2 HARDWARE CHARACTERISTICS...................................................................................................59
4.3 User Requirements............................................................................................................59
4.4 Input and Output Requirements........................................................................................60
4.5 Communications Requirements.........................................................................................61
4.5.1 COMMUNICATIONS HARDWARE.................................................................................................61
4.5.2 COMMUNICATIONS SOFTWARE..................................................................................................61
4.6 Usability Requirements......................................................................................................61
5.0 Non-Functional Requirements.......................................................................................62
5.1 Accuracy............................................................................................................................62
5.2 Audit Trail..........................................................................................................................62
5.3 Availability.........................................................................................................................62
5.4 Capacity Limits...................................................................................................................62
5.5 Data Retention...................................................................................................................62
5.6 Operational Requirements.................................................................................................63
5.7 Performance......................................................................................................................63
5.8 Portability..........................................................................................................................63
5.9 Recoverability....................................................................................................................63
5.10 Reliability...........................................................................................................................63
5.11 Security Requirements.......................................................................................................64
5.12 Usability.............................................................................................................................64
6.0 Data Requirements........................................................................................................65
6.1 Data Structures and Relationships.....................................................................................65
6.2 Data Framework and Relationships...................................................................................65
6.3 Data Inputs........................................................................................................................65
6.4 Data Outputs.....................................................................................................................65
6.5 Inter-functional Data Definitions.......................................................................................65
6.6 Component Cross Reference.............................................................................................65
7.0 External Interface Requirements...................................................................................66
7.1 Software Interfaces............................................................................................................66
7.2 Hardware Interfaces..........................................................................................................66
7.3 Communications Interfaces...............................................................................................66
7.4 User Interfaces...................................................................................................................66
8.0 Design Constraints.........................................................................................................68
8.1 Software Design Constraints..............................................................................................68
8.1.1 SOFTWARE INTERFACES............................................................................................................68
8.1.2 SOFTWARE PACKAGES.............................................................................................................69
8.1.3 DATABASE.............................................................................................................................69
8.1.4 OPERATING SYSTEM................................................................................................................69
8.1.5 TOLERANCE, MARGINS AND CONTINGENCY.................................................................................69
8.2 Hardware Design Constraints............................................................................................70
8.2.1 HARDWARE REQUIREMENTS AND ENVIRONMENT.........................................................................70
8.2.2 HARDWARE STANDARDS..........................................................................................................70
8.2.3 HARDWARE INTERFACES...........................................................................................................70
8.3 User Interface Constraints.................................................................................................71

8.3.1 USER CHARACTERISTICS...........................................................................................................71
8.3.2 ENVIRONMENT/OPERATIONAL CONSTRAINTS...............................................................................71
8.3.3 MEMORY CONSTRAINTS..........................................................................................................71
9.0 Improvements and Impacts...........................................................................................72
9.1 Improvements to Existing Capabilities...............................................................................72
9.1.1 UPGRADES AND ENHANCEMENTS TO EXISTING CAPABILITIES...........................................................72
9.2 Impacts..............................................................................................................................72
9.2.1 USER IMPACTS.......................................................................................................................72
10.0 Requirements Traceability Matrix......................................................................................74
A. Document Release History
Sl. Version Release Prepared By Reviewed & Reasons for New

No. Number Date Approved By Release
1
2
3
B. Circulation Details
A soft copy of this version of the document is available to all Navsoft employees on our
Alfresco Project Directory and on its PDB with appropriate access control.
No controlled hard copy of this document has been circulated by the Project Manager so
far. If any controlled hard copy is issued in future, details of the same will be recorded in
the table below.
Copy Designation of Copy Holder Location of the Copy

No.
C. List of Amendments Made on the Previous Version:
Sl. Section No. / Description of the Approved by Change Request No.

No. amendment & Date
Page No.
1.0 Introduction
1.1 Purpose of this document
This document defines the system behavior and system requirements for developing an
integrated ecommerce platform for the client for selling their grocery, pharmacy and
flower products online using web application and native mobile app (iPhone & Android).
The intended purpose is:
 To ensure the requirements are what the Sharjah is expecting for ecommerce
platform project.
 For the developer to build his/her low-level design documents.
 To be used by QA as a reference to create the test specifications.
1.2 Scope
Navsoft will develop a fully integrated ecommerce platform for the UAE based client
Sharjah and it helps them to manage their operations seamlessly. Proposed ecommerce
platform will run from web as well as from mobile apps (for both - Android, iOS). We will
build native mobile app for iPhone and Android platforms so that users can easily
download the app from play store and use it from anywhere and at any time.
The application will help users to quickly search for grocery, pharmacy and flower
products online from anywhere and anytime. Proposed online store will encourage
shoppers to buy items from anywhere and anytime and easily track their orders.
Customers will able to select items from whatever shop they need and can place their
order online. The store will deliver the orders to the customer's door within few hours.
There will be a GRN app which will be used by the client’s warehouse staffs and it will
help them to easily pick & scan items for serving the orders.
There will be a last mile delivery app which will be designed for easily delivering the
orders to the customers’ door. It will help to streamline the client’s delivery process by
automatically assign a delivery boy to an order, real-time tracking on transit and
notifications.
There will be a proposed ecommerce backend which will be a order processing system
using which pending orders will be grouped according to the delivery slot and order
processing steps like picklist generation, invoice generation, delivery planning, shipping
manifest generation will be performed.
We will develop web based store backend console using which store admin can manage
entire online business operations including the product stocks, inventory, orders,
customers, e-marketing & promotions, taxations, store settings and many more.
1.3 Organization Profile

Sharjah Group Company is a Public Share Holding Co; established in 1976 with the aim of
actively participating in investment in Real estate, Financial Instruments and Leasing of
Rental Properties.
The company continues to successfully implement its strategic vision by evaluating the
potential of new & emerging markets, investing in prestigious projects and diversifying its
scope of operations, all the while maintaining superior quality, unyielding technical
standards and excellence.
Now, Sharjah Group has decided to develop a fully integrated ecommerce platform for
grocery, pharmacy and flower products online from anywhere and anytime. Proposed
online store will encourage shoppers to buy items from anywhere and anytime and easily
track their orders.
1.4 Assumptions
We assume below points for developing proposed Sharjah Group, ecommerce platform:
 The application will run on web as well as app and need internet connectivity for
accessing this application.
 All the products will be updated from the backend system and accordingly it will
be displayed in the frontend.
 There will be a GRN app which will be used to manage the warehouse. The GRN
app will be used by the staffs and it will help them to easily pick & scan items for
serving the orders.
 Users can place the order from the website as well as the app. All the orders will
be updated in the backend system.
 There will be a delivery app as well which will be used by the delivery guys to
deliver the products to the customers. It will help to streamline the client’s
delivery process by automatically assign a delivery boy to an order.
 Customers can also track the delivery of the orders. Real-time tracking on transit
and notifications will be provided to the customer.
 The Backend of the proposed ecommerce system will run from web and secured
by login id and password.
 The system will be developed for single language and support ‘English’ as default
language.
 Navsoft developers will follow their indigenously developed coding standards and
style for developing the system – if the Client has any specific standards to be
followed then they must be sent to the development team before the start of the
core functional things.
 Client will afford the cost of all agreed tools, services, copyright free images &
software (may be 3rd Party) that are going to be used in this system.
 Client will arrange the hosting server as per the server specification given by us
and provide us full access of the server for deployment.
 The client will also provide for and do basic quality assurance to confirm features
developed.
 Navsoft will not be responsible for the development and/or operational
performance of any third party tools/services used or selected by the client.
 Navsoft will not be responsible for any data loss because of the miss-handling of
the application by admins or system personnel.
1.5 Constraints
Proposed ecommerce system will have following system constraints:
 Internet Connectivity – Users need high-speed internet connectivity for accessing
the app from smartphones.
 Data Syncing between App & Platform – We will establish bi-directional data
syncing between the mobile app and system backend using RESTful web-service
or APIs.
 Push Notifications – System will send push notification to the patients for
medicine refilling or upcoming appointments using 3rd party Email & SMS
gateways.
 Report Generation – System will generate different type of reports using 3 rd party
report generation tool.
1.6 Dependencies
Every project has its own dependencies and without addressing those dependencies,
planned targets couldn’t be achieved. Here, we are including but not limited to Sharjah
project dependencies:
 Hosting server must have same components, versions & configurations as it is
specified in the development environment.
 The functional modules of the Sharjah ecommerce System are inter-dependent
and the unit testing cannot be started until the front-end features are completed.
 Sharjah mobile apps cannot be functional until the web-based backend features,
web services are developed and ready.
 Sharjah ecommerce system wouldn't work offline or with very low internet
connectivity.
 Client will purchase the SSL certificate (if client want to add) and provide us the
credentials within development period.
 Sharjah ecommerce system’s performance will depend on the 3rd party tools and
services that are agreed by client and included in this system. We have no
responsibility on the performance of these 3 rd party tools, plug-ins and services.
Sharjah platform’s performance can be affected because of these external
services.
 Performance of SMS push notifications will be completely depending on the SMS
Gateway API.
 The performance of Sharjah ecommerce system will depend on the hardware
selected, internet bandwidth allocated, network connectivity, size of data and
concurrent users.
2.0 Overall Descriptions

2.1 Product Perspective
 Business Perspective
o What are the business goals of the client?
Before start development of Sharjah ecommerce System, we had a discussion with the
client regarding his business goals, vision & missions through this project. Based on the
discussion will be providing an ecommerce platform which will be used in web as well as
mobile app. The ecommerce platform will be having a GRN warehousing system, a
delivery app as well as a backend system. The warehouse will be managed by the
warehouse staffs, delivery app will be used by the delivery boys and backend will be
managed by the admin users for order processing.
o What problems we are trying to solve?
The client is planning to build this ecommerce system in SAAS model. We have planned to
build this system module-wise so that each module can function independently. We will
build system in such a manner that user can purchase the products from anywhere. The
transaction information will get updated to the backend as well as the GRN system. After
the order get processed it will get updated automatically to the delivery boy app. The
delivery boy will automatically deliver the product to the customer. Customer can also
view the status of the delivery.
o How will we solve the problems?
We will solve the problem by implementing a SAAS model that can run on web as well as
mobile (Android and iOS) platforms. Basically the system will help the buyers to purchase
the necessary items and getting it delivered in the most easiest way. We will build a fully
integrated platform that can interfaced with internal systems via RESTful APIs. Apps will
be optimized for push notifications, automatic reminders and prescription manager. Even
the website will also be responsive from all type of devices and browsers. Also we will use
Algolia search for better and faster search experience.
 Technology Perspective
o Technology Plan
We have decided to go with Django, a Python MVC framework for server-side
programming and PostgreSQL as database. Also we will use React JS for website front-end
design. Both Android and iOS app will be native app and will be built respectively on Java
and Swift Code.
 User Perspective
o How to meet User Expectations?
The client is actively involved in healthcare industry and has transferred the knowledge
related to the existing manual processes of his healthcare clinic. We got an overview of all
departments of the clinic and how they're functioning. After analyzing the workflow of
the client's existing clinic processes and departmental operations, we have suggested an
integrated system that will connect various departments like Facilities, Doctors, Walk-Ins,
Staffs, Wards, Online Booking, Medicines, Pharmacy and etc.
2.2 Product Functions

A. STORE-FRONT FEATURES (WEB & MOBILE APP)
1. Signup & Login
a. Signup
b. Account Verification
c. Login
2. Search products
a. Siri Search in Store App (iOS)
b. Smart Multi-Lingual Search
c. Product Tagging
d. Product Sorting & Filtering
3. Shop products
a. Select Shop
b. Browse Products within Shop
c. Product Details
d. Out of Stock Notifications
e. Add-To-Cart
f. View Available Promo
4. Online checkout process
a. Login/Signup
b. View Cart Items
c. Actions in Shopping Cart
d. Select Delivery Address
e. Select Delivery Options
f. Review Order
g. Online Payment
5. Customer account
a. Manage Personal Details
b. Manage Orders
c. Manage Saved List
B. GRN APP FEATURES
1. Pick list products

a. View Pending Orders
b. Create Pick list
2. Good Received Note (GRN)
a. Create GRN for Picked Orders
b. Identify Shortage Items
c. Add Substitute Items
d. Complete GRN
3. Change product price
a. Selected Picked Order
b. Change Unit Price
c. Ready for Invoice
4. Invoice
a. Ready for Invoice
b. Generate Invoice
c. Print Invoice
C. LAST MILE DELIVERY APP

1. Delivery operational settings
a. Vehicle Management
b. Area Management
c. Delivery Persons Management
d. Delivery Time Slots Management
2. Plan your delivery process
a. Orders Packing & Loading Logic
b. Automatic Order Allocation to the Delivery Persons & Vehicles
3. Delivery app features

a. App Login
b. Check-In
c. Km Reading Entry
d. View Assigned Orders
e. Start for Delivery
f. Real-Time Tracking
g. Reach to the Customer’s Location
D. INTELLIGENT ORDER PROCESSING LOGIC

1. Customer placed order from store-front (web or mobile app)
2. Order captured by the system
3. Automatic pick list generation
4. GRN entry
5. Delivery planner
a. Order Listing Logic
b. Vehicle Allocation Logic
6. Generate invoice
7. Delivery note
E. BACKEND ADMIN PANEL FEATURES

1. Admin login
2. Settings & configurations
a. Website Setup
b. Manage Localizations
c. Manage Global Settings
d. Manage On page SEO Settings
e. Manage Google Analytics
3. Orders management
a. View Orders
b. Edit/Delete
c. Search & Filter Orders
d. Create Shipment
4. Product management
a. Manage Category
b. Manage Product
c. Add Product
d. Assign to Category
e. Manage Product Status
f. Manage Alternative Products
g. Product Search
5. Inventory & stock management
a. Import Stock On Hand Data Automatically
b. Update Product Status Automatically
c. Import Products Manually
d. Import Products Automatically
e. Check Stock Availability
f. Data Export
6. Customers management
7. Other utility features
8. Manage informational pages
2.3 Operating Environment

The ecommerce platform will support the following operating environments:
 Mobile app will run on Android OS. It will be compatible for Android 4.4.4 or
higher version.
 Mobile app will run on iOS and it will be compatible for 10.3 or higher version
 Web front end and Admin Panel will run in any platform based browser. Means it
will be cross browser and cross platform supported.
2.4 User Characteristics

The ecommerce platform will be accessed by the following user groups:
 Store-Front users – The store-front users can use anyone of the web platform or
the mobile app to order items.
 GRN app users – This app will be used by the support staffs for managing
warehouse.
 Delivery app users – This app will be used by the delivery person to deliver the
items to the customers.
 Administrator – The platform owner who will manage everything from the top
and have highest level of access on all significant features.
3.0 Detailed Functional Requirements

3.1 STORE-FRONT FEATURES (WEB & MOBILE APP)
Both the web and the mobile app will be having the similar flow. User needs to type the
website address in the web browser. After providing the address user will launch into the
homepage.
If the user uses the app then he/she needs to download the app from the store. After
downloading the app user needs to tap on the launch icon to open the. After opening the
app, splash screen will appear for 2-3 seconds then it will take the user to the
registration/login page. User can skip the registration/login part and launch into
dashboard. But when user wants to post to post an ad or wants to communicate for a
posted ad then it will take the user again to the registration/login section.
1. Login & Signup
a. Manual signup – To signup user needs to provide the following information:
i. First Name: This field is a mandatory field.
ii. Last Name: This field is a mandatory field.
iii. Location: This field is a mandatory field. It will ask the user
iv. Phone Number: This field is a mandatory field.
v. Email ID: This field is a mandatory field.
vi. Password: This field is a mandatory field.
vii. Agree on Terms & Conditions: This field is a mandatory field.
If the user provides the phone number then it will ask the user to verify the OTP. After
verifying the OTP the phone no. will get verified.
b. Social signup – Following social media signup option will be available to the users:
i. Facebook
ii. Google
iii. Twitter
c. Manual login – User can login in to their account using mobile or website. To login
user has to provide-
i. Email ID/Phone Number
ii. Password
d. Social login – Following social media login option will be available to the users:
i. Facebook
ii. Google
iii. Twitter
e. Mobile Login With Facial Recognition – Store app will use multifactor user
authenticator with face login. Our store application will use a web service to connect
an OpenID Connect and OAuth 2.0 identity service and enable user to login with facial
recognition.
f. Mobile Login with Fingerprint - Our store app will enable fingerprint login for Android
& iPhone devices by registering user's fingerprint(s) in their iPhone/Android settings.
g. Remember Me – The browser will store user’s given email ID/phone number &
password in the browser cache and show them every time when they go to the login
page. If user login through app, then app will always store login season in app data.
h. Forgot Password – Click on this link will open a popup window and ask user to enter
the registered email. A system generated reset password email sent to the user’s
registered email ID that will include the link to reset password.
i. Login unsuccessful: If email ID, password, fingerprint or face doesn’t matches with
the database then the system will update the user with a login unsuccessful message.
2. Location identification – The browser will ask the user to permit the access of the
location. If user allows then using the geolocation and current position the position of the
user will be identified.
If user is using mobile app then it will automatically identify the user’s location by the
location app feature of the mobile.
3. Language – The language of the website and app will be by default English.
4. Homepage banner – In this section homepage banner will be displayed. Banners will
display ads of different products. If user click on a specific banner then it will take the user
to the detail section of that product. There can be multiple banners. All the banners are
updatable from the admin section.
5. Search products
a. Siri Search in Store App (iOS) - We will integrate SiriKit in our iOS store app so that
shoppers can easily search for a product or store by using voice command from their
mobile phones. We will add intent extensions to integrate Siri with our store app.
b. Smart Multi-Lingual Search - Ecommerce store-front will have a smart search feature
using which users can easily search items by name, description, item ID and etc. in
fact, the store will support searching items by two languages (English & Arabic).
c. Product Tagging - The store backend will have the tag option where language based
searching tags can be added against each product. Also the search result page will
show all matching items along with ‘Add to Cart’ option, so that customers can add
desire item into the cart without any effort.
d. Product Sorting & Filtering - Users can either browse items by category or via filtering
option. Users will reach to the products listing page and can sort the listing by
popularity, new arrival, and price: high to low or low to high. Also buyers can filter the
products by category, price range, brand, discount and etc.
6. Shop products
a. Select categories– Users can find all categories that have enlisted in this ecommerce
platform and they can select items from whatever categories they need. Categories
are updateable from the admin section. Categories can be as follows:
i. Grocery
ii. Household
iii. Fruits & vegetables
iv. Beverages
After selection of the category sub-categories will be displayed. After selecting the
sub-category it will take the user to the product listing section. Admin can edit/delete
the categories and sub-categories from the admin section.
b. Browse Products within Shop – Within a shop, users can browse or search for the
products that are offered by that shop. Users can find categorical listing of the
products along with below details:
i. Product Name: In this section name of the product will be displayed.
ii. Product Image: In this section image of the product will be displayed.
iii. Variant Options: In this section variants will be displayed like size, color,
weight etc.
iv. Price: In this section price of the product will be displayed.
v. Add to favorite: From this section user can add a product in the favorite list.
The product will be available in the favorite
vi. Add-To-Cart: From this section user can add a product in the shopping cart.
c. Product Details– Users can reach to the product details page from listing page and
detail page will include:
i. Product Name: In this section name of the product will be displayed.
ii. Description: In this section description of the product will be displayed.
iii. Shipping Information
iv. Variant options: In this section variant options like size, color, weight etc. will
be displayed.
v. Product Image: In this section product images will be displayed.
vi. Price: In this section price of the product will be displayed.
vii. Discount: In this section discount of the product will be displayed.
viii. Review and rating: In this section review and rating will be displayed. Add
new review functionality will be available as well from where user can add
further reviews.
ix. Category: In this section category will be displayed.
x. Quantity: In this section quantity will be displayed. User can
increase/decrease the quantity.
xi. Add-To-Cart: From this section user can add a product in the shopping cart.
d. Best selling items – In this section the bestselling items will be displayed. This section
will be available in the homepage of the website or dashboard of the mobile app.
Only the best selling items will be displayed in this section. There will be an option to
view more using which user can view others items which are available in the
bestselling option.
e. Deal of the day – In this section the items which will be having deals or offers for that
day will be displayed. This section also will be available in the homepage itself. There
will be an option to view more using which user can view others items which are
available in the deal of the day option.
f. Fruit and vegetables – In this section the items which are related to fruit and
vegetables will be displayed. There will be an option to view more using which user
can view others items which are available in fruits and vegetables.
g. Out of Stock Notifications - In case the stock isn’t available of a product, then ‘Notify
Me’ button will be there in the Product Details page. The bottom of the product detail
page will display the up-sell and cross sell items.
h. Add-To-Cart– Users can add-to-cart an item from the product listing as well as details
page of a shop. It doesn’t require login and shop will allow to add-to-cart as many
items as they wish. The items in the shopping cart will provide the following
information:
i. Item description
ii. Unit price
iii. Quantity
iv. Sub total
User can also increase/decrease the items in the cart itself. Based on the selected
items total price will be displayed. The pricing detail table will include the following:
i. Sub total
ii. Delivery charges
iii. Promo code discount
Adding promo code option will be available in the pricing detail. If user applies promo
code and if it matches with database then pricing will get updated accordingly.
i. View Available Promo- The ‘View Available Promo’ button will enable users to see the
active promo codes offered by the shop. Users can apply any one of them if it is
applicable as per the conditions given there.
j. Filters– Following filter option will be available to the users:
i. Categories: From this section user can select categories and can view specific
category wise listing.
ii. Brands: In this section list of brands will be displayed. User can select one or
multiple brands to view brand specific products. User can also search brands
from the multiple brands.
iii. Price: Price scale will be there using which user can increase/decrease the
price range. User can also type the price range.
iv. Pack size: From this section user can select the pack size. Based on the
selection of the size, products will be displayed.
v. Pack type: From this section user can select the pack type. Based on the
selection of the type, products will be displayed.
vi. Flavors: From this section user can select the flavors. Based on the selection
of the flavor, products will be displayed.
vii. Servings: From this section user can select the flavors. Based on the selection
of the flavor, products will be displayed.
viii. Food preferences: From this section user can select the flavors. Based on the
selection of the flavor, products will be displayed.
k. Wish list – In this section list of items which the user has marked as favorite will be
displayed.
7. Place order
a. Login/Signup - From the Shopping Cart, when users are trying to move to the
checkout process, the store will check their login status. If user isn’t logged in, then
the store will ask him/her to login first and then go to the checkout steps.
b. View Cart Items – Users can add items to the cart from one shop at a time. It means,
orders from multiple shops isn’t allowed in this platform. If user has added few items
in first shop and then move to second shop – then cart items of first shop will be
removed automatically. User’s shopping cart will include:
i. Item Name
ii. Unit Price
iii. Quantity
iv. Sub-Total
v. Savings
c. Actions in Shopping Cart – Users can perform following activities in the shopping cart
page:
vi. Delete an Item
vii. Increase/Decrease Quantity
viii. Empty Cart
ix. Continue Shopping
x. Checkout
d. Select Delivery Address – user will be asked to either select a delivery address from
address book or add a new delivery address for the order. Add New Address will
include:
xi. First Name
xii. Last Name
xiii. Contact Number
xiv. Apartment Name & House No
xv. Street Name
xvi. Nearest Landmark
xvii. Area Name
xviii. City
xix. State
xx. Postal Code
xxi. Country
e. Select Delivery Options - The store will offer single page checkout process where
customers need to confirm the delivery address, Delivery Time Slot, Review Order
and Make Online Payment. Buyers will see only the next available time slots from
where the store will ask them to choose their preferred delivery time slot and the
order will be delivered to their addresses accordingly.
f. Review Order - In this checkout step, customers will be asked to review the order by
checking the ordered items, their pricing & quantities, apply promo code, add
delivery instruction and etc.
g. Online Payment - This is the final step of the checkout process where the store will
ask buyers to make online payment using credit card / debit card / net banking or
cash on delivery. Once they placed the order – the store will capture buyer's payment
and redirects them to the order success page.
If card information, user information or PIN doesn’t matches with then it will update
with payment successful message.
3rd party payment gateway integration will be there. Admin can activate/deactivate
the payment gateway from the admin section.
h. How it works - In this section how the site works and its steps will be displayed.
Mainly contents will be displayed in this section. The contents are updatable from the
admin section.
i. Other content sections – Following are the other content sections:
 Free shipping
 Support 24X7
 15 days returns
 100% payment secure
 About us
 In NEWS
 Store location
 Payments
 Shipping
 Cancellation & returns
 FAQ
 Terms & conditions
 Return policy
 Privacy policy
 Careers
All the contents are updatable from the admin section. Admin can also edit/delete
the content sections as well.
8. Download app - In this section both android and iOS app reference will be displayed. If
user selects any app then it will redirect the user to that specific app store.
9. Social media follow - In this section social media follow options will be displayed. Social
media options are Facebook, Twitter and G+.
10. Customer account – This section will be having the following sub-sections:
a. Manage Personal Details – Customers will able to manage account details including.
 Edit Profile – Here customer can edit profile details including:
o Name
o Email
o Mobile Number
o Location
 Manage Delivery Addresses – Here customer can see existing delivery
addresses and also can add new delivery address if necessary.
 Change Password – Here customer can change account password by giving:
o Current Password: This field is mandatory. User needs to provide the
current password.
o Enter New Password: This field is mandatory. User needs to provide
the new password.
o Confirm New Password: This field is mandatory. User needs to
provide the new password.
 Email Addresses – Here customer can either change the primary email id
where store notifications will be sent or add secondary email address which
will be used for sending promotions.
b. My orders – In this section following subsections will be displayed:
 Order ID: In this section order ID will be displayed. If user selects a specific
order then it will take the user in the order detail section. The detail section
will be having the following information:
o Order history details: This section will be having following sub

sections:
 Order ID
 Date
 Delivery slot time
 Shipping address
 Delivery address
o Item description: In this section item details will be displayed. The
item details will display the following information:
 Item description
 Quantity
 Cost
 Sub total
 Total
o Repeat order: From this section user can repeat the order. If user
select to repeat then it will take the user to cart section with the
orders.
o Request invoice: From this section user can request an invoice.
o Return item: From this section user can return items. If user request
for return then it will updated to the admin section as well.
 Order date: In this section order date will be displayed.
 Amount/payment mode: In this section payment mode will be displayed.
Payment mode can be online payment or cash on delivery.
 Payment status: In this section payment status will be displayed. Payment
status can be Payment successful, unpaid or failed.
 Order status: In this section order status will be displayed. Order status can
be approved, cancelled and delivered.
 Action: User can make payment from this section if the order status is unpaid.
3.2 GRN APP FEATURES

GRN App will be used by the warehouse staffs who will pick and pack the ordered items
for delivery. This type of user will be created by the admin from the web backend section.
We will develop a native android app using which warehouse staffs can scan the picked
items and packaged for delivery:
1. Login
a. Login – The login credential of the GRN app will be created and provided by the
admin. To login user has to provide –
i. Email ID: In this section GRN app user needs to provide the email ID. This
is a mandatory field.
ii. Password: In this section user needs to provide the password. This is a
mandatory field.
b. Remember Me – The browser will store user’s given email ID & password in the
browser cache and show them every time when they go to the login page. If user
login through app, then app will always store login season in app data.
c. Forgot Password – Click on this link will open a popup window and ask user to
enter the registered email. A system generated reset password email sent to the
user’s registered email ID that will include the link to reset password.
d. Login unsuccessful: If email ID, password doesn’t matches with the database then
the system will update the user with a login unsuccessful message.
e. Logout – User will be able to logout from their account.
2. Pick list Products
a. View Pending Orders – Once customer’s order is received in backend, admin will
able to create pick list by selecting one or multiple pending orders from order
management module and assign them to specific warehouse. Pending order list
will include the following:
i. Order ID
ii. Order Date
iii. Time Slot
iv. Customer Name
v. Assigned Warehouse
vi. No. of Items Ordered
vii. Payment Type
viii. Payment Status
ix. Order Status
b. Create Pick list – Admin will create pick list of all selected orders and it will
include:
i. Pick List No
ii. Pick list Creation Date
iii. Warehouse Name
iv. Order Numbers that are Picked
v. Delivery Date
vi. Picked Item Details – It will display list of all ordered items that are
needed to be picked from the warehouse:
 Product Name
 Product SKU
 Unit of Measure
 Product Variant
 Price per Unit
 In-Stock Quantity
 Ordered Quantity
3. Good Received Note (GRN)

a. Create GRN for Picked Orders – GRN of the picked orders can done from web as
well as from mobile app. Warehouse staff will able to select a picked order and
perform following activities:
i. View Picked Item Details - Warehouse staff can see all picked item details
including:
 Item Name
 SKU
 Quantity Ordered
 Picked Quantity
 In-Stock Quantity
 Item Price
 Item Discount
ii. Scan Item Barcode using Mobile App: Scanning functionality will be
available in the app. After scanning the barcode it will match with the DB
and the item will get listed. If the barcode doesn’t matches then it will
provide scan unsuccessful message.
iii. Scan Basket Tag using Mobile App: User can scan the basket tag as well
using the mobile app. After scanning the tag it will match with the DB and
the item will get listed. If the tag doesn’t matches then it will provide
scan unsuccessful message.
iv. Shortage Item Quantity Entry: From this section user can update the
items which are falling short or not available. According to the entry the
item list will get updated.
v. Return Item Quantity Entry: From this section user can update the items
which has been returned by the consumer. According to the entry the
item list will get updated.
vi. 3rd Party Item Quantity Entry: In this section user can enter the 3 rd party
item quantity. According to the entry the item list will get updated.
b. Identify Shortage Items – Once the ordered items are picked from the warehouse
and the item barcode is scanned then scanned item quantity will automatically
increase in mobile app. Warehouse staff can easily identify shortage quantity of
an item by calculating the difference between scanned item quantity and picked
item quantity.
c. Add Substitute Items – The app will have an option to complete the GRN of an
order with substitute items if there is a shortage. There will be a link for
substitute item next to each of the picked item. It will help warehouse staff to
select a substitute item if there is a shortage in quantity.
d. Complete GRN – Once all ordered items are scanned and ordered quantity and
scanned quantity are matched then GRN process will be completed and system
will be notified automatically.
4. Change Product Price

a. Selected Picked Order – Once the products are scanned and crate/baskets are
scanned, then warehouse staffs will be given option to update product prices as
per ordered price. Once a picked order is selected, warehouse staffs will able to
see following information of the ordered items:
i. Item Name
ii. Item SKU
iii. No of Quantity Ordered
iv. No of Quantity Scanned
v. No of Shortage Quantity
vi. No of Returned Quantity
vii. Unit Price
viii. Net Price
b. Change Unit Price – Warehouse staff will have an option to change following
information of each item:
i. Change Unit Price of an Item
ii. Add Note
iii. Save
c. Ready for Invoice – Once all Price changes are confirmed, warehouse staff will
able to release the order for generating invoice.
5. Invoice
a. Ready for Invoice – Once the GRN process is completed for an order, it will
automatically move to Ready to Invoice list and display following details:
i. Order ID
ii. Order Date
iii. GRN Completion Date
iv. Order Delivery Date
v. Customer Name
vi. Customer Shipping Address
vii. No of Items Ordered
b. Generate Invoice – Warehouse staff can either select one or multiple orders from
the list or click on the generate invoice button to generate the invoices for
selected orders.
c. Print Invoice – Once invoice is generated, warehouse staff can select an order and
print invoice copy and attach it in the crate/basket using which the picked items
will be delivered to the end customer.
3.3 LAST MILE DELIVERY APP

Last Mile Delivery App is considered to be the fastest and the easiest way to deliver the
orders right to the customers' door. It helps to streamline the entire delivery process by
automatically assign the delivery person to an order and track them in real-time. Here is
the list of features we are suggesting for the last mile delivery app.
1. Login
a. Login – The login credential of the last mile delivery app will be created and
provided by the admin. To login user has to provide –
i. Email ID
ii. Password
b. Remember Me – The browser will store user’s given email ID & password in the
browser cache and show them every time when they go to the login page. If user
login through app, then app will always store login season in app data.
c. Forgot Password – Click on this link will open a popup window and ask user to
enter the registered email. A system generated reset password email sent to the
user’s registered email ID that will include the link to reset password.
d. Login unsuccessful: If email ID, password doesn’t matches with the database then
the system will update the user with a login unsuccessful message.
e. Logout – User will be able to logout from their account.
2. Delivery operational settings
a. Vehicle Management – Here app admin will find all vehicles that are reserved for
delivering the customers’ orders. Admin can add more vehicles if he/she wishes.
The vehicle will have following characteristics:
i. Loading Capacity - Each vehicle will have specific no of orders loading

capacity and admin must mention the max no of orders loading capacity
per vehicle.
ii. Assign Delivery Boy - Admin needs to select a delivery man who will use
this vehicle for delivering the orders.
iii. Select Zone/Location - Admin needs to assign the vehicle to a specific
zone/area where it operates.
b. Area Management - Admin will able to divide the supported delivery locations in
multiple zones. Each zone will have multiple areas and each area may have
multiple sub-areas. Following are the characteristics of delivery zones:
i. Define Zone Location – Admin needs to define the zone location by
selecting the Country, State, City for that zone.
ii. Supported Zip Codes – Admin needs to specify the supported zip codes
for the zone.
iii. Zone Manager – Admin needs to select a zone manager who will take
care of the orders of that zone.
iv. Warehouse – Admin needs to select a warehouse for the zone so that
when orders are coming to that zone, it automatically redirects to the
specified warehouse for shipment.
c. Delivery Persons Management – App admin will find all delivery persons who
have added to the system for delivering the orders. The store admin will create
the account of the delivery persons and provide the delivery app login access to
them. Each delivery person will be assigned to specific zone and can be
considered for delivering the orders of that zone only (depending on their
availability).
d. Delivery Time Slots Management – Delivery time slots will be created for the
buyers so that they can select their preferred day & time for the order delivery.
The store admin will able to manage the delivery time slots that are zone specific.
Each time slot will have the following characteristics:
i. Zone Specific – Each delivery zone may have different time slots. Also
admin can have multiple slots per day per zone. For example – Zone 1
may have two delivery time slots – one is 5 PM to 7:30 PM every day and
another is 7:30 PM to 10:00 PM every day.
ii. Max. Order Limit – Admin will able to set the maximum no of orders
delivering capacity for each time slot per day and per zone. Suppose Zone
1 has maximum order delivering capacity of 5 for the time slot 5:30 PM to
7:00 PM in Monday. It means the store will accept maximum 5 orders on
that delivery time slot when people are placing order from the same zone
and same day. Once the maximum order limit is completed, next
customer wouldn’t able to select the same time slot from the same
delivery zone and on the same day.
iii. Default Cutoff Time – Admin will able to define the reference time from
when the same day delivery and next day delivery will be counted. For
example - If the default cutoff time is 10:00 AM and the store is offering
same day delivery. Now, if a customer is trying to place an order at 9:45
AM on Monday, he/she will able to select the Monday’s available delivery
time slots (if their max. order limit hasn’t exceeded) but if a customer is
trying to place an order after 10:00 AM on Monday then he/she can’t find
the Monday’s time slots and see only the Tuesday’s available delivery
time slots.
3. Plan your delivery process

The delivery planner tool will help the store admin to ship thousands of orders every day
without any hassle. With help of the zone wise delivery time slot settings, the application
will easily group the same zone, same day and same slot orders. In delivery planning
stage, admin can easily pack the orders, correctly load them in the vehicles and assign
delivery person for dispatching the consignments. Here admin will able to can perform
following activates:
i. Orders Packing & Loading Logic – In the delivery planning stage, this
application will intelligently list the orders so that the store owner can
pack the orders systematically and load them correctly to the assigned
vehicles. The order listing process follows the logic of:
 The order delivery location will be measured from the store's
warehouse location. For the 1st delivery time slot orders, the
nearest delivery location comes first and the far most delivery
location comes last.
 For 2nd delivery time slot orders, the far most delivery location
order (measured from the location of the last order location of
the 1st slot) comes first and the nearest delivery location of the
order comes last.
ii. Automatic Order Allocation to the Delivery Persons & Vehicles - The
application will automatically assign the delivery persons and vehicles to
the orders based on certain logic as specified below:
 Check Delivery Zip Code - The delivery persons and vehicles will
be assigned to transport the consignments on one or multiple zip
codes based on Google Map and pre-assigned territory set by
admin. In delivery planning stage, the application will check the
order's delivery location pin code and search for the delivery
persons and vehicles who are available on that zip code.
 Check Max. Load Capacity - Each vehicle will have maximum
number of orders carrying capacity (as defined by admin in
Vehicle Management section). Similarly, each delivery person will
have max number of order delivery capacity per day (as defined
by admin in Delivery Boy Management section). Here the
application will check the capacity of delivery person & vehicle
and discard them who aren't capable of carrying the total
consignment.
 Check Time Slot Availability - The application will check the time
slot availability of the vehicles & delivery persons with the time
slot of the orders for which the shipment has been created. The
system will show only those vehicles and delivery persons who
are available on the delivery time slot for which the shipment is
created.
 Confirmation - Based on the above logics, the application will
show the vehicles & delivery persons and will ask admin to pick
the vehicle number and delivery person's name who will deliver
the whole order consignments to the customers.
4. Delivery app features
The app admin will create the account of the delivery persons and give them access to
the last mile delivery app. The delivery persons will have the mobile device and the
delivery app install on it. They will open the app from their mobile device and login to the
delivery app with the correct username and password provided them. Delivery persons
will perform the following activities from the last mile delivery app:
i. App Login – The delivery person will login to the app using the
username/password created from the application’s backend console.
ii. Check-In – ‘Check-in’ button will indicate that the delivery person is ready
for dispatching the assigned orders. Once click on this button from the
app, the system will notify about the delivery person’s status and his
status becomes ‘Available’.
iii. Km Reading Entry - As per the application's operational settings, each
delivery person will be assigned to a vehicle. After check-in from the
delivery app, it will ask the delivery person to enter the starting kilometer
reading of the vehicle. This information will be posted to the application
and admin will be informed about starting kilometer reading of vehicle.
iv. View Assigned Orders - Delivery person will only see the assigned orders
for the day along with the latitude & longitude location of each order. The
app will list the first slot orders as per the delivery location distance
measured from the vehicle's initial position. The nearest delivery location
will come first and the far most delivery location will come last. For the
second slot orders - the distance would be measured from the location of
the last order of the first slot. For 2nd slot orders, the far most delivery
location order (measured from the location of the last order location of
the 1st slot) will come first and the nearest delivery location of the order
will come last.
v. Start for Delivery - when the delivery person will start for delivering the
orders, he needs to update the kilometer reading of his vehicle. The
application will able to track the delivery person and his vehicle on real-
time using GPS tracking mechanism. The app will update the latitude and
longitude of the vehicle all the time during transit.
vi. Real-Time Tracking - Admin will able to track all delivery persons from the
application's backend console who are available on the delivery app and
on the way to delivering the assigned orders to the customers. The
application will offer GPS tracking mechanism to show the real-time
location of the delivery persons and their vehicles on Google Map.
vii. Reach to the Customer’s Location - When the delivery person will reach
to the customer's location, he needs to open the order detail screen from
the app and finds two buttons there as ‘Deliver’ and ‘call to CS’. Delivery
person needs to press any one of them depending on various situations.
 Deliver - If the customer is available to receive the order, ready to
accept the whole order and ready to pay the dues (in case of
COD) then the delivery person will perform the following
formalities and press the 'Deliver' button from the app at the
end:
o After handover the ordered items and collecting money
from the customer (in case of COD), delivery person will
ask the customer to make e-sign on the app and save it.
o Delivery person will add the customer's feedback at the
bottom of the order in the delivery app.
o Press ‘Deliver’ button and the order status will be
updated automatically.
 Call to CS - When delivery person reaches to the customer's
house and either find the customer's door is locked or the
customer denies to accept the full/partial order because of the
poor quality of items or one/multiple items are broken during
transit, then he will press the 'Call to CS' button from the app.
Once the 'Call to CS' button is pressed by the delivery person, the
'Deliver' button gets disabled immediately.
3.4 INTELLIGENT ORDER PROCESSING LOGIC

Proposed ecommerce solution will have an in-built intelligent order processing engine
that enables store admin to quickly process the orders and ship to the customer’s door
within few hours. Order processing flow include following activities:
1. Customer placed order from store-front (web or mobile app)
Customers can place order from the store-front. A customer’s order may consist of the
grocery items like 1 KG Pack of Rice or 1 KG Pack of Wheat etc. and Fruits like 500 grams
of Apple, 500 Grams of Pomegranate and etc.
2. Order captured by the system

Once customer placed order successfully, the platform will immediately capture the order
and display at backend.
3. Automatic pick list generation

The platform has a defined Order Cutoff Time to trigger an automatic scheduler and fetch
all pending orders of last 24 hours and generate the Pick list automatically. The process
works without any time delay and the system automatically fetch all orders of last 24
hours. Also the platform creates the daily Pick list in CSV file format and saves in a specific
server location so that 3rd party supplier can easily access the file and ship the pick list
items to the store owner’s warehouse.
Note –While creating the pick list, the system is intelligently grouping the same items
together and increase the quantity. For example – if a grocery item ‘Basmati Rice: 1 KG
Pack’ is ordered by four different customers 1 Quantity each then instead of listing the
same item four times in the Pick list, it is listed only once but the quantity is increased to
‘4’. Similarly, if a fruit item ‘Green Apple: 500 Grams Pack’ is ordered by two different
customers where first customer ordered 1 quantity and second customer has ordered 2
quantities – then the item comes once in the Pick list but its quantity will be shown as ‘3’.
4. GRN entry
At GRN stage, the system performs two things intelligently. First, display the orders as per
the delivery date and slot. Second, display the pick list items order-wise so that GRN
entry, barcode scanning and packing can be done in parallel. It's a great help for the
warehouse staffs who always prefer to perform all these activities in parallel.
Grocery items are normally delivered through the 'crate'. Once the pick list items are
received from the supplier, the warehouse staff needs to perform two things prior to
open the GRN entry page - a) ready the barcode attached crates where the ordered items
will be delivered b) take a printout of the orders for which the pick list is generated.
Once the above prerequisites are completed, then the warehouse staff can start the GRN
entry with help of a hand-held scanner device. First, he/she scans the crate and assign it
to the order. Then, pick one item, select ‘Scan EAN’ textbox next to that item in the
screen, scan it and put it in the crate. Perform the same set of operations for all remaining
items of that order. In case one crate isn't sufficient to store all items of an order then
take another crate, scan it and assign it to the same order and then put the rest items
there after performing the same set of operations. That’s all!!!
In case of a ‘Shortage’ or ‘Return’ Item, the platform provides an option next to each item
where warehouse staff can mention the quantity in the respective textbox and credit the
due amount to the customer’s wallet.
5. Delivery planner
This platform provides a very smart and innovative delivery planner tool using which the
store owner can easily deliver thousands of orders every day without any hassle. This
automated tool reduces the delivery time & effort remarkably and replacing the
erroneous manual process. The store owner will have the complete control of creating no
of delivery slots per day, no of crates carrying capacity of each vehicle, manage vehicles,
manage drivers, manage delivery zones & areas and many more. The foundation of the
Delivery Planning system has been designed with the custom order listing logic and
vehicle allocation logic as described below:
i. Order Listing Logic - System will list down the first slot orders as per the
delivery location distance measured from the store owner's warehouse
location. The nearest delivery location comes first and the far most
delivery location comes last. For second slot orders - the distance would
be measured from the 1st slot’s last order location. For 2nd slot orders,
the far most delivery location order (measured from the location of the
last order location of the 1st slot) comes first and the nearest delivery
location of the order comes last.
ii. Vehicle Allocation Logic – system will automatically allocate the vehicle
against each time slot based on verifying the following parameters.
 Order Post Code – each vehicle will transport the goods on one
or multiple post codes as defined by the store owner. In delivery
planner step, system will check the order delivery location post
code and search the vehicles that can transport the goods on that
post code.
 No of Crates – each vehicle will have the maximum number of
crates carrying capacity as defined by the store owner (say 50
crates per vehicle). System will check the no of crates assigned to
a vehicle and show the availability accordingly.
 Time Slot Availability – each vehicle will be assigned to a specific
time slot as defined by the store owner. System will check the
vehicle’s time slot and the order’s time slot and show only the
available vehicles on the order’s time slot.
Based on the above 3 parameters, system will display all available
vehicles and ask store owner to assign the vehicle number and delivery
boy name who will deliver the orders on that vehicle.
6. Generate invoice
Once the delivery planning is done by the store owner, then system will ask to generate
the invoice against each order of two time slots of a day. In the invoice, store owner will
able to see the no of crates used for an order. The system will have the option to print
two copy of each invoice – one is customer copy and another will be used by the delivery
person.
7. Delivery note
Delivery note will be used by the delivery boy who will use the Last Mile Delivery App and
ship the orders to the customer’s doorstep. The delivery note will be generated against
order that is assigned to the delivery man. The store owner will print the delivery note
and signed by the delivery man who will be accountable to deliver the goods to the
customer.
3.5 BACKEND ADMIN PANEL FEATURES

1. Login
a. Login with admin username and password.
b. Manage admin login details and email notifications if forget password.
c. Login unsuccessful: If email ID, password matches with the database then the
system will update the user with a login unsuccessful message.
2. Settings & configurations
a. Website Setup - It will include following functionalities.
i. Store Settings – Here admin will able to setup the business name, logo,
industry, store address, and etc.
ii. Design Settings – Here admin will able to activate the design template of
the store.
iii. Payment Gateway Setup – Here admin will able to setup the payment
gateways for the store.
iv. Shipping Method Setup – Here admin will able to setup the shipping
methods for the store.
b. Manage Localizations: Admin will able to set the custom fields, website on/off,
and design elements.
c. Manage Global Settings – Admin will able to set the store’s global setting
parameters like date format, timeline, order prefix, product SKU prefix etc.
d. Manage On page SEO Settings: Admin will able to set SEO friendly page title, meta
keywords, description and etc.
e. Manage Google Analytics: Admin can set the Google Analytics code in the
website page and check the website analytics data from Google dashboard.
3. Banner Management
a. View All Banner – Admin will able to see all active ads along with following
details:
i. Banner Title
ii. Date Posted
iii. Author
iv. Banner Image
v. Page & Position
vi. Banner Link
vii. Status
b. Add New Banner– Admin will able to add new banner and it will include:
i. Ad Title
ii. Description
iii. Select Page & Position
iv. Upload Banner Image
v. Add Link/URL
vi. Status
c. Edit – Admin will able to edit information of a banner and it may include:
i. Edit Title
ii. Change Link/URL
iii. Upload New Image
d. Delete – Admin will able to entirely delete a banner (if necessary) and the deleted
banner will no more display in that page.
e. Active/Inactive – Admin can active/inactive a banner and inactive banner
wouldn’t displayed in the front-end.
4. Category and Sub-category management
a. View category – In this section list of categories, their related sub-categories and
hierarchy will be displayed.
b. Edit/Delete - Admin will able to edit a category as well as sub-category from this
section (if necessary). Admin will be also able to define the order of the
categories as well.
5. Orders management
a. View Orders - Once an order is placed from any sales channel (either web-store or
mobile app), the platform will immediately capture the order and display at
backend. The Order Listing page will show the following things:
i. Order ID
ii. Order Date &Time
iii. Delivery Time Slot
iv. Customer Name
v. Shipping Address
vi. Order Amount
vii. Weight
viii. Order Status
b. Edit/Delete - Admin will able to edit an order if necessary. Edit order will enable
admin to perform following changes in the order details page:
i. Change Customer Details
ii. Change Delivery Address
iii. Change Cart Items, Quantities
iv. Apply Coupon Code
v. Change Shipping & Handling Charge
vi. Change Tax Amount
c. Search & Filter Orders - Admin will able to search & filter orders by:
i. Order Status
ii. Zone/Area
iii. Assign Warehouse
iv. Tag
v. Date Range
vi. Save Filters
d. Create Shipment - Admin will able to shipment one or multiple orders in bulk and
it consists of multiple sub-processes as explained below:
i. Picklist Generation - The application will have the defined Order Cutoff
Time to trigger an automatic scheduler and fetch all pending orders of
last 24 hours and generate the Picklist automatically.
ii. GRN Entry - At GRN stage, the system will perform two things
intelligently. First, display the orders as per the delivery date and slot.
Second, display the picklist items order-wise so that GRN entry, barcode
scanning and packing can be done in parallel. It's a great help for the
warehouse staffs who always prefer to perform all these activities in
parallel.
iii. Delivery Planner - This automated tool will reduce the delivery time &
effort remarkably and replace the erroneous manual process. The store
owner will have the complete control of creating no of delivery slots per
day, no of crates carrying capacity of each vehicle, manage vehicles,
manage drivers, manage delivery zones & areas and many more.
iv. Generate Invoice – once the delivery planning is done by the store owner,
then system will ask to generate the invoice against each order of two
time slots of a day. In the invoice, store owner will able to see the no of
crates used for an order. The system will have the option to print two
copy of each invoice – one is customer copy and another will be used by
the delivery person.
v. Delivery Note – Delivery note will be used by the delivery person who will
use the Last Mile Delivery App and ship the orders to the customer’s
doorstep. The delivery note will be generated against order that is
assigned to the delivery person. The store owner will print the delivery
note and signed by the delivery man who will be accountable to deliver
the goods to the customer.
6. Product management
a. Manage Product - The application will enable admin to view and add/edit the
product by giving following details:
i. Product Name
ii. Item Code
iii. Image
iv. Price
v. Description
b. Add Product – Admin can easily add product and stock from the backend console
and the ecommerce platform will support:
i. Manual Add Product – Ecommerce admin can add new product manually
by entering the product details like:
 Product Name
 Item SKU
 Category
 Upload Product Image
 Description
 Inventory Information
ii. Bulk Upload Products - Admin can use our pre-integrated CSV import
feature to upload products in bulk.
c. Assign to Category - Admin will decide which product will add on what category.
The back office will have the ability to enable/disable a product by category &
sub-category. Also admin can set the price of a product by store and store groups.
d. Manage Product Status - Admin will have the authority to change the product
status to 'out of stock' manually which updates the same at the store-front.
e. Manage Alternative Products - The application will suggest alternative product
options in case customer's originally ordered product isn't available in the store.
Here admin will able to add the alternative product options next to each product
and save them.
f. Product Search - The back office application will enable admin to search product
by product name, item code, out of stock items, disabled items, coming soon and
etc. Also admin can browse products by category.
7. Inventory & stock management
a. Import Stock On Hand Data Automatically - The back office will have an automatic
scheduler function using which stock on hand data of the store will be imported
into the system on a specific time every day. System will maintain a pre-defined
format of CSV file which will be triggered and updated the stock on hand data of
the store.
b. Update Product Status Automatically - Once the stock on hand data is imported
into the application, the system will automatically identify and change the status
of item as per the stock on hand data.
c. Import Products Manually - The application will enable the admin to import item
master and images through CSV file manually.
d. Import Products Automatically - There will be a specific server location where
product CSV file and image folder with image name as barcode will be maintained
by the admin. The back office application will run a time driven scheduler
everyday which fetch the CSV file & image names from that server location and
automatically update into the application.
e. Check Stock Availability - The product will have a start date & end date from
where the application will automatically identify the status of product availability.
Also the application will automatic identify item start date and end date and
change the status of product availability accordingly while manual import.
f. Data Export - The application will enable admin to export the sales and customer
data to a folder in a predefined format.
8. Customers management
a. View Customers along with their Name, Email ID, Phone Number, Status etc.
b. Add/Edit Customers and Active/Inactive as necessary.
c. Delete customer and all data related to that customer will be erased from the
system automatically.
d. Manage Contact Group and add/edit/delete the contacts as necessary.
e. Assign customers under an available contact group.
f. View all orders history of a customer and contact him/her if necessary.
g. Notify customer related to an order.
9. Other utility features
a. Automatic Pick List Generation Process
b. Ability to see the orders on map with status
c. Ability to see the driver on the map and route guide
d. Bar Code Printer
e. Repeat Order \ Wishlist \ Order list work, Price \ Discount \ Availability
f. Manage Stocks and Products in Multiple Warehouses
g. Manage Different Customer Groups (Normal \ Premium \ Business)
h. Calculation of Price, Availability, Discount for Customers who Add Items to Cart
but Order Later
i. Admin Notification about Out of Stock, Safe Stock for one and multiple Location,
Store
j. Customer Application to see the Delivery Count down in Real-Time.
k. Offer Discount for a Given Interval (example: 5PM to 8PM)
l. Delivery App Enables Driver to Give Feedback to the Customer
m. Automatic Invoice Print
10. Manage informational pages
a. View All Informational pages along with the Page Name, Publish Date, Author,
and Status.
b. Add/Update/Delete New Page by entering the Page Title, Descriptions, Images,
Links, Key Features, Highlighted Texts and etc.
c. Active/Inactive an informational page.
4.0 System Requirements

4.1 Software Requirements
Navsoft will develop a complete Clinic solution, front end and native mobile app (Android
& iPhone) for the client. The application will run from the Linux server (Apache web
server) and use PostgreSQL as application database. The client and Navsoft has mutually
agreed on using Django, a Python based MVC framework for server side programming
language and PostGreSQL as the application database. For developing the iOS app we will
use Swift Code and for Android we will use Java (including Android SDK) programming
language.
Operating System/Development Server Linux (UBUNTU)
Web Sever Apache 2x
Database PostgreSQL 9.3
Scripting Language Python 3.6.3
Framework Django MVC 1.11
Front End Framework Angular JS 5
IOS App App Development Language Swift Code 4.1
Android App Development Language Android SDK, Java based Platform
APIs Google (Login and Map), Facebook (Login),

Twilio SMS Gateway, Algolia Search API,
Clearbit Company Logo and Name finder
API
.1.1 Software Functionality

The functional modules of the proposed Clinic website & native mobile app (Android &
iOS) will be built on the above specified software platform. Details functionalities of the
MDnius application has been discussed above under section# 3.0.
.1.2 Software Characteristics

Here are the essential characteristics of the proposed Clinic website & native mobile app:
 Admin Panel will be cross browser and cross platform supported.

 Mobile App Compatible with the latest Android & iOS operating system
environments. It will be best compatible for Android 4.4.4 or higher version and
for iOS it will be compatible for 10.3 or higher version.
 Accessible by Logged in Users (Patient, Doctor, Staffs and Admin).
 Well Planned Information Architecture.
 Fast Loading Time & High Performance.
 Browser Consistency.
 Effective Navigation.
 Proper Error Handling.
 Valid Mark-Up & Clean Code.
4.2 Hardware Requirements

Since neither the mobile app nor the Admin & front end panel have any designated
hardware, it does not have any direct hardware requirements. The hardware connection
to the database server is managed by the underlying operating system on the mobile app
and the web server.
However, MDnius web & mobile application will be deployed on the client’s given hosted
server. We suggest the following hosting server requirements for this application:
 Linux Server Platform
 At least 4 GB Ram
 Dual Core Processor
 SSH Access
 Memcached Enabled
 Apache 2x Server
 Python 3x Programming
 Django MVC Framework
 PostgreSQL 9x Server Database
 Ability to set up Scheduler Jobs (For scheduling the emails, running reports etc. at
specific pre-defined time)
 Ability to override options using .htaccess files
.2.1 Hardware Functionality

We will deploy the MDnius Clinic Website & mobile apps on the client’s given hosting
server, propagate the domain, configure email accounts and setup the application
database to the client’s server. Also we will create two separate instances – one for the
live site and another for the future development purpose. Two instances will be
synchronized simultaneously without any error.
.2.2 Hardware Characteristics

As stated above, MDnius Clinic website or mobile app has no direct hardware
connectivity. However, the application will be deployed on the hosted server. Below given
the hosting server characteristics that is recommended for MDnius Clinic application.
 Sufficient Storage Space
 Unlimited Bandwidth
 Email Accounts are Active
 Easy Install of External Tools / Services
 Technical Support
 Mobile App Deployment Support
 Availability of Shell Access
 Accessibility of .htaccess Files
 Easy to Run Cron Jobs
 Automatic Backup of the application
 Storage & backup of the Database
 Maximum Up-Time
4.3 User Requirements

The online users need to have the following things in order to comfortably navigate the
CRM application:
 Internet Connectivity – In order to access the MDnius Clinic application. users
need to have internet connectivity.
 Web Browser – CRM web-admin panel can be accessible from most of the web
browsers and for viewing the website properly, users need to have the almost
latest updated version of the web browser.
 Smartphone – Customer need to download & install the MDnius Clinic app
(Android & iPhone) in their smartphone and access from there smartphone.
Eventually they can use mobile browser and open the MDnius Clinic site. For
mobile browsers Users need to have the almost latest updated version of the web
browser.
 Basic Browsing Knowledge – Customer need to have basic internet browsing

knowledge to navigate the Clinic application. MDnius Clinic site will be login
protected and therefore, users need to have correct login credentials to access
the application.
4.4 Input and Output Requirements

The main inputs, outputs and major functions of MDnius application are as follows:
 Inputs
o Admin Add Customer account details.
o Customer enters his or her user id and password.
o Admin enter his user id and password.
o Customer/guest user can do browse and search ads.
o Admin can manage users, settings has been elaborated in functional
description of this DOC.
o Admin can manage category and ads, rating and reviews. Settings has
been elaborated in functional description of this DOC.
o Admin will update informative page contents.
o Customer Update their profile.
o Customer Post ads.
 Outputs
o Guest user and customer can see list of Clinic ads.
o Logged in customer can see owner details.
o Customer and visitors can open informative pages to see details.
o Customer can see their posted ads.
o Customer will get SMS and email for their account creation.
4.5 Communications Requirements

MDnius will use HTTP and HTTPS protocols for communication over the internet.
.5.1 Communications Hardware

Since MDnius will run over the internet, all the hardware will require to connect internet
will be hardware interface for the system. As for e.g. Modem, WAN – LAN, Ethernet Cross-
Cable.
.5.2 Communications Software

We will use HTTP/HTTPs protocol for communicating the mobile app with the MDnius
backend. Website and mobile app will communicate with each other and always synced
with the latest information.
4.6 Usability Requirements

The usability requirements of the MDnius Clinic application are as follows:
 Clinic website will provide a uniform look & feel between all pages.
 Clinic website will have responsive design which will be adjusted automatically
based on the user’s screen size. It means – the app remains uniform based on the
user’s screen size.
 Usable & workable links throughout the apps.
 Smooth navigation of all sections and inter-linked sections.
 Use of meaningful images and icons throughout the website.
 Use of back buttons for mobile app usability.
 Minimized data input to improve mobile app usability.
 Easy navigation of the mobile app.
5.0 Non-Functional Requirements

5.1 Accuracy
We will maintain accuracy in calculating and displaying data throughout the MDnius Clinic
website and it will consist of:
 All mathematical calculation will deliver accurate result.
 All reports & stats will display accurate result up to two decimal.
 All query that runs to fetch application data, will deliver accurate result.
5.2 Audit Trail
All audited objects will be defined by us and we will maintain full traceability of
transactions:
 Audited Database Fields - We will define which data fields are required audit info.
 File characteristics – size before, size after, structure. User and transactional time
stamps, etc.
5.3 Availability
We will ensure maximum uptime of the Clinic website and trace below parameters:
 Hours of Operation
 Offline Duration - holidays, maintenance times, etc.
 Locations of Operation – where will it be available from, what are the connection
requirements etc.
5.4 Capacity Limits
We will analyze the following capacity of the Clinic website and create provision for the
future enhancements:
 Throughput – We will analyze how many transactions at peak time does the
application needs to be able to handle.
 Storage (memory/disk) – volume of data Clinic website will persist at run time to
disk.
 Year-on-Year Growth Requirements - It will include the analysis of users,
processing & storage.
5.5 Data Retention
We will keep Clinic website data and maintain the consistency of events, values, methods,
measures, expectations & outcomes.
 Data Retention Plan - create plan for handling deleted data from the website.
 Data Integrity – referential integrity in database tables and interfaces.
 Data Backup - Create automated data backup plan for the application database.
 Information Integrity – during transformation.
5.6 Operational Requirements
We will identify the essential capabilities, associated requirements, performance
measures, and the process or series of actions to be taken in effecting the results that are
desired for MDnius Clinic website.
5.7 Performance
We will follow industry standard guidelines for maintaining high performance of the Clinic
website and mobile apps:
 Response times – Clinic website & mobile app loading time, browser refresh
times, etc.
 Processing times – Functions, calculations, imports, exports.
 Query and Reporting times – Initial loads and subsequent loads, ETL times.
 Interoperability
5.8 Portability
We will build the Clinic website and apps in such a manner that it is easy to maintain by
anyone. We will maintain following best practices:
 Conformance to Enterprise Architecture Standards.
 Conformance to Technical Design Standards.
 Conformance to Coding Standards.
 Conformance to Development Best Practices.
5.9 Recoverability
Clinic website and app will have defined recovery process in the event of failure by
ensuring following things:
 Recovery Point Objectives (RPO)
 Recovery Time Objectives (RTO)
 Backup Frequencies – how often is the transaction data, configuration data, code
backed-up?
5.10 Reliability
We will ensure the reliability of Clinic website and application by tracing the following
parameters:
 On-Load Testing - The ability of Clinic website and app to perform its required
functions under stated conditions for a specific period of time.
 Mean Time Between Failures – Identify what is the acceptable threshold for
down-time.
 Mean Time To Recovery – Identify how much time is available to get the system
backup again while broken.
5.11 Security Requirements
We will take care of the following key security requirements of the Clinic website and
mobile app:
 File System Security - Set permissions for Clinic website data may only be
changed or deleted by the application administrator.
 Inactivity Timeouts – It will include durations, actions, traceability of the Clinic
website admin panel.
 Data Backup – Clinic website data backed up every 24 hours and copies stored in
a secure off-site location.
 Data Classification / System Accreditation: All Data must be protectively marked
and stored / protected.
5.12 Usability
We will maintain industry standard rules to maintain usability aspects & it will include:
 Responsive UI/UX for Web browsers, Smart Phones and Tablets.
 Localization Requirements – Languages, Spellings, Keyboards, etc.
6.0 Data Requirements

6.1 Data Structures and Relationships
6.2 Data Framework and Relationships
6.3 Data Inputs
6.4 Data Outputs
6.5 Inter-functional Data Definitions
6.6 Component Cross Reference
7.0 External Interface Requirements

7.1 Software Interfaces
MDnius Clinic website and app (native iOS and Android) programming layer will
communicate with the database layer, create connectivity (app will get connectivity via
website API web-services) and fetch data when & where it is necessary and display in the
application front-end. For Google account and Facebook account login system will use
respectively Google and Facebook Login API. For SMS- OTP activity system will use Twilio
SMS gateway API. Also will use Algolia Search API for better and fast search experience.
We will use Clearbit Company Logo and Name finder API for automatic company name
and logo fetch during company registration time. For Analytics base on Map we will use
Goole Map API (cluster feature).
7.2 Hardware Interfaces

MDnius Clinic website is a client-server application that does not require additional
hardware interfaces to function, other than hosting server. We will deploy CRM
application on a Linux based server where Python 3.x and PostgreSQL 9.x or higher are
installed and other essential components are available.
Since CRM application must run over the internet, all the hardware will require to
connect internet will be hardware interface for the system. As for e.g. Modem, WAN –
LAN, Ethernet Cross-Cable.
7.3 Communications Interfaces

MDnius Clinic website and API request for app and website requires HTTP & HTTPS
protocols to communicate with server. The application can be configured to be accessed
via any available port. The web & mobile based UI is the only means of communication
between the user and the application. MDnius application is accessible through all
popular web browsers that interact with JavaScript & HTML page
7.4 User Interfaces

MDnius Clinic website and app will be designed as a secured system, which will be
accessed by the any authenticated user (e.g. Admin, Customer). Nonetheless, the
application will restrict access to its various components, to users with varied
characteristics. The UI will be easy to navigate without additional training. The user will
be able to interact with the application in English language only. The pages will use
uniform design elements, will be built with a good sense of color and contrast, and should
be printable, using keys. All pages of the Clinic website will be accessible from any page.
8.0 Design Constraints

8.1 Software Design Constraints
Following design constraints are considered for developing the MDnius Clinic website &
app and it will help us to prevent unavoidable circumstances:
 Design Responsiveness - We will account for the fact that viewers can stretch and
distort the designs. We will design with flexibility.
 Fault Tolerance - CRM application data can be recovered in an orderly way. We
will create a process or object class that will provide special code that recovers
when triggered.
 Use content adaptation - Basic structure of the Clinic application will be the same
across all devices, but specific elements, such as image sizes or the appearance of
videos will change based on what the device can support.
 Limit Module Size - We will use optimum module size for the fewest defects.
Structural problems creep into large modules.
 Reuse codes/modules - It is difficult for anyone unfamiliar with a module to alter
it and this often leads to redoing the project rather than reusing it. For that
reason, we will reuse tested, error-free modules as is.
.1.1 Software Interfaces

MDnius Clinic website and app interface will communicate with other processes and sub-
systems to create a seamless connectivity and create smooth flow:
 MDnius Clinic website front-end will communicate with website backend for
storing user accounts.
 MDnius mobile app will communicate with MDnius website backend for listing
and displaying ads, post ads, review rating and for other information.
 MDnius mobile app will communicate with MDnius website backend for customer
account login.
 For Google and Facebook Login Service and basic data collect both app and
website will communicate with respectively Google and Facebook API services.
 For OTP send both website and mobile app will communicate with Twilio API
service.
 For Search ads both website and mobile app will communicate Algolia Search API.
 For auto fetch company name and logo during registration we will use Clearbit
Company Logo and Name finder API.
 For Analytics base on Map we will use Google Custer Map API.
.1.2 Software Packages

As specified above, MDnius will have web based front end and Admin panel as well as
mobile app (native Android & iPhone - both) which will be deployed on the hosting server
and respective Google Playstore and Apple App store and run through the domain and
mobile devices (Android and iOS). We will deploy the application source files, design
interfaces and database on the hosting server and run the application from the online
hosting server.
.1.3 Database
MDnius Clinic website will use PostgreSQL as database which will be connected to the
code written in Python language (server side scripting language). Android will use Java
language (scripting language) and iOS will us Swift Code language (scripting language).
.1.4 Operating System

As per the suggested configuration, we will use Apache web server which will run on the
Linux – UBUNTU operating system environment. MDnius website will run from the Linux
server with PostgreSQL as backend database and Python as server side scripting
language. For app run need Android OS and iOS.
.1.5 Tolerance, Margins and Contingency

We will create system design fault tolerance model which have four ways to deal with the
system fault:
 Prevention,
 Removal,
 Fault tolerance, and
 Input sequence workarounds.
8.2 Hardware Design Constraints
MDnius is a client-server application which will be deployed on the hosting server

provided by the external service provider. Design of the hosting server component is
beyond the scope of this project.
.2.1 Hardware Requirements and Environment

As stated above, hosting server environment for the MDnius Clinic application will be
supplied by the external server provider. However, we will guide the client to book the
correctly configured server that can comfortably host the application. Our preferred
hosting server environment will include the below components:
 Sufficient Storage Space
 Unlimited Bandwidth
 Email Accounts are Active
 Easy Install of External Tools / Services
 Technical Support
 Mobile App Deployment Support
 Availability of Shell Access
 Accessibility of .htaccess Files
 Easy to Run Cron Jobs
 Automatic Backup of the application
 Storage & backup of the Database
 Maximum Up-Time
.2.2 Hardware Standards

Hardware standards will be provided by the hosting server provider and the client will
finalize the hosting server based on meeting the standards of the hosting server.
.2.3 Hardware Interfaces

Since MDnius will run over the internet, all the hardware will require to connect internet
will be hardware interface for the system. As for e.g. Modem, WAN – LAN, Ethernet Cross-
Cable.
8.3 User Interface Constraints

 The Admin user interface for the MDnius will be compatible to any browser such
as Internet Explorer, Mozilla or Chrome by which user can access to the system.
 The admin user interface will be implemented using Angular JS framework.
 The admin and app user interface will be mobile responsive and fit to the
desktop, laptop, tablet or mobile screen sizes depending on the user's selection
of the devices.
 The user interface remains intact and identical in spite of selection of different
screen sizes and operating systems.
.3.1 User Characteristics

MDnius Clinic application will be accessed by visitors as well as registered customers.
Hosts will able to login using their user id (mobile number or email ID) & password and
perform the assigned activities as defined by the application admin.
.3.2 Environment/Operational Constraints

Customer/admin will able to get access of the MDnius application with following
conditions:
 Customer/admin will have correct login credentials
 Customer’s/admin’s smartphone/PC has internet connections and latest web
browser.
 Customer have basic understanding of the website & mobile app browsing
knowledge.
.3.3 Memory Constraints

Hosting server of the MDnius Website application requires a minimum of 512 MB of
primary memory and 3GB of secondary memory for deployment and execution.
9.0 Improvements and Impacts

9.1 Improvements to Existing Capabilities
MDnius application capabilities can be improved by applying following recommendations:
 Use Attractive Call to Action – Instead of using small size buttons for highlighting
actions in different pages, the client can think about using of colorful call-to-
action buttons and it will be easy for users to perform different activities.
 Use Images & Icons – Instead of links, the client may think of using images and
glossy icons in the tables for viewing data records. It will help users to identify the
appropriate action easily.
 Free Space - Create enough space between the texts and images so the viewer is
able to absorb all of the features of the website and business to offer.
 Attractive Dashboard – Customer account dashboard should be attractive by
applying graphical charts and table reports so that users can easily get all
important business data in one page.
.1.1 Upgrades and Enhancements to Existing Capabilities

All functional area already elaborated here. If client need any new module or up
gradation then we will do analysis on that request will confirm officially to client (may be
client’s suggestion would be extended work or up gradation on current requirement). But
our development system will be fully capable to upgrade functionality.
9.2 Impacts
Above discussed features and enhancements have minor impacts on existing modules.
But the new features & enhancements can be easily accomplished because of the
scalable code and database.
.2.1 User Impacts

There are positive impacts on the Customer because of the above discussed
improvements and enhancements. Following impacts can be reflected after implementing
the above discussed improvements:
 Increased patient satisfaction and effectively improve healthcare services.
 Happy patients help spread positive word-of-mouth.
 Patients need a strong visual presentation of the healthcare services offered by this
application and it will help them understand it, want it, and choose right service
from list, means it will help as post sale marketing tool.
 Higher number of positive reviews & ratings by satisfied patients.
10.0 Requirements Traceability Matrix

Bi-Directional Requirement Traceability Matrix will be managed via Google Spreadsheet
and daily updated by team members for transparent tasks updates by PM. PM will
approve the impact analysis and design specification given by developer prior to start
development by developers.

SRS Lifco Ver 1.0 (May'19)

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SRS Lifco Ver 1.0 (May'19)

Загружено:

Авторское право:

Доступные форматы

Software Requirements Specification

INTEGRATED ECOMMERCE PLATFORM

Version No.: 1.0

A. Document Release History 5

8.3 User Interface Constraints.................................................................................................71

A. Document Release History

Sl. Version Release Prepared By Reviewed & Reasons for New

Copy Designation of Copy Holder Location of the Copy

C. List of Amendments Made on the Previous Version:

Sl. Section No. / Description of the Approved by Change Request No.

1.3 Organization Profile

2.0 Overall Descriptions

2.2 Product Functions

1. Signup & Login

B. GRN APP FEATURES

1. Pick list products

C. LAST MILE DELIVERY APP

3. Delivery app features

D. INTELLIGENT ORDER PROCESSING LOGIC

E. BACKEND ADMIN PANEL FEATURES

2.3 Operating Environment

2.4 User Characteristics

3.0 Detailed Functional Requirements

o Order history details: This section will be having following sub

3.2 GRN APP FEATURES

3. Good Received Note (GRN)

4. Change Product Price

3.3 LAST MILE DELIVERY APP

i. Loading Capacity - Each vehicle will have specific no of orders loading

3. Plan your delivery process

3.4 INTELLIGENT ORDER PROCESSING LOGIC

2. Order captured by the system

3. Automatic pick list generation

3.5 BACKEND ADMIN PANEL FEATURES

4.0 System Requirements

Operating System/Development Server Linux (UBUNTU)

Web Sever Apache 2x

Database PostgreSQL 9.3

Scripting Language Python 3.6.3

Framework Django MVC 1.11

Front End Framework Angular JS 5

IOS App App Development Language Swift Code 4.1

Android App Development Language Android SDK, Java based Platform

APIs Google (Login and Map), Facebook (Login),

.1.1 Software Functionality

.1.2 Software Characteristics

 Admin Panel will be cross browser and cross platform supported.

4.2 Hardware Requirements

.2.1 Hardware Functionality

.2.2 Hardware Characteristics

4.3 User Requirements

 Basic Browsing Knowledge – Customer need to have basic internet browsing

4.4 Input and Output Requirements

4.5 Communications Requirements

.5.1 Communications Hardware

.5.2 Communications Software

4.6 Usability Requirements

5.0 Non-Functional Requirements

6.0 Data Requirements

6.2 Data Framework and Relationships

6.3 Data Inputs

6.4 Data Outputs

6.5 Inter-functional Data Definitions