Business Requirements Document (BRD)

The PhotoBooth Web Development

May 2021
Version 2
 Business Requirement Document -PhotoBooth – V1 – Sprint1

Version
Date Document Changes
Number
15/05/2021 1 Initial Draft (Vaibhav Agarwal, Project Manager)
29/05/2021 2 Baselined Version (Vaibhav Agarwal, Project Manager)
03/06/2021 2.1 Baselined Version (After incorporating inputs given by Alex)

Reviews and Approvals

Role Name Remarks Date
Author (VDOIT) Vaibhav Agarwal 1st May – 31st
May 2021

Contributors (VDOIT) Alex, Vaibhav, Sweksha, Indu, Pinki, Gaurav, Reviewed 1st May – 31st
Neetu, Narinder, Kritika, May 2021

Reviewer (VDOIT) Narinder Kamra Reviewed - NK May 31,

2021

Reviewer (VDOIT) Neetu Gupta Reviewed - NG May 29,

2021

Reviewer and Alex

Approver (The Photo
Booth)
 Business Requirement Document -PhotoBooth – V1 – Sprint1

1 Introduction 1
1.1 Purpose of Document 1
1.2 Project Summary 1
1.2.1 Objectives 1
1.2.2 Current State 1
1.2.3 Artifacts shared (Architecture, Features and Verticals) 3
1.2.4 Business Drivers 4
2 Project Scope and Processes 5
2.1 Mobile responsive end Customer UI 5
2.1.1 Administrator Panel UI 7
2.1.2 Printer Specifics and Connections 11
2.2 Admin Levels 11
2.2.1 Customer Login and Data Policy 12
2.2.2 Verticals 13
2.2.3 Product Management 16
2.2.4 Image Processing 17
2.2.5 Payment Methods and Integrations 17
2.2.6 Subscription/Revenue Model 18
2.2.7 Refund Process 19
2.2.8 Reporting System 21
2.2.9 Gallery Mode 21
2.2.10 Thin Websites 21
3 Data base Design - ERD 22
4 Exceptional Scenarios 23
5 Second Phase Development Items 23
6 Issues, Risks and Dependencies 23
7 Infrastructure still in discussion 26
 Business Requirement Document -PhotoBooth – V1 – Sprint1
1 Introduction
1.1 Purpose of Document
Document is outcome of the requirement understanding of the Project “The Photobooth” through
research, meetings and interviews with Client. This document would be a Living document until Product gets
into market as per expectations mentioned in Agreement. This document also server the purpose of “Statement
of Work” to guide the team during development. Any significant Scope change would lead a separate discussion,
analysis and changes in Schedule or Cost if required. At the time of final release, an updated version of this
document would be transitioned to the Owner of Product.

1.2 Project Summary

1.2.1 Objectives
Develop the complete Web platform that process and prints photos directly takes orders from
customers computers or phones to the printer. The web app is going to have a front-end tool for
the end customers and multi-tenant system for the administration. The web app is to be mobile
responsive.
Following are key goals
● Image Processing
● Payment
● External printer integration
● Multi-tenant Users
● Multi-Location Content Management
● Analytics: Dashboards, reports, warnings
● CRM activities: B2B, B2C, Support, Contact

1.2.2 Current State

“The Photobooth” has been using 3rd Party software to manage the operations – printbudii
which is a standard solution developed owned by 3rd Party vendor. “printbuddi” is a responsive
web app giving an admin panel.
Here is the high level scope to be taken care while developing in-house platform for “The
Photobooth”.

1. Admin panel to be enhanced having functionalities (Reference- prinstamatic.)

2. The web app is to include multiple image processing features.
3. Manage multiple verticals and its users.
4. Region/Country wise features functionality.
5. Payment options and Security to be enhanced.

Here are couple of screenshots of old system:

 Business Requirement Document -PhotoBooth – V1 – Sprint1

Customer Side Screen

Admin Dashboard
 Business Requirement Document -PhotoBooth – V1 – Sprint1

1.2.3 Artifacts shared (Architecture, Features and Verticals)

Business Requirement Document -PhotoBooth – V1 – Sprint1
 Business Requirement Document -PhotoBooth – V1 – Sprint1
1.2.4 Business Drivers
The Founder, Alexandra, started The Photo Booth Co in 2008 as a photo booth event rental
company. She soon realized there was a niche in the market for non-passport, social media
photo booths and started The Photo Booth Co (UK) Ltd in 2011 with a focus on branded photo
booths for vending and profit share.
Now taking her vision further she wishes to develop a hassle-free, fast and easy to use system
that eases the way people get their pictures printed.

● For the prints, customer must wait for delivery or at shop, but the process can be made fast by just choosing
the image and printing at desired location.
● Customers do not have to plan for the print to be taken. If nearby printer just open app, process, print, it is
that simple.
● Client requires a scalable solution to track the printers with options to add multiple users to take actions on
respective printers.
● The scope of the system to be placed is for multiple counties across many continents thus requires localized
User Experience.

2 Project Scope and Processes

The overall project scope can be broadly divided into two parts. Any point can be related to
multiple pages. The descriptions of these points are expanded in the pages in separate sections
below:
1. Mobile responsive end customer UI
2. Administrator Panel UI
3. Printer Specifics and Connections
4. Admin Levels
5. Customer Login and Data
6. Verticals
7. Products
8. Image Processing
9. Payment Methods and Integrations
10. Subscription/Revenue Model
11. Refund Process
12. Reporting System
13. Gallery Mode
14. Thin Websites
15. ERD
16. Use Cases/Scenarios

2.1 Mobile responsive end Customer UI

The UI consists of the following pages, in the order of the UX flow.
1. Login/Signup
a. Direct registration and Login through Email/Password
 Business Requirement Document -PhotoBooth – V1 – Sprint1
b. Social – Google, Facebook
c. Consent for sign up checkbox and link to privacy statement
2. Select Location/Scan QR
a. Centre Live or Not
b. Timings
c. Distance
3. Select Product
a. Photos
b. Biometric Passports
c. Collages
d. Strip Photos
4. Select or Take Photos
a. Select from Gallery
b. Click new image
5. Image Processing
a. Frames – General Occasions (Birthday, Anniversary etc), Region wise Festivals
b. Crop/Zoom/Adjust/Rotate
c. Background Colour
d. Text
e. Draw
f. Stickers
g. Shapes
6. Cart
a. Manage Quantity
b. Edit/Delete
7. Checkout
a. Promo
b. Scan QR
c. Payment Gateway (Stripe)
d. Consent for order
8. Settings (Menu) –
a. Profile
i. Edit Photo, Name, email, phone
b. Order History
i. View all order history
ii. Reorder same
iii. Contact us about this order
c. Notification
i. Photos – Printed or Failed
ii. Mode – Push/Mail/SMS
9. Support/Contact
a. Number/Email
b. Contact us form
 Business Requirement Document -PhotoBooth – V1 – Sprint1

Disclaimer: The UI images are for reference purpose only. These will be upgraded as per requirement.

2.1.1 Administrator Panel UI

1. Super Admin
a. Dashboard – Sales/Indicators - Tabular and Graphical Data
i. Revenue
ii. All Printers – Status
b. Client/Partners (Group Admin)

c. Outlets (Admin)
 Business Requirement Document -PhotoBooth – V1 – Sprint1

d. Customers

e. Orders

f. Photos
i. Occasions
 Business Requirement Document -PhotoBooth – V1 – Sprint1

ii. Frames

iii. Stickers

g. Printers
 Business Requirement Document -PhotoBooth – V1 – Sprint1

h. Reports
i. Settings
i. Countries
ii. Printer Types
iii. Verticals
iv. Products
v. Packages

2. Group Admin (Multi-chain store/Partner Company) (TBD)

a. Similar to Super Admin but can only access/manage relevant details related to the printers
assigned to it.
b. Country is Fixed
3. Admin/Individual Store/Technician (TBD)
a. Dashboard
b. View only relevant Details
4. Investigation
a. Dashboard
b. Prison Order details and Gallery
 Business Requirement Document -PhotoBooth – V1 – Sprint1

Disclaimer: The UI images are as on 03rd June 2021. The UI images are for reference purpose only. These will be
upgraded as per requirement.

2.1.2 Printer Specifics and Connections

The details of printer to be integrated:

● Brand: DNP

● Model: RX1HS

● Resolution: 300 dpi

● Print Sizes: 2″ x 6″ *, 4″ x 6″, 6″x 6″, 6″ x 8″

● Print Speed: 12 sec/print (2″ x 6″*), 12.4 sec/print (4″ x 6″), 21.9 sec/print (6″ x 8″)

● Paper: 1400 sheets/roll (2″ x 6″*), 700 sheets/roll (4″ x 6″), 350 sheets/roll (6″ x 8″)

● Weight: 30 lbs

● Dimensions: 12.67″ x 13.8″ x 11.06″ (W x D x H)

The connection to the printer is made with the help of Raspberry Pi. Our server connects with raspberry
system which in turn controls the printer. A screen is connected with the pi module to display QR codes
and status. (TBD)

2.2 Admin Levels

There are four levels defined in the Administration Network. The below chart depicts the hierarchy of
admin levels. The login for all admin levels will consists of two factor authentication through password
as well as SMS OTP.
1. Super Admin
 Business Requirement Document -PhotoBooth – V1 – Sprint1
The PhotoBooth Company will act as the Super Admin. They will have all power over all machines
and features.
2. Group Admin
The Group admin is the Client having multiple locations where the printer can be placed. The Group
Admin has all power on over all features and printers assigned to it. In case of a Client having
presence in multiple countries, different group admins are made for different countries like Hard
rock cafe - France, Hard rock cafe - Belarus
3. Admin
The Admin is the Client having a single store/location. An admin can only view relevant details but
not edit any settings.
4. Investigation
This level is specific to the Prison Vertical. The data of orders sent to Prison is saved and can be
accessed by the investigating person. This data includes photos, prisoner name, sender name,
inmate pin.
++

2.2.1 Customer Login and Data Policy

The customer must either signup or use guest login when logging in first time into the web app.
a. Signup – Customer can sign up using Email or using Social Login. The Social Logins applicable here
are Facebook and Gmail. Customer has to provide Mobile number while signing up.
b. Guest – Customer can proceed using soft signup using email. A login will be created for this email
with a temporary password which will be emailed to the customer. The customer can change the
password after logging to the app.
Two Factor Authentication
Every time the customer login using email or social, another verification must be done using OTP on
customer’s mobile number before logging in. (TBD- Compulsory or Optional)
Data Policy
a. Order Data – The order data is retained in the system after taking consent of the customer only. The
customer can delete the data at any time.
b. Image Data – Image data is stored only in the case of sending and receiving data from Prison and in
case of an Event. An expiry date of 90 days for Prison and 6 months for event is to be assigned to
this data after which the images get delete. In case of Event, the expiry date can be extended if the
user buys a subscription. The event user should also be able to download all images from the event
gallery.
The SuperAdmin or GroupAdmin are not able to view the photos. They are only able to see the
thumbnails of photos while accessing the orders.

2.2.2 Verticals
There are five kinds to verticals to be included the system namely Prison, Events, Retail, Leisure and
Social. The permissions/rules defined for individual vertical are different. The verticals are discussed in
detail below.

2.2.2.1 Prison
One of the locations that the printer can be placed is Prison. There are two scenarios in this vertical.
 Business Requirement Document -PhotoBooth – V1 – Sprint1
a. The relatives/friends of prisoner can place the orders online from home with photo
uploading with printing location selected. No cash is involved.
Fields to complete: Sender’s name, sender’s email, Prisoner Name, Prisoner PIN
b. The prisoner can send a postcard picture with a message to the family/friend through the
Admin. The photo prints at a predefined location where it is further shipped.
Fields to Complete: Senders/Prisoner Name, Recipient Name, Recipient Address

2.2.2.2 Event
This is a vertical that comes into play when a scheduled event is going to happen. Let’s take an
example of a wedding.
a. A representative of a wedding comes to the Outlet/Admin and ask for the printer services to
be placed at an event.
 Business Requirement Document -PhotoBooth – V1 – Sprint1
b. The Super/Group Admin then creates an Event defining the preferences. Event preferences
include:
● Date

● Time

● Location

● Photos free or paid

● Photo products

● Event gallery
c. Admin can also upload multiple watermarks/Frames that will be printed in all photos during
event. The guest has to choose a watermark among these.
d. For the guest login, the admin can choose from one of the below options when creating the
event.
● No details required: The guest can directly print the photos without filling any
details.
● Basic Details Required: The guest have to fill Name and email to access the app.
e. Specific static QR code and Link is generated for that event. This QR code/Link is used to
access the Photobooth web app where the printer is pre-selected.
f. There is no checkout option. The photo prints directly from the cart.
Business Requirement Document -PhotoBooth – V1 – Sprint1
 Business Requirement Document -PhotoBooth – V1 – Sprint1

2.2.2.3 Retail/Leisure/Social
The process of these verticals is currently set as the normal process. These verticals are tagged for
future purposes if some preferences need to be set differentiating these verticals.

2.2.2.4 Auto Print Mode

In case of all the verticals, a checkbox for ambassador mode is provided at the outlet level. When
selected, the app directly prints from application when the customer clicks print button. If not
selected, then the print is to be manually triggered by either scanning the QR code or by typing the PIN
on the screen. The initial display will show the QR code and below that the statement “Touch here to
input PIN”.

2.2.3 Product Management

There are currently four types of products that a customer can choose from. There are multiple
selections available in some of the products which can be seen in the flowchart below.
 Business Requirement Document -PhotoBooth – V1 – Sprint1

