Chronological order of UML diagrams

[mariem...@yahoo.fr]

Hi,
Is it any chronological order of UML diagrams? Especially between
component diagram and activity diagram.
With which Diagram should i start?
Best regards.

[H. S. Lahman]

Responding to mariem_haoues...

It depends on what you are modeling and what methodology you use. Most
OOA/D methodologies advise this order:

(1) Component Diagram to identify major subsystems
(2) Class Diagram for each subsystem for static structure skeleton
(3) Activity diagrams, Statecharts, and/or Abstract Action Language
(AAL) to specify object behavior.

Typically one will construct at least rough Interaction Diagrams when
doing the Class Diagram because it enables one to keep one eye on
collaborations when identifying object responsibilities. (If the
methodology employs Statecharts and AAL, then tools supporting that
methodology can automatically generate Interaction Diagrams for
documentation.)

Note that this order represents: overview -> static structure -> dynamic
structure.

--
Life is the only flaw in an otherwise perfect nonexistence
-- Schopenhauer

Rene Descartes went into a bar. The bartender asked if he would like a drink. Descartes said, "I think not," and disappeared.

H. S. Lahman
H.la...@verizon.net
software blog: http://pathfinderpeople.blogs.com/hslahman/index.html

[Francois Coetzee]

You did not mention the type of system you are developing.

For a user requirements driven system I do the following in order:

1. Record user requirements
2. Use Case diagrams
3. Class diagrams
4. Composite Structure diagrams for use cases
5. Activity diagrams OR sequence diagrams and interaction overview diagrams
6. Component diagrams
7. Deployment diagrams

Regards,
 
Francois Coetzee
Innovation Specialist
Enterprise Architect

Be brave enough to live creatively. The creative is the place where no one
else has ever been. You have to leave the city of your comfort and go into
the wilderness of your intuition. You can't get there by bus, only by hard
work, risking, and by not quite knowing what you're doing. What you'll
discover will be wonderful: yourself --Alan Alda

--
You received this message because you are subscribed to the Google Groups
"UML Forum" group.
Public website: www.umlforum.com
To post to this group, send email to umlf...@googlegroups.com To
unsubscribe from this group, send email to
umlforum+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/umlforum?hl=en?hl=en

[Hickerson, David A]

It really depends on the project. If you are deploying into existing systems or working larger systems, after use cases I find it easier to start with deployment diagrams and component diagrams breaking higher level functionality into components looking at the data flows. From here I look at sequence diagrams for components. It is from here I look at the classes that make up the components and their interactions.

This method breaks down the problems one step at a time promoting OO.

Dave Hickerson