What do you think?
Rate this book
Requirements Writing for System Engineering
What You Will Learn Audience
Writing Requirements teaches you to write requirements the correct way. It is targeted at the requirements engineer who wants to improve and master his craft. This is also an excellent book from which to teach requirements engineering at the university level. Government organizations at all levels, from Federal to local levels, can use this book to ensure they begin all development projects correctly. As well, contractor companies supporting government development are also excellent audiences for this book.
Writing Requirements teaches you to write requirements the correct way. It is targeted at the requirements engineer who wants to improve and master his craft. This is also an excellent book from which to teach requirements engineering at the university level. Government organizations at all levels, from Federal to local levels, can use this book to ensure they begin all development projects correctly. As well, contractor companies supporting government development are also excellent audiences for this book.
- GenresSoftware
424 pages, Paperback
Published October 20, 2016
8 people are currently reading
17 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 2 of 2 reviews
July 7, 2019
good book
November 16, 2016
This is a very good overview of the job of a full-time requirements engineer.
It covers everything you will need to know in order to build anything in the traditional waterfall method. It will also give you some ideas on bringing in some more modern alternatives to the traditional requirements document.
Requirements writing in the world of software building has changed significantly over the last few years and what the book lacks is the framework to identify when certain methods/models are more suitable for others. I'm not a fan of books that prescribe something without at least telling what it is good at and when NOT to use it as there are better options. Mr Koelsch has spent years doing this and besides a very brief discussion on the topic does not, in fact, cover the BIG WHYs.
Considering the objective of the book, I expected more concise wisdom and fewer personal anecdotes. I'd I've written the book backwards as I prefer to understand why I should do something, how to make the right decision and then the rest of the book, broken into how to do it with all the required tips and tricks of the trade.
It covers everything you will need to know in order to build anything in the traditional waterfall method. It will also give you some ideas on bringing in some more modern alternatives to the traditional requirements document.
Requirements writing in the world of software building has changed significantly over the last few years and what the book lacks is the framework to identify when certain methods/models are more suitable for others. I'm not a fan of books that prescribe something without at least telling what it is good at and when NOT to use it as there are better options. Mr Koelsch has spent years doing this and besides a very brief discussion on the topic does not, in fact, cover the BIG WHYs.
Considering the objective of the book, I expected more concise wisdom and fewer personal anecdotes. I'd I've written the book backwards as I prefer to understand why I should do something, how to make the right decision and then the rest of the book, broken into how to do it with all the required tips and tricks of the trade.
Displaying 1 - 2 of 2 reviews