There must always be an explicit link between business processes and requirements.
It should start at a high level for the coverage perspective, but the requirements must be collected in detail. Asking the five Ws is always a good idea to ensure that enough details are collected.
The six Ws are Why, What, Where, Who, and When, as well as Which.
When solution envisioning is performed, another crucial question, How, is answered.
When solution envisioning is performed, another crucial question, How, is answered.
All the business processes that will be part of the initiative and each of their subprocesses must be considered in order to prepare the requirements list. There should never be a requirement without it being linked to one or many processes; alternatively, there should not be any process/subprocess that does not have any requirements. Any such situation wherein a requirement does not belong to any business...