2.2.4 Image Processing

After selecting the product, customers can process the image by adding a frame, sticker, or rotating,
adjusting the image. Multiple features are provided for modifying the image before checkout as
presented in the flowchart below.
 Business Requirement Document -PhotoBooth – V1 – Sprint1

2.2.5 Payment Methods and Integrations

A customer can basically do payment through online payment (Stripe) or paying at Cashier, which
requires scanning QR code presented by cashier. The promo code can be applied at the time of
checkout.
The promo code is generated and managed by Super Admin or Group Admin. The expiry date is defined
for the promo code while creating.
 Business Requirement Document -PhotoBooth – V1 – Sprint1

2.2.6 Subscription/Revenue Model

The Photobooth company has two business model that will be integrated to the system for revenue
calculations.
g. Revenue Share Model
The PhotoBooth Company owns the printer in this Model. A percentage of monthly revenue
will be shared with the Admin where the printer is placed. The percentage can be defined by
the super admin while onboarding the group admin or outlet. The initial payment from
customer goes into the PhotoBooth account. The split of revenue is done manually by
PhotoBooth.
 Business Requirement Document -PhotoBooth – V1 – Sprint1
h. Subscription Model
In this model the printer is owned by the partner and subscription for the software is bought
by them. The software will be linked to the subscription as if the subscription expires the
printer will be showed offline to the customer during selection. The complete payment by
customer comes directly to Client’s account.

2.2.7 Refund Process

A customer can ask for refund by calling the customer support in case of Print did not happen, print
blurry but photo is fine etc. The customer will have the option to change the outlet in any of the case,
but outlet of that Particular Group Admin can only be selected as the Payment was given to them.
 Business Requirement Document -PhotoBooth – V1 – Sprint1
The Customer support is The PhotoBooth Company in case of Revenue Share Model and the client in
case of Subscription Model. While doing the refund the Customer Support adds justification by using
pre-defined drop down menu or writing their own. Customer Support also mentions the mode of
refund.
There will also be a possibility of partial payment, the total refund amount is shown initially in the
system but the customer support can manually enter the partial pay amount and proceed with refund.
 Business Requirement Document -PhotoBooth – V1 – Sprint1

2.2.8 Reporting System

There are currently 2 types of reports to be published on daily basis.
1. Printer Health Report
 Business Requirement Document -PhotoBooth – V1 – Sprint1
This report consists of the whole day heath report of all printers (excluding Subscription Model
Printers) which includes
a. Printer paper and ink level check in the morning at 9 am and evening at 6 pm local time.
b. Printer Online/Offline status at every 5 minutes. Green/Red dot to be shown in the UI
against the printer in case of Printer being Online/Offline respectively.
2. Revenue/Audit Report
This report consists of multiple parameters like number of prints based on product, country, client,
business model, total revenue etc for the day in Daily report.
The revenue will be further divided based on revenue share percentage by the clients and
Technician.

2.2.9 Gallery Mode

This field is applicable to Prison and Event Verticals only. The description is as below:
1. Prison: While someone is sending pictures to prison or vice versa, these images are saved for
investigation purposes. The investigator can login and check all the images pertaining to a prison.
Investigator can filter the images based on Order Number, Sender’s Name, Prisoner’s Name, Inmate
Pin and Date.
2. Event: In case of an event, the images that are printed by guests during the event can be saved in a
Gallery. A checkbox will be shown to the guest at the time of photo upload if she wishes to upload
the photos to the event gallery. While creating an event a password protected link is created to view
the gallery of that particular event. This gallery can be used to run a slideshow during the event and
can be used to share all the event images among guests.

2.2.10 Thin Websites

This field is applicable to Prison and Retail (In case of Subscription Model- will refer as SM) verticals only.
A different Customer Landing page for each Prison and Retail (SM) has to be generated. This will be
done from the Super Admin Login only.
The parameters to be set for each landing pages:
a. Logo
b. Background Colour
c. Privacy Policy
d. Consent
e. Customer Support Number/email
 Business Requirement Document -PhotoBooth – V1 – Sprint1
3 Data base Design - ERD
Business Requirement Document -PhotoBooth – V1 – Sprint1
 Business Requirement Document -PhotoBooth – V1 – Sprint1
4 Exceptional Scenarios
There can be other use cases also in the complete application. The major ones which are discussed, and
solution is formed are below.
1. If network is Disconnected at printer level (OFFLINE Mode):
The printer only triggers the print when QR code at printer is scanned by Customer. If customer has
done the payment and is unable to scan the QR due to printer being offline or unable to display QR,
the customer will have the option to change the printer but within that Group Admin printers only
as the payment is done to that particular group admin. Customer can also ask for refund which is
described in Refund Process section.
2. If network is not available at customer end: (In Discussion)
The printer should be able to share its Wi-Fi to which the customer connects and prints photo from
the phone. (TBD)

