this ppts is about the business analysis

2. Types of requirement including
Business, Functional and NonFunctional
•
•
•
•
PABBA CHANDRAKAMAL(208)
CHARAN
PRIYATHAM
SAI CHARAN

3. • A Business Requirement usually begins with a
statement of a specific strategy or goal developed
by a leadership team. The team identifies business
strategies and goals to meet business needs arising
from competitive, regulatory, operational, and other
business pressures.

4. • Business requirements provide answers about
what must be accomplished for the project to
be considered a success. The following are some
of the typical questions that must be answered:
• What business functions are to be performed?
• What information is required?
• What results are expected?
• At what locations?
• For whom?
• How often?

8. High-Level Business Requirements

12. Detailed Business Requirements
• Overview
• Before developing Detailed Business
Requirements, the project team should have:
– • Documented the High-Level Business
Requirements.
– • Developed a Conceptual Design for the solution.
– • Determined the project’s estimated cost.
– • Presented all findings to the project sponsors for
approval.

14. Functional Requirements
• The documents and tracks the necessary
information required to effectively define
business and functional requirements. The
Functional Requirements Definition document
is created during the Planning Phase of the
project. Its intended audience is the project
manager, project team, project
sponsor, client/user, and any stakeholder
whose input/approval into the requirements
definitions process is needed.

15. • BUSINESS REQUIREMENTS OVERVIEW
[Describe here the business requirements that the project work will fulfill and
how and/or where the completed project product will fit into any existing
systems. Assign a unique ID number to each requirement.]
• ASSUMPTIONS / CONSTRAINTS
[Describe any overall assumptions / constraints related to project
requirements]
• FUNCTIONAL REQUIREMENTS
[Functional requirements capture and specify specific intended behavior of the
system being developed. They define things such as system calculations, data
manipulation and processing, user interface and interaction with the
application, and other specific functionality that show how user requirements
are satisfied. Assign a unique ID number to each requirement.]
• USABILITY REQUIREMENTS
[Describe all of the functional requirements that affect usability such as ease of
learning, task efficiency, ease of
remembering, understandability, attractiveness, etc. Assign a unique ID number
to each requirement.]
• PERFORMANCE REQUIREMENTS
[Describe all of the functional requirements that affect performance such as
speed, safety, precision, reliability and availability, capacity, scalability, etc.
Assign a unique ID number to each requirement.]

16. •
•
•
•
•
•
SUPPORTABILITY REQUIREMENTS
[Describe all of the functional requirements that affect supportability and
maintainability such as training, ramp-up time, documentation, facilities, etc.
Assign a unique ID number to each requirement.]
SECURITY REQUIREMENTS
[Describe all of the functional requirements that affect security such as security
audits, identification/authentication, privacy, facility access times, etc. Assign a
unique ID number to each requirement.]
INTERFACE REQUIREMENTS
[Describe all of the functional requirements that affect interfaces such as user
navigation, presentation of application and associated functionality, screen
location of interface elements, data display and manipulation, etc. Assign a unique
ID number to each requirement.]
ASSUMPTIONS / CONSTRAINTS
[Describe any functional assumptions / constraints related to any of the project’s
requirements]
COMPLIANCE REQUIREMENTS
[Describe the existing compliance environment as it affects project requirements.
Include an overview of the compliance requirements necessary to achieve the
project’s objectives. Assign a unique ID number to each requirement.]
ASSUMPTIONS / CONSTRAINTS
[Describe any compliance assumptions / constraints related to any of the project’s
requirements]

17. Non-Functional Requirements
• The Non-Functional Requirements (also referred
to as Quality of Service by the International
Institute of Business Analysts, Business Analysis
Body of Knowledge) Definition documents and
tracks the necessary information required to
effectively define business and non-functional and
technical requirements. The Non-Functional
Requirements Definition document is created
during the Planning Phase of the project. Its
intended audience is the project manager, project
team, project sponsor, client/user, and any
stakeholder whose input/approval into the
requirements definitions process is needed

18. •
•
•
•
•
•
BUSINESS REQUIREMENTS OVERVIEW
[Describe here the business requirements that the project work will fulfill and how
and/or where the completed project product will fit into any existing systems.
Assign a unique ID number to each requirement.]
ASSUMPTIONS / CONSTRAINTS
[Describe any overall assumptions / constraints related to project requirements]
NON-FUNCTIONAL REQUIREMENTS
[Describe the existing non-functional (also referred to as Quality of Service by the
International Institute of Business Analysts, Business Analysis Body of
Knowledge), technical environment, systems, functions, and processes. Include an
overview of the non-functional requirements necessary to achieve the project’s
objectives.]
HARDWARE REQUIREMENTS
[Describe hardware requirements and any related processes. Include a detailed
description of specific hardware requirements and associate them to specific
project functionality/deliverables. Include information such as type of
hardware, brand name, specifications, size, security, etc. Assign a unique ID
number to each requirement.]
SOFTWARE REQUIREMENTS[Describe software requirements and any related
processes. Include a detailed description of specific software requirements and
associate them to specific project functionality/deliverables. Include information
such as in-house development or purchasing, security, coding language, version
numbering, functionality, data, interface requirements, brand

19. •
•
•
•
•
•
•
•
•
•
PERFORMANCE REQUIREMENTS
[Describe performance requirements and any related processes. Include a detailed
description of specific performance requirements and associate them to specific
project functionality/deliverables. Include information such as cycle time, speed per
transaction, test requirements, minimum bug counts, speed, reliability, utilization
etc.]
SUPPORTABILITY REQUIREMENTS
[Describe all of the technical requirements that affect supportability and
maintainability such as coding standards, naming conventions, maintenance
access, required utilities, etc. Assign a unique ID number to each requirement.]
SECURITY REQUIREMENTS
[Describe all of the technical requirements that affect security such as security
audits, cryptography, user data, system identification/authentication, resource
utilization, etc. Assign a unique ID number to each requirement.]
INTERFACE REQUIREMENTS
[Describe all of the technical requirements that affect interfaces such as protocol
management, scheduling, directory services, broadcasts, message types, error and
buffer management, security, etc. Assign a unique ID number to each requirement.]
AVAILABILITY REQUIREMENTS
[Describe all of the technical requirements that affect availability such as hours of
operation, level of availability required, down-time impact, support availability, etc.
Assign a unique ID number to each requirement.]

23. • Thank u