Object Design & Cohesion – Issue & potential refactoring

Abstract

Object Design & Cohesion – Issue & potential refactoring

Abstract

Object Design & Cohesion – Issue & potential refactoring

Abstract

Builder pattern inside interface. Bad design decision?

I am having trouble evaluating an implementation of the builder pattern I just came up with.

Builder pattern inside interface. Bad design decision?

I am having trouble evaluating an implementation of the builder pattern I just came up with.

Builder pattern inside interface. Bad design decision?

I am having trouble evaluating an implementation of the builder pattern I just came up with.

Builder pattern inside interface. Bad design decision?

I am having trouble evaluating an implementation of the builder pattern I just came up with.

Builder pattern inside interface. Bad design decision?

I am having trouble evaluating an implementation of the builder pattern I just came up with.

Does it make sense to use interfaces if you don’t have polymorphism?

Suppose I have distinct classes that have the same behavior, which can be represented like this:

Separation of concerns between objects

I have two objects which work together to provide interaction with HIDs on a machine. One object is responsible for the communication (read/write) to the HID and the other object is responsible for modelling the HID. Information is read and written to the HID as byte arrays.