Morgan Masters posted on April 22, 2010 03:49
There is no one standard definition of an Availability Non-Functional Requirement. It will be defined for each project where it needs to be specified. This principle is true of all non-functional requirements.
For the purposes of this article an Availability Requirement is any requirement that is not a functional, data or process requirement concerned with defining the periods when the solution can be used.
The ‘definition’ may be ambiguous. That is not material to the success of the project. What is material is that all requirements (including non-functional) are captured and progressed. This definition means what it needs to mean to the project that are defining the requirements. For the purposes of this article, it means times of day and days of year when the solution can be used and by definition when it will not be available for use.
One general point about availability requirements that in principle applies to all requirements anyway: quite often the availability requirement will be stated as “The solution needs to be available 100% of the time”. There are issues with this requirement in that...
[Read More...]