Featurewise Organisation
A book in development. These are its provisional contents, and they'll change as it's written.
- 0Introduction
What featurewise organisation is, and the two claims the book makes about what follows from it.
- 1Features
A feature is a whole job the stakeholders would recognise. Features come in three families, and their outputs in result cases.
- 2Anatomy of a service
Features, the model, facilities and entrypoints: ports and adapters under other names, with one real difference.
- 3Links
A feature's input is a link, so the core can offer the next step itself, and the service gets good manners.
- 4One way to build a UI
The back end and the front end the book's demos use.
- 5What we need from the UI
A generic UI is already usable. The UI's job is to make it good, feature by feature.
- 6Hypermedia idioms
Patterns of features and links, each a classic usability principle decided once, in the core.
- 7Front ends
Every caller gets the service's usability: a generic UI, a hand-made one, an agent.
- 8A real project
A passport office, built featurewise from the start.
- 9Stories
Features as the building blocks of the stories we tell about a system.
- 10Service boundaries
Where one service ends and the next begins.
- 11Who's calling?
A service's callers, and whether any of them is choosing.
- 12Featurewise organisation and coding agents
Why the practice suits software written with agents.
- AThe principles document
The rules a featurewise service is built by, ready to copy.
- BOther platforms
Featurewise organisation beyond .NET.
- CDrawing a service
How the book's diagrams are drawn from the code.