uml class diagrams

Why does it matter to the use case what technology you write your UI in?

Use cases are use cases - sequence diagrams are the same for web and desktop UI, except for the classes that participate.

If you design your system well you should be able to have the same functionality used by BOTH web and desktop. A well-defined service layer can be called by either.

%

duffymoa at 2007-7-13 20:40:29 >

> hi,

>

> i think i have confused myself and everyone here :).

I know you're confused.

> what i meant was what is the difference between the

> domain model and class diagrams. when i do research

> in web sites and books it seems they are similar.

> that they both represent the whole system...

Domain model is exactly that - the subset of classes that model the domain you're interested in (e.g., finance, engineering, shopping site, etc.)

In addition to those, it's likely that you'll have UI classes, persistence classes, adapter classes, etc. These are not necessarily part of the domain, but they will appear in your class diagrams.

So the domain model is a subset of the complete class diagrams. You're likely to have them in one package named "model" or something clever like that.

%

duffymoa at 2007-7-13 20:40:30 >

> when i design an application, then there should be

> class diagrams(that describe each process of the

> system)..

When you say "process", I think sequence or activity diagrams. Those show how classes interact to accomplish a given task. You'll have a sequence diagram for each use case you want your system to implement.

> then there should me a domain model that describes the whole system ...

Domain model classes describe the problem you're trying to solve. The problem exists regardless of UI or persistence. You're also likely to design classes that will comprise the UI and persistence layers if you have them. The two areas together describe the whole system.

%

duffymoa at 2007-7-13 20:40:30 >