Studies and experience have shown that the cost of fixing requirements related errors increases through the lifecycle of a project, so it makes sense to catch errors at the start and during the Analysis stage rather than during Implementation. Even with great analysts and processes in place - errors can still get through.
We review requirements against agreed criteria. Some of the common examples are:
- Suitability for hand over to development teams both onshore and offshore
- Adherence to client standards or a particular method e.g. UML
- Consistent requirements
- Unambiguous language
- Testability
- Solution and Jargon free
- Non Functional and Functional
| Do you want to be kept up to dates with news from Be Positive? Are you interested in the latest BA developments and techniques? Then join our Linked in group. | |
| Join Friends of Be Positive on: |  |
