CSC/ECE 517 Fall 2010/ch7 7c DF: Difference between revisions
| Line 1: | Line 1: | ||
'''Pure Fabrication pattern''' | '''Pure Fabrication pattern''' | ||
== Introduction == | == Introduction == | ||
The GRASP design patterns suggest methods in which the responsibilities of a system can be distributed amongst classes. One of these is the pure fabrication principle, which guides the creation of classes that are not directly represented within a system's problem domain. Pure fabrication indicates that such extra classes should be created when there are responsibilities that do not fit well within any objects. By fabricating these extra classes, the designer is able to maintain a higher level of cohesiveness with less coupling than would be the case if the responsibilities were relegated only to the classes directly related to the problem domain. | |||
== Role in Doman Driven Design == | == Role in Doman Driven Design == | ||
Revision as of 03:04, 1 December 2010
Pure Fabrication pattern
Introduction
The GRASP design patterns suggest methods in which the responsibilities of a system can be distributed amongst classes. One of these is the pure fabrication principle, which guides the creation of classes that are not directly represented within a system's problem domain. Pure fabrication indicates that such extra classes should be created when there are responsibilities that do not fit well within any objects. By fabricating these extra classes, the designer is able to maintain a higher level of cohesiveness with less coupling than would be the case if the responsibilities were relegated only to the classes directly related to the problem domain.
Role in Doman Driven Design
Usage
References
http://en.wikipedia.org/wiki/Domain-driven_design
http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)
http://en.wikipedia.org/wiki/Service_(systems_architecture)
http://en.wikipedia.org/wiki/Service-oriented_architecture
http://www.ibm.com/developerworks/webservices/library/ws-soa-design1/