[ Read E-pub ] ☯ Software Requirements: Practical Techniques for Gathering and Managing Requirements Throughout the Product Development Cycle ♾ MOBI eBook or Kindle ePUB free

Been a BA for about 20 years Best book on this topic I have read If I was teaching a class on the documentation artifacts that a BA uses in a typical waterfall style SDLC this would be THE book If you are not looking for that topic in particular this book might be a 4 or possibly even 3 stars.First the good things Excellent discussion and overview of all the major requiremetns documentation artifacts that are used today Covers not only the documents but tries to also cover the why behi Been a BA for about 20 years Best book on this topic I have read If I was teaching a class on the documentation artifacts that a BA uses in a typical waterfall style SDLC this would be THE book If you are not looking for that topic in particular this book might be a 4 or possibly even 3 stars.First the good things Excellent discussion and overview of all the major requiremetns documentation artifacts that are used today Covers not only the documents but tries to also cover the why behind you should do these documents requirements management and traceability for example Too often BAs tend to fall into the follow the template and churn out a document trap, it is alwas good to step back and think a bit about why we do what we do Gives sample templates to illustrate what he is saying Covers the SDLC from the start for things like vision statement and scope.Now the not quite so good things I found the preaching about the need for good requirements misplaced While valuable and important I would assume anybody who plunks down money for this book and then wades through the 500 pages is already motivated on this topic The style is a bit academic and theoretical This is not a good how to book, it is a valuable reference I did not find the book that helpful for understanding when something is not so good as a tool For example you will read things like Don t try to force every requirement you encounter into a use case And lots of descriptions of what a use case does well but I think some examples of where it does not work well would be helpful This pretty much assumes a standard waterfall style SDLC approach It is a bit dated and not helpful for, say, an agile methodology using stories If you are looking for a nice quick easy to read summary this is not the book you want The book is trying to cover a lot and so it does not adequately cover everything in detail If you are looking for specific information to get better on a particular topic, like a use case, get a book on use cases Easy to read Not at all boring. Has many important points on requirements development and capture But I feel that it could beconcise. Definitely a must read for any beginner Business Analyst The book well structured and informative, and very practical Improved a lot in my BA processes after reading it P S Very very long and boring [ Read E-pub ] ♪ Software Requirements: Practical Techniques for Gathering and Managing Requirements Throughout the Product Development Cycle ☳ 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 Great introduction to the software requirements process Would recommend to anyone who is working on software development in any capacity development, project management, testing, etc. Great choice as your first in BA The only reason to read this book is for people who want to get impression of what Business Analysts do But, first two chapters would be enough The rest of the book is devoted to making rocket science out of simplest concepts If a junior BA is not an idiot with below avg IQ, he she would find it all out in the heat of the battle without much risk. Actually read V3 I consider the book in the must read category for business and system analyst Apart from BABOK this one ispractical. I m new to requirements analysis business analysis, but not new to tech I m a career tech writer who was hired to write documentation and requirements, the only person in either role at a small company I needed somethingthan the Pragmatic Institute training I was sent to and somethingthan the agile party line on requirements document requirements as you go and just enough, not too much less isunless it s not enough After reading this cover to cover, it s geared mainly a I m new to requirements analysis business analysis, but not new to tech I m a career tech writer who was hired to write documentation and requirements, the only person in either role at a small company I needed somethingthan the Pragmatic Institute training I was sent to and somethingthan the agile party line on requirements document requirements as you go and just enough, not too much less isunless it s not enough After reading this cover to cover, it s geared mainly at new RAs BAs and has pretty much everything you need to know to start writing traditional software requirements or agile requirements, or reqs that fall somewhere in the middle Later chapters also deal with process improvement analysis improvement strategies so I imagine it would also be helpful to experienced RAs BAs With lots of scenarios and example projects each ch starts with an anecdote for an example project it is a bit inflated but I skimmed or skipped some of that stuff The book comes with sample documents supplemental material available online from the publisher, which is incredibly handy