“Having all expected attributes on the table up front give us a great input”

 

In our roles as system architects, developers or project managers we know there are more requirements than the long list of functional change requests we got as an input.

Often the most complex requirements are the non-functional. On top of this they are often not even written in the specifications but just expected by the stakeholders. “Of course the system should be easy to use”, “of course the application should deliver the performance we need during the coming 10 years”, “bye the way, the system must be compliant to all legal aspects in Saudi Arabia…”.

The discussions regarding requirements often boils down to a pretty simple question; what is quality?

Using industry standards as a platform IT informa has developed a model and a process how to define quality. The process includes functional and non-functional quality attributes and ensures all aspects are prioritized, defined, owned and verified.

E.g. during application development the main driver of the architecture process are the non-functional requirements. Another example is the test strategy. Having all expected attributes on the table up front give us a great input when deciding how to ensure quality including required tools, skills and activities.