Scribd
Upload
7 views4 pages

Amnex Infotechnogies

The document outlines the differences between Software Requirement Specification (SRS) and Functional Requirement Specification (FRS), highlighting their purposes, maintainers, and focus areas. It also discusses the components of Business Requirement Documents (BRDs), including company overview, project scope, business goals, requirements, project roadmaps, stakeholder consultation, project risks, infrastructure requirements, and budgets. The BRDs are crucial for aligning project stakeholders and ensuring successful project execution.

Uploaded by

Ajay Wanjare
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
7 views4 pages

Amnex Infotechnogies

The document outlines the differences between Software Requirement Specification (SRS) and Functional Requirement Specification (FRS), highlighting their purposes, maintainers, and focus areas. It also discusses the components of Business Requirement Documents (BRDs), including company overview, project scope, business goals, requirements, project roadmaps, stakeholder consultation, project risks, infrastructure requirements, and budgets. The BRDs are crucial for aligning project stakeholders and ensuring successful project execution.

Uploaded by

Ajay Wanjare
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Difference SRS & FRS

Sr.No SRS FRS

SRS is short used for Software FRS is short used for Functional
1
Requirement Specification. Requirement Specification.

SRS is also called a Product FRS is also called a Functional


Requirement Specification and Specification Document, Functional
2
System Requirement Specs, and Product Specification
Specification. Document.

It is maintained by the
It is maintained by Business
3 Implementation lead or System
Analyst or System Analyst.
Analyst.

Focus on detailed aspects of the


Focus on the functional and
4 functional and non- functional
non-functional requirements.
requirements.

Bridges gap between user and Bridges gap of users with functions
5
developer. of software.

Used for planning phase and testing


6 Used for planning phase.
phase.

SRS is used by the Project


FRS is used by Testing teams and
7 managers, technical leads, and
technical teams.
Subject matter experts.

Road Ambulance

 PMC CARE

CARE eFAQ Mobile App is an initiative to provide an efficient channel for all citizens (external
stakeholders) and PMC staff (internal stakeholder)...
Company Overview
The BRDs start with an overview of the company explaining the company’s
mission, vision, and business strategy. This section also covers company’s
portfolio of products, services, customers, and service delivery. Sometimes
company’s business model and operations are also included in the BRDs.
This helps the solution provider to get a holistic look at the company they are
undertaking the project. In some BRDs, instead of a company overview, an
executive summary will be presented.

Project scope
This is the important section of the BRDs that explains the project scope in
detail. This provides an outline of what is covered in the project and more
importantly what is out of scope. This defines a clear boundary for the project
landscape. The consensus needs to be sought out among the project
stakeholders about the project scope. The project scope identifies and defines
clear business goals along with project high-level outcomes.

Business goals
The business objectives of the projects should be clearly documented to align
project stakeholders for successful execution. These goals provide a strategic
outcome of the project and detailing the “Why” of this project is required.

Functional and non-functional


requirements
This section of the business requirement document talks about the functional
and non-functional business requirements. The functional requirements
describe essential features that the solution “must-have” to satisfy the project
stakeholder needs. The functional requirements are assigned different
statuses such as “essential”, “important” and “desirable” and these
requirements can be prioritised.
Non-functional requirements are also documented to include any reporting,
analytics, and integration requirements.

Project Roadmaps
Project roadmaps contain the schedule for project execution. It includes
project milestones and stakeholder meetings along with estimated timelines. It
also charts out the dependencies in project activities and contingencies. The
rule of thumb is to include 20% buffer time for all activities to manage
uncertainties that may arise during project execution.

Stakeholder consultation
The stakeholder consultation meeting includes items that need to be
discussed with solution provider after successful project kick-off. This includes
 Business process maps

 Reporting requirements

 Operational requirements

 Service delivery mechanism

 Data privacy

 Service Level Agreements

 Existing business systems

 Business and IT architecture

 Compliance and regulatory requirements

Project risks
This section elaborates on the project risks. Project risks explain the strategic
and tactical risks that the project Senior Responsible Officer (SRO) needs to
manage during project implementation. The risk plan consists of risk name,
risk priority, risk likelihood of occurrence, mitigation strategies, and risk owner.

Infrastructure requirements
For IT and digital transformation projects, infrastructure requirements can be
included in the technical section. This includes servers, licensing costs, and so
on.

Budgets
Budgets section covers phased/milestone-based payment schedules along
with the disbursement amount. The budget needs to cover onboarding cost,
stakeholder consultation cost, vendor cost, operation cost, and any non-
essential project costs.
Project governance committee is set up to oversee the project execution. This
committee includes Senior Responsible Officer (SRO), Project Director,
Project Manager, business analysts, and business stakeholders. The
committee meets at regular time intervals to ensure smooth project
operations. The business analyst usually drafts the business requirement
document. The BRDs are verified by a project manager and validated by the
project director.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy