SOFTWARE REQUIREMENT

SPECIFICATION
(SRS DOCUMENT)

for
E-Brochure
 Table of Contents
1. Introduction .........................................................................................................................1
2. Use Case Diagram ...............................................................................................................2
2.1 User Use Case Diagram ............................................................................................2
3. Detailed Use Case ...............................................................................................................3
4. Fucntional Requirement ......................................................................................................8
5. Non-Functional Requirement ..............................................................................................9
6. Detail ...................................................................................................................................9
7. Relatable System ...............................................................................................................10
8. Features ............................................................................................................................10
1. Introduction

E-brochures significantly reduce printing costs and cut marketing costs. This system is
modern and a need in this digitalized world. This system helps in printing and posting e-
brochures are without significant costs. Even on a PDF file you may make them. This
makes professional, interactive PDF flip-section digital brochures, booklets, or pamphlets.
Share everywhere, publish online. And this is great, because you can be creative in a
brochure and try new things when you decide the design, write the content and promote it
on the web. This process helps you to broaden your horizons, enhance your abilities and
better understand your audience. Moreover, it attracts the attention of your customers and
works towards your business success.

2. Use Case Diagram

2.1. User Use case Diagram
 3. Detailed Use Case Diagram

3.1 UC-01: Login

Use Case Name: Login

Actors: Admin (primary actor), User (primary actor),
Description: User shall login to get access to his/her account in order to facilitate him/her self with the system.

Trigger: User clicks the “Login” button to sign in his/her account

Preconditions: PRE-1. User is registered in the system

PRE-2. System is available to the user
Postconditions: POST-1. User successfully logged in his/her account and has access to his/her profile.

Normal Flow: 1. User clicks on the sign in button.

2. User enters his/her credentials.
3. User clicks on the login button.
Alternative Flows: N/A
Exceptions: 2a. In step 2 of normal flow, if the user enters invalid credentials.
1. System will prompt an error message to user “invalid username or password”.
2. User will enter correct credentials.
3. Use case resumes on the step 3 of normal flow.
Business Rules N/A
Assumptions 1. User has internet connection.
2. User has a registered account.

3.2 UC-02: Register

Use Case Name: Login
Actors: User (primary actor),
Description: User shall login to register his/her account in order to facilitate him/her self with the system.

Trigger: User clicks the “Signup” button to sign in his/her account

Preconditions: PRE-1. System is available to the user

Postconditions: POST-1. User successfully signup his/her account and has access to his/her profile.

Normal Flow: 1. 1. User clicks on the sign up button.

2. 2. User fills the sign up form
3. 3. User clicks on the submit button
4. 4. System verifies user details
5. 5. User is registered in the system
Alternative Flows: 2a. In step 2 of normal flow, if the user clicks on signup with Gmail/FB option
1. System will redirect to gmail account or Facebook account
 2. User will verify the credentials
3. Use case resumes on the step 5 of the normal flow
Exceptions: N/A
Business Rules N/A
Assumptions 1. User has internet connection.
2. User has a registered account.

3.3 UC-03: Logout

Use Case Name: Logout

Actors: Admin (primary actor), User (primary actor)
Description: User shall logout from his/her account once he/she is finished acquiring the system resources.

Trigger: User clicks the “Logout” button to sign in his/her account

Preconditions: PRE-1. User is logged in the system

PRE-2. System is available to the user
Postconditions: POST-1. User successfully logged out of his/her account.

Normal Flow: 1. User clicks on the logout button from the menu.
2. User is redirected to the Login page.
Alternative Flows: N/A
Exceptions: N/A
Business Rules N/A

3.4 UC-04: Create Brochure

Use Case Name: Create Brochure

Actors: User (primary actor)
Description: User shall be able to create brochure by clicking Create button.

Trigger: User clicks the “Create” button to create a new brochure

Preconditions: PRE-1. User is logged in the system

PRE-2. System is available to the user
Postconditions: POST-1. User successfully created a new brochure.

Normal Flow: 1. User clicks on the create brochure button from the dashboard
2. System give user two option “upload a pdf” or “ start with a demo”
3. User clicks on “upload a pdf” button.
4. System prompts user to upload a file.
5. User uploads the pdf file
6. System process it, (it will take few minutes)
7. System opens a window with brochure design as a flipbook and side bar menu with
 options from where user can edit it
8. After adding information and gifs and images and video links etc.
9. User clicks on next button
10. System displays the e-brochure flipbook with public link and download options
Alternative Flows: 4. In step two of the normal flow if the user clicks on “start with demo”
1. The system will load a demo brochure file with dummy data in it
2. The use case resumes on step 7 of the normal flow
Exceptions: N/A
Business Rules N/A

3.5 UC-05: Edit Brochure

Use Case Name: Edit Brochure

Actors: User (primary actor)
Description: User shall be able to create brochure by clicking Customize button.

Trigger: User clicks the “Customize ” button to edit the brochure

Preconditions: PRE-1. User is logged in the system

PRE-2. System is available to the user
Postconditions: POST-1. User successfully updated the details of his/her account.

Normal Flow: 1. User navigates to his/her dashboard.

2. List of all brochures created by the user is available to user
3. User clicks on the customize button option on the specific brochure he/she wants to edit
4. The system opens the window where user can edit the details
5. The user edits the detail of the brochure
6. The user clicks on the save button
7. The brochure is updated.
Alternative Flows: N/A
Exceptions: N/A
Business Rules N/A

3.6 UC-06: View Brochure stats

Use Case Name: View Brochure stats

Actors: User (primary actor)
Description: User shall be able to create brochure by clicking view stats button.

Trigger: User clicks the “view stats ” button to edit the brochure

Preconditions: PRE-1. User is logged in the system

PRE-2. System is available to the user
Postconditions: POST-1. User successfully viewed how many viewers have visited and opened and viewed his
Brochure
Normal Flow: 1. User navigates to his/her dashboard.
2. List of all brochures created by the user is available to user
3. User clicks on the view stats option of the specific brochure he/she wants to view
4. The system opens the new window where user can view stats of his/her brochure
5. User can check how many viewers have viewed his/her brochure and how many viewers
visits and opened his brochure etc.
Alternative Flows: 4 In step 4 of the normal flow if user clicks on export button
1. User clicks on the export button on the top right corner of the system
2. System shall prompt a new window asking user with options that “What time period data
you want” and “what kind of data you want to export”.
3. User selects the details and clicks on the “export” button
4. System shall sent the detail document CSV file on the user email address and prompts a
“thankyou message” to user.
Exceptions: N/A
Business Rules N/A

3.7 UC-07: Share brochure

Use Case Name: Share brochure

Actors: User (primary actor)
Description: User shall be able to share brochure to different platform by clicking share button.

Trigger: User clicks the “share” button to edit the brochure

Preconditions: PRE-1. User is logged in the system

PRE-2. System is available to the user
Postconditions: POST-1. User successfully shared his/her brochure.

Normal Flow: 1. User navigates to his/her dashboard.

2. List of all brochures created by the user is available to user
3. User clicks on the share button, of the specific brochure he/she wants to share
4. The system opens the new window with public, private, specific, and traceable brochure
link option
5. User selects public links option
6. User can copy the link and can also share it to social media platforms
7. Anyone with brochure link can view it.
Alternative Flows: 4a. In step 4 of the normal flow user clicks on the traceable link option.
1. The system will provide user with a traceable link.
2. He/she can this one-to-one link with the client and can view stats
3. System will send user details of stats through email.

4b. In step 4 of the normal flow user clicks on the private link
1. The system will prompt user with a private link
2. The specific people with access to it can only view the brochure

4c. In step 4 of the normal flow if user clicks on the specific link option
1. The system will prompt user to the add the specific website URL.
2. The brochure will open in the specific website.
Exceptions: N/A
Business Rules N/A
 3.8 UC-08: Embed Brochure

Use Case Name: Embed Brochure

Actors: User (primary actor)
Description: User shall be able to embed brochure by clicking embed button.

Trigger: User clicks the “embed” button.

Preconditions: PRE-1. User is logged in the system

PRE-2. System is available to the user
Postconditions: POST-1. User successfully embed the brochure code to his/her website.

Normal Flow: 1. User navigates to his/her dashboard.

2. List of all brochures created by the user is available to user
3. User clicks on the embed option of the specific brochure he/she wants to view
4. The system process and opens a dialogue box with code to embed to his website or
wordpress site.
5. User can copy the simply copy the code and embed it to his/her website
Alternative Flows: N/A
Exceptions: N/A
Business Rules N/A

3.9 UC-09: Login Restriction

Use Case Name: Login restriction

Actors: User (primary actor), Viewer(secondary actor)
Description: User shall be able to add login restriction so that a viewer must login to the website to view the
brochure.
Trigger: User clicks the “restrict” button.

Preconditions: PRE-1. User is logged in the system

PRE-2. System is available to the user
Postconditions: POST-1. User successfully added the login restriction to his e-brochure on the website so he can
retract his viewers
Normal Flow: 1. User navigates to his/her dashboard.
2. List of all brochures created by the user is available to user
3. User clicks on the restrict option of the specific brochure he/she wants to add the
functionality.
4. The system prompt user with a form displaying multiple options for viewers signin
i.e.(through Fb, Gmail etc)
5. User chooses the login methods and click enable button
6. Login restriction added to the brochure Successfully
Alternative Flows: N/A
Exceptions: N/A
Business Rules N/A
 4. Functional Requirements
The following are the functional requirements of the e brochure system.

ID Requirement Dependencies
FR-01 The user shall be able to login in the system with the FR-02, FR-03
correct credentials
FR-02 The user shall be able to sign-up in the system by N/A
filling signup form
FR-03 The user shall be able to sign-up using Gmail. N/A
FR-04 The system shall validate user login credentials FR-01
FR-05 System shall redirect user to his/her dashboard after FR-01, FR-03, FR-02
logging in or signing up to the site.
FR-05 The user shall be able to view different e brochures FR-01
on the site
FR-06 The user shall be able to start creating e brochure FR-01
process by clicking create button
FR-07 The user shall be able to upload image, pdf files FR-01
that he wants to upload in the brochure
FR-08 The system shall validate the image, pdf file size FR-01, FR-07
uploaded by user is optimized
FR-09 The user shall be able to add text, descriptions in FR-01, FR-06
the brochure
FR-10 The user shall be able to add embedded links in the FR-01
brochure
FR-11 The user shall be able to add gifs in the brochure FR-01
FR-12 The user shall be to add support links in the FR-01
brochure
FR-13 The user shall be able to add google maps in the FR-01
brochure
FR-14 User shall be able to point to specific objects in the FR-01
brochure and zoom it or view notes associated with
it
FR-15 User shall be able to zoom in and zoom out the FR-01, FR-14
brochure.
FR-16 User shall be able to add multiple pages to a brochure. FR-01
FR-17 User shall be able to create a brochure by selecting FR-01
components like image, video, rich text as a heading
and or paragraph.
FR-18 User shall be able to edit brochures FR-01
FR-19 System shall auto save any edits made by user in the FR-01
brochure
FR-20 User shall be able to get brochure shareable link once FR-01
by clicking share button
FR-21 System shall allow anyone to view brochure details FR-01
with e-brochure link
FR-22 System shall validate that the brochure shared should FR-01
be responsive for all screen sizes
FR-23 Admin shall be able to view details of all user FR-01
registered in the system
FR-24 Admin shall be change status of a user brochure to FR-01
active/deactivate.
FR-25 System shall validate that active status brochures links FR-01
are working and user can view the brochure details
FR-26 System shall validate that the deactivated brochures FR-01
links are not working and doesn’t show details of the
brochure to viewers/users.
FR-27 The user shall be able to add login restriction to the e- FR-01
brochure so that the user has to login first to view the
brochure
FR-28 User shall be able to make brochure shareable link FR-01
private/specific/public.

5. Non-Functional Requirements:
Following are the functional requirement of the system.

 Performance

PER-1: The average response time per every user click shall be less than 4 seconds. And
the maximum average time per every click shall be less than 6 seconds.

 Usability

USE-1: The system user interface shall be user friendly. i.e. the minimum amount of time
taken by novice user to learn the system shall be 15 minutes.

6. Details

The project is E-Brochure website where user will create a profile and will be able to create an
online brochure. Two main parties using this system.
1. Users.
2. Viewers.
Users: Who will design an E-Brochure. User will first create a profile by email account logged
in user shall be displayed with a Dashboard screen. For creation of e-brochure.
 Project Name/Brochure name, Description, view and way to copy a unique link, creation
and modification date, delete.
 Link should be sharable to anyone.
 User should be able to delete it. Confirm if you would like to have a delete feature.
 User should be able to share a link of the brochure with anyone irrespective of whether
person is a registered user or not.
 User should be able to login using Gmail.
 Standard login logout features.
7. Relatable System

1. Flipping book:
This system is most closely relatable to our proposed system. Development team can
view this as reference

https://flippingbook.com/online-digital-brochure

8. Features
Following are the most notable features of our system
 Easy Navigation
 Video and Links
 Content Protection
 Lead Capture Form
 Document Tracking