Birth and Death Registration System Standards

System Requirement Specifications (Digital Hoarding 1.0)

System Requirement Specifications

Document Version History Version 1.0 1.1 Date 09-10-2012 Author Krishna Comments Initial Draft Modified draft

Key Milestone Summary Milestone Creation Submission Sign-off Versio n 1.0 Date 03-10-2012 Personnel

Page 2

System Requirement Specifications

Table of Contents 1 INTRODUCTION ................................................................................................. 4 1.1 1.2 1.3 1.4 1.5 2 3 4 5 OVERVIEW ........................................................................................................ 4 OUT OF SCOPE .................................................................................................. 4 ASSUMPTIONS .................................................................................................. 5 DEFINITIONS ............................................ ERROR! BOOKMARK NOT DEFINED. INTEGRATION WITH OTHER MODULES ..... ERROR! BOOKMARK NOT DEFINED.

SYSTEM OVERVIEW ....................... ERROR! BOOKMARK NOT DEFINED. HIGH LEVEL PROCESS OVERVIEW ............................................................ 6 USE CASES ........................................................................................................... 7 PRODUCT FEATURES ....................................................................................... 8 5.1 5.2 FEATURE-1 .............................................. ERROR! BOOKMARK NOT DEFINED. FEATURE-2 .............................................. ERROR! BOOKMARK NOT DEFINED. REPORT-1 ................................................ ERROR! BOOKMARK NOT DEFINED. REPORT-2 ................................................ ERROR! BOOKMARK NOT DEFINED. MASTER SCREEN-1 .................................. ERROR! BOOKMARK NOT DEFINED. MASTER SCREEN-2 .................................. ERROR! BOOKMARK NOT DEFINED. OTHER MASTER DATA ............................. ERROR! BOOKMARK NOT DEFINED.

REPORTS ............................................................................................................ 16 6.1 6.2

MASTER DATA ................................................................................................. 22 7.1 7.2 7.3

CHANGE REQUEST HISTORY...... ERROR! BOOKMARK NOT DEFINED.

Page 3

System Requirement Specifications

1 Introduction
1.1 Overview A businessmen having 100 hoardings in a city in that he have a number customers throughout the city from different places , now he wants to change those with electronic hoardings for that he need a web portal for his customers to place requests and an administrator software for him. Requirements of Businessmen for Hoarding Web Portal: 1. Total no of hoarding are 100 2. User places his requests through the web portal. 3. The user will be having the facility to select the hoardings in area wise and measurement wise 4. The portal should display the price status of the hoarding based on area wise and measurement wise. 5. The price is variable for different areas 6. It should display the hoarding status with area wise and size wise along with the price 7. The portal should have inbox facility and he need to check the previous placed data (History). 8. If the user reserve any slot through web portal it need to generate acknowledgment message through mail or mobile. 9. Prolong facility will be provided, but user need to follow conditions of Administer. 10. The user should place standard measurements specified by administer. 11. It should have a cancelation facility within 2 days. 12. It should have a multiple ads running features 13. Multiple booking slots and the user should for days only not hours 14. It should have a extend facility(conditions he need to follow)

Requirements of Admin Module 1. The portal should have a login facility 2. It should retract the user requests daily 3. It should have facility for prolong the contract of user ads if the slots are free other he need to place the again 4. It should have the extend facility also 5. It should have the modification facility based on user taste 6. It should have the cancellation facility 7. It should have the refund facility

Page 4

System Requirement Specifications

1.2 Out of scope

1) Due to any calamities if the web is not functioning, in that time booking hoarding

is not possible through web portal 2) The mobile version of digital hoarding is not available 3) The payment is not possible through the foreign operated banks 1.3 Assumptions 1) The user need to have an account with digital hoarding web portal otherwise not pot possible to place a request 2) The payment possible through payment gateway onl y. It doesnt accept the cheques and cash through hands 3) All the user requests are not accepted, inappropriate and unauthorized content only accepted.

Page 5

System Requirement Specifications

2 High level process overview

Process Diagram of Digital Hoarding Phase

Transaction

History of Transaction

end

Search Hoarding

Availability

END

Modify Request

Create Modify Request

User Module

Start

Register

Sign in

Booking Hoarding

Payment Gateway

Confirmation of Request

Alert

End

Cancel Request Extend

refund

End

Yes Availability

Create Extend Request

NO End

Modify User Request Yes start

Administer Module

Login by administer

Receiving User request NO

User Request Feasible

Booking of user request

Processing Team

Output

End

End

Cancel/ delete of user request

Refund

End

Extend

Create Extend Request

Page 6

System Requirement Specifications

3 Use cases (User Module)

System

Create Request

Modify Request

Cancel Request

Search Hoarding

User Customer Modify

Alerts

Refund

Extend

Page 7

System Requirement Specifications

4 Use cases (Administer Module)

System Create Request

Confirm Request

Modify Request

Cancel Request

Search Hoarding

Create user

User Status

cancel Hoadrding

Administer Create Hoarding

Modify Hoarding

Price Status

Alerts

Refund

Reports

Page 8

System Requirement Specifications

Product features 4.1 Modify the Hoarding Request This feature gives the user a privilege to change requirement of already booking request. By using this feature may save money and it improves the quality of his business 4.1.1 Process for Modification of Hoarding Request

Modify Request Phase

Processing Team

End

Process diagram

Yes start login Create Modify the request Conformation of modification Alert Administer Open User Request Feasibility

No End

. 4.1.2 User interface Navigation: Sign in Master Page Modify Hoarding ModifysubmitAdminister SelectionSend to processing team 1. Sign in

Page 9

System Requirement Specifications

2. Master Page

3. Create Modify Request

4. Administer Modify Request Selection

5. Modify Request
Page 10

System Requirement Specifications

6. Output

4.1.3 Data fields

Field 1. 2. 3. Sign in Master page Create modify request

Field Type

Required (Y/N) Y Y Y Y y

Comments Should have an account Depends on user requirement Need to clarify Modify Request

4. Administer Selection of Modification Requests 5. Open the Request and send to processing Team

Page 11

System Requirement Specifications

4.1.4 Output

The Output will generate a Alert request through the email or phone number

4.1.5 Rules

To modify the request first the user need book the hoarding, otherwise not possible The modification is possible within the two days of booking the hoarding

4.1.6 Alternate Flows If the internet not working, so the user need to book from the administer 4.1.7 Assumptions 1. To book the hoarding he needs to have an account 2. All the user requests are not accepted, inappropriate and unauthorized content only accepted.

4.2 Booking the Hoarding 4.2.1 Process Diagram

Booking Request Phase

Process Diagram

Yes Start Sign in Book Hoarding request Confirm of Hoarding Request Pay Gate Alert Administer Open User Request Feasibility Processing Team End

No End

Page 12

System Requirement Specifications

4.2.2 User interface Navigation: URLSign In page Master PageBooking the HoardingCreate Booking RequestPay GateAdminister SelectionSend to Processing TeamOut put 1. Sign in

2. Master Page

3. Booking the hoarding

4. Payment

Page 13

System Requirement Specifications

5. Administer Selection of Booking Request

6. Administer Selection and send to processing team

7. Output

Page 14

System Requirement Specifications

4.2.3 Data fields

Field 1. 2. 3. Sign in Book hoarding Create Request

Field Required Comments Type (Y/N) y y y y y y User need to have Account User should login Booking is available only on specified areas only

4. Pay Now 5. Administer Selection 6. send to Processing Team 4.2.4 Output

After booking the Hoarding it will generate a alert through the email or mobile about the confirmation.

4.2.5 Rules

There is no rules for booking the hoarding

4.2.6 Suggested work flow

Add the work flow existing in the system

4.2.7 Alternate Flows If the internet not working, so the user need to book from the administer 4.2.8 Assumptions
If the user wants to book the hoarding he need to select from the specified areas only.
Page 15

System Requirement Specifications

4.3 Cancel the Hoarding Suppose if the user wants to cancel the hoarding, he need to follow the following flow First of all he should book the hoarding Cancellation is possible with the two days booking the hoarding 4.3.1 Process Diagram for cancellation
Cancel Request
Phase

Refund

End

Process Diagram

Start

Sign in

Create Cancel Request

Confirm Cancel Request

Administer Selection of Cancel Request

If the Request Meets Condition

End

4.3.2 User interface Navigation: Sign inMaster Page Create Cancel Request Administer Selection of Cancel Request 1. Sign in

2. Master Page

Page 16

System Requirement Specifications

3. Cancellation Request

4.4 Extend 4.4.1 Process for Extend 4.4.2 User interface Navigation: Sign in Master Page Extend AvailabilityCreate Extend RequestPay GateAdminister Selection and Send to processing teamOutput Prototypes: 1. Sign in

2. Master Page

3. Availability Status
Page 17

System Requirement Specifications

[In this case the user checks for availability of the Hoarding as he booked previously, if it is free he send a request to administer and then administer sends to the processing team.]

4. Create Extend Request Here the user sends a create extend request to administer

5. Pay Gate

Page 18

System Requirement Specifications

6. Administer Selection of Extend Request Here administer open the user request and checks whether it meet the conditions and he send to the processing team.

7. Output

4.4.3 Data fields

Field 1. Sign in

Field Type

Require d (Y/N) Y

Comments

Page 19

System Requirement Specifications

Field 2. Extend 3. Availability 4. Extend Request 5. Pay Gate 6. Admin selection 7. Out Put

Field Type

Require d (Y/N) Y Y Y Y Y Y

Comments

4.4.4 Suggested work flow

User need follow the user interface

4.4.5 Alternate Flows

If the internet is not working, so the user can directly place the request from administer

4.4.6 Assumptions

To extend the contract first the user need to book the hoarding prior to extend

4.5 Transaction History

This feature gives all the previous transactions of the user, its like a draft. 4.5.1 Process Diagram

Page 20

System Requirement Specifications

Transaction History
Phase

Process Diagram

start

Login

Transaction History

User Tansactions

end

4.5.2 User interface

Navigation: Sign in Master Page Transaction 1. Sign in

History

2. Master Page

3. Transaction History

Page 21

System Requirement Specifications 4.5.3 Data fields

Field 1. Sign in 2. Master Page 3. Transaction History Field Type Required (Y/N) N N N Comments

4.5.4 Assumptions
The transactions will be available only, if the user had done any transactions

4.6 Search Hoarding

This feature makes the user easy to search hoarding in his desire areas and also shows the availability of Hoarding. 4.6.1 Process Diagram
Title
Phase

Function

Start

Sign in

Search Hoarding

Selection of Hoarding

End

4.6.2 User Interface Sign in Master PageSearch HoardingSelection of Hoarding

1. Sign in

Page 22

System Requirement Specifications

2. Master Page

3. Search Hoarding

4.6.3 Data fields

Field 1. Sign in 2. Master Page 3. Search Hoarding Field Type Required (Y/N) N N N Comments

4.6.4 Suggested work flow It will be like user interface

Page 23

System Requirement Specifications

5 Master data
5.1 User Master Screen 1
User master screen1 used for Login as well as Registration.

5.1.

User Interface

For registration If the User wants to sign up or Register he needs to choose Register now

5.2 User Master Screen 2 User master screen2 is used by the User, it has different features
Page 24

System Requirement Specifications

1. Booking hoarding: It is used for creating a hoarding request 2. Cancel Hoarding: it is used for cancellation of previously booked hoarding request 3. Extend: if the user wants to continue the contracts, so he need to follow steps via extend 4. Modification: if the user needs to change or modify the existing request he need to follow the modification request feature 5. Search Hoarding: This feature gives the user to search hoarding availability in different areas 6. Transaction History: this feature gives the user to verify the previous booking transactions. 5.2.1 User interface

5.2.2 Data Fields Field Book hoarding Modify hoarding Cancel hoarding Extend Transaction History Search Hoarding Field Type Require d (Y/N) y y y y Y N Comments

5.2.3 Output

Output will generate acknowledgment from the administer about user requests

Page 25

System Requirement Specifications

5.2.4 Alternate Flows Mobile application is not available, may be in the next version it may be released If the internet is not worked in that time the user need to consult the administer

Page 26

System Requirement Specifications

Page 27