Menu
I create a new model Analysis Model and then a new use case diagram Simple Uses Cases inside it.
Why does it automatically create a new model named the same - Simple Uses Cases at the same level with Analysis Model?
I would like to understand the rationale behind this behavior of Visual Paradigm.
Update 1
I have created two use cases, and for each one a subdiagram of type sequence diagram:
Why are those models empty (Simple use cases, UseCase sequence diagram, UseCase2 sequence diagram)? What are their usages? Why are they created in the root of the project, regardless of the depth of the diagram I create?
462
Quote from Google: “A model is an abstraction that contains all the elements needed to describe the intention of the thing being modeled. This can include all aspects concerning the business, systems, relationships, and more. A diagram is a specific view into what you are trying to understand in a specific context.”
Models and diagrams are representations of a real-world application. Models provide an abstract view of the system, while different diagrams provide concrete representations of the system.
Right click on the target model and select Sub Diagrams > New Diagram... from the pop-up menu. When the New Diagram window pops out, select the type of diagram to be created and then click Next. Enter the diagram name and click OK to confirm the creation.
UML Diagram Types Guide: Learn About All Types of UML Diagrams with Examples. UML stands for Unified Modeling Language. It's a rich language to model software solutions, application structures, system behavior and business processes. There are 14 UML diagram types to help you model these behaviors.
Visual Paradigm offers the so called "Models" in order for you to organize yourself. Just that simple.
If you follow the link bellow it will get you into this:
"For small scale project, it would be easy to use Diagram Navigator to manage it. However, for middle to large scale project which has considerable numbers of diagrams and model elements, it would be better to use Model Structure view to organize the project."
https://www.visual-paradigm.com/support/documents/vpuserguide/12/74/6302_organizingdi.html
In the image below it also show the models avaliable:
If you look at the oprtions of models it gives, you will see that the Analysis Model is the best suited for grouping use cases.
The reason for that is simple and also answers one of your questions.
Answer: A Use Case (in this case, a diagram itself) serves the purpose of modeling the EXTERNAL BEHAVIOR of the system, which means, how actors interact with the system.
That is a step done in Systems Analysis. Which is prior to Design, Implementation or Deployment, the other models avaliable.
Since you are not modeling a process you wouldn't choose the last two options neither.
So, to answer these questions...
Why are those models empty (Simple use cases, UseCase sequence diagram, UseCase2 sequence diagram)? What are their usages?
...you should understand the semantics of each diagram. In order to do that i advise you to read from any reference on the web like http://www.uml-diagrams.org.
But, to be short, those diagrams do not build themselves alone, nor automatically. Visual Paradigm would never do that, just because it doesn't know how you would design or implement your use case (into a sequence diagram).
And to answer your last question...
Why are they created in the root of the project, regardless of the depth of the diagram I create?
This is simply because of the organization I explained above.
142
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
