1. May 3rd, 2006

    10 Approaches to Software Design

    Architecture Driven Design: If we abstract the problem definition, and do a mile-high view of the solution, we can make it work.

    Consumer Driven Design: Assume all people are stupid …

    Customer Driven Design: We believe it’s best to solve one problem at a time.

    Enterprise Driven Design: … but only if it leverages our core competency to maximize our bottom line.

    Language Driven Design: It won’t scale! You need to use Java.

    Outsource Driven Design: There’s no problem too big or too complex.

    Pundit Driven Design: No I can’t do it myself, but how hard can it be?

    Resume Driven Design: I can’t find that tool you were talking about on Monster.com.

    Test Driven Design: I test therefore I code.

    Web Driven Design: It works for Amazon.

      Which group are you in?Update: (I forgot to copy this from the draft) Examples in the wild.

    Printable PDF | Posted by Assaf Filed in general 2 Comments »

    1. May 4th, 2006

      Daniel

      > It won’t scale! You need to use Java.
      Shouldn’t that be part of Enterprise driven design? Everyone knows that it’s not Enterprise unless it’s Java. Although admittedly .NET is encroaching on Java’s share of the Enterpriseyness market.

    2. May 4th, 2006

      Assaf

      .Net is a real threat!

      Microsoft did well by focusing it on one language, providing a lot of PPTs for architecture driven design, and as we all know it plays well (at least here) with resume driven design.

      And just in time when outsource driven design is picking up steam.

    Your comment, here ⇓