RERA: Update Quarter Wise Project Progress

System Requirement
Specifications

Submitted By: Submitted to:

MAP_IT, Bhopal RERA

Govt. of MP

0|Page
System Requirement Specifications

DOCUMENT CONTROL

Document Publication History

Date Description of changes Version Author

Reviewers

Date Version Reviewer Remarks

Distribution

Date Version Name Location

Abbrevations and Definitions Page 1

System Requirement Specifications

Table of Contents
RERA: Update Quarter Wise Project Progress................................................................................................. 0

Abbrevations and Definitions .............................................................................................................................. 5

1 Introduction ................................................................................................................................................. 6

1.1 Purpose ................................................................................................................................................ 6

2 Overall Description ...................................................................................................................................... 7

2.1 Application Perspective ....................................................................................................................... 7

2.1.1 System Interfaces ........................................................................................................................ 7

2.1.2 User Interfaces ............................................................................................................................ 7

2.1.3 Software interfaces ..................................................................................................................... 7

2.2 User Characteristic .............................................................................................................................. 8

2.3 Constraints........................................................................................................................................... 8

2.4 Assumption & Dependency ................................................................................................................. 8

3 Update Quarter Wise Project Details .......................................................................................................... 9

3.1 Process Description ............................................................................................................................. 9

3.2 To be Implement ............................................................................................................................... 10

3.3 Use Case: Update Quarter wise Project Progress ............................................................................. 10

3.3.1 Pre – Condition .......................................................................................................................... 10

3.3.2 Activity Work flow ..................................................................................................................... 11

3.3.3 Post – Condition ........................................................................................................................ 11

3.3.4 Interface Requirement: Quarter List ......................................................................................... 11

3.3.5 Interface Requirement: Update Project Progress ..................................................................... 12

3.3.6 Interface Requirement: View Project Progress ......................................................................... 12

3.4 Use Case: Revise Quarter wise Project Progress ............................................................................... 12

3.4.1 Pre – Condition .......................................................................................................................... 12

3.4.2 Activity Work flow ..................................................................................................................... 12

3.4.3 Post – Condition ........................................................................................................................ 13

Abbrevations and Definitions Page 2

System Requirement Specifications

3.4.4 Interface Requirement: Quarter List ......................................................................................... 13

3.4.5 Interface Requirement: Revise Project Progress ....................................................................... 13

3.4.6 Interface Requirement: View Project Progress ......................................................................... 13

4 Unlock Quarter. ......................................................................................................................................... 14

4.1 Process Description ........................................................................................................................... 14

4.2 To be Implement ............................................................................................................................... 14

4.3 Use case: Initiate Request ................................................................................................................. 15

4.3.1 Pre – Condition .......................................................................................................................... 15

4.3.2 Activity workflow ....................................................................................................................... 15

4.3.3 Post Condition ........................................................................................................................... 15

4.3.4 Interface Requirement: Quarter List ......................................................................................... 15

4.3.5 Interface Requirement: Initiate List .......................................................................................... 15

4.4 Use case: Process Request ................................................................................................................ 16

4.4.1 Pre – Condition .......................................................................................................................... 16

4.4.2 Activity Work flow ..................................................................................................................... 16

4.4.3 Post – condition ......................................................................................................................... 16

4.4.4 Interface Requirement: Request List ......................................................................................... 16

4.4.5 Interface Requirement: Unlock Quarter. .................................................................................. 16

4.5 Use Case: Update Project Progress ................................................................................................... 16

4.5.1 Pre- condition ............................................................................................................................ 16

4.5.2 Activity Work flow ..................................................................................................................... 16

4.5.3 Post – condition ......................................................................................................................... 17

4.5.4 Interface requirement: Quarter List .......................................................................................... 17

4.5.5 Interface requirement: Update Project Progress ...................................................................... 17

5 Penalty Deposit and Reconciliation. .......................................................................................................... 18

5.1 Process Description ........................................................................................................................... 18

5.2 To be Implement ............................................................................................................................... 18

Abbrevations and Definitions Page 3

System Requirement Specifications

5.3 Use Case: Deposit Penalty ................................................................................................................. 18

5.3.1 Pre – Condition .......................................................................................................................... 19

5.3.2 Activity Work Flow..................................................................................................................... 19

5.3.3 Post – Condition ........................................................................................................................ 19

5.3.4 Interface Requirement: Penalty Deposit List............................................................................. 19

5.3.5 Interface Requirement: Penalty Deposit ................................................................................... 19

5.4 Use Case: Reconcile Deposit Penalty................................................................................................. 19

5.4.1 Pre – Condition .......................................................................................................................... 19

5.4.2 Activity Work Flow..................................................................................................................... 19

5.4.3 Post – Condition ........................................................................................................................ 20

5.4.4 Interface Requirement: Penalty Deposit List............................................................................. 20

5.4.5 Interface Requirement: Reconcile Penalty Deposit .................................................................. 20

Abbrevations and Definitions Page 4

System Requirement Specifications

Abbrevations and Definitions

Abbrevations and Definitions Page 5

System Requirement Specifications

1 Introduction
1.1 Purpose
The broad purpose of this SRS Document is to set out our approach for the execution of the ERP project.
Included in the document is the articulation of the overall requirements related to proposed methodology.
SRS acts as a blueprint of the project.

The purpose of this SRS document is to provide a detailed overview of our software product, its parameters
and goals. This document describes the project's target audience and its user interface, hardware and software
requirements. It defines how our client, team and audience see the product and its functionality. Nonetheless,
it helps any designer and developer to assist in software delivery lifecycle (SDLC) processes.

It is important for the contents of the SRS document to be understood and agreed by RERA Authority. Inputs
from RERA Authority and MAP_IT (the stakeholders) are vital for the further development, as the leadership
of RERA Authority must validate proposed tasks in order to be activated. In order to be accurate and
accomplish the proposed work, it will be important for personnel from RERA Authority and other stakeholders
to cooperate to complete the necessary task.

Introduction Page 6
System Requirement Specifications

2 Overall Description
2.1 Application Perspective
This application will be primarily used by Promoters and IT Official of RERA.

2.1.1 System Interfaces

A web-based system is envisaged and hosting of this system will depend on the decision by RERA. The
application shall be accessed over the Internet and the authorized officials of the RERA shall make the data
entry of the relevant modules and sub-modules.

2.1.2 User Interfaces

 The user interface to all modules that deal with databases will be one adhering to standard Windows
compatible applications design guidelines.
 All the screens for the modules will have the similar look and feel so that retraining of user will not be
required when shifting from one module to another.
 The exact screen designs will be finalized after consulting with the concerned users.

2.1.3 Software interfaces

This is the software needed to provide the basic interface between the users and the hardware/software parts
of the system. It is further divided as

2.1.3.1 Operating system software

This will be the Network Operating System required to manage the network and provide basic services to
client PCs.

2.1.3.2 Application development software

This will be set of tools using which the systems will be developed and deployed. These will act as a set of
connectors between the Operating System Software and the requirements.

2.1.3.3 Memory constraints

The memory configuration for servers as well as client machines should be as sufficient as to efficiently run
the application software system.

2.1.3.4 Operations

a) Mode of Operation:
System operations can be subdivided into following 3 categories.
1. Manual Operation: Acceptance of data in hard copy format.
2. Automated Operations: Data entry of forms can be done using Form Processing Technology. The
various operations in Form processing will be building database after validations and processing for
future references and use in other modules and reports.

Overall Description Page 7

System Requirement Specifications

3. Workflow Automation: As the application will be a web-based application, instead of physically

sending the document/report to the HQ, the data will be accessible from any location to authorized
users. Also the document/report can be electronically sent (email) in prescribed hierarchy.

