CSC/ECE 517 Fall 2010/ch6 6h mf: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Domain Model= | =Domain Model= | ||
The domain model is an [http://en.wikipedia.org/wiki/Object_model object model] that encapsulates the rules, logic, and data associated with the [http://en.wikipedia.org/wiki/Problem_domain problem domain.] The purpose of domain modeling is to [http://en.wikipedia.org/wiki/Separation_of_concerns separate the concern] of problem solving from other concerns like the user interface and persistent storage. | The domain model is an [http://en.wikipedia.org/wiki/Object_model object model] that encapsulates the rules, logic, and data associated with the [http://en.wikipedia.org/wiki/Problem_domain problem domain.] The purpose of domain modeling is to [http://en.wikipedia.org/wiki/Separation_of_concerns separate the concern] of problem solving from other concerns like the user interface and persistent storage. For example, consider the Spring framework [http://static.springsource.org/docs/petclinic.html PetClinic] sample application. | ||
Revision as of 17:33, 17 November 2010
Domain Model
The domain model is an object model that encapsulates the rules, logic, and data associated with the problem domain. The purpose of domain modeling is to separate the concern of problem solving from other concerns like the user interface and persistent storage. For example, consider the Spring framework PetClinic sample application.