5 Second Phase Development Items

The work items that are pushed to second Phase are
1. Customer Subscription/Packages.
2. Languages of Customer side UI.
3. Expose APIs for Retail Customers to integrate into their app/system.
4. Event Gallery: Option of bulk upload by the photographer.

6 Issues, Risks and Dependencies

S. No. Topic Description Owner Status Update

1 Price per photo to Outlet - Multiple printers in outlet Alex Closed Price per photo to be
be associated with (Admin level) is possible? If yes, so associated with Outlet
printer or region or how prices will be defined?
some group?
VDOIT: Tabular Form of Products and
Prices initially to be set up at Group
Level and Outlets can overwrite.

2 QR code - Printer When any Printer gets onboarded, it’s Alex Open Alex: This is correct.
Level identity is mapped through QR code
Yet to receive the APIs,
and that code should be digitally
so keeping it Open.
displayed on Raspberry PI Device
coupled with Printer

3 Raspberry PI Alex has to check and share the Alex Open

Specifications
 Business Requirement Document -PhotoBooth – V1 – Sprint1
4 Consent on Upload For every kind go Photo upload, there Alex Open
should be consent accepted by
Customer to meet the GDPR
Compliance. Consent Text can vary
based on Category, so Admin Panel
will keep that Dynamic for Category.

5 Free Photo Purpose is to collect the data (Name, Alex Open

Email and other) in the limits of GDPR

6 If network is Queue the photos to be printed that Alex & Open

Disconnected at are already paid by customer and wait vDoIT
printer level till the printer goes online and then
(OFFLINE Mode) print photos.

7 If network is not The printer should be able to share its Alex Open
available at wifi to which the customer connects
customer end and prints photo from the phone.

8 Gallery Mode The photos for orders of verticals Alex Open

Prison and Event are to be retained for
a particular period of time. The time is
yet to be defined. The photos can be
viewed as Gallery from Admin panel in
case of Event and Investigation in case
of Prison.

9 Events Do we need to get profile of Guest Alex Closed Alex: No, we do not
created when he/she scans QR Code need to create a profile
during the event or this has to be of the guest. The guest
limited to just "Scan and Print whoever should be able to
he is" and forget. “Scan-print-forget”

10 s3 servers Alex confirmed operations in US, Alex Open

London, Europe, Australia, Singapore
and AWS has datacenters in all these
countries to meet GDPR Standards so
that data can be stored in those
respective countries only.
vDoIT – Super Admin structure will be
a bit complex and Maintenance will
increase.

11 Printer status Check for paper and ink in morning Alex Open
record and evening. Check On and Off every 5
mins. APIs yet to be provided

12 Event Gallery Link Event Gallery link is to be made Alex, Open

password protected. VDOIT
VDOIT Team needs to do research on
 Business Requirement Document -PhotoBooth – V1 – Sprint1
feasibility of Session-less (Mobile only)
mode how this can be made OTP
(Event Level) protected

13 Event Print A limitation on the prints occurring vDoIT Open

Limitation from a particular device must be
applied. This can be done based on
IP/MAC address of the device.
Research is to be done by Technical
Team to confirm the feasibility-
(Sweksha, Pinki)

14 Event Gallery There will be limited storage for the Narinde Open
Storage event photos to upload. This limit can r
be increased for customer, but the
customer needs to buy more storage.
In discussion - Package design can
incorporate Storage as one of the
parameters
Storage costs is to be explored on
different services that will help design
packages.

15 Printer Screen While printing the photos, the first vDoIT Open
photo of an order to be displayed on
the screen connected to Raspberry Pi.
This requirement can be confirmed
after reviewing the details of
Raspberry PI API/Capability.

16 Country wise Data Data Policy to retain photos is to be Alex Open

Policy defined country/region wise. Example
- In Europe photos can be saved upto
30 days and in USA according to
customer preference. Exact
information is yet to be defined.

17 Best Practices from Alex has shared Admin Panel of similar ALL Open
Admin Panel of solution and Team has to do deep
PrintBuddi study so that best practices can be
adapted in "The Photobooth"
platform.

18 Encryption Encryption is required for Alex and Open

vDoIT
-Personal Information
-Images
-Customer Related details like
 Business Requirement Document -PhotoBooth – V1 – Sprint1
Transaction id, order id, Location

vDoIT have to get back regarding

Images Encryption.

7 Infrastructure still in discussion