Application should be partitioning to main modules.
For example, i will consider train system.
It is consists from: Train, routes, stations, search train, add route, rich WPF UI, console UI, user click some button to get stations etc.
DO - domain object. It is anemic entity, consists only Train, Route, Station
BL - business logic. It is operations on DO: search route, serialization/deserialization of DO objects etc.
UI - is how all this looks like on screen. Can be made by WPF, WinForms, Console etc.
How knows who?
DO do not know anyone.
BL knows DO only.
UI knows both BL and DO.
Its very superficial review, but it is very important to understand this concept
For example, i will consider train system.
It is consists from: Train, routes, stations, search train, add route, rich WPF UI, console UI, user click some button to get stations etc.
DO - domain object. It is anemic entity, consists only Train, Route, Station
BL - business logic. It is operations on DO: search route, serialization/deserialization of DO objects etc.
UI - is how all this looks like on screen. Can be made by WPF, WinForms, Console etc.
How knows who?
DO do not know anyone.
BL knows DO only.
UI knows both BL and DO.
Its very superficial review, but it is very important to understand this concept
No comments:
Post a Comment