12.1. Testing Your Model
Testing a model doesn't involve rocket science; instead, it calls for some common-sense measures designed to identify errors and/or omissions:
First of all, revisit all requirements-related project documentation—the original problem statement and the supporting use cases—to ensure that no requirements were overlooked. You'll do so for our SRS model in a moment.
Conduct a minimum of two separate formal walk-throughs of the model: one with the development team members, and a second with the future users of the system. A formal walk-through should involve, at least, the items in the following list. Make sure to distribute copies of the following documentation to each of the participants far enough in advance to allow them ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access