I believe you are just looking for opinions on the 9 UML diagrams, so here's
mine.
Short Answer:
Vital: Use Case, Class, and Sequence Diagrams.
Non-Vital: Collaboration, Component, Deployment, State Chart, Activity,
Object.
Long Answer:
Know why each is useful, then eliminate those that are not:
Component: Eliminate if your system will not have multiple
threads/processes/executables.
Deployment: Eliminate if your system will be on one node (processor).
Activity: Use if textual story of a use case is getting too complicated to
understand to visually model the flow of the use case's story.
Object: Use to prove that someone's choices on multiplicity are incorrect
by creating an instance (object) diagram that allows something the class
diagram author didn't want, yet still conforms to the class diagram's
multiplicity.
Collaboration: Use to study the coupling and cohesion on a given class, to
try to improve the quality of the design.
State Chart: Use only if an individual class is very complicated statewise
to ensure that all operations have been found, and that all possible
combinations of operation calls and attribute values has been determined.
Use Cases: Use to show WHY we are building the system.
Sequence: Use to show what classes will be needed, and exactly what
operations each class should have to accomplish (realize) the use case.
Class: Use to show what the code should look like if using an OO language.
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
