Static vs non Static modelling used in UML

Hi,

I would like to know more about 'Static vs non Static modelling used in UML'.

When, where, how we use it. Advantages, disadvantages, practical uses of each approach.


please advise
Any links resources ideas highly appreciated. Thanks in advance
LVL 7
gudii9Asked:
Who is Participating?
 
Angelp1ayConnect With a Mentor Commented:
The wiki article has a nice picture of the types of diagrams broken down into a hierarchy. The way I perceive it the structure diagram types are essentially static and behaviour diagrams are essentially dynamic

http://en.wikipedia.org/wiki/Unified_Modeling_Language#Modeling
UML Diagram Hierarchy
Personally I tend to stick to very few UML diagram types:

- Class diagrams
>>> great for defining data semantics

- Object diagrams
>>> great for communicating with the rest of the business who better understand real data examples instead of types and relations

- State diagrams
>>> great for defining workflows
0
 
gudii9Author Commented:
great for communicating with the rest of the business who better understand real data examples instead of types and relations

Can you please elaborate on this. I have not understood how real data examples are different. What are types and relations. Please advise
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.