NFRs are Constraints

NFRs — Non Functional Requirements (qualities of a system like Scalability, Security, etc) are constraints of a system once built and in place. For example: Architecture team determines that Amazon Web Services (AWS) should be the one to go with (this is alignment with ‘Scalability’)… then they make this as one of their ASRs (Architecturally Significant Requirements). Once this ASR is in place, it constraints upcoming functional requirements that use web services … AWS will be used instead of another web services from somewhere else.

NFRs are part of the Definition of Done (DoD).

NFRs are initially enablers along the architecture runway… supporting / enabling a functional requirement to its fruition.

NFRs and Enablers are like the devil and angel on your shoulders as you build functionality of your system.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s