Top critical review
3 of 3 people found this helpful
Who is this book for
on June 13, 2001
This is an academic document of someone who has participated on the process of gathering requirements.
The detail of every chapter, the context of the user, roles, the things to consider, the tips, the relations to other systems, the different kinds of requirements, the guides, the testing, all is there and complete. But it belongs to the classroom.
I was looking for a book that I can lend to the people in my organization so we can improve in our actual development process. There are no tips on how to use formats like the Use Case, it does not even appear on any page. Nor does it show the actual deliverables to the analysis and development team or suggestions on traceability for testing on the final product.
The writer has taken care on keeping things open so people could discuss, improve or use alternate approaches. But software development needs standards and method, there are no suggestion on how you can improve on these.