Quote:
|
Originally Posted by MTalbot
I think this is actually a really great point. In an SRS, how have you typically handled or called our requirements that you know are incomplete/wrong at the time of writing?
|
Well...
...as a rule, all my requirements start out this way. And in reality, it's pretty safe to assume that they end that way too! (That's just the Precautionary Principle.)
I am not by nature a pessimist, but every requirement has a "confidence level" of between 0% and 99%. All requirements begin at 0%. I only increase the percentage after I've written the requirement. Then again after it's been checked. And so on throughout its lifetime. Proactive planning means I also agree one or more target levels for each requirement. The difference is accounted for in two ways: in part it's the work I have left to do, in part it's the risks, assumptions, issues and dependencies that are logged elsewhere and referred out to. In the example given, confidence is reduced by a dependency on an incomplete task: changes in the status of this task will affect the confidence level.