Object Oriented anti patterns

Question 1

Anemic Domain model

Answer 1

The use of the domain model without any business logic. The domain model’s objects cannot guarantee their correctness at any moment, because their validation and mutation logic is placed somewhere outside (most likely in multiple places). Martin Fowler considers this to be an anti-pattern, but some disagree that it is always an anti-pattern

Question 2

Constant interface

Answer 2

Using interfaces to define constants

Question 3

Circular dependency

Answer 3

Introducing unnecessary direct or indirect mutual dependencies between objects or software modules

Question 4

God object

Answer 4

Concentrating too many functions in a single part of the design (class)

Question 5

Sequential coupling

Answer 5

A class that requires its methods to be called in a particular order