This resource is no longer available

Just Enough Early Architecture to Guide Development


With the domain modeled, basic requirements gathered, a development team rarin' to get going... Now what? How do you ensure that each developer is coding the bits the same way? That is, how do you keep from getting multiple persistence mechanisms, or different ways to handle the User Interface-to-server communication?

This session is designed to help you capture the best architecture/technical solutions and ensure that they are repeated by all developers. By tackling the architecture up-front in a serial manner, subsequent parallel development will be much more manageable and predictable. In addition, a consistent approach allows bolting on other techniques (like test harnesses, unit tests) to help make development easier as time goes on. Consistency also lends itself to refactoring, to extending the app, to changes in requirements.

In this session architects and developers learn:

  • The techniques used to help ensure consistency across an application;
  • The benefits of consistency across development team members, such as the ability to add on other techniques to make development easier as time goes on;
  • What the pitfalls look like when members of the development team have too much flexibility in implementation details.
  • Why this session delivers specific time-saving/cost-cutting expertise: Development lifecycle professionals typically spend 50 percent or more in application architecture and design before a line of code is written. In a time when it is vital to build and deploy mission-critical applications as quickly as possible, no team can be taking months simply drawing diagrams and debating design approaches. Agile development expert Jon Kern tells you the minimum amount of architecture needed in order to get moving forward on essential development projects. This approach to application development can save months of effort and hundreds of thousands of dollars in development costs, in addition to getting revenue-producing or money-saving applications into production months earlier.


    Jon Kern Co-author, The Agile Manifesto; Software Architect and Agile Manifestor, Immuexa Outspoken software engineering evangelist, Agile Manifesto co-author, speaker, and author, Jon Kern's experience is wide-ranging across varied problem domains and technology platforms. From jet engine R&D (he's an aerospace engineer, after all) to real-time flight simulator design and development, from TogetherSoft's and OptimalJ's commercially successful modeling tools, to building IBM's Manufacturing Execution System software - Jon has seen and done a lot. In September 1999, Jon joined Peter Coad to help launch TogetherSoft. Jon was a driving force behind the success of the company and its products prior to its sale to Borland. Jon's a nut when it comes to modeling effectively (focused on the business), building and architecting consistently, and doing it in an agile manner to deliver results. John co-authored Java Design (2ed) with his long-time mentor, Peter Coad. Currently Jon helps teams and companies succeed in developing projects and agile teams.
    Oracle Corporation
    21 Oct 2009

    This resource is no longer available.