So, the basic requriement writing recommendation states that high level requirement shall be design independent. I have this requirement
"The system shall have the capability to compute XYZ ". Let's say XYZ = Speed.
The lower level decomposition states the necessary inputs, outputs, equations, etc. needed for the computation. Which can be easily verified.
However, I get into the issue of verifiying this High level requriement. How can we verify this requirement ?....Or is this is a bad requirement that needs modification, if yes, then how....but remember at a high level, the requriements needs to be design independent and only answer the "What?" the system does...not "How?" the system does it...
any help would be appreciated.
Where did you get that " basic requriement writing recommendation states that high level requirement shall be design independent"? Because, all requirements are design independent.
Defining the computation is also design-independent. We could say these days that the computation is a business rule, not a requirement, because it exists irrespective of your writing of requirements or eventual inclusion in a system.
But I digress, your question is about verification of a high-level requirement. If your SME or sponsor reads it and says "that is my requirement", then it has been verified. If you are asking about how to validate a requirement, that is different.
David Wright
http://about.me/dwwright99
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: