Design patterns indirection software#

Invent a new class that is solely responsible for saving objects. But the above solution leads to: Low Cohesion: database tasks not related to Sale High Coupling: Should Sale interface with database? Low Reusability: General task of saving to a database is one that other classes may share.Д¤ Instead, fabricate a new class, PersistentStorage What does Information Expert tell us to do? Assign this responsibility to the Sale class, since Sale has the data that needs to be saved.

Solution: Assign a highly cohesive set of responsibilities to вЂњmade up,вЂќ fabricated class-it does not need to represent a problem domain concept-in order to support high cohesion, low coupling & reuse.ДЇor NextGen POS, there is a requirement to save the Sale instances in a database.

Problem: you must assign a responsibility to a class, but assigning it to a class that already represents a problem domain entity would ruin its low coupling and/or high cohesion. Blank, Lehigh UniversityДў Pure Fabrication Another GRASP design pattern

Design patterns indirection software#

Larman, chapters 25 and 26 CSE432 Object-Oriented Software Engineering Glenn D. 1 Pure Fabrication and вЂњGang of FourвЂќ Design Patterns