Assumptions
Assertions
List assertions, e.g., forces, systems and activities in the world, that might contribute to requirements. These will have an effect on the eventual design of the product. An Assertion is something that is factual, verifiable and quantifiable.
For example, one ton of de-icing material will treat 3 miles of single lane roadway.
An assumption however is an educated oppinion.
Assumptions
List the assumptions that developers are making. These can be about anything that has an effect on the product. It is important to declare the assumptions people are making and to ensure everyone on the project is aware of assumptions that have been made.
For example, assumptions are made about what is expected to be ready in time for developers to use, such as the completion of other projects, software tools and software components.
People often make unconscious assumptions. It is necessary to talk to the members of the project team to discover if this has happened. Ask questions like "What software tools are you expecting to be available, are you expecting to use a current product in a new way....?" Consider whether the assumption is correct, and where relevant, a provide a list of alternatives if something that is assumed does not happen.
|
