6

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.

enter image description here

Update 1

I have created two use cases, and for each one a subdiagram of type sequence diagram:

enter image description here

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?

Flavius
  • 13,566
  • 13
  • 80
  • 126
  • I think the tool expects you to create one use case diagram for each domain or subsystem (give it a name). It creates a new model for each domain/subsystem, so that you can use that model to further design the details of that domain/subsystem. – www.admiraalit.nl Nov 21 '15 at 22:03
  • @www.admiraalit.nl please see my update. – Flavius Nov 22 '15 at 07:05

1 Answers1

1

How does Visual Paradigm works? (based on its documentation)

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:

enter image description here

So why does it create a Analysis Model for my Use Cases?

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.

gustavogbc
  • 695
  • 11
  • 33
  • I like your answer, however, for clarity: what kind of diagrams go into those models created automatically and why? I also don't understand this: `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).` - Could you provide a sample workflow of how you do it, from the beginning to "the end"? – Flavius Mar 24 '17 at 18:09
  • Q: "what kind of diagrams go into those models created automatically and why? " A: I believe this answer is @ visual paradigm's documentation. Q: "Could you provide a sample workflow of how you do it, from the beginning to "the end"?" A:The workflow for building the diagrams follows the "modus operandi" of each company or even the way each person does it. It is a very specific answer. But I can tell you that I follow some well known standards of software engineering like RUP (https://en.wikipedia.org/wiki/Rational_Unified_Process) to know what and when to build something. – gustavogbc Mar 24 '17 at 19:10