Requirements must be clear and deterministic (verifiable); in other words, at the end of the project, you should easily be able to determine whether a requirement has been met.
For example, a customer might say that the new network must help reduce overall costs. This goal must be translated into requirements that can be implemented and measured. For example, reducing costs could mean that a web-based ordering system replaces call-center ordering, or it could mean that unreliable equipment is replaced. Each of these options has its own initial and operating costs, so you must understand what the network owner means when he states his goals.
Each of the requirements should also be assessed for its importance, and a weighting factor should be assigned so that if conflicts arise (for example, an inadequate budget), the most important requirements can be met.
Was this article helpful?