0

I have been trying to learn about DCI (Data Context Interaction) (http://tidyjava.com/dci-architecture-visionary/)

It seems to me that 'roles' can be simulated by creating derived classes which inherit from a base class and have access to all the private members. Is that a reasonable statement?

Alternatively, could this be regarded as too much infrastructure? I mean, DCI seems to be about separating actions from classes. Isn't that just good ol' C, where you have functions that operate on structures?

blippy
  • 1,490
  • 1
  • 13
  • 22

1 Answers1

0

The difference between DCI objects and structs is explained early in the page you link:

The major difference between DCI‘s data object and a typical entity is that the data object is relatively stupid. It’s not anemic. It can still contain important domain methods that would preserve it’s invariants etc.

What that means is that classes still may contain the necessary boilerplate (getters, setters, constructors, destructor and more complex stuff), that maintain its consistency (i.e. make sure it is used correctly). So implementing your use cases is not burdened with these concerns.

kamikaze
  • 1,529
  • 8
  • 18
  • I guess data is something like a FILE struct in C. The actual components of the struct is opaque to programmers, but it does have functions that manipulate it (open, read, close, etc). So DCI seems to be advocating going back to good decomposition principles that our father's knew. – blippy Jul 07 '17 at 08:53