
When writing requirements, accompany each group of statements on what the system is to do with a statement saying why
When writing requirements, accompany each group of statements on what the system is to do with a statement saying why. This achieves two goals. It provides an alternative statement on the requirements that can aid in eliminating misinterpretation, and it gives a focus for organization of the statements on what the system shall do.
An IntentStatement can be replaced by referencing a BusinessUseCase. However, the value to effort ratio is so large that use of an IntentStatement is recommended in any case. Having an alternate way of expressing a set of requirements helps eliminate CommonModeError. The IntentStatement was to some degree a precursor of the UseCase. However many writers of Use Cases omit the IntentStatement, or give a Goal statement that can be inadequate for the purpose of eliminating misinterpretation.