Since the application handles detailed information about cricket matches, constructing objects like TableBatsman and TableBowler, which contain multiple properties and settings, can become complex. The Builder pattern provides a structured way to handle this complexity. Attached UML diagram.
Positive Consequences:
- Allows you to build complex objects in a custom way, facilitating the creation of instances with specific and optional values.
- Decouples the construction process from the internal representation of the object, allowing changes to the internal structure without affecting the construction.
Negative consequences:
- Introduces complexity by creating additional interfaces and classes, which could make the code difficult to understand.
Since the application handles detailed information about cricket matches, constructing objects like TableBatsman and TableBowler, which contain multiple properties and settings, can become complex. The Builder pattern provides a structured way to handle this complexity. Attached UML diagram.
Positive Consequences:
Negative consequences: