Object-Oriented Analysis and Object-Oriented Design (from the 90s!) have all but disappeared. Their shortcomings are well-known (UML diagrams, anyone?), and the Method Wars, the Model-Driven Architecture disaster, and the Agile revolution all played a part in killing off these techniques. But surely there is a modern-day successor that tells us how to, well, structure our objects - right? Not really. We examine the good parts of OOA/OOD, the transition to data modeling, and show how you can use them to improve your architecture and design.

Target Audience: architects, developers
Prerequisites:basic OO knowledge
Level: Practicing

Extended Abstract:
DDD and its associated collaborative modeling techniques focus on processes, not objects. That's a bummer, as proper object modeling can have crucial impact on the architecture, enhance our understanding of the domain, enable cross-context communication, and anticipate future requirements. Even better, using immutable data instead of objects and using the techniques of functional programming and design recipes to structure that data improves architectural flexibility and clarity of semantics.