Im in a confusion on the sequence of drawing UML diagrams. I cannot understand where to start drawing them. Which diagram should come first if I have the scenario with me?
Asked
Active
Viewed 887 times
3
-
1See [agilemodeling.com: Requirements Envisioning: An Agile Best Practice](http://agilemodeling.com/essays/initialRequirementsModeling.htm) – xmojmr Feb 24 '16 at 13:00
-
Thank you I will take a look – Sachini Wickramaratne Feb 25 '16 at 05:05
3 Answers
3
Start with Use Cases (and the related diagrams). Once Actors and Use Cases are identified, you can start designing a Class model. Create Collaborations realizing the Use Cases. Then inside show how the Instances of the Classes collaborate to actually realize what is needed for the Use Cases.
I recommend the ICONIX approach since that is what got me going a long time ago.
qwerty_so
- 35,448
- 8
- 62
- 86
-
1Thank you!! But I'm confused as there is only one actor. do I still need to draw the use case? I have a Business flow chart with me. and a product story board too.. – Sachini Wickramaratne Feb 25 '16 at 05:04
-
Well, are you afraid of it ;-? The use cases are those basics you can discuss with business and developers (requirements alone can not really be discussed). So yes: draw the single actor and the use case(s). – qwerty_so Feb 25 '16 at 08:36
0
The other option is to start with Activity Diagram. I.e. make a business process analysis.
utom
- 482
- 1
- 3
- 15
0
I always start with a problem-domain class diagram. (Some examples of what I mean are here and here.) Understanding the concepts in the domain and the relationships between them is extremely important. If you don't understand the problem domain, everything else will be confused and brittle, including business processes, requirements, use cases, and collaborations. Here is an example of an improper domain model, and here are the recommended corrections.
