Ruby Midwest 2011 - Keynote: Architecture the Lost Years by Robert Martin

Caption notes

At Ruby Midwest 2011, Robert C. Martin starts with a Rails project’s directories and asks why they reveal the framework before they reveal what the application does. He proposes organizing the application around use cases and letting its rules interact with web and database details across boundaries. In his FitNesse account, the team kept developing with temporary in-memory storage and later files, adding a database option when an actual requirement arose. The example explains what he means by deferring decisions: establish the behavior the application needs while keeping implementation options open. He also distinguishes direct tests of business rules from a smaller set of acceptance tests through the UI. This guide follows his spoken account. Code, diagrams and project results await independent verification.