Abstract
The work is devoted to revision of Abstract Factory Pattern for its practical use in information system development. Provided variation of Abstract Factory Pattern signifi-cantly simplifies the process of information system development making the system more flexible, robust to change and maintainable.
Highlights
To reduce the resistance of the infrastructure we can introduce instead of huge number of methods one generic Create method which takes as a parameter an interface and returns an appropriate realization of that interface or throws an exception when it is not able to resolve the binding (Fig.3)
The collection of “interface - realization” bindings represented within the constructor defines the only one area of the class opened to change [7]
In case when we need to create an object produced by the first factory which is dependent on an object produced by the second factory, it would be better to resolve the situation by injecting factory responsible for creation of dependency object into the factory used to create dependent one
Summary
The suggested solution significantly reduces the resistance of the system to change making it highly flexible. Each time when we add new interface and its realization to the appropriate package(assembly) we do not need to correct the factory by adding new methods and correcting the logic within its constructor
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