b) Period of interactive operations and unattended operations:

 The details of all the masters shall be entered only once by an authorized user.
 The data to be captured for other functions shall be added/updated timely

2.2 User Characteristic

User of application are characterized as follows:

 IT Admin/ Promoter: A moderate level of computer literacy and would be using the application mainly
from the office.

2.3 Constraints

 Changes in basic way of functionality, changes in rules at client side may affect system design options.
 The reliability of requirement collected from RERA shall depend on the information/ details provided
by RERA officials. The non-reliable information shall affect the software design and development
option.
 The system shall provide security on the basis of organization structure of RERA. Only the specified
users shall be able to read, write or update the data. It is proposed that the system shall provide logins
and password for a user to log into the system. An access to viewing and printing of some reports/
data shall be different for different users. The system will abide the security related aspects that will
be governed by RERA Policies.

2.4 Assumption & Dependency

 It is assumed that users are well versed in using web applications.

 It is assumed that internet connectivity is available.
 It is assumed that departmental users are well versed in using mobile and web applications.
 User will input required, valid and authentic data into the system.
 System will validate identified user inputs. However, factual inputs cannot be validated by system for
which, the user will be needed to enter valid data.
 System will be designed, assuming that, required system software, middleware and connectivity
hardware resource are available in working condition with organization.

Overall Description Page 8

System Requirement Specifications

3 Update Quarter Wise Project Details

3.1 Process Description

Process Map : Update Quarter Wise Project Details

List of all applicable quarters gets

Open application and navigate to Select Quarter from list to perform
display to him along with delay and
Quarter updates action.
penalty, if applicable.

Quarter update Delay due to Delay more than

Quarter Details

Timelines Dpptt Approval 90 days

Not Submitted yet Delayed No Yes

Already
Submitted Yes No
Within time
Previous calculated
View Quarter updates Enter Quarter updates
Unlock Quarter
Enter Quarter updates Process
Penalty

System does not allow Not without penalty

Promoter

to enter updates. Paid

updates
Revise

No
Paid
Yes Submit Quarter updates Submit Quarter updates
Quarter Update
Time Expired

Enter Quarter updates .

No Revise Quarter Updates

Yes
Submit Quarter updates B

Revise quarter updates B

A

No
Submit updates
Yes

A
Unsuccessful Successful
Data Submit
System

Calculate and Display

Display an error Message Display a notification
penalty.
B

1. Promoter shall login into application using his/ her project Specific credentials and navigate to
Quarter wise Project Progress Link. A list of all applicable quarters gets display to him. System shall
also display the quarter wise delay period. System shall also display imposed penalties over quarter,
if applicable, along with their reconciliation status. Promoter shall either Submit Quarter updates,
View Quarter updates and revise Quarter updates.
2. To Submit Quarter Updates,
a. This feature shall be applicable, only in case, quarter updates are not submitted.
b. Promoter shall select Quarter from list to submit quarter details.
c. System shall check quarter update timelines.
d. In Case, Quarter update timeline is not expired, System shall check whether previously
imposed penalties, if any, is paid or not.
i. In case, all imposed penalties are not paid, then System shall not allow promoter to
update project progress details.
ii. In case, all imposed penalties are paid and reconciled, then system shall allow
promoter to update project details. A page shall open, in which, promoter shall enter
project updates. Once project updates are entered, he/she shall submit project
updates.

Update Quarter Wise Project Details Page 9

System Requirement Specifications

