I use UML for modeling, therefore constructing domain model, will analysis level class diagram will be an ideal
toolor there will be some other effective modeling methodologies. There are scenarios when I feel analysis level
class diagram is not well suited for forming domain models.
Also building domain model and update in it according to change in business process is needed every kind of system
development or not??
Any suggestions...........
Kumar Rohit
Hi Kumar,
Why do you think that a class diagram is not well suited for a domain model? Do you have examples of the types of scenarios?
- Adrian
Hi Adrian,
Means to say that in initial stage of modeling when requirements are often not complete and vague (In large sized projects)
then building a domain model with class diagram becomes tedious task as entities and their responsibilities
are not well identified at that time.
A business entity model is a great asset to any project and, I would argue, it should be created as soon as possible. Otherwise you run the risk of ambiguous requirements. Remember that all requirements refer to "things" and "nouns" of the business and these things (business entities) need to be well defined.
Now - if you starting from scratch you will have to update the domain model many times before it becomes stable. One option you have is to begin with a simple dictionary of business terms and describe them using words. Once the dictionary becomes stable, begin to create your business entity model.
brought to you by enabling practitioners & organizations to achieve their goals using: