9:00am Matthew Woodward - Building Sustainable Software with Frameworks

The first step towards recovery is admitting there is a problem. Nearly 80% of projects fail in some way.

What is sustainable software? It meets the needs of current generation without compromising the needs of future needs.

There is a good book by Kevin Tate, Sustainable development an agile perspective.

What are we trying to build?

In order to react to change and evolve over time, software should not be thought of as a building but more as an ecosystem.

Software that is built as an ecosystem is able to be modified and get better rather than it make the software worse.

Not - Death spiral projects, where you work harder and harder marching toward the project doom.

Key Points: · Working Product at all times. o Always be ready to ship what is there o Build most important features first o Continual refinement o Refactor agressivly o Write the best code you can · Fix then code (not code then fix) o Defect prevention o Test Driven Development o Test as you go · Have high standards and hold all team members to them. o Coding standards and guidelines o Development Standards · Build what the customer needs. o Use UI Prototypes · Zero tolerance for defects · Replan often o Continuous integration o Don't neglect performance · Team Culture o Leadership at all levels o Visionary and Tactical Approach o Colaborative Working o Be risk aware o Continually improving and learning

An OO Based MVC framework encourages good development practices and has low impact maintenance where things can easily be changed.

Your model should be unaware of the framework. An example is the MAX Blog, which has MachII, Model-Glue, and Fusebox.

Well designed objects are easier to maintain than procedural code.

Each object should only do one thing.

Loose coupling allows low impact between objects.

XML configuration can be reviewed to see the whol overview of the application.

There should be three layers. View, Service Layer, Model.

Every kludge increases technical debt, and one day the debt will have to be paid.

Don't write throwaway code.