Design Patterns -- part 2
Criticism about Design Patterns:
Failed to provide clear criteria for when to use what pattern, and
explain the criteria for the rules or choices (such as cost/benefit analysis of
find & change costs or something from Category Metrics).
Focused mostly on Systems Software, mostly ignoring database and Crud Screen-centric applications.
Usage of Design Patterns:
Design patterns have two
usages in Software development lifecycle:
1. Providing common platform for developers using
standard terminologies and are specific to particular scenario. For example, a
prototype design pattern will be creating a prototype design which creates
clone of actual object to be used in the program.
2. Learning these design patters helps inexperienced developers to learn software development in a fast and easy way. These design patterns are being used from longer period of time and provide best solution to maximum of the problems in programming.
Comments
Post a Comment