File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Agile and Other Processes and the fly likes Implementation Patterns: When to apply patterns? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Implementation Patterns: When to apply patterns?" Watch "Implementation Patterns: When to apply patterns?" New topic

Implementation Patterns: When to apply patterns?

victor pereira

Joined: Mar 10, 2004
Posts: 3
Hi Kent!
Head First Object Oriented Analysis & Design some times say that design patterns are applied at the implementation phase of software development. Head First Design Patterns say that design patterns can be applied at any phase(as I understood: analysis, design, implementation ). I agree, partially, with both. In my humble opinion, some times it is difficult to decide when. Does your book help us clarify moment that we can implent patterns?
Kent Beck
Ranch Hand

Joined: Nov 07, 2003
Posts: 45
Dear Victor,

Finding the right time to make a decision is as important a skill as knowing how to make the decision. Too much too early and you delay feedback and give yourself a design you have to work around. Too little too late and you start to sink in complexity. Implementation Patterns doesn't address the timing of using patterns thoroughly. The patterns are all intended to be used at coding time. However, I am sure the book contains some of my bias towards deferring decisions until I am certain. I use this strategy whether I am working with architectural, analysis, design, implementation, or optimization decisions.


Kent Beck
Three Rivers Institute

Author of <a href="" target="_blank" rel="nofollow">JUnit Pocket Guide</a>
I agree. Here's the link:
subject: Implementation Patterns: When to apply patterns?
It's not a secret anymore!