<< 1 >>
Rating: Summary: The best book on Internet software requirements gathering Review: Ms Ferdinandi does an excellent job exploring the unique process of gathering requirements for web-based development projects. When your business partner is operating on "Internet time" it's easy to take shortcuts that can have disastrous consequences later. This book provides a methodology that ensures you can deliver systems quickly while not neglecting important aspects of the requirements gathering and management process. Covers initial project requirements as well as enhancement requirements. Highly recommended.
Rating: Summary: An excellent source for requirement engineering information. Review: This book servers as an excellent source for gaining insight into the field of requirements engineering. Developers, Managers, Requirements Engineers and Testers could all benefit from reading this book. In addition to providing important information about requirements engineering in general, the book presents a requirement pattern framework targeted for e-business and web based applications.
Rating: Summary: A Recommendation book for Successfull Project Review: This is the first book about Requirements Pattern. You can easily understanding your problems after define all project's requirements. This book also provides a completes framework to categorizes and organizes the different types of requirements, forming a requirements set. It makes our project done on time and within budget. Thanks to Pat for this excellent book.
Rating: Summary: Requirements at their best! Review: Through the years, I have continually learned and implemented new approaches to developing information technology products. All of these approaches were helpful, but none perfect in capturing all that is needed to build a quality system.When John Zachman introduced his Information System Framework, it provided the beginning of a framework that would help me to cross-check that I've captured all the details needed to build an effective and efficient software system. The Requirements Set Framework I've developed expands Zachman's work to incorporate System Requirements (non-functional requirements) and other Business Practice Requirements that are so notoriously forgotten until much later in stages of development. Plus this approach works with all current system development methods and techniques. The book describes, in detail, the type of requirements that need to be captured, how to categorize them, how to evolve them for designers, and how to manage them throughout the product's life. The book can be used as training tool for beginners, or as a cross-check tool for senior systems engineers, or anyone responsible for capturing, analyzing, specifying, and validating requirements. As a result of reading this book, you will have learned the steps to ensure the following: -There are no glaring gaps in knowledge. -All dependencies between requirements have been defined. -All relationship between requirements have been qualified. -All requirement details are captured. The book also discusses The Requirements Pattern and the associated Anti-Patterns in great detail. The use of patterns and anti-patterns have become widely accepted in the system engineering community and assists project teams in avoiding the typical mishaps of a requirement effort. I hope you are able to use my book as a reference for years to come,as new approaches to software development emerge, or with any individual or mix of existing approaches to product development.
Rating: Summary: Excellent Book. Improved my Professional Career. Review: Validating requirements is a tough job especially for someone like me that is not intimately involved in the project. I'm called in to review requirements for quality. Sure, I can use the checklist that appears in so many requirement type books. This is the FIRST book that talks about looking at all the requirements and checking to see if you have any gaps in knowledge. The way the author categorizes requirements, it is easy to follow and so simple to implement in any size organization for any type of project. I will be able to help the team way before design begins. The cross-checking techniques will save me time and the company money.
Rating: Summary: Great reference for developing high quality requirements Review: Validating requirements is a tough job especially for someone like me that is not intimately involved in the project. I'm called in to review requirements for quality. Sure, I can use the checklist that appears in so many requirement type books. This is the FIRST book that talks about looking at all the requirements and checking to see if you have any gaps in knowledge. The way the author categorizes requirements, it is easy to follow and so simple to implement in any size organization for any type of project. I will be able to help the team way before design begins. The cross-checking techniques will save me time and the company money.
<< 1 >>
|