Stop calling requirements ‘non-functional’!

by May 24, 2023Shorts

Stop calling requirements ‘non-functional’!

You want deliveries that don’t function?

Why name it wrong? Call it what it is!

If you look closer at non-functional requirements, they fall into two groups:

1๏ธโƒฃ Operational requirements ๐Ÿš€

Just like Function requirements, it describes what users can observe at runtime: the behavior. But we focus more on how it does this, like Performance and Availability.

2๏ธโƒฃ Developmental requirements ๐Ÿ› ๏ธ

Users can’t observe these, but they are also important. These are developmental qualities, requirements from the development team. Like Maintainability, Portability, and guidelines.

Change the conversation by doing this! ๐Ÿ’ก

Remy van Duijkeren

Remy van Duijkeren

Power Platform Automator

Automation and integration arenโ€™t just what I doโ€”theyโ€™re what I do best.

I help businesses work smarter by removing friction, automating what slows them down, and connecting systems that shouldโ€™ve been talking all along.

 

Get My Thoughts on Automation & Development

Join my personal newsletter and get practical insights on building faster, integrating smarter, and removing friction in IT systems โ€” especially on Power Platform and Dynamics 365.

Related