architecture - Design Patterns: Do you use them in your projects? - Stack Overflow

architecture - Design Patterns: Do you use them in your projects? - Stack Overflow

How do you decide on which design pattern to choose for?

My approach to development projects has always been.

1. Take down business requirement.
2. Design the database.
3. Decide on technology (This decision is almost always driven by the client.)
4. Start developing a prototype.
5. Get prototype approved. (iterative)
6. Build the application.
7. Release for testing. (iterative)
8. Hand over for maintenance.

I am not sure where a design pattern would be useful.

Read full article from architecture - Design Patterns: Do you use them in your projects? - Stack Overflow