Balanced Scorecard is 30th Technique from BABOK 3.0. I tried to put this concept so simple to understand, stick to this space for material

1. 10.30 NON-FUNCTIONAL REQUIREMENTS
ANALYSIS
B A A C A D E M Y 1

2. WHAT ARE NFRS?
 Non- functional requirements define the overall qualities or
attributes of the resulting solution or solution components.
They state the qualities of behaviour or quality attributes
that stakeholders want.
Simple example :
Bob and Jenny are gathering requirements from enduser stakeholder group who
came up with a user story
“ As an enduser I want the order booking site to be available 99.999 percent of the
time I try to access it, so that I don't get frustrated or do manual job”.
What are NFRs here?
Availability, Reliability, Performance Efficiency, Usability
B A A C A D E M Y 2

3. BABOK 3.0 DEFINITION
 Non-functional requirements (also known as quality attributes
or quality of service requirements) are often associated with
system solutions, but they also apply more broadly to both
process and people aspects of solutions. They augment the
functional requirements of a solution, identify constraints on
those requirements, or describe quality attributes a solution
must exhibit when based on those functional requirements.
 Non-functional requirements are generally expressed in
textual formats as declarative statements or in matrices.
B A A C A D E M Y 3

4. WHAT ARE CATEGORIES OF NFRS ?
Availability
Certification
Compliance
Compatibility
Extensibility
Functionality
Localisation
Maintainability
B A A C A D E M Y 4
Performance Efficiency
Portability
Reliability
Scalability
Security
Service Level
Agreement
Usability

5. HOW TO MEMORISE ALL NFRS?
Mnemonic to memorise NRFs categories
PePS CRCULM ACESS
This Mnemonic doesn't have any meaning but we can memorise it like this
Our Bob is currently working on a wireframe for a university’s learning
and development portal which is called as PePs CRCLUM ACESS
module.
B A A C A D E M Y 5

6. WHAT ARE OTHER ELEMENTS OF NFRS ?
B A A C A D E M Y 6
 Measurement of Non-Functional Requirements
Non-functional requirements must be quantified whenever possible
Including an appropriate measure of success provides the
opportunity for verification.
Eg: "The process must be easy to learn" can be expressed as "90% of
operators must be able to use the new process after no more than
six hours of training“

7. WHAT ARE ELEMENTS OF NFRS ?
B A A C A D E M Y 7
 Context of Non-Functional Requirements
Depending on the category of non-functional requirements, the
context may have to be considered.
Eg: A regulatory agency may impose context impacting compliance
and security requirements, or an organization that is expanding
operations abroad may have to consider localization and scalability
requirements.

8. B A A C A D E M Y 8
USAGE CONSIDERATIONS
Strengths
 Clearly states the constraints that apply to a set of functional requirements.
 Provides measurable expressions of how well the functional requirements must
perform, leaving it to the functional requirements to express what the solution
must do or how it must behave. This will also have a strong influence on
whether the solution is accepted by the users
Limitations
 The clarity and usefulness of a non-functional requirement depends on what
the stakeholders know about the needs for the solution and how well they can
express those needs.
 A set of non-functional requirements may have inherent conflicts and require
negotiation.
 Many non-functional requirements are qualitative and therefore may be
difficult to be measured on a scale,

9. KNOWLEDGE TEST
 Which of the following describe common non-functional
requirement categories???
A) Reliability, Scalability, Capability, Adaptability
B) Reliability, Compatibility, Scalability, Localization
C) Reliability, Availability, Scalability, Traceability
D) Reliability, Expandability, Scalability, Localization
B A A C A D E M Y 9

10. KNOWLEDGE TEST
 Which of the following describe common non-functional
requirement categories???
A) Reliability, Scalability, Capability, Adaptability
B) Reliability, Compatibility, Scalability, Localization
C) Reliability, Availability, Scalability, Traceability
D) Reliability, Expandability, Scalability, Localization
B A A C A D E M Y 10

11. KNOWLEDGE TEST
 Non-functional requirements analysis is a stated technique
for which of the following tasks in the Requirements Analysis
and Design Definition knowledge area??
A) Verify Requirements
B) Validate Requirements
C) Specify and Model Requirements
D) Define Design Options
B A A C A D E M Y 11

12. KNOWLEDGE TEST
 Non-functional requirements analysis is a stated technique
for which of the following tasks in the Requirements
Analysis and Design Definition knowledge area??
A) Verify Requirements
B) Validate Requirements
C) Specify and Model Requirements
D) Define Design Options
B A A C A D E M Y 12

13. FEW IMPORTANT POINTS TO MEMORISE
 Non-functional requirements are generally expressed in textual
formats as declarative statements or in matrices.
 Declarative non-functional requirements statements will typically
have a constraining factor to them.
 Non-functional requirements often describe quality characteristics
in vague terms
 Depending on the category of non-functional requirements, the
context may have to be considered.
 Context is dynamic by nature and non-functional requirements may
need to be adjusted or removed outright.
 PePs CRCLUM ACESS
B A A C A D E M Y 13

14. THANK YOU
B A A C A D E M Y 14
Durga Prasad CBAP® CSM®