> View this now

Published on: October 21, 2009
Type of content: VIDEO
Format: Unknown
Price: FREE

Overview:
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:

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.