Filed Under (Methodology) by jonr on November-15-2008

Corner-Case-Driven-Development is an exciting version of development where all extreme corner cases are highlighted each step of the way.  It is especially important to interject a corner-case once someone starts to talk about the fundamental features of the system, as getting distracted by the core things, like what a user wants to accomplish, is a no-no in the corner-case methodology.  When embracing corner-case-driven-development, a team can expect a number of exciting things to happen, including: difficulty developing and maintaining the code, un-met deadlines, and generally low team morale.

Read about more exciting methodologies here: http://www.scottberkun.com/blog/2007/asshole-driven-development/.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • DZone
  • Digg
  • del.icio.us
  • Reddit
  • Facebook
  • LinkedIn

Comments:
Stu Stern on November 16th, 2008 at 1:16 pm #

Another favorite is Conceivable-Case-Driven development where time is spent analyzing and developing for every conceivable case that could arise in the future. Favorites include “What if we someday we want to use a non-SQL database?”, “What if we need to access the system from an iPhone?” and “What if volumes grow to 100X the maximum we currently anticipate?”.

Post a comment
Name: 
Email: 
URL: 
Comments: