The dynamic factory pattern

Abstract

The DYNAMIC FACTORY pattern describes how to create a factory that allows the creation of unanticipated products derived from the same abstraction by storing the information about their concrete type in external metadata. ContextA software system uses a framework (a set of classes that embodies an abstract design for solutions to a family of related problems, and supports reuse at a larger granularity than classes [JF98]), where collaborations between high-level abstractions determine the execution flow.Individual solutions are created by extending existing classes and combining these extensions with other existing classes [Foote88]. The configuration of these combinations of implementers of abstractions should be done without the need of modifying the application.New implementations of the established abstractions can be created by as long as they conform to established protocols. The system should be able to inject these new abstractions into the framework without the need to modify its core. These new abstractions can be created after the system has been delivered. ExampleA workflow system has a rule evaluation module. Each rule implements a well defined interface, and is injected into a container that evaluates it. The rules can be simple or composite (using the COMPOSITE [GoF95] and INTERPRETER [GoF95] patterns) allowing the creation of complex expressions by composing finer-grained elements.The creation of the rules is delegated to a factory that has a standard interface for creating instances of the abstractions. The clients of the rules request an instance of the rule and the factory provides it.The workflow system vendor supplies a fixed set of rules. New rules could be added by simply implementing the rule interface. The problem comes at rule instantiation, since the factories that contain the logic for creating instances of the rules may need to be modified to support new types of rules.

PhageScanner, a flexible machine learning pipeline for automated bacteriophage genomic and metagenomic feature annotation

“…The feature extraction segment of the pipeline allows end-users to experiment with various feature extraction techniques commonly applied for PVP identification and other protein-focused models [13]. In PhageScanner, we employ a factory design pattern [25], a software design approach that facilitates the simple combination of different extracted features into a more comprehensive feature vector. In essence, each feature method extracts a specific feature from the provided protein, and the resulting feature vectors are subsequently concatenated to form a more extensive vector (Equation 1; see S1 Text for feature descriptions).…”

A framework for processing large scale geospatial and remote sensing data in MapReduce environment

“…1. AEGIS provides the possibility to control the realization of the geometries using metadata, as in case of the dynamic factory pattern [33].…”

Επίδραση Των Προτύπων Σχεδίασης Στην Ποιότητα Λογισμικού

“…Επιπλέον, στο[168], οι συγγραφείς παρουσιάζουν μια συζήτηση πάνω σε μια παραλλαγή του προτύπου σχεδίασης Επαναλήπτης (Iterator). Τέλος, στο[206], εισάγονται εναλλακτικές για τη δημιουργία αντικειμένων, όμοια με το Abstract Factory.2.1 :Ποια είναι η ένταση της ερευνητικής δραστηριότητας στον τομέα των μεθόδων τεχνολογίας λογισμικού για παιχνίδια ηλεκτρονικών υπολογιστών;RQ 2 :…”