iii. On Successful Submit, system shall display a notification for successful save. On
unsuccessful submit, system shall display an error message.
e. In case, Quarter update timeline is expired, System shall check whether delay is happed due to
departmental approval or not.
i. In case, delay of selected quarter is due to departmental approval, then system shall
allow promoter to update project progress details and do not impose any penalty on
submission of quarter update.
ii. In case, delay of selected quarter is not due to departmental approval, then system
shall check whether delay is more than 90 days or less than 90 days.
iii. In case delay in less than 90 days, system shall allow promoter to update project
progress details and impose penalty as per rule on submission of quarter update.
System shall confirm before imposing penalty. On Successful Submit, system shall
display a notification for successful save. On unsuccessful submit, system shall display
an error message
iv. In case delay in more than 90 days, System shall lock quarter and promoter shall
initiate request to unlock quarters.
3. To Revise Quarter Updates
a. This feature shall be applicable, only in case, quarter updates are submitted.
b. Promoter shall select Quarter from list to revise quarter details.
c. System shall check quarter update timelines.
d. In Case, Quarter is not revised once,
i. In case, Quarter update timeline is not expired, system shall allow promoter to update
revise quarter details and system shall not impose any penalty.
ii. In case Quarter update timeline is expired, System shall allow promoter to update
revise quarter details and impose penalty as per rule. System shall confirm before
imposing penalty. On Successful Submit, system shall display a notification for
successful save. On unsuccessful submit, system shall display an error message.
e. In case Quarter is revised, then system shall not allow to revise quarter updates.
4. To View Quarter Updater, Promoter shall select quarter from list and view project progress of
quarter.

3.2 To be Implement

“Update Quarter wise project progress” Implementation

Stake Holder Use Case Main Goal & Key Activities
Update Quarter wise View List of Quarters, enter Project Progress, Submit
Promoter
Project Progress Quarter update
Revise Quarter
Promoter View List of quarters, Revise Project Progress
Update

3.3 Use Case: Update Quarter wise Project Progress

The objective of this use case is to submit the progress of ongoing project for a quarter to RERA. CA certificate
and Engineer certificates for project progress shall also be enclosed. Primary stakeholder of this use case is
“Promoter”.

3.3.1 Pre – Condition

 Project shall be registered and approved with RERA.

Update Quarter Wise Project Details Page 10

System Requirement Specifications

3.3.2 Activity Work flow

 Promoter shall login into application using his/ her project Specific credentials and navigate to Quarter
wise Project Progress Link. A list of all applicable quarters gets display to him. System shall also display
the quarter wise delay period. System shall also display imposed penalties over quarter, if applicable,
along with their reconciliation status.
 Promoter shall select Quarter from list to submit quarter details.
 System shall check quarter update timelines.
 In Case, Quarter update timeline is not expired, System shall check whether previously imposed
penalties, if any, is paid or not.
o In case, all imposed penalties are not paid, then System shall not allow promoter to update
project progress details.
o In case, all imposed penalties are paid and reconciled, then system shall allow promoter to
update project details. A page shall open, in which, promoter shall enter project updates. Once
project updates are entered, he/she shall submit project updates.
o On Successful Submit, system shall display a notification for successful save. On unsuccessful
submit, system shall display an error message.
 In case, Quarter update timeline is expired, System shall check whether delay is happed due to
departmental approval or not.
o In case, delay of selected quarter is due to departmental approval, then system shall allow
promoter to update project progress details and do not impose any penalty on submission of
quarter update.
o In case, delay of selected quarter is not due to departmental approval, then system shall check
whether delay is more than 90 days or less than 90 days.
 In case delay in less than 90 days, system shall allow promoter to update project
progress details and impose penalty as per rule on submission of quarter update.
System shall confirm before imposing penalty. On Successful Submit, system shall
display a notification for successful save. On unsuccessful submit, system shall display
an error message
 In case delay in more than 90 days, System shall lock quarter and promoter shall
initiate request to unlock quarters.

3.3.3 Post – Condition

 Quarter wise project progress will be updated.

 System shall impose penalty due to delay in quarter update.

3.3.4 Interface Requirement: Quarter List

 System shall provide the facility to view list of applicable quarters for project.
 System shall validate that quarters shall be applicable from date of application submission.
 System shall validate that quarters shall be display in list only when project is approved from RERA.
 System shall provide the facility to update quarter wise project progress.
 System shall provide the facility to revise project progress of a quarter.
 System shall provide the facility to initiate unlock quarter request.
 System shall provide the facility to view submitted project progress details under a quarter.
 System shall provide the facility to display whether quarter is open or close.
 System shall validate that quarter shall be closed after defined period. (Time lines to open Quarter as
is follow:
o January to March: 01 April to 31 May
o April to June: 01 July to 31 July

Update Quarter Wise Project Details Page 11

System Requirement Specifications

o July to September: 01 October to 31 October

o October to December: 01 January to 31 January).
 System shall provide the facility to display delay in quarter.
 System shall provide the facility to view status of quarter update.
 System shall provide the facility to display quarter wise penalty, if imposed.
 System shall provide the facility to display status of Penalty (Paid/ not paid/ under reconciliation).
 System shall not allow to enter quarter update, in case delay is more than 90 days.

3.3.5 Interface Requirement: Update Project Progress

 System shall provide the facility to enter project progress of quarter.

 System shall provide the facility to submit the project progress.
 System shall take confirmation before impose penalty.
 System shall have imposed penalty as per rule, if applicable, on confirmation of user.
 System shall validate that penalty shall be calculated from next day of quarter closing.
 System shall not update project progress, in case user not confirm the penalty impose.
 System shall generate a notification on successful submit.
 System shall generate an error message on unsuccessful submit.
 System shall not impose penalty due to delay in case, Project approval date is greater than quarter
closing date as well as delayed quarter is just one previous than current open quarter.

3.3.6 Interface Requirement: View Project Progress

 System shall provide the facility to view project progress of quarter.

3.4 Use Case: Revise Quarter wise Project Progress

The objective of this use case is to revise the submitted progress of ongoing project for a quarter to RERA. CA
certificate and Engineer certificates for project progress shall also be enclosed. Primary stakeholder of this use
case is “Promoter”.

3.4.1 Pre – Condition

 Quarter wise project progress would have submitted for quarter.

3.4.2 Activity Work flow

 Promoter shall login into application using his/ her project Specific credentials and navigate to Quarter
wise Project Progress Link.
 A list of all applicable quarters gets display to him.
 System shall also display the quarter wise delay period. System shall also display imposed penalties
over quarter, if applicable, along with their reconciliation status.
 Promoter shall select Quarter from list to revise quarter details.
 System shall check quarter update timelines.
 In Case, Quarter is not revised once,
o In case, Quarter update timeline is not expired,
 System shall allow promoter to update revise quarter details
 System shall not impose any penalty.
o In case Quarter update timeline is expired,
 System shall allow promoter to update revise quarter details
 System shall impose penalty as per rule.

Update Quarter Wise Project Details Page 12

System Requirement Specifications

 System shall confirm before imposing penalty.

 On Successful Submit, system shall display a notification for successful save.
 On unsuccessful submit, system shall display an error message.
 In case Quarter is revised, then system shall not allow to revise quarter updates.

3.4.3 Post – Condition

 Quarter wise project progress will be revised.

 System shall impose penalty due to quarter revision.

3.4.4 Interface Requirement: Quarter List

 System shall provide the facility to view list of applicable quarters for project.
 System shall validate that quarters shall be applicable from date of application submission.
 System shall validate that quarters shall be display in list only when project is approved from RERA.
 System shall provide the facility to update quarter wise project progress.
 System shall provide the facility to revise project progress of a quarter.
 System shall provide the facility to initiate unlock quarter request.
 System shall provide the facility to view submitted project progress details under a quarter.
 System shall provide the facility to display whether quarter is open or close.
 System shall provide the facility to display delay in quarter.
 System shall provide the facility to view status of quarter update.
 System shall provide the facility to display quarter wise penalty, if imposed.
 System shall provide the facility to display status of Penalty (Paid/ not paid/ under reconciliation).

