I have a lot of feelings. First write down
1.There are two types of Design Software
One is to make the design as simple as possible without obvious defects.
The other is to make the design as complex as possible without obvious defects.
---- C. a.r. Hoare
2.Neither design nor too many designs are good, so what is proper design?
Without refactoring, you must ensure that the pre-made design is correct. This is too much pressure.
Due to stress"Excessive Design",However, if refactoring removes this pressure"Excessive Design"? 1. But no, it is an appropriate design.
3.Architecture
Transaction script Model
Domain Model
Table Model
---- Enterprise application architecture model
4.When will the database be created?
The transformation of thinking: the traditional development process, Dev prefers to design dB first and design the business layer.
The database is the implementation details and should be considered as soon as possible.
5.Business Layer, UI Layer, Dao Layer
The business layer is object-oriented, so what if the UI Layer and Dao layer adapt to this change?
Introduce viewmodel to the UI Layer
Dao layer introduced O-R mapping (because the object database is not mature, so currently can only use this technology)