Practical Software Requirements: A Manual of Content and Style
Kovitz, Benjamin L
Sold by KuleliBooks, Phoenix, AZ, U.S.A.
AbeBooks Seller since June 11, 2021
Used - Soft cover
Condition: Used - Good
Quantity: 1 available
Add to basketSold by KuleliBooks, Phoenix, AZ, U.S.A.
AbeBooks Seller since June 11, 2021
Condition: Used - Good
Quantity: 1 available
Add to basketThe book may have minor cosmetic wear (i.e. creased spine/cover, scratches, curled corners, folded pages, minor sunburn, minor water damage, minor bent). The book may have some highlights/notes/underlined pages - Accessories such as CD, codes, toys, may not be included - Safe and Secure Mailer - No Hassle Return.
Seller Inventory # 521YH0000988
An extensive style section addresses the detail of making information understandable focusing on how to group and sequence topics, writing definitions, and how to avoid boring the reader. Filled with examples this title should be considered required reading BEFORE graduation!" -- CompBookReview.com, October 99
"It takes an outstanding writer to bring an unexciting topic to life, and in this era of hype-ridden tomes about Java, open source software, Microsoft lawsuits, Year 2000, and .com "best practices," I was frankly skeptical about staying awake through a book on software requirements. However, Kovitz pulled it off in a way that's thorough as well as captivating, with copious examples." -- Alan Zeichick for Software Development, July, 1999
"Kovitz presents a very different view of requirements engineering from the prevailing view. I found the book to be quite excellent. This is quite a refreshing view. In addition, the author has an online discussion forum where readers can ask questions and receive direct help from the author. I found this to be an excellent resource, and the author is to be commended for such participation and dedication." -- Slashdot.org, October 99
"Kovitz starts by demolishing "the myth of functional decomposition" (which is actually the title of Section 1.1). As he points out, a good engineer is one who knows a lot about problems that have been solved in the past, and can use that knowledge to figure out which of those proven solutions should be applied to the present problem. Defining a problem's requirements is therefore really about gathering the information needed to choose, and customize, a solution (or set of solutions).
All of this is good stuff, and I learned quite a bit from the first few chapters of this book -- especially Chapter 5, which describes five common kinds of problems, and the sorts of questions that a requirements document should answer for each." -- Gregory V. Wilson for Dr. Dobb's Journal, August, 1999
Kovitz has written a fresh, lively, honest, funny, and provocative book on a serious engineering topic.... -- Ian Alexander's Reviews of Books on Requirements Engineering
The book is well organized, literate, and readable...a delightful discovery. -- ACM Computing Reviews
"About this title" may belong to another edition of this title.
We guarantee the condition of every book as it's described on the Abebooks web
sites. If you're dissatisfied with your purchase (Incorrect Book/Not as
Described/Damaged) or if the order hasn't arrived, you're eligible for a refund
within 30 days of the estimated delivery date. If you've changed your mind about a book that you've ordered, please use the Ask bookseller a question link to contact us and we'll respond within 2 business days.
Order quantity | 5 to 14 business days | 3 to 6 business days |
---|---|---|
First item | US$ 4.21 | US$ 8.99 |
Delivery times are set by sellers and vary by carrier and location. Orders passing through Customs may face delays and buyers are responsible for any associated duties or fees. Sellers may contact you regarding additional charges to cover any increased costs to ship your items.