3.4.5 Interface Requirement: Revise Project Progress

 System shall provide the facility to view submitted project progress of quarter.
 System shall provide the facility to update the project progress.
 System shall validate that quarter details are revised only once for a quarter.
 System shall take confirmation before impose penalty.
 System shall have imposed penalty as per rule, if applicable, on confirmation of user.
 System shall not update project progress, in case user not confirm the penalty impose.
 System shall generate a notification on successful submit.
 System shall generate an error message on unsuccessful submit.

3.4.6 Interface Requirement: View Project Progress

 System shall provide the facility to view project progress of quarter.

Update Quarter Wise Project Details Page 13

System Requirement Specifications

4 Unlock Quarter.

4.1 Process Description

Process Map : Unlock Quarter

Promoter

List of all applicable quarters gets

Open application and navigate to Select Quarter and Request for
display to him along with delay and
Quarter updates Unlock Qaurter.
penalty, if applicable.
Controller
Finance

Impose Penalty and Period to update

View Request details.
Quarter details.
Check Period
Validity

Revoke Penalty from Quarter and

Expired
Close Quarter to update.
System

Available

Open Quarter and allow Promoter to

Impose Penalty on Prommoter.
update Quarter details.
Promoter

Submit Quarter Update Details.

1. Promoter shall login into application using project specific credentials and navigate to Quarter wise
Project Progress Link. A list of all applicable quarters gets display to him. System shall also display
the quarter wise delay period. System shall also display imposed penalties over quarter, if applicable,
along with their reconciliation status. Promoter shall Initiate Quarter Unlock Request.
2. To Initiate Request, Promoter shall click on Initiate unlock request. A page shall open in which
promoter shall enter his remarks. Once remarks are entered, promoter shall submit remarks. On
successful submit, system shall display a notification for successful initiation. On unsuccessful
submit, system shall display an error message.
3. Once request is initiated, Finance Controller shall view the initiated requests. He/ she select the
request to view request details. He/ She shall impose penalty and period validity.
4. Once details are entered, Finance Controller shall submit details. On successful submit, system shall
display a notification. On unsuccessful submit, system shall display an error message. On successful
submission, system shall send a notification to promoter.
5. System shall check whether period validity is expired or not. In case, period validity is expired, System
shall revoke penalty from quarter and close quarter for update.
6. In case period validity is not expired, system shall allow promoter to update quarter details and
impose penalty on quarter.

4.2 To be Implement

“Unlock Quarter” Implementation

Stake Holder Use Case Main Goal & Key Activities
Promoter Initiate Request Select Quarter, Initiate request to unlock quarter
View Initiated request, View Request Details, Impose
Finance Controller Process Request
penalty, Enter quarter open duration.

Unlock Quarter. Page 14

System Requirement Specifications

Update Project Enter project Progress during quarter, submit project

Promoter
Progress progress

4.3 Use case: Initiate Request

The objective of this use case is to initiate the request to unlock the quarter. Those Quarter are locked for
update project progress, in which delay is more than 90 days from quarter closing date. Primary stakeholder
for this use case is “Promoter”.

4.3.1 Pre – Condition

 Quarter progress is not updated and delay is more than 90 days.

 Quarter is not delayed due to departmental approval.

4.3.2 Activity workflow

 Promoter shall login into application using project specific credentials and navigate to Quarter wise
Project Progress Link.
 A list of all applicable quarters gets display to him.
 System shall also display the quarter wise delay period.
 System shall also display imposed penalties over quarter, if applicable, along with their reconciliation
status.
 Promoter shall Initiate Quarter Unlock Request.
 To Initiate Request, Promoter shall click on Initiate unlock request.
 A page shall open in which promoter shall enter his remarks.
 Once remarks are entered, promoter shall submit remarks.
 On successful submission, system shall display a notification for successful initiation.
 On unsuccessful submission, system shall display an error message.

4.3.3 Post Condition

 System shall generate a unique request id.

4.3.4 Interface Requirement: Quarter List

 Please refer section 3.4.4

4.3.5 Interface Requirement: Initiate List

 System shall provide the facility to initiate request for unlock quarter.
 System shall provide the facility to enter remarks.
 System shall validate that request shall be initiated only for those quarters, which are delayed more
than 90 days as well as this delay is not due to departmental approval.
 System shall provide the facility to submit request.
 On successful submission, system shall generate a notification.
 On unsuccessful submission, system shall generate an error message.
 On successful submission, system shall generate a unique request number.

Unlock Quarter. Page 15

System Requirement Specifications

4.4 Use case: Process Request

The objective is this use case is to open the locked quarter based on request to update project progress. The
primary stakeholder for this use-case is “Finance Controller”.

4.4.1 Pre – Condition

 Request would be initiated to unlock quarter.

4.4.2 Activity Work flow

 Finance Controller shall view the initiated requests.

 He/ she select the request to view request details.
 He/ She shall impose penalty and period validity.
 Once details are entered, Finance Controller shall submit details.
 On successful submission, system shall display a notification.
 On unsuccessful submission, system shall display an error message.
 On successful submission, system shall send a notification to promoter.

4.4.3 Post – condition

 Locked quarter shall open to update project progress.

4.4.4 Interface Requirement: Request List

 System shall provide the facility to view list of initiated requests.

 System shall provide the facility to view request details.
 System shall provide the facility to unlock quarter.

4.4.5 Interface Requirement: Unlock Quarter.

 System shall provide the facility to enter penalty to open quarter.

 System shall provide the facility to enter quarter unlock period.
 System shall provide the facility to unlock quarter.
 System shall generate a notification on successful unlock.
 System shall generate an error message on unsuccessful unlock.
 System shall send notification to promoter on successful unlock.

4.5 Use Case: Update Project Progress

The objective of this use-case is to update project progress for unlocked quarter. The primary stakeholder for
this use-case is “Promoter”.

4.5.1 Pre- condition

 Quarter shall be unlocked.

4.5.2 Activity Work flow

 System shall check whether period validity is expired or not.

 In case period validity is not expired, system shall allow promoter to update quarter details and impose
penalty on quarter.

Unlock Quarter. Page 16

System Requirement Specifications

 In case, period validity is expired, System shall revoke penalty from quarter and close quarter for
update

4.5.3 Post – condition

 Project progress shall be updated.

 Penalty shall be imposed.

4.5.4 Interface requirement: Quarter List

 Please refer section 3.4.4

4.5.5 Interface requirement: Update Project Progress

 System shall provide the facility to enter project progress of quarter.

 System shall provide the facility to submit the project progress.
 System shall take confirmation before impose penalty.
 System shall not allow user update project progress, in case quarter unlock period expire.
 System shall not update project progress, in case user not confirm the penalty impose.
 System shall generate a notification on successful submit.
 System shall generate an error message on unsuccessful submit.

Unlock Quarter. Page 17

System Requirement Specifications

5 Penalty Deposit and Reconciliation.

5.1 Process Description

Process Map : Penalty Deposit and Reconciliation

Deposit Penalty

Open application and List of Deposited Submit Deposit

New Enter Deposit Details.
navigate to Penalty Details. Penalties get displayed. Details.
Promoter

View

Select and View Deposit

Details.
Controller
Finance

Reconcile and Mark Status

of Deposit Details.
System

Update Penalty Status

1. Promoter shall open application using project specific credentials and navigate to Penalty. A list of
deposited penalties gets displayed to him. Promoter shall either view deposit details and deposit
new penalty.
2. To deposit new penalty, Promoter shall click on deposit button. A page shall open in which promoter
shall enter deposit penalty details. Once details are entered, promoter shall submit deposit details.
On successful submission, system shall generate a notification. On unsuccessful submission, system
shall generate an error message.
3. To view Deposit penalty, Promoter shall select deposit details from list. Deposit penalty details get
display to him. He/ she shall view details.
4. Once deposit detail is submitted, it shall display to Finance Controller. Finance Controller shall view
deposit details. He/ She check from bank statement and mark reconciliation status on deposit.
5. In case, Deposit is reconciled, System shall change status of penalty and allow promoter to update
open quarter details.
6. In case, deposit is not reconciled, System shall not allow to promoter to update open quarter details.

5.2 To be Implement

“Penalty Deposit and Reconciliation” Implementation

Stake Holder Use Case Main Goal & Key Activities
Enter Penalty Deposit Details, Map Delayed Quarter,
Promoter Deposit Penalty
Submit Deposit Details.
Reconcile Deposit
Finance Controller View Deposit Details, Reconcile Deposit details.
Penalty

5.3 Use Case: Deposit Penalty

The objective of this use case is to give intimation of penalty deposits to RERA for delayed quarter. The primary
stakeholder for this use case is “Promoter”.

Penalty Deposit and Reconciliation. Page 18

System Requirement Specifications

5.3.1 Pre – Condition

 Penalty shall be imposed on Quarters due to delay.

5.3.2 Activity Work Flow

 Promoter shall open application using project specific credentials and navigate to Penalty.
 A list of deposited penalties gets displayed to him.
 To deposit new penalty, Promoter shall click on deposit button.
 A page shall open in which promoter shall enter deposit penalty details.
 Once details are entered, promoter shall submit deposit details.
 On successful submission, system shall generate a notification.
 On unsuccessful submission, system shall generate an error message.
 To view Deposit penalty, Promoter shall select deposit details from list. Deposit penalty details get
display to him. He/ she shall view details.

5.3.3 Post – Condition

 Penalty Deposit Information shall be send to IT Admin for Penalty deposit reconciliation.

5.3.4 Interface Requirement: Penalty Deposit List

 System shall provide the facility to view list of deposit penalties.

 System shall provide the facility to enter new penalty deposit.
 System shall provide the facility to view penalty deposit details.
 System shall provide the facility to view status of penalty deposit.

5.3.5 Interface Requirement: Penalty Deposit

 System shall provide the facility to enter penalty deposit details.

 System shall provide the facility to map quarters for which penalty is being deposit.
 System shall provide the facility to submit deposit details.
 System shall generate a notification on successful deposit.
 System shall generate an error message on unsuccessful deposit.
 System shall generate a deposit number on successful submission.

5.4 Use Case: Reconcile Deposit Penalty

The objective of this use case is to reconcile the quarter for which penalty is being paid. The primary
stakeholder for this use case is “Finance Controller”.

5.4.1 Pre – Condition

 Penalty deposit shall be submitted.

5.4.2 Activity Work Flow

 Finance Controller shall view deposit details.

 He/ She check from bank statement and mark reconciliation status on deposit.
 In case, Deposit is reconciled, System shall change status of penalty
 System shall allow promoter to update open quarter details.
 In case, deposit is not reconciled, System shall not allow to promoter to update open quarter details

Penalty Deposit and Reconciliation. Page 19

System Requirement Specifications

5.4.3 Post – Condition

 Delayed Quarter shall be reconciled.

 Status of imposed penalty is changed.
 Promoter shall be allowed to update project progress for recent open quarter.

5.4.4 Interface Requirement: Penalty Deposit List

 System shall provide the facility to view list of deposit penalties.

 System shall provide the facility to view penalty deposit details.
 System shall provide the facility to reconcile penalty deposit.

5.4.5 Interface Requirement: Reconcile Penalty Deposit

 System shall provide the facility to mark status of penalty deposit.

 On successful reconcile, System shall generate a notification.
 On successful reconciliation, Status of imposed penalties is changed.
 On successful reconciliation, Status of delayed quarter is changed.

Penalty Deposit and Reconciliation. Page 20