Page History
...
- Naming is critical in software domain modeling. There are two qualities that you should be looking for in a good name for an entity in your model:
- Consistent. Business and developers should always use the same term to define a single concept.
- Exact. A name should exactly define the responsibilities of an entity in the domain model.
- It should only contain POJOs. The responsibilities assigned to an entity in the domain model should be limited to only those necessary for the software domain.
- The domain model shouldn't shouldn’t change because the underlying persistence implementation or the UI or any other layer changes.
- Domain Models should not be dependent on the mechanism used to persist them.
- SQLException or any other storage level object or response should not be exposed in the domain.
- DSpaceObject classes should not be hardcoded to SQL storage calls or directly to DatabaseManager.
- A software domain model should be easy to understand for a business domain model expert and it shouldn't shouldn’t have any discrepancy.
- There are two reasons why you want to make sure that the code quality of the domain model is top-notch:
- The domain model is the foundation of your application. If it is bad, the whole thing can fall apart.
- It changes a lot. There are very few areas in your code that are going to change so many times as the domain model.
...
Overview
Content Tools