
Writing Great Specifications
Kamil Nicieja · 2018
Programming and computer science › Software design and clean code
#10,570 most recommended
Hacker News
3
mentions by 3 people · top 64% of 15,732 books
Open Library
—
No ratings yet
1 want to read
Wikipedia
—
No article yet
About the book
A practical guide to writing software specifications, meaning the requirements that describe what a system should do before and during its development. It covers how teams gather, write, and maintain these requirements so that developers, testers, and business stakeholders work from the same understanding. Vague or abstract requirements cause misunderstandings, rework, and defects, and concrete examples make requirements precise enough to act on. The book argues that specifications should be written collaboratively and kept close to the software, so that they can be checked automatically and stay current. It presents example-driven practices, in the spirit of specification by example and behaviour-driven development, as a way to reduce ambiguity and align teams.
Written by Claude from what it knows of this book.
What Hacker News says 100% recommend · 0% critical
In the commenters’ own words
It can be difficult to wrangle Gherkin. I've tried to use "Writing Great Specifications" as a kind of guide. Reducing specs to (mostly) one each of Given…
I think you have to formalize the process first. If everyone in the company does something different every time a requirements doc is written, it is just…
What Open Library readers say
No Open Library reader has rated it yet.
- 1 want to read
- 0 reading
- 0 have read
What critics say, via Wikipedia
No Wikipedia article about this book yet, so no critics to quote.
Reddit communities — coming later
Details
- First published
- 2018
- ISBN
- 9781617294105
- Editions known
- 2 at Open Library
- Open Library
- OL19541960W
Communication of technical informationComputer software, developmentComputer software, testing
Read next: its neighbours on the mosaic
Specification by exampleGojko Adzic · 2011 · recommended by 2 people · similar by subject and what people say about it
Writing Effective Use CasesAlistair Cockburn · 2000 · recommended by 4 people · similar by subject and what people say about it
Principles of program designM. A. Jackson · 1975 · recommended by 4 people · loosely similar by subject
Your Code as a Crime SceneAdam Tornhill · 2015 · recommended by 12 people · loosely similar by subject
Software inspectionTom Gilb · 1993 · recommended by 1 person · similar by subject and what people say about it
Testing computer softwareCem Kaner · 1988 · recommended by 2 people · similar by subject and what people say about it
Software requirements & specificationsMichael J. Jackson · 1995 · recommended by 2 people · similar by subject and what people say about it
Piloting PalmAndrea Butter · 2001 · recommended by 3 people · loosely similar by subject
Test-driven developmentKent Beck · 2002 · recommended by 30 people · similar by subject and what people say about it
Developing quality technical informationGretchen Hargis · 2004 · recommended by 3 people · similar by subject and what people say about it
Antinet ZettelkastenScott Scheper · 2022 · recommended by 2 people · loosely similar by subject
XUnit Test PatternsGerard Meszaros · 2007 · recommended by 5 people · similar by subject and what people say about it
Writing solid codeSteve Maguire · 1993 · recommended by 18 people · similar by subject and what people say about it
The Best Software Writing IJoel Spolsky · 2005 · recommended by 4 people · similar by subject and what people say about it
Effective Software TestingMauricio Aniche · 2022 · recommended by 2 people · similar by subject and what people say about it
Docs for DevelopersJared Bhatti · 2021 · recommended by 4 people · similar by subject and what people say about it
The RSpec BookDavid Chelimsky · 2010 · recommended by 8 people · similar by subject and what people say about it
Sweating BulletsRobert Gaskins · 2012 · recommended by 8 people · loosely similar by subject
Software RequirementsKarl Eugene Wiegers · 1999 · recommended by 2 people · similar by subject and what people say about it
Shipping greatnessChris Vander Mey · 2012 · recommended by 3 people · similar by subject and what people say about it
Lessons learned in software testingCem Kaner · 2001 · recommended by 4 people · similar by subject and what people say about it
Software CraftsmanshipPete McBreen · 2001 · recommended by 4 people · similar by subject and what people say about it
Better Embedded System SoftwarePhilip Koopman · 2010 · recommended by 2 people · similar by subject and what people say about it
The Software CraftsmanSandro Mancuso · 2014 · recommended by 9 people · similar by subject and what people say about it