domain modelling(urgent)

[nitin kumar]

Hi
I got a doubt regarding domain modelling.That is that first we identify our domains and we go for the usecases.Is it a rule that is strict to follow?cant it be reverse that I write my usecases and put them into domains.If it is difficult to identify domains but Im able document my usecases.Is my approach correct :Im confused: ?I need explanation.
bye
nitin

[Junilu Lacar]

While it is true that certain things have to come before others, you have to remember that there is also a great deal of going back and forth from one activity to the other. Things you learn from writing use cases help you define/refine your domain model. Conversely, defining/refining your domain model may help you think of additional use cases.
I am more comfortable with starting with identifying the more important use cases and then using those as the basis for defining the domain model. After that the two activities pretty much feed on each other.
The point is not to get stuck by thinking that you can't proceed with the other activity just because you haven't "completed" the first. If you get stuck, switching to the other for a while will likely help get your juices going again.
HTH,
Junilu
[ August 30, 2002: Message edited by: Junilu Lacar ]

[nitin kumar]

hi junilu lucar
thanks for ur reply.Here Im having some more queries exactly what we are going to acheive by breaking the project into domains
1)Is it something similar that we are breaking into modules .Is it a categorization that simplifies our design
2)If any usecase does not fit into any domain Can we send the usecases into a separate thing
3)How to identify domains.What is nature of domain is it a verb noun .
4)By domain modelling and usecase can we atleast make some design decision
5)I was told by some of my friend that if u are going for a graphical project then 2d is one domain and 3d is one domain
6)are there any strict rules in identifying the domains
please can u give me the answers
bye
nitin

[nitin kumar]

hi junilu lucar
thanks for ur reply.Here Im having some more queries exactly what we are going to acheive by breaking the project into domains
1)Is it something similar that we are breaking into modules .Is it a categorization that simplifies our design
2)If any usecase does not fit into any domain Can we send the usecases into a separate thing
3)How to identify domains.What is nature of domain is it a verb noun .
4)By domain modelling and usecase can we atleast make some design decision
5)I was told by some of my friend that if u are going for a graphical project then 2d is one domain and 3d is one domain
6)are there any strict rules in identifying the domains
please can u give me the answers
bye
nitin

[Jose Botella]

1)Is it something similar that we are breaking into modules .Is it a categorization that simplifies our design

domain modeling is part of the analisys of the problem. It will help to undertand better the problem, and it will be like a foundation for the design.

3)How to identify domains.What is nature of domain is it a verb noun .

In order to identify the conceptual classes shown in a domain model, the nouns provided by the use cases are helpful. You can also look at the the conceptual class list shown on page 134 of Applying UML and Patterns by Larman.

The domain model shows the main concepts in the domain, their attributes and the relationships between the concepts.

4)By domain modelling and usecase can we atleast make some design decision

I think I have read in that book that early design decissions aren't a good idea.
I really think that book is really well suitable to resolve your doubts.

[nitin kumar]

hi jose
Ok when I identify my domains is that they should be any interconnectivity between domains.
2)Later if I design a class is there any possibilty that it includes more than one domain
please let me know
bye
nitin

[Jose Botella]

Please tell me in which sense you are using the word domain.
a)the problem to model into a program
b)each of the conceptual classes in a domain model
c)other...

[Kyle Brown]

This is insane. You don't have multiple domains in a program -- you only have one (unless it's a HUGE program). I can't imagine a case in which artificially segregating the objects in your system in separate "domains" would provide any benefit.

I'd suggest you go to www.domainlanguage.com, download Eric's book, and explore more about what domain modeling is in depth...
Kyle
(edited by jlacar to fix link)
[ September 03, 2002: Message edited by: Junilu Lacar ]

[nitin kumar]

hi jose
Actually Im talking about the conceptual classes
Im haiving in my project monitoring -real time and batch .Can I put those into separate domains

bye
nitin

[Kyle Brown]

These are just two different modes of interaction -- the conceptual classes are still usually the same. Again, what's the reason you want to do this?
Kyle