Software Requirements 2 Paperback – March 26, 2003
Author: Visit Amazon's Karl Wiegers Page | Language: English | ISBN: 0735618798 | Format: PDF, EPUB
Download Software Requirements 2 – March 26, 2003
Posts about Download The Book Download Software Requirements 2 – March 26, 2003 for everyone book 4shared, mediafire, hotfile, and mirror link Without formal, verifiable software requirements⠠and an effective system for managing them⠠the programs that developers think they⠠ve agreed to build often will not be the same products their customers are expecting. In SOFTWARE REQUIREMENTS, Second Edition, requirements engineering authority Karl Wiegers amplifies the best practices presented in his original award-winning text?now a mainstay for anyone participating in the software development process. In this book, you⠠ll discover effective techniques for managing the requirements engineering process all the way through the development cycle⠠including dozens of techniques to facilitate that all-important communication between users, developers, and management. This updated edition features new case examples, anecdotes culled from the author⠠s extensive consulting career, and specific Next Steps for putting the book⠠s process-improvement principles into practice. You⠠ll also find several new chapters, sample documents, and an incisive troubleshooting guide. Discover how to: Set achievable expectations for functionality and quality NEW: Incorporate business rules into application development Employ use cases to discover user requirements Arrest creeping requirements and manage change requests NEW: Deal with requirements on maintenance, outsourced, and package solution projects Curb the impulse to ⠠gold-plate⠠ your programs NEW: Grow effective requirements analysts Cut revisions⠠and costs⠠dramatically Produce better software! No matter what kind of software you build, or what your role in the development process, SOFTWARE REQUIREMENTS, Second Edition, delivers expert guidance and field-tested techniques for engineering software
Done.
Books with free ebook downloads available Download Software Requirements 2 – March 26, 2003 Software Requirements 2 Software Requirements 2 enlarge Other Views Author Paperback Number Of Items 1 Dimensions in 7 5 x 1 5 x 9 Publication Date March 26 2003 ISBN Books Software Requirements 2 Paperback by Karl Wiegers Release Date March 26 2003 Software Requirements Paperback If You Enjoy Software Requirements 2 Paperback Software Requirements 2 amazon com book buy Publisher Microsoft Press 2 edition March 26 2003 Book or download Software Requirements 2 can be found Paperback 240 pages Publisher Software Requirements Practical Techniques for Gathering Software Requirements has 188 ratings and 15 reviews Paperback Second Edition 516 pages Published March 8th 2003 by Microsoft Press
Posts about Download The Book Download Software Requirements 2 – March 26, 2003 for everyone book 4shared, mediafire, hotfile, and mirror link Without formal, verifiable software requirements⠠and an effective system for managing them⠠the programs that developers think they⠠ve agreed to build often will not be the same products their customers are expecting. In SOFTWARE REQUIREMENTS, Second Edition, requirements engineering authority Karl Wiegers amplifies the best practices presented in his original award-winning text?now a mainstay for anyone participating in the software development process. In this book, you⠠ll discover effective techniques for managing the requirements engineering process all the way through the development cycle⠠including dozens of techniques to facilitate that all-important communication between users, developers, and management. This updated edition features new case examples, anecdotes culled from the author⠠s extensive consulting career, and specific Next Steps for putting the book⠠s process-improvement principles into practice. You⠠ll also find several new chapters, sample documents, and an incisive troubleshooting guide. Discover how to: Set achievable expectations for functionality and quality NEW: Incorporate business rules into application development Employ use cases to discover user requirements Arrest creeping requirements and manage change requests NEW: Deal with requirements on maintenance, outsourced, and package solution projects Curb the impulse to ⠠gold-plate⠠ your programs NEW: Grow effective requirements analysts Cut revisions⠠and costs⠠dramatically Produce better software! No matter what kind of software you build, or what your role in the development process, SOFTWARE REQUIREMENTS, Second Edition, delivers expert guidance and field-tested techniques for engineering software
Done.
Books with free ebook downloads available Download Software Requirements 2 – March 26, 2003 Software Requirements 2 Software Requirements 2 enlarge Other Views Author Paperback Number Of Items 1 Dimensions in 7 5 x 1 5 x 9 Publication Date March 26 2003 ISBN Books Software Requirements 2 Paperback by Karl Wiegers Release Date March 26 2003 Software Requirements Paperback If You Enjoy Software Requirements 2 Paperback Software Requirements 2 amazon com book buy Publisher Microsoft Press 2 edition March 26 2003 Book or download Software Requirements 2 can be found Paperback 240 pages Publisher Software Requirements Practical Techniques for Gathering Software Requirements has 188 ratings and 15 reviews Paperback Second Edition 516 pages Published March 8th 2003 by Microsoft Press
- Paperback: 544 pages
- Publisher: Microsoft Press; 2 edition (March 26, 2003)
- Language: English
- ISBN-10: 0735618798
- ISBN-13: 978-0735618794
- Product Dimensions: 7.5 x 1.5 x 9 inches
- Shipping Weight: 1.8 pounds (View shipping rates and policies)
- Amazon Best Sellers Rank: #422,435 in Books (See Top 100 in Books)
- #36 in Books > Computers & Technology > Computer Science > AI & Machine Learning > Expert Systems
- #65 in Books > Computers & Technology > Computer Science > AI & Machine Learning > Machine Theory
- #79 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Tools
How do you know if you have good software requirements? Some use the simple technique of checking if the requirements definition is complete, clear, and consistent. Every book on requirements engineering has some variation of this theme and in this book, you are advised to check if the requirements statement is complete, correct, feasible, necessary, prioritized, unambiguous, and verifiable.
If you haven't used techniques like this one before, it is definitely a good idea to pick up a solid book like this one on the best practices in requirements engineering. There are several good books in the market on the topic of software requirements and this is one of the best ones out there.
I found three other books that complement this one - Requirements Engineering by Kotonya and Sommerville (used more as a textbook), Managing Software Requirements by Leffingwell and Widrig (part of the Object Technology Series), and Effective Requirements Practices by Ralph R. Young (comes with a CD-ROM).
If you are a project manager, business analyst or anyone that has a lot to lose because of bad requirements, you will benefit tremendously from this current book being reviewed. The book is divided into three parts - What and Why, Development, and Management of Software Requirements. The part names are self explanatory. This book is very readable and is full of best practices that stand true to their name!
The unique things about this book - in chapter 2, the author outlines the Requirements Bill of Rights for Software Customers and the Requirements Bill of Responsibilities for Software Customers. When I first read this, I felt like every customer has to read this before attempting a software project.
In my opinion the hardest part about programming is gathering and analysing a complete, accurate and verifiable set of user requirements.
Unfortunately, good software requirements are also key to a project's success.
Those good at programming have laser-like focus and great analytical skills - usually traits associated those who are tend to be introverted / thinking and judging-oriented (cf. Myers-Briggs). Such people often find they have a tough when it comes time to gathering requirements e.g. listening and talking with users, understanding what they want, gaining their trust etc. - usually traits associated with those who are extroverted / feeling and perception-oriented.
As a person with some Introvert / Thinking and Judging tendencies, this book was the book that set me right and gave me a process I could follow and reference at any time during the requirements phase.
With the process and templates in place I can focus more on listening to what is being said and more importantly what is NOT being said (e.g. implicit or non-functional requirements)
The book is loaded throughout with best practices on
- Requirements Management (e.g. use change control)
- Project Management (e.g. manage requirement risks)
- Requirements Elicitataion (e.g. identify use cases)
- Requirements Analysis (e.g. create prototypes)
- Requirements Specification (e.g. Requirements traceability)
- Requirements Verification (e.g. Write test cases from requirements)
and so much more . . .
The book also contains some very helpful templates (e.g.
0 Response to "Download Software Requirements 2 – March 26, 2003"
Post a Comment
Note: Only a member of this blog may post a comment.