Study Mate

SIS & LMS IMPLEMENTATION

SM- Business Requirements Document (BRD)

Prepared by: Diksha Tewari

Prepared for: CEON
Date Submitted: [Date]

Project Sponsor: Project Sponsor's Name

Client Acceptor:
Project Manager: Diksha Tewari

Document Number: Studymate IT Implementation /BRD

Security Classification: High
Version: 0.1

Last Updated: January 20, 2013

Creation Date: January 20, 2013
Business Requirements Document Project Name

Revision History
NOTE: The revision history cycle begins once changes or enhancements are requested after
the initial Business Requirements Document has been completed.

Date Version Description Author

Date when BRD 0.1 Initial version. Insert name of RAEM Analyst
started

Date when 1.0 Approved version Business Owner name (date of

Business approval)
Owner/Business Business Liaison name (date of
Liaison and OIT approval)
sign-off
OIT name (date of approval)

Last revised:13/01/2013 Page 2 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Table of Contents

TABLE OF CONTENTS ............................................................................................................................. 3

1. INTRODUCTION............................................................................................................................... 5
1.1. DOCUMENT PURPOSE ................................................................................................................... 5
1.2. INTENDED AUDIENCE ................................................................................................................... 5
1.3. PROJECT BACKGROUND ............................................................................................................... 5
1.4. PURPOSE OF THE BUSINESS REQUIREMENTS ................................................................................ 6
1.5. BUSINESS GOALS/OBJECTIVES TO BE ACHIEVED .......................................................................... 6
1.6. BENEFITS/RATIONALE .................................................................................................................. 7
1.7. STAKEHOLDERS ........................................................................................................................... 8
1.8. DEPENDENCIES ON EXISTING SYSTEMS ......................................................................................... 9
1.9. ASSUMPTIONS .............................................................................................................................. 9
2. REQUIREMENTS SCOPE ..............................................................................................................10
2.1. IN SCOPE .....................................................................................................................................10
2.2. OUT OF SCOPE .............................................................................................................................10
3. FUNCTIONAL REQUIREMENTS .................................................................................................10
3.1. ACTOR PROFILES SPECIFICATION ................................................................................................10
3.2. ESSENTIAL USE CASE DIAGRAM .................................................................................................12
HUMAR RESOURCE MANAGEMENT .................................................................................................28
ACADEMIC PROCESSES ........................................................................................................................34
4. DATA REQUIREMENTS ................................................................................................................37
4.1. DATA RETENTION AND ARCHIVING ............................................................................................38
4.2. FOI/PRIVACY IMPLICATIONS ......................................................................................................38
5. NON-FUNCTIONAL REQUIREMENTS .......................................................................................39
5.1. SECURITY REQUIREMENTS ..........................................................................................................39
5.1.1. Authentication........................................................................................................................40
5.1.2. Authorization and Access Controls........................................................................................41
5.2. AVAILABILITY REQUIREMENTS ...................................................................................................42
5.3. USABILITY REQUIREMENTS.........................................................................................................43
5.4. SYSTEM HELP REQUIREMENTS ....................................................................................................43
5.5. PERFORMANCE REQUIREMENTS ..................................................................................................44
5.6. SCALABILITY REQUIREMENTS .....................................................................................................45
5.6.1. User Scalability .....................................................................................................................45
5.6.2. Application Scalability...........................................................................................................45
6. INTERFACE REQUIREMENTS ....................................................................................................45
6.1. USER INTERFACE REQUIREMENTS ...............................................................................................45
6.2. SYSTEM INTERFACE REQUIREMENTS ..........................................................................................45
7. BUSINESS GLOSSARY ...................................................................................................................46
APPROVAL .................................................................................................................................................48
ANNEXURE 1: ............................................................................................................................................49
ENQUIRY FORM .........................................................................................................................................49

Last revised:13/01/2013 Page 3 of 61

document1
Security Classification: High
Business Requirements Document Project Name

ANNEXURE 2: ............................................................................................................................................49
REGISTRATION FORM .................................................................................................................................49
ANNEXURE 3 .............................................................................................................................................51
RECEIPT.....................................................................................................................................................51
ANNEXURE 4: ............................................................................................................................................51
FEATURES VS BENEFITS ............................................................................................................................51
ANNEXURE 5 .............................................................................................................................................54
OBJECTIONS HANDLING ............................................................................................................................54
ANNEXURE 6 .............................................................................................................................................57
STUDYMATE SALES ENABLER ...................................................................................................................57

Last revised:13/01/2013 Page 4 of 61

document1
Security Classification: High
Business Requirements Document Project Name

1. Introduction

1.1. Document Purpose

The purpose of this document is to describe business requirements of SIS & LMS implementation
completely, accurately and unambiguously in technology-independent manner. All attempts have been
made in using mostly business terminology and business language while describing the requirements in
this document. Very minimal and commonly understood technical terminology is used. Use case
approach is used in modeling the business requirements in this document

1.2. Intended Audience

The main intended audience for this document are the business owners of the proposed system. This
document should be readable by business owners of the proposed system. They must be able to verify
that their business requirements have been documented here completely, accurately and unambiguously.

Data Architects, Application Architects and Technical Architects would also find the information in this
document useful when they need to design a solution that will address these business requirements.

Since the requirements are documented here in Technology-independent manner, the end-users of the
system should be able to comprehend the requirements fairly easily from this document.

1.3. Project Background

As Studymate continues to scale up, we require to move some of the manual processes to automated
processes to drive operational efficiencies. In addition, after a recent competitive and consumer survey,
the adoption of digital learning systems is critical to deriving a competitive edge in the market. The
implementation of IT systems in Studymate is envisaged in two phases; implement SIS system to derive
operational efficiency & manage scaled operations. Implement LMS systems to manage routine learning
tasks like assessment systems, content creation and management and performance analysis. Implement
LMS to facilitate video simulcast across all centers, online classes and customized coaching through
asynchronous classes.Mention here briefly if these business requirements are as a result of any previous
meetings, correspondence, legislations etc.
Last revised:13/01/2013 Page 5 of 61
document1
Security Classification: High
Business Requirements Document Project Name

1.4. Purpose of the Business Requirements

The purpose of the Business Requirements document is to

 List down the key processes in Studymate, work flow of the processes &
enhancements/up gradation required in the processes with implementation of IT
solutions.
 Automating the manual processes by implementation of new software application
development. Understand benefits from such implementation.
 Replacement of the legacy software used for data management, remove use of excels for
recording the data.
 Development of business requirement document as the only source document of
reference for developing the system specification document.

1.5. Business Goals/Objectives to be achieved

This section describes the major goals/objectives to be achieved with the implementation of the Business
Requirements.
o To replace the legacy software system with a much more sophisticated system.
o To provide a platform which will help the business to scale up in future year. The current
system does not have the sophistication or the features that are required to run a large
multi-centre operation.
o To upgrade the current manual processes by automating them for deriving operational
efficiencies. Increase accuracy in process, save time & effort. Gain competitive edge by
digital learning platform. Enhance the availability of information to various stakeholders
&provide data for sensitive analysis & different reports for different processes &
stakeholders. The system will be a control system to avoid any manipulation in data and
minimise human errors.
o To develop a platform for new virtual e-learning products which can be retailed online
once digital content library is also available

Last revised:13/01/2013 Page 6 of 61

document1
Security Classification: High
Business Requirements Document Project Name

1.6. Benefits/Rationale

o By automation of key financial and academic processes, linking of the same with
monitoring tools, will provide opportunity to expand operations without investing in more
administrative manpower
o Will help in cost saving of up to Rs. 2 Lacs per centre due to non-hiring of additional work
force to manage the MIS & operational records
o Will reduce manual effort & mandays, centralised data management, easy in information
flow & availability, sales force optimization& enhance customer reach
o Will provide a much needed Customer Relationship Management (CRM) tool to help the
admission process, record keeping and aid other MIS requirements
o Will provide a direct linkage to the company website for online monitoring of academic
processes & student performance records
o Will provide capability to link the attendance system with advanced monitoring devices
viz. RFID/ Biometric devices
o Will provide a robust communication management platform for marketing/ communicating
messages to current/ prospective students
o Provide opportunities to develop and market virtual e-learning products which can be
retailed online as a new product once virtual content library has been developed by the
company

Last revised:13/01/2013 Page 7 of 61

document1
Security Classification: High
Business Requirements Document Project Name

1.7. Stakeholders

Stakeholders are the individuals or groups who have a vested interest in this project and whose interests
need to be considered throughout the project. This section lists the Stakeholders of the Application /
Project for which these Business requirements are documented.

Acronym Description Role

* Authorize Has ultimate signing authority for any changes to the document
R Responsible Responsible for creating this document
A Accountable for accuracy of this document (e.g. project manager)
S Supports Provides supporting services in the production of this document
C Consulted Provide inputs related to the process
I Informed informed of any changes

Name Position * R A S C I

Anand Ramabhadran 

Anand Aggarwal 

Dhrubajyoti Banik  

Debojit Sen  

Diksha Tewari  

Karishma Seth  

Ishant Juneja  

Sneha Deshmukh  

Last revised:13/01/2013 Page 8 of 61

document1
Security Classification: High
Business Requirements Document Project Name

1.8. Dependencies on existing systems

The software application will be depended on the sale, admission, finance, HR & academic databases
available in the existing software/excels.

o Sales data - Last 3 year & current year student database generated through various
marketing activities, School programs, inbound enquiries, dump database etc. which is
required to be imported in the system for future reference & analysis.
o Enrolment data – current year student enrolment data with completed detail of the
students need to be imported in the system.
o Finance data – Student fee records, complete details of the each & every payment made
by the customer, fee receivable & realised in current year need to be imported in the
system.
o HR data – All the current & old center staff, academic staff & corporate database is
required to be imported in the system.
o Academic data – Course curriculum, academic calendar, timetable schedule, product
description, content availability (print & TAT), testing & assessment (question banks)

1.9. Assumptions

This section describes major assumptions that were made prior to or during the Business Requirements
gathering and documentation.
- The BRD will be the only source of any further documentation or technical development.
- The selected software system will provide holistic IT solution for all the major processes of the
business i.e. manage sales & marketing activities, prospect & customer data, academic data,
content, fee management, HR, operations & communication management.
- Single source of MIS & reporting.
- The system will be SAAS based & therefore provide scalability to the business.

Last revised:13/01/2013 Page 9 of 61

document1
Security Classification: High
Business Requirements Document Project Name

2. Requirements Scope

This section shows what business functionality is in scope and out of scope for Implementation. In Use
case approach, the out of scope Use cases are indicated in a separate boundary box. In Oracle Designer
approach the out of scope Functions are shown in grey coloured boxes.

2.1. In Scope

 Process mapping and System requirement documentation

 Implementation of a Student Information System (SIS)
 Implement the Customer Relationship Management (CRM)
 Fee management system and cash management system at centers
 Implement a Learning Management System (LMS)

2.2. Out of Scope

 AP, AR, JL to be integrated with SAP only

 Content development & authorising

3. Functional Requirements
This section describes the Functional requirements part of the Business Requirements. In Use case
approach, the Functional Requirements comprises of Actor Profile Specification, Essential Use case
charts and Essential Use case specification in narrative text form.

3.1. Actor Profiles Specification

This section describes all the Actors and their profiles within the context of the Business Requirements
being documented. An Actor is a person, organization or an external system/sub-system/program that
has interactions with the Application. Actors, by definition, are external to the system with which they are
having interactions. Actors have goals that are achieved by use cases. Typically, Actors have behaviour
and are represented by the roles they play in the use cases. An Actor stimulates the system by providing
input and/or receiving something of measurable value from the system.

Last revised:13/01/2013 Page 10 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Actor Name Actor Type Access Type needed Comments

Counsellor Stakeholder Create Print Access to update enquiry data,

Primary Actor Read Export student information, print
Supporting Actor Update Others receipts & invoices.
Delete
Center Heads Stakeholder Create Print
Primary Actor Read Export
Supporting Actor Update Others
Delete
Sales, Stakeholder Create Print
Operations & Primary Actor Read Export
Marketing Supporting Actor Update Others
Head Delete
HODS & Stakeholder Create Print
CKO Primary Actor Read Export
Supporting Actor Update Others
Delete
Faculty Stakeholder Create Print
Primary Actor Read Export
Supporting Actor Update Others
Delete
HR Stakeholder Create Print
Primary Actor Read Export
Supporting Actor Update Others
Delete
IT Stakeholder Create Print
administrator Primary Actor Read Export
Supporting Actor Update Others
Delete

Last revised:13/01/2013 Page 11 of 61

document1
Security Classification: High
Business Requirements Document Project Name

3.2. Essential Use Case Diagram

This section is applicable only to Use case approach. This section depicts the Business Requirements in
the form of Essential Use case diagram. In the Use case approach, the Functional Requirements are
decomposed into a number of Essential Use cases. Essential use cases are of primary importance early
in a project’s requirements/analysis phase. Their purpose is to document the business process that the
Application must support without bias to technology and implementation.

Use Case # 1

Use Case Name In bound calling

Description All the calls landing at the center from various sources
such as newspaper ads, word of mouth, referral,
brand ambassador or internet are inbound calls.
These calls are high priority prospect because they
approach the center on their own.

Actors
Counsellor & Center Head

Business Rules - Only approximate fee could be shared for

reference.

Basic Flow Alternate Flows

– For inbound calls coming at the center
the counselor will open the SIS system
& takes the following information after
greeting the caller:

o Name

o Class

o Program interested in

o Subjects interested

o Primary contact number

o Alternate number

o Address

o Source of awareness

Last revised:13/01/2013 Page 12 of 61

document1
Security Classification: High
Business Requirements Document Project Name

– The SIS system should have above

mentioned fields as mandatory along
with the list of fields mentioned in
enquiry form. Refer to annexure

– The counselor fixes up the date & time

on which the customer wills walk-in at
the center. The counselor will record
the probable walk-in date & time in the
system

– Special requests for demo classes are

also recorded & fixed with the customer
at the same type (if applicable). The
Subject demo date & time should also
be recorded in system.

– Basic information regarding course

details, 5 edge points, TAT and state of
the art infrastructure should be shared
over the phone. Other information like
student portal, parent portal, timely
communication & regular update to
parents over student performance
should be shared with the parent. The
software should have the softcopies of
all the sales documents mentioned
above integrated in the system.

– Auto SMS & emails should be sent via

system after each call. Refer to
annexure for SMS templates & E-
brochure. – Karishma to develop

Non-Functional Requirements - When the counsellor enters student detail in the

system the system should suggest if it’s a
duplicate enquiry based on unique information
such as phone number.
- Enquiry form should be generated from the
system.
Pre-Conditions Process - Before taking any calls the counsellor should
make sure that the documents such as sales enabler,
course manual, schedule, FABing (Features vs.
Benefits) document is readily available at the her desk
Course details or Manual, Schedule & Pricing details
for each course should be available in the SIS system
for counsellor.
System – Each counsellor should login in into SIS and
enter the details of student with each call.

Post-Conditions After each call the counsellor has to update the follow
up date & time, remarks & description of call.
Extension Points Extension Condition Extending Use Case

Last revised:13/01/2013 Page 13 of 61

document1
Security Classification: High
Business Requirements Document Project Name

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases
Profiling of the prospect

Use Case #2

Use Case Name Out bound calling – call center

Description In the cold calling process the outsourced agency/call
center calls on the database generated via various
marketing activities. The call center briefs the
prospects about company profile & categorizes the
leads into Hot/warm/cold based on the interest levels
of the prospect.

Actors
Calling Agency

Business Rules

Basic Flow Alternate Flows

- The call center agency will be provided - The call center agency will be provided
the SIS logins created only for call calling spreadsheet in the format compatible
center people. with the SIS system.
- The database would be imported in the - The Information captured in the sheet will be
system in advance & each caller will be imported in the SIS system & centers will be
allotted leads by area to call. allotted the calls based on the next follow up
- Post calling & updating the remarks, date
follow up date and lead classification, - Based on the conversation with the prospect
the lead should be forwarded or the call center categorizes the database in to
transferred to sales rep (counsellors) of hot/warm/cold/dump.
respective center. - Admin will import the leads in SIS & assign
- The centers thereafter will follow up on cases based to a particular center. Criteria of
the cases & put remarks or description allotment will be decided by Sales head.
of call for each case. - The assigned leads should be visible to the
- Number of Hot/Warm/Cold/Dump counsellors for follow up on their login.
cases should be visible as lead - Further follow-ups will be recorded in
dashboard on counsellor & CH login. system.
- System would have the sms/email facility
and the counsellors can select prospective
customer to send the sms post conversation.
Non-Functional Requirements

Pre-Conditions Before cold calling the outsourced agency is provided

Last revised:13/01/2013 Page 14 of 61
document1
Security Classification: High
Business Requirements Document Project Name

proper training & relevant documents such as sales

scripts, company profile, and enquiry sheet to record
additional information of the prospect. (refer to
annexure)
The sheet used will be in the defined format
compatible with the SIS system.
Post-Conditions Complete calling sheet
Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases
Follow ups

Use Case #3

Use Case Name Out bound calling – In house

Description The cold calling on the databases generated through
various marketing activities conducted in the
catchment of the center or inside the center such as
school camps, in center workshops etc.

These are high priority calls done at center other than

the database which is sent to call center.

Actors
Counsellor & Center Head

Business Rules

Basic Flow Alternate Flows

– For out bound calls done at the center
the counselor segregates the database
based on the following criteria:

o Source of database (core

activity from which the data is
generated)

o Class wise & subject wise

o Suitable/available product
offerings

o Location of prospect

– The objective of segregating the

database & bundling the same is to
ensure focused calling.

– The segregated data should be in the

Last revised:13/01/2013 Page 15 of 61

document1
Security Classification: High
Business Requirements Document Project Name

format compatible with the SIS and

could be either imported or manually
entered in the system.

– Data import rights should only be

available with the admin who can allot
the database to a particular center as
and when required. The right to transfer
the authority of allocating the lead to
CH should be available with admin

– There are different sales scripts, feature

vs. benefit notes, objection handling
tools which are used while cold calling.
Refer to annexure. All the scripts &
tools for sales should be stored at one
place in the SIS system.

– Post explaining the company profile,

product offered etc. the counsellor
ensure that the prospect walk-ins at the
center. The key points & notes should
be available on the counsellor’s login in
the system, which helps her during the
sale.

– The counselor fix up the date & time on

which the customer will walk-in at the
center

– Special requests for demo classes are

also recorded & fixed with the customer
at the same type (if applicable)

– Basic information regarding course

details, 5 edge points, TAT and state of
the art infrastructure can be given over
phone

– No information regarding fees structure

to be given to caller under any
circumstances

Non-Functional Requirements

Pre-Conditions Before cold calling the outsourced agency is provided

proper training & relevant documents such as sales
scripts, company profile, and enquiry sheet to record
additional information of the prospect.

Post-Conditions

Extension Points Extension Condition Extending Use Case

Last revised:13/01/2013 Page 16 of 61
document1
Security Classification: High
Business Requirements Document Project Name

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases
Follow ups Lead Management

Use Case #5

Use Case Name Walk-ins

Description Direct walk-ins at the center are either by word of
mouth, referral, Newspaper ads & inserts. These are
high priority leads. These are high priority leads which
are very positive & rate of conversion is high.

Actors
Counsellor & Center Head

Business Rules

Basic Flow Alternate Flows

– The walk-in enquiry is greeted by the
counselor and asked to fill an enquiry
form in which the prospective customer
fills in the basic information. Refer to
annexure for enquiry form.

– The counsellor refers to the enquiry

form for further discussion with the
parent.

– Student profile, performance etc is

discussed with the parent & thereafter
the courses & solutions are offered. The
counsellor makes sure that all the
objection, queries & suggestions are
handled efficiently in order to delight
the customer & push immediate
enrolment.

– The counsellor also takes the prospect

to the center visit & explains teaching
methodology followed at Studymate.

– Sample course material, schedule & fee

structure is thereafter shared with the
parent for reference

– The counsellor has to fill in the enquiry

details in the SIS system. The important
information which is must to be taken
from the prospect has to be mandatory
Last revised:13/01/2013 Page 17 of 61
document1
Security Classification: High
Business Requirements Document Project Name

field in the system.

– There should be a provision of printing

the enquiry form generated by the
system.

Non-Functional Requirements

Pre-Conditions – The Counselor / Center Staff will have to

ensure that the front-office is neat & tidy.
The following materials should always be
readily available at the table:

o Enquiry forms – Display (Refer to

Annexure 1 for a copy of the Enquiry
form)

o Brochures - Display

o Registration form – Display (Refer to

Annexure 2 for a copy of the
Registration form)

o Schedule - Display

o Receipt Book - Not immediate

display (Refer to Annexure 3 for a
copy of the Receipt Book)

o Fees Structures – Not immediate

display

Post-Conditions The walk-ins are the highest priority prospective leads

therefore the counsellor should fix up the date of
enrolment post discussion with the parent & close the
case to the earliest possible. If required arrange quick
meetings with center principal or subject teachers.
The SIS system should sent the appointment details to
the appropriate teacher & reminders for the same.
The Center principal’s login should have all the details
of students who are supposed to meet them or to
other subject teachers.
Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

Last revised:13/01/2013 Page 18 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Use case # 6

Use Case Name Follow Up

Description For the types of enquiries there is a process of follow
up which is based on the follow up script. These
scripts are designed based on the various products
offering, course features, deliverable, customer
requirements & suggest solutions. Refer to annexure
4&5

Actors
Counsellor & Center Head

Business Rules The number of follow ups is restricted to 5. Any case

must be closed by 5th conversations with the
customer. Not responding, switched off, number busy
or not reachable is not considered as a follow up.

Basic Flow Alternate Flows

- The follow up calls is done for all three
type of enquiry – walk in, In bound call,
out bound call.
- There are different scripts & tools for
various types of the follow up.
- The SIS system should have the
provision of entering follow ups for
each lead.
- For each follow fill details like Name of
the person spoken to, description of the
call, next follow up date, probable
admission date, follow up done by.
- The system should have the capability
to send the SMS & emails to the
prospect after the conversation. Details
discussed in communication use case.
- The counsellor & center head login
should clearly reflect the number of
follow ups scheduled for a day on their
respective logins.

Non-Functional Requirements

Pre-Conditions Before starting the follow up the counsellor or center

head should open the profile of the student on the SIS
system for reference.
Any pending information of the prospect should be
recorded during the follow up.

Post-Conditions Post follow up the counsellor has to enter the

description of the follow up, next follow up date or

Last revised:13/01/2013 Page 19 of 61

document1
Security Classification: High
Business Requirements Document Project Name

probable admission date, current status of the lead &

further actions in the SIS system.

Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

Use case # 7

Use Case Name Prospect Profiling

Description Seeking most relevant & important information about
the prospective customer is profiling of the prospect.
This helps in understanding on the very first level the
basic nature of the lead.
The details of the lead help a counsellor in suggesting
the best program/course or solution to the customer.
Actors Counsellor & Center Head
Business Rules
Basic Flow Alternate Flows
- In prospect profiling the information
which is mandatory to take are
o Student Name
o Class
o Stream
o Address
o Parent Name
o Source of awareness
o Course interested in
o Current School
- Other information includes
o Aggregate marks in the last
school exam
o Subject wise marks
o Scholarship status

Non-Functional Requirements

Pre-Conditions
Post-Conditions
Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

Last revised:13/01/2013 Page 20 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Use case # 8

Use Case Name Enquiry classification

Description Based on the level of interest the leads are classified
in to HOT WARM & COLD.
- HOT leads are the most positive cases which
will enrol immediately.
- WARM leads are those which are interested
cases but prefer taking some time to decide.
- COLD leads are cases which have major
issues in Fee, schedule, distance problem,
student performance etc.
Actors
Counsellor & Center Head
Business Rules

Basic Flow Alternate Flows

- The counsellor marks the lead as hot
warm or cold based on the conversation
with the prospect.
- The initial status defines the actions
required on that particular case.
- The initial classification of lead keeps
changing as per the conversation with
the prospect.
- The SIS should therefore have the
feature of marking the lead status in the
system.
Non-Functional Requirements

Pre-Conditions
Post-Conditions
Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

Use case # 8

Use Case Name Enquiry Closure

Description Every enquiry post follow ups either converts in to an
admission or get dump due to various reasons.

Actors
Counsellor & Center Head
Business Rules The counsellor has to enter the admission in the SIS
with the proper details of student. For all dump
Last revised:13/01/2013 Page 21 of 61
document1
Security Classification: High
Business Requirements Document Project Name

enquiries the counsellor has to mention the reason.

Basic Flow Alternate Flows

- In case of student enrolment the
enquiry of that student is closed by
marking it converted in the sales
pipeline. The SIS should have the
capability to mark the enquiry as
converted with the conversion date.
- In case of disinterest of the prospect the
enquiry is dumped with appropriate
reason for marking the enquiry as the
dump.
- The SIS should have the capability to
add the dump reasons in the setup and
the counsellor can pick up the
appropriate reason from the list of
mentioned reasons.
Non-Functional Requirements

Pre-Conditions
Post-Conditions
Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

Use case # 9

Use Case Name Student enrolment

Description The process of admission in a particular course.
Actors Counsellor & center Head

Business Rules .

Basic Flow Alternate Flows

- The prospect shows interest in joining a - The prospect can themselves fill their
particular course & are called at the SM information & fee details i.e cheque
center with following: number, cheque amount & bank in the
o Fee Cheques/DD/CC – Full DP software at the center.
or PDC cheques - Post filling the information the counsellor
o Student Photographs - 3 will cross check the information, confirm the
o School mark sheet admission & provides confirmation letter to
- The counsellor makes sure that all the parent.
documents & payment is received & - The parent has to sign the confirmation
asks the parent to fill the registration letter & submit one copy at the center.
form. The registration form is to gather - The counsellor then gives the students SM
further details of the student & study material, bag & student ID card along
Last revised:13/01/2013 Page 22 of 61
document1
Security Classification: High
Business Requirements Document Project Name

guardian. with the login details of the student & parent

- Post filling the form & collection of portal. She/he also explains the parent how
document & cheques the counsellor & why to use the student/parent portal.
enters the admission in the SIS & - The invoices of the fee paid are given to the
generated the receipt or confirmation parent only after the money has been
letter. realised. The SIS should provide e-
- The parent has to sign the confirmation receipts/invoices on the parent portal of
letter & submit one copy at the center. which they can take a print also
- The counsellor then gives the student
SM study material, bag, academic
calendar, schedule & student id card
along with the login details of the
student & parent portal. She/he also
explains the parent how & why to use
the student/parent portal.
- The invoices of the fee paid are given to
the parent only after the money has
been realised. The SIS should provide e-
receipts/invoices on the parent portal
of which they can take a print also.
Non-Functional Requirements

Pre-Conditions Before enrolment the counsellor should make sure

that they send a SMS to the parent for the time
allotted to them for the enrolment & the important
documents & payment cheque they have to bring in
order to enrol.
Post-Conditions Post admission the counsellor should ask the parent &
student for the appropriate time for a brief training
on the student & parent portal, importance &
relevance of the same by the expert. The appoint of
the parent training should be marked in the student
profile.
Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

Use case # 10

Last revised:13/01/2013 Page 23 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Use Case Name Fee Collection

Description An enrolment is only valid once the fee for that
particular course is received. The Fee collection at SM
is by defined payment options.

Actors Counsellor & Center Head

Business Rules No cash payment is excepted in SM. Payment could

be made only through Cheques/DD/Debit or Credit
cards or NEFT/RTGS

Basic Flow Alternate Flows

- While enrolment the student/parent
has to decide on the payment plan &
then the payment accordingly.
- In case of full down payment or
onetime payment, the parent can pay
the fee either by cheque/DD/CC or also
do NEFT transfer.
- In case of instalment payment option,
the parent can select to do the first
down payment either by cheque/DD or
by credit/debit card. For the remaining
instalments the parent is supposed to
deposit PDC cheques at the center with
the defined date.
- The PDC dates are define in the pricing
sheet. Finance (Ishant will share the
pricing sheet)
- In case of EMI option the parent can do
the payment by credit card and get it
converted in to EMI. This option is
available in the selected bank only.
Finance will provide list of Banks
Non-Functional Requirements

Pre-Conditions
Post-Conditions
Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

Last revised:13/01/2013 Page 24 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Use case # 11

Use Case Name Cheque Management System (DP + PDCs)

Description Post collection of fee the center has to deposit the
cheque/DD in the bank. And send the PDC cheques to
the corporate office. This is a critical process post
student enrolment.

Actors Counsellor & Center Head

Business Rules The cheque/DD has to deposit in the Bank within 3

days of the admission & the PDCs are to be send to
the Corp office every Monday by Courier. The deposit
slip has to be attached with each cheque/DD
deposited in the Bank.

Basic Flow Alternate Flows

- Post entering the cheque/DD details in
the SIS i.e. cheque no., amount, bank
name & cheque date or DD no., DD
bank, DD date, the counsellor has to
make CMS i.e. deposit the cheque in
bank.
- The CMS should happen from the
System and the 2 copies of the deposit
slip should be generated from system.
One copy of bank & one for center
record. The Deposit slip number series
will be provided by finance team which
will be compliant to Bank.
- For the PDC the CMS should happen
from system & 2 copies of deposit slip
should be generated one for center &
other for corporate office.
- The Cheque deposited in the Bank or
CO should automatically get marked as
deposited in the SIS.
- Based on the status of the cheque in
Bank the finance team should have the
right to mark the cheque as cleared or
bounced.
- For all the PDCs the entire cheque
management i.e. depositing the
cheques in Bank & receiving the status
should happen at the finance end.
Finance should deposit the cheque from
system & have deposit slip number for
the same.
- SIS should have the capability to match
the cheque with the cheque number.
Center & bank so that finance can
import the final status in the system

Last revised:13/01/2013 Page 25 of 61

document1
Security Classification: High
Business Requirements Document Project Name

rather than marking each & every

cheque manually in the system.
- The cheque deposit detail report should
be available from the system centrally
to the finance team for bank
reconciliation.
Non-Functional Requirements

Pre-Conditions
Post-Conditions
Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

Use case # 12

Use Case Name Credit /debit card payment

Description The parent can choose to make the fee payment by
either debit card or credit card. In case of credit card
payment the payment option can be both lump sum
and EMI. In case of debit card it has to be lump sum.

Actors Counsellor & Center Head

Business Rules EMI option is available in the selected Banks. Plutus

machine is used for the card swiping.

Basic Flow Alternate Flows

- In case of payment by credit/debit card
the counsellor swipes the card in the
plutous machine & selects whether it’s
a full payment or EMI option.
- The machine automatically converts the
payment into EMI.
- There is a receipt generated from the
system which the parent is require to
sign. One copy of the receipt is kept in
center records and other is given to
parent along with the admission
confirmation letter.
- The card details are then recorded in
the SIS system this includes;
o Credit card/debit card number
– first four & last four digits
o Type of card – Master/Visa
o Bank Name
o Card Holder Number
Last revised:13/01/2013 Page 26 of 61
document1
Security Classification: High
Business Requirements Document Project Name

o Transaction ID – generated
from plutous machine

Non-Functional Requirements

Pre-Conditions The plutous machine should be functional throughout

the day i.e. SM working hours. The counsellor should
check that there is paper roll in the machine & it is
connected to the system.
Post-Conditions The credit card details should be recorded in the SIS
immediately in the student record.
Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

Use case # 13

Use Case Name Online enquiries

Description The enquiries received from SM website, SEM or SEO,
Face book or other social networking sites are online
or internet enquiries.

Actors Marketing POC

Business Rules The enquiry for at any online source should be in sync
with the enquiry form available in the SIS system &
flow directly in the system.

Basic Flow Alternate Flows

- Prospects lands at the online enquiry
page from various sources i.e. website,
Social networking sites, SEM, SEO etc.
- The prospect fills an enquiry form
online. The information should flows
from the online enquiry to the SIS and
reflects on the counsellor login.
- The counsellor than calls that enquiry.
Non-Functional Requirements

Pre-Conditions
Post-Conditions
Extension Points Extension Condition Extending Use Case

Last revised:13/01/2013 Page 27 of 61

document1
Security Classification: High
Business Requirements Document Project Name

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

HUMAR RESOURCE MANAGEMENT

Use case # 1

Use Case Name Organisation Structure

Description The organisation structure of Studymate is divided in
Academic & Non-Academic. The structure defines the
hierarchical arrangement of lines of authority,
communication, rights& duties of an organisation. It
determines how the roles, power & responsibilities
are assigned, controlled & coordinated & how the
information flows between the different levels of
management.
Actors Sneha

Business Rules

Basic Flow Alternate Flows

- The information relate to sales flow
from Sales manager to the Center Head
& then to the counsellors at the
centers.
- The mechanism of approval is also
defined by the level of the organisation
chart i.e. counsellors to CH & then to
the Sales Head.
- However there are certain areas such as
HR & finance where the information has
to go from counsellors to the HR POC or
Finance POC for any special approval
pertaining specifically in these areas.
- In case of academic structure the
information flows from the Chief
knowledge officer to the HODs who
then depart the information to the full
time or Part time teachers.
- In case of approvals the request from
fulltime & part time teachers has to go
to the HODs first & then to CKO.
- The user rights & control in the SIS
system will be defined on the basis of
the organisation structure.
- The MIS reporting structure will also
involve organisation structure.
Refer to Annexure
Non-Functional Requirements
Last revised:13/01/2013 Page 28 of 61
document1
Security Classification: High
Business Requirements Document Project Name

Pre-Conditions
Post-Conditions
Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

Use case # 2

Use Case Name Employee File

Description The employee file is basically the collection of
employee’s personal, academic & professional details.
Actors Sneha

Business Rules

Basic Flow Alternate Flows

- The HR division maintains the employee
file which consists of all the critical &
crucial information of the employee.
- This include personal information –
Name, Contact number, Emergency
contact numbers, Address, Email ID,
Blood group, DOB, Marital status.
- The employee application information
includes – employee designation, role &
responsibilities, work experience, salary
details, education details.
Refer to annexure
- The software system should have all the
fields to maintain the employee file
online.
- The software should have the capability
to upload the softcopy of the employee
qualification certificates, photographs,
resume & other relevant documents.
Non-Functional Requirements

Pre-Conditions Before preparing the employee file the HR makes sure

that all the relevant documents are collected & the
verification is done for the employee.
The software should have a field to record the
verification information.
Post-Conditions
Extension Points Extension Condition Extending Use Case

Last revised:13/01/2013 Page 29 of 61

document1
Security Classification: High
Business Requirements Document Project Name

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

Use case # 3

Use Case Name Employee ID, Attendance & Leave

Description Employee attendance system is managing the staff
attendance & leave records centrally in order to keep
a track on the scheduled working hours of the staff &
staff utilization analysis.
Actors Sneha

Business Rules

Basic Flow Alternate Flows

- Every employee is provided an ID card
which is the attendance card also. The
new software system should generate
the ID cards of all the employee.
- The employee has to swipe the card for
each in & out from the center.
- The current attendance system is of
saviour through which a text file is
exported and used to cross check the
attendance record.
- Other than that the HR also maintains a
excel file for the attendance of the staff.
- The current system is not very accurate
for attendance management.
- The software system should have the
capability for ID card integration, RFID
or Biometrics for attendance
management.
- The login & out time of a center staff
could also be recorded by evaluating
the login & log out from the SIS system.
- All employees apply for leave via email
to their respective reporting heads. All
the records of the same is maintained
by the HR division.
- The Software system should have the
capability to apply for leaves online &
also based on the leave status suggest
the attendance matrix.
- The system should have the capability
to send reminders & notification about
the same.
- All attendance & leave related MIS
should be available to the HR on their

Last revised:13/01/2013 Page 30 of 61

document1
Security Classification: High
Business Requirements Document Project Name

respective portal.

Non-Functional Requirements Card integration with the software system so that

automatic attendance management is fucnctional.

Pre-Conditions
Post-Conditions
Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

Use case # 4

Use Case Name Job posting

Description Placing job requirements in Newspaper Ads or
company website is known as posting jobs.
Actors Sneha (HR)

Business Rules

Basic Flow Alternate Flows

- The advertisement of the job opening
done on the website lead to inflow of
candidate enquiries.
- All the candidate enquiry record basic
details such as Name, contact number &
email Id, areas of interest, qualification
& experience, and source of awareness.
- All such information should flow in the
system directly from the website.
- Profile of other candidate who come
from newspaper ads should be entered
in the system by the HR.
- A report should be generated which will
give details for all candidate at one
place with respective areas of interest
to the HR department
Non-Functional Requirements

Pre-Conditions
Post-Conditions
Extension Points Extension Condition Extending Use Case

Last revised:13/01/2013 Page 31 of 61

document1
Security Classification: High
Business Requirements Document Project Name

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

Use case # 5

Use Case Name Employee Training

Description
Actors Sneha (HR)

Business Rules

Basic Flow Alternate Flows

- The HR department organizes training
programs for both the sales staff
(counsellor & center heads) and for the
academic staff (HODS & teachers).
- The HR department should have the
feature available to plan & schedule the
training programs.
- Send invites & reminders of the training
via the system
- Mark the status of the training program
as conducted or cancelled or reschedule
- People participating in the program
should be able to block their seats in
advance
- HR should be able to the mark the
attendance of the participants
- Mandays utilized in the any training
program should also be noted in the
system
Non-Functional Requirements

Pre-Conditions
Post-Conditions
Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

Use case # 6

Use Case Name Performance Appraisals

Description The systematic evaluation of the performance of the
employee and understanding the abilities of the
person for future growth & development.

Last revised:13/01/2013 Page 32 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Actors Sneha (HR)

Business Rules

Basic Flow Alternate Flows

- The performance appraisal form is
shared with the employee, which is
required to be filled by them &
submitted back to HR post discussion
on the same with the reporting head.
- The system should have the capability
to send online forms to the staff, who
can then fill it online and send it back to
HR and also take print of the same.
- The updates & reminders related to the
performance appraisal meetings should
be send via system.

Non-Functional Requirements

Pre-Conditions
Post-Conditions
Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

Use case # 7

Use Case Name Employee Exit profiling

Description The process of employee separation i.e. termination
of the employment term of the employee & employer
is followed by a exit interview or profiling in which the
details such as reason for separation is discussed &
recorded
Actors Sneha (HR)

Business Rules

Basic Flow Alternate Flows

- The employee separation process
includes filling in the exit form &
meeting with the reporting heads to
discuss the reasons for exit.

Last revised:13/01/2013 Page 33 of 61

document1
Security Classification: High
Business Requirements Document Project Name

- The employee exit profile consists of

o Name
o Total tenure
o Date of exit
o Reasons

Non-Functional Requirements

Pre-Conditions
Post-Conditions
Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

ACADEMIC PROCESSES

Use case # 1

Use Case Name Scheduling

Description Scheduling is the creation of timetable, teacher
allotment, teacher utilization, class room utilization.
The objective of scheduling is syllabus coverage
including teaching, revision, assessment &
assignments within stipulated time. Clarity of product
delivery pattern to counsellors (for better sales) and
students (for planning vacation/other activities)
Actors HOD, Scheduling Committee, Chief knowledge officer,
Business Head
Business Rules

Basic Flow Alternate Flows

- Before creation of schedule all
possible products for the year are
discussed & listed down, so that there
won’t be any friction in launching the
same.
- Schedule is required to be frozen 2
weeks before the admission
announcement – includes teaching,
assessment & revision plan.
- No changes in the schedule is allowed
after commencement of the same.
- The schedule preparation requires
o Teaching Hrs per topic, chapter
o Reinforcement (revision,
doubts)
Last revised:13/01/2013 Page 34 of 61
document1
Security Classification: High
Business Requirements Document Project Name

o Assessments (chapters, term

tests)
o Other activities (monthly,
weekly or full year)
- Scheduling parameters include
o Room availability
o Student availability
o Faculty availability
o Faculty level/ability
o Subject turns per week etc
- The IT system should have the
capability of Dynamic scheduling, i.e. is
auto generation of scheduled based on
the defined scheduling parameters.

Non-Functional Requirements

Pre-Conditions
Post-Conditions
Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

Last revised:13/01/2013 Page 35 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Use case # 2

Use Case Name Content Development

Description Development of print content (study material) and
TAT used for class room lecture delivery. The content
should be based on CBSE curriculum &
comprehensive for students understanding
Actors HOD, Scheduling Committee, Chief knowledge officer,
Business Head
Business Rules

Basic Flow Alternate Flows

- The scheduling committee places the
request for content development to the
academic head.
- Academic head & HODs brief the DTP
team and supervise the TAT
development.
- The processing of the content &
delivery on time is key responsibility of
the operations head..
- The IT system should have the
capability of uploading content (all
formats), online using & sourcing of
content & provide all the feature of a
LMS
Non-Functional Requirements

Pre-Conditions
Post-Conditions
Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

Use case # 3

Use Case Name Testing & Assessment

Description The regular & timely assessment of student
performance based on the various tests conducted
during the year.
Actors HODs/Chief Knowledge officer
Business Rules

Basic Flow Alternate Flows

Last revised:13/01/2013 Page 36 of 61

document1
Security Classification: High
Business Requirements Document Project Name

- The request for the test paper is

placed by testing committee
- The test paper development is the key
process which includes question
selection & phrasing by teachers, typing
the questions & creating question banks
is done by DTP.
- Post creation of the papers they are
dispatched to the center staff who then
use it for conducting the test & dispatch
the solved sheets to respective
teachers.
- Teacher check the papers & submit
the marks back to testing committee
who then get the report cards
generated by the DTP
- The generation of test papers & report
cards should happen with the new IT
system.
- The communications to parent is
currently passed through class rooms,
letter to parent, emails, phone calls &
SMS reminders.
- The email/sms communication to the
parent should go through the system.
Non-Functional Requirements

Pre-Conditions
Post-Conditions
Extension Points Extension Condition Extending Use Case

List of <<included>> use cases List of <<extended>> use cases List of “inherited from (parent)”
use cases

4. Data Requirements

This section describes the Data requirements part of the Business Requirements. The data requirement
includes:

 Old database – 2010-11, 2011-12, 2012-13 valid data, data generated by school activities & other
initiatives.

Last revised:13/01/2013 Page 37 of 61

document1
Security Classification: High
Business Requirements Document Project Name

 Current year data – 2013-14 sales pipeline & student enrolment data.
 HR data – Center, academic & corporate staff data
 Academic data – lecture scheduling, lesson planning, academic calendar, course details, content
details (question bank & print + TAT)
 Financial data base – fee detail (pricing sheet), collection
 Detailed MIS reporting document – description of reports required by various stakeholders &
management.

4.1. Data Retention and Archiving

This section describes the Data retention (time frames for online Data retention before archiving) and also
the archiving requirements.
- The database should be stored on 2 servers.
- Weekly backups should be taken & shared with the IT POC.
- The offline backup facility should be available

4.2. FOI/Privacy Implications

This section describes the sensitivity levels of each class of data. The following criteria are used in
determining the sensitivity level of each conceptual class/entity in line with the Government Core Policy
Manual).

 Non-sensitive information that would not reasonably be expected to cause injury (harm) if
released to the public;

 Protected A: information that, if compromised, could reasonably be expected to cause injury

(harm), e.g. loss of privacy;

 Protected B: information that, if compromised, could reasonably be expected to cause serious

injury (harm), e.g. the conduct of a court proceeding would be adversely affected;

 Protected C: information that, if compromised, could reasonably be expected to cause extremely

grave injury (harm), e.g. loss of life.

Last revised:13/01/2013 Page 38 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Conceptual Class / Entity Data Sensitivity Level

Name (Non-sensitive,
Protected A,
Protected B,
Protected C)

5. Non-Functional requirements

This section describes the non-functional requirements part of the Business Requirements. A non-
functional requirement is typically a special requirement that is not easily or naturally specified in the text
of the use case’s or function’s event flow. Examples of non-functional requirements include legal and
regulatory requirements, application standards, and quality attributes of the system to be built including
usability, reliability, performance or supportability requirements.

5.1. Security Requirements

This section describes the Security requirements part of the Business Requirements.

Last revised:13/01/2013 Page 39 of 61

document1
Security Classification: High
Business Requirements Document Project Name

5.1.1. Authentication

This section describes the Authentication requirements part of the Business Requirements.
Authentication is the process of verifying the genuineness of claims that a person/group makes to
establish identity/eligibility for access to services. In order to ascertain the Authentication requirements of
the Application, it is required to analyse the type of transactions that different Use cases/Business
Functions trigger within the Application. The following criteria is used in determining transaction types of
each use case/function (in line with the Government Core Policy Manual) :

Level 0 : Anonymous transaction – triggers transactions that do not require or allow a person to be
identified, or transactions which require protection of a person's identity. For example, access to
online information about government programs or services or protecting a person's identity.
Combining the transaction data with other data must not allow identification of a particular individual.

Level 1 : Pseudonymous transaction – triggers transactions that do not require a person to be

identified but do require a means for further contact to deliver a product or service. For example, a
note from [email protected] can not be readily translated into an individual’s name, but it may
be sufficient to request information, to provide some services, or on-going follow up.

Level 2 : Identified transaction – triggers transactions that require that a person be specifically
identified. The nature of the transaction may require confirmation of a person's identity (e.g., name,
address, birth date, etc.) and/or data linking the person to a transaction (e.g., invoice number,
personal health number, etc.).

Level 3 : Verified transaction – triggers transactions that require: the person to be specifically
identified; verification of the integrity of the data exchanged and the exchange itself; and, the creation
of sufficient evidence to indicate that the person agreed to be bound by the transaction. For example,
a note signed with a digital certificate, audit trails and security logs may provide sufficient evidence
that a specific person intended to conduct a transaction.

Use Case / Business Transaction type triggered

Function Name (Level 0 : Anonymous,
Level 1 : Pseudonymous,
Level 2 : Identified,

Last revised:13/01/2013 Page 40 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Level 3 : Verified)

5.1.2. Authorization and Access Controls

This section describes the Authorization and Access Control requirements part of the Business
Requirements at a high-level. Authorization is the process of determining if the person/group, once
identified through the “Authentication process”, is permitted to have access to certain services. The
Authorization and Access Control requirements are best described through a matrix.

Actor / Business Conceptual Class / Type of Access Control

Unit Name Business Entity Name needed on the
Conceptual Class /
Business Entity :

C  Create
R  Read
U  Update
D  Delete

Last revised:13/01/2013 Page 41 of 61

document1
Security Classification: High
Business Requirements Document Project Name

5.2. Availability Requirements

This section describes the system availability requirements.

Last revised:13/01/2013 Page 42 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Use Case / Business Availability Requirements

Function Name - Regular work hours
- 24x7
- Any other (please describe)

5.3. Usability Requirements

This section describes the system usability requirements. A usability requirement specifies how easy the
system must be to use. Usability is a non-functional requirement, because in its essence it doesn't specify
parts of the system functionality, but specifies only how that functionality is to be perceived by the user,
for instance how easy it must be to learn and operate the system.

5.4. System Help Requirements

This section describes what kind of System Help features are needed to be built into the system.

Last revised:13/01/2013 Page 43 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Use Case / Business Help Requirements

Function Name - Field level (online)
- Screen level (online)
- Help Printing Options
- Operations Manual (Offline)
- Any other (please describe)

5.5. Performance Requirements

This section describes system performance expectation levels (response times).

Use Case Name / Business Performance Requirements

Function Name / Transaction (response time)
description (in seconds or minutes)

Last revised:13/01/2013 Page 44 of 61

document1
Security Classification: High
Business Requirements Document Project Name

5.6. Scalability Requirements

This section describes how the system is expected to scale to new higher or lower levels. Both user and
application scalability requirements are described here. Data scalability is not described here as it is
already described in the “data volumes” section earlier.

5.6.1. User Scalability

5.6.2. Application Scalability

6. Interface Requirements

This section describes User and System Interface requirements for the proposed system.

6.1. User Interface Requirements

6.2. System Interface Requirements

Last revised:13/01/2013 Page 45 of 61

document1
Security Classification: High
Business Requirements Document Project Name

7. Business Glossary

Last revised:13/01/2013 Page 46 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Last revised:13/01/2013 Page 47 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Approval
This document has been approved as the official Business Requirements Document for the
Project Name project.

Following approval of this document, changes will be governed by the project’s change
management process, including impact analysis, appropriate reviews and approvals, under the
general control of the Master Project Plan and according to Project Support Office policy.

Prepared by Signature Date

Diksha Tewari

Project Manager
Studymate

Approved by Signature Date

[Client Acceptor’s Name]

[Title]
[Organization]

Last revised:13/01/2013 Page 48 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Annexures:

Annexure 1:

Enquiry Form

Annexure 2:

Registration form

Last revised:13/01/2013 Page 49 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Last revised:13/01/2013 Page 50 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Annexure 3

Receipt

Annexure 4:

Features Vs Benefits

Features Benefits

TAT Retention of concepts

Ensures longer retention of concept and topics for

students.
TAT To make learning more interactive and experimental
Easier understanding of the difficult concepts with
visuals and animations.

Comprehensive Course Coverage Full course coverage twice in a year

Best quality study material prepared by content

experts
Comprehensive Course Coverage Continuous evaluation on weekly and quarterly basis
by way of test and exams ensures track of
performance of the student.

Last revised:13/01/2013 Page 51 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Detailed theory portion helps in building a strong

foundation
Simplifies the concepts through appropriate and
simple examples
Illustration of basic concepts & core concepts of the
subjects
Scientifically developed study plans More hours of teaching than CBSE allotment
Child is much ahead of the curriculum being taught in
Hyped Up Schedule during Summer Vacations
school
Our teachers also give tips and tricks on how to solve
Tips and Tricks
the Boards and school exams before the exams
Studymate aims at the overall development of the
Value added sessions
child and not only the academics.

Feedback helps analyse the child's strengths and

developmental needs - be it in the realm of learning,
competence in a subject or simple careless errors.
Academic Counselling Academic counselling by experienced faculty and
counselors, guide students to reach their full potential.
Separate counseling session for parents also help
parents stay ahead of the process.

Stress management/time management, parent

counseling sessions to help in the overall development
Stress Mgmt, Time Mgmt sessions of the child. These sessions are conducted by the well
renowned people in the industry and every possible
concern of the child is addressed in these sessions.

Career Counselling and Personality Conducted KhudkoJaano in 26 schools of delhi : Help

Development: student to understand their personality and according
best suited career option avaliable for the students
MCQ Tests To assess understanding and absorption of key topics
To provide complete performance analysis
The key to developing a good relationship with
PTM teachers
Platform to voice your opinions and get the queries
resolved
Mind Mapping Tools to improve memory
Career Counseling Overall Development
Stress / Time management Reducing stress level
Hum Se Poocho: Delhi's only 24 x 7 Board To help students in their last few minutes of
Exam Helpline preparation / last minute queries

Last revised:13/01/2013 Page 52 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Infra Comfortable learning environment

Best in Class Infrastructure To make student comfortable
Well lit A/c classrooms For effective learning
Very colorful & vibrant classrooms To keep student stress free
Projectors & multiple white boards Promoting wellness and better preparatory tools

Faculty Experience

Specialists in their subject by having 15-20 years of

experience
Have a passion for teaching.
Faculty Experts in counseling & motivating
Trained thoroughly to deliver our teaching
methodology
Not only a teacher but a friend, guide and philosopher
Child gets individual doubt sessions to clear the doubts
Specialised Subject Teachers
as and when required.
Testing Regular and Rigorous
MCQ tests, Term Tests and Final Exam Tests keeps the
Regular Testing and Tip
student up to date

Structured doubt sessions during the course of the

year enable kids to not only clarify their own doubts,
but also to learn from the doubts raised by others.
Doubt Clearing Sessions
While students can always approach teachers at any
point with their queries and doubts, we also have
specific sessions before the exams

Testing at Studymate is structured to periodically

assess a student's grasp of a subject after every
module. Rather than leave it to the end of the term, a
student gets used to being regularly examined, which
is what keeps them prepared on crucial exam dates.
Regular Testing and feedback
We also follow a structured process of distributing
solved questions right after the paper to facilitate
immediate clarification of doubts as well as an
opportunity to identify areas where increased focus is
needed.

Last revised:13/01/2013 Page 53 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Annexure 5

Objections Handling

 Distance or Transport
 Weekend Batch
 Car Pooling
 Transport-Vendor Contact Details
 List of Students from same area
 Alternate Modes Of Transport (Auto Rickshaw, Cycle Rickshaw, or Metro)
 Best available solution in terms of time & money

 FEE
 TPS ( Third Party Story)
 Fee is high because the quality is so good
 Verdict By senior Person (Center Head or Center Principal)
 Encourage for Lump Sum Option
 Start Fee Conversation with “Investment for your Child Future”
 Calculate the possible Cost Benefits
 Focus on SM Result

 Home Tuitions
 Competition -Group studies-Prepare Students for Competition
 TAT-Technology Aided Teaching
 Build Up Question Bank-In group more doubts & Questions are asked and sorted out during
class hours
 Organized & Disciplined Atmosphere-Well Planned Time Table, Academic calendar, Periodic
Exams, Routine MCQ,& Regular PTMs
 Extra Hours-Regular Extra Classes & Remedial Classes-Leads to Personal & Individual Attentions
 Value Added Sessions-Time Management skills
 Our Faculty are-Topic experts
 Guide Students in answering questions in school exams as per Marking Scheme
 As per CCE –Lots of Assignments & Projects are given to Students
Our Teachers guide students in the same. Example-NASA Students, Plus as it involves group
presentation, group studies help them in performing well in group.

Last revised:13/01/2013 Page 54 of 61

document1
Security Classification: High
Business Requirements Document Project Name

 Afternoon Schools

 Weekend Batch
 Some students do not go to school in class XI & XII
 Another Study Mate Center-where class Take place in weekend batch at different timings
 Students can come for discussing their doubts

 Schedule

 Fixed Schedule ( so that student can plan their year in advance)

 Adjust with other tuition center or competition tuition center.
 1 week free demo classes for the subjects clashing, so that if child likes the way we take classes
can take all subjects with us, instead of wasting timing in traveling from one center to other.

 Why Min 2?

 Focus on trial classes of subjects not interested like Science, SST and English
 Encourage Student to take Exam of subjects not opted at SM and Student can discuss answer
sheet with our expert faculty.
 Under one roof-Student can study all subjects in case taking some subjects at other center or
home tuition- rather wasting timing in traveling from one center to other.

 Subject Not Available

 Acknowledge Student &Parent Request-and suggest if we will get more request for the same,
we will start it later or can even start with crash course batch, as we have done last year as well.

 Only CBSE
 Importance of C.B.S.E 40% weight age in IIT JEE
 Strong CBSE base-student horizon widen (IIT, Medical, D.U.)
 Quote Examples of rank holders.
 Did you know series (To be given by Karishma)

 If parent say-child is weak in studies

SM can arrange child class with our expert faculty to understand where child stand, and how can we
help him by providing some extra hours via remedial classes.
 If parent say-child is quiet

We can say in group tuitions when other students will ask questions, his doubts will also get solved, and
he will gain confidence and become outspoken.

Last revised:13/01/2013 Page 55 of 61

document1
Security Classification: High
Business Requirements Document Project Name

 Batch size

 Our Experienced teachers can make out by their behavior regarding Student’s Seriousness
towards Studies.
 Separate Doubt Clarification sessions

 I will think over it.

 Prepare a Check list

 I am the best person to help you know about SM
 We provide Students with Free Question Bank & Study Material which help student score much
better

 Negative Feedback

 Acknowledge
 Create Expectation Management

Last revised:13/01/2013 Page 56 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Annexure 6

Studymate Sales Enabler

Last revised:13/01/2013 Page 57 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Last revised:13/01/2013 Page 58 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Last revised:13/01/2013 Page 59 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Last revised:13/01/2013 Page 60 of 61

document1
Security Classification: High
Business Requirements Document Project Name

Annexure 7 :

Academic Processes
Note.docx

Annexure 8:

Studymate
Operations Process Note.docx

Last revised:13/01/2013 Page 61 of 61

document1
Security Classification: High