IIBA® Melbourne brings you the topic of producing Functional and Non-Functional requirements. This can be a challenge because the demarcation between FR and NFR ‘s is often blurred and subject to debate. This interactive presentation analyses some of these challenges in clearly categorizing a Solution Requirement as a FR or NFR. A case study will also be presented which specifically looks at WCAG 2 requirements to include clients with special needs.

1. IIBA® Melbourne
NFRs vs FRs
26 October 2022

2. IIBA® Australia acknowledges the Traditional Owners of
country throughout Australia and recognise their continuing
connection to land, waters and culture.
We pay our respects to Elders past, present and emerging
and extend our respects to all Aboriginal and Torres Strait
Islander people present with us today.
Acknowledgement of Country

3. Welcome

4. Meet your Melbourne Branch Committee
Mohammad Mirkarimi
Corporate Engagement
Chaden Berbari
Education & Certification
Charmaine Mckie
Events
Tom Wilson
Operations
Angelo Thomas
Mentoring
Shane De Silva
Marketing
Liza Laya
Melbourne Chair

5. For more information and to register visit
https://australia.iiba.org/events-list
Future Events
27 October 2022
IIBA® Adelaide - Requirements and How to Find Them
1 November & 2 November 2022
Global Business Analysis Day Event
10 November 2022
(Scaling) agile through the lens of a Business Analyst using SAFe
23 November 2022
IIBA® Melbourne – Secrets behind AI project successes

6. Call for Volunteers
The IIBA Australia Chapter invites your expressions of interest (EOI) to join and support
us in providing our services to our members and community. Chapter volunteering is
activity and capacity based. In addition to completing this form, you are strongly
encouraged to get involved by attending Chapter events held in your local city.
For more information and to express your interest visit:
https://australia.iiba.org/volunteer

7. Follow us on Social Media
Join the Conversation NOW!
IIBA Australia IIBA Australia Chapter
@IIBAAUS
Iiba_australia IIBA Australia
Chapter Ltd
iibaaustralia.com

8. Mr Rajiv (Max) Roy
Solution/Data Architect
Accenture Inc
e: squash7733@gmail.com
t: @squash7733
LinkedIn: https://www.linkedin.com/in/rajiv-max-roy-73433b8/
8
IIBA – NFR vs FR

9. Functional Requirement (FR) of a system
 What is required to get done
 Done or Not - kind of binary
Non-Functional Requirement (NFR)
 How will they be implemented?
 Aesthetics of achieving/implementing the FR’s
9
Business Context

10. Non-Functional Requirement (NFR) are mainly the
 “--- bilities” e.g. Usability, Portability,
Accessibility
 “--- iveness” e.g. Responsiveness, Robustness
So not the core functionality of the application system
 But there are grey areas!
 Depends on Business/Solution context
 Client/Site specific
10
What is an NFR?

11. Non-functional requirements as requirements
that “do not relate directly to the behaviour
or functionality of the solution, but rather
describe conditions under which a solution
must remain effective or qualities that a
solution must have”
11
NFRs according to BABOK v3

12.  Operability / Usability – User friendliness
 Performance – Responsiveness (within 3 secs)
 Accessibility - Usable by a range of users
 Maintainability - Can be changed when required
 Reliability – Available when needed
 Robustness – recovers gracefully from
application aborts/disaster events
 Security – information can be trusted
 Compatibility – integrates with other
applications
12
Prime Examples of NFRs

13. 13
Common example: Bicycle

14.  Functional Requirements (FR)
 Two wheels with drive chain
 Frame & handlebars
 Seat & pedals
 Gears (Derailleur)?
 Lights – front & back ?
 Non-Functional Requirements (NFR)
 Padded seats for comfort
 Bell or horn?
 Bike-stand?
 Water bottle?
14
FRs vs. NFRs of a Bicycle

15.  Go to www. Menti.com
Code: 43952837
Link:
https://www.menti.com/e8h77
pjr4g
15
Menti Voting – Bicycle NFRs

16.  BABOK v3 – Trusted Information
 Used to be NFR
 Become an integral part of applications
 https://babokpage.wordpress.com/techniq
ues/non-functional-requirements-analysis/
 Cyber threats & attacks
 Hacker/Ransomware/Malware
 Application / endpoint hardening
 Essential 8
 CTI – Cyber Threat Intelligence
16
Application Security

17.  Dept of Immigration & Border Protection
 Merge of two Federal Departments
 AU Customs – Air/Sea/Land Cargo
 Immigration – Visas/ Refugees/ etc
 About 400 Business Requirements
 ~ 220 core functional (FR)
 ~ 80 - 100 NFR’s
 Remaining were mixed bag of solution features
/ Nice-to-have’s /etc
17
Case Study - DIBP

18.  Web Content Accessibility Guidelines
 Users with Disabilities e.g. Vision Impaired
 Immigration – Visas/ Refugees/ etc
 Mandatory implementation
 https://www.w3.org/TR/2018/REC-
WCAG21-20180605/
18
Case Study – WCAG 2.0 Compliance

19. I. Text Alternatives
II. Time-based media
III. Adaptable
IV. Distinguishable
19
WCAG 2.1 Principles - Perceivable

20. I. Keyboard Accessible
II. Enough Time
III. Seizures & Physical Reactions
IV. Navigable
V. Input Modalities
20
WCAG 2.1 Principles - Operable

21. I. Readable
II. Predictable
III. Input Assistance enabled
21
WCAG 2.1 Principles - Understandable

22. I. System recovers gracefully after abort events
II. Rollback to stable, safe checkpoint
III. Status Messages
22
WCAG 2.1 Principles - Robust

23.  Traditional/legacy Waterfall
 Do the NFR’s at the end ?!?
 Nice to have’s !
 AGILE Sprints
 Separate User Stories for each NFR?
 Built-in integration
 User story not ‘Done’ until NFR is also tested!
23
When are NFRs done?

24. Grey areas between FR & NFR
 Depends on site/business solutioning
 Subject to mutual understanding
Prioritization
 Which are required in Agile Sprints
 Measures while testing NFR’s
Implementation strategy
 Integrated with FR User Stories
 Revisited before Releases
24
Final Takeaways

25. Thank you