Featurewise

Featurewise Organisation

A book in development. These are its provisional contents, and they'll change as it's written.

  1. 0
    Introduction

    What featurewise organisation is, and the two claims the book makes about what follows from it.

  2. 1
    Features

    A feature is a whole job the stakeholders would recognise. Features come in three families, and their outputs in result cases.

  3. 2
    Anatomy of a service

    Features, the model, facilities and entrypoints: ports and adapters under other names, with one real difference.

  4. 3
    Links

    A feature's input is a link, so the core can offer the next step itself, and the service gets good manners.

  5. 4
    One way to build a UI

    The back end and the front end the book's demos use.

  6. 5
    What we need from the UI

    A generic UI is already usable. The UI's job is to make it good, feature by feature.

  7. 6
    Hypermedia idioms

    Patterns of features and links, each a classic usability principle decided once, in the core.

  8. 7
    Front ends

    Every caller gets the service's usability: a generic UI, a hand-made one, an agent.

  9. 8
    A real project

    A passport office, built featurewise from the start.

  10. 9
    Stories

    Features as the building blocks of the stories we tell about a system.

  11. 10
    Service boundaries

    Where one service ends and the next begins.

  12. 11
    Who's calling?

    A service's callers, and whether any of them is choosing.

  13. 12
    Featurewise organisation and coding agents

    Why the practice suits software written with agents.

  14. A
    The principles document

    The rules a featurewise service is built by, ready to copy.

  15. B
    Other platforms

    Featurewise organisation beyond .NET.

  16. C
    Drawing a service

    How the book's diagrams are drawn from the code.