Hi Experts.
I have been going through a document that was made by an experienced company but what actually took my attention is that they classify Reporting Requirements as Non Functional. How come this happens, if you say the system shall allow reporting on responses where results can be anlaysed on different levels, x, y, z.
Or Reports should be produced to enable the decision makers to view their teams performance against targets. This can be through a dashboard that enables extracted pdf format outputs.
This is a system function that shouldn't be nonfunctional, but all the reporting requirements are classified as Non-Functional in this document.
Thank you for the explanation if you can explain this.
Madimo
Hi,
Its an interesting question on Reports classification.
From my experience in my projects the software applications which we built has tracking on their performance and application availability such as the number of session time outs,server timeouts etc.
These attributes get classified under non functional requirements as they are grouped under availability and performance. They are tracked as well. Most commonly it happens after a Production release or after an Upgrade.So from my point of view Reporting requirements will exist for both Functional and Nonfunctional requirements.
I hope this answers.
Hi Shree
Thanks for the opinion, which is useful
I was just wondering about the example I posted because it is written in a way that combines the outcome with its specification, so it is a system functional task this is why I wondered why it was classified as a Non-Functional Requirement from the beginning.
Many thanks if you can elaborate and thanks for the already provided explanation
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: