We did something like DDD: - we did the ubiquitous language part, working with clients to arrive at consistent, particular language to describe the problem -

We did something like DDD: - we did the ubiquitous language part, working with clients to arrive at consistent, particular language to describe the problem - we then made a big chart of things and their relationships; get clients to sign off this describes problem - but we didn’t bother with any formal steps passed that; we just took the chart as a systems diagram and implemented that There’s some deep sense in which any program which encodes the chart is a type embodying the semantics of the chart, viewed as a categorical diagram. So it’s not too surprising this works out alright. I think the ubiquitous language part of DDD is great; I’m not sure it has much to say about turning domain diagrams into software.