Tag Info

New answers tagged

2

I think that the SRP translates directly to the principles of orthogonal design and full normalization in relational databases. If you recollect that SRP states that there there should never be more than one reason for a class to change then the analogy becomes immediately apparent. However, whether the database should be split into multiple smaller ...


1

The SRP applies to the classes and methods you define. A database is not a user-defined entity, it is a piece of infrastructure that transcends individual requirements and responsibilities (in fact, it is better having to deal with only one database for a system than having to juggle multiple ones). Therefore, there is no point worrying about the fact that ...


1

Publisher/Subscriber, also known as Observer comes to mind. A Task factory can subscribe to status changes published by your Entity and create the Task instances as dictated by the change in status of the Entity.



Top 50 recent answers are included