Avoiding Over and Under Design

Error message

  • Strict warning: Declaration of role_expire_handler_field_rid::pre_render() should be compatible with views_handler_field::pre_render(&$values) in require_once() (line 83 of /home2/netobje2/public_html/sites/all/modules/role_expire-7.x-1.0-beta2/role_expire/role_expire.views.inc).
  • Strict warning: Only variables should be passed by reference in eval() (line 3 of /home2/netobje2/public_html/modules/php/php.module(80) : eval()'d code).

2:00pm-3:15pm. Thursday, October 13
The question of how much design to do up-front on a project is an engaging one. Too much design often results in overkill, complexity, and wasted work. Too little design results in insufficient system structures that require rework, additional complexity, and wasted effort. How can we know what the right balance is? Alan Shalloway shows how to use the advice from Design Patterns coupled with the attitude of not building what you don’t need from Agile. The trick is in discovering what you don’t know, how it may affect you, and then how to isolate these risks in your code in a simple manner. Alan describes the essence of Emergent Design – that is, starting with a simple design and letting it evolve as the requirements evolve. He also demonstrates how to refactor to better designs and how this is different from refactoring bad code.

Back to the Essential Agile Development Practices | The Net Objectives at Microsoft Conference Series page.

All the Details

Type:
Presentation
Published:
Thursday, October 13, 2011
Length:
1 hour
Author:
Topics: