11 September 2009

Design patterns

Up until about a year ago I had never heard of Design Patterns.  I learned about it shortly after I joined a team and the techies were in the process of  'interviewing' me.

In the time since then I have noticed many PMs and BAs I have spent with are unfamiliar with the term and concepts behind it.  No surprise really, as I had worked with I.T. projects for over 10 years as a 'business' oriented person, and I never got invited into the programmer's library.  Why should I expect everyone else has?

What is a Deign Pattern?  It is what it sounds like. I'll not go into detail explaining it, but will instead provide a short reading list.  Let' start with Wikipedia.
Patterns particularly relevant to me
Image care of Penguin & Fish cc at Flickr

6 comments:

  1. There is 'Analysis pattern' book that may be more relavent for business analysts.

    Analysis Patterns: Reusable Object Models by Martin Fowler

    I got taught design pattern in uni (did a computer science degree) and when I got a businss analyst job I wanted to find something similar and found this.

    ReplyDelete
  2. Reminds me of my Information Engineering days where it became apparent to me, after coming up with a number of high level conceptual data models, that there are repeating concepts that tend to correspond to various subject areas. Having done more and more models has resulted in the identification of repeating and predictable designs. The trick, at the end of the day, is not in knowing that the models are predictable but rather in the ability to identify them well in advance in order to cut down design and development times.

    ReplyDelete
  3. Yuan - what did you thnk about the Fowler book?

    ReplyDelete
  4. I don’t know how, but this is something I’ve honestly never heard of – so I’m looking forward to learning / reading more and implementing some of the techniques. What link do you see between design patterns and SCRUM/Agile methodologies?

    ReplyDelete
  5. Gabriel

    I think the idea around planning as you go and forgoing up front planning is relative to your ability to hit a problem and deal with it on the run.

    If you aren’t familiar with the problem domain you’ll need to think about it up front to a greater degree. This goes for business problem domains as much as technical ones.

    Patterns are a shortcut to problem solving that come augment a person’s natural accumulation of experience.

    That’s my thinking.

    Craig

    ReplyDelete
  6. I have read your blog it is very helpful for me. I want to say thanks to you. I have bookmark your site for future updates. free printable wall art

    ReplyDelete

Search This Blog