|
Hi
Daniel,
The
Rational Unified process defines the domain model as:
domain
model
A domain model captures the most important types of objects in
the context of the domain.
The domain objects represent the entities that exist or events that transpire in
the environment in which the system works. The domain model is a subset of the
business object model.
Think of it as a glossary for the
domain that is presented in a graphical form. Of course, you need
definitions of the classes and attributes if you define them, but the advantage
of the graphical representation is the representation of associations between
the classes and details like role names, multiplicity, generalizations,
etc. I prefer to leave the specification of operations on the domain
classes to be an outcome of carrying use cases forward into analysis (I.e. use
case realizations).
My
experience with domain modeling has always been
that the
domain model was built either before use cases or in concert
with. An iterative
approach says that there is really less "before or after" and more of "some of
this focused on one area and some of that focused on the same area then
repeat for other areas". You want the domain model defined before you
build use case realizations because it defines the common vocabulary of the
domain, but the work of creating use cases and their specifications can go
hand-in-hand with domain modeling.
The domain model is usually built by
the domain experts for a particular project, but I also work with
Rational customers who have people tasked to look across applications and
define a domain model for a broader scope than just one project. The goal of this activity is to find
commonality for the purpose of integrating applications together or
building a reusable framework in the business. In this case, one might have
to go back and refactor the use cases of one project to match the domain model
defined at a broader scope.
Rational
Unified Process is a good resource. I couldn't find any other books on my
bookshelf that explained it better than
RUP.
Cindy VanEpps
Software Engineering Specialist
Rational Software
[EMAIL PROTECTED]
281.648.7996
http://www.rational.com
��Complexity is just a disarrangement of
simplicities.��
-----Original Message-----
From:
daniel wang [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December
21, 2000 7:54 PM
To: [EMAIL PROTECTED]
Subject: (ROSE)
hey, how to define domain model with rose
hi group:
would anyone give me an
explaination of business domain model. what's the purpose defining domain
model and when should we do the work(before or after difining use case
model).
is there any resource we can learn
about this?
thanks in advance.
daniel
|
