Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Am kind of new to sequence diagrams and am a bit confused with sequence diagrams. I have a system where an administrator will manage the system, so my problem is if i am drawing a sequence diagram for my system , should i show the administrator interacting with all the features in the system ?
For example i have only shown administrator interacting with registering a new patient feature only , but there are other features as well such as managing records , register new doctors , so should i show the interaction with those features as well ? Or only the main features ?
Thank you for your time.
UML is not Bible. Feel free while using it.
If your diagrams get complicated, then show different aspects at different diagrams.
And this is generally better.
So it is OKEY to show "register new doctor" and "manage records" in different sequence diagrams.
There is no obligation such that you have to show everthing in a single diagram.And for each diagram you should also not have to show "everthing". It is okey to filter unnecessary details: to prefer not to show them based on modeler view. Because UML is just a visual thinking and communication tool.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
If we imagine we are given with a domain diagram and we also have a use case.
I am struggling to understand, what exactly can we derive?
Ex domain model, found on google.
I want to get to the interaction diagrams as a result.
I think the path is, system sequence diagrams -> operation contracts -> interaction diagrams
I just dont get the logic of how to derive all this from a domain diagram because on communication diagrams we can have instance creations that comes out from no where.
Can anyone explain how to derive all this from a domain diagram (if there are steps)?
This domain model represents the static structure of your domain. It does not give any information about its dynamics (how it behaves/changes over time). Sequence diagrams and interaction diagrams model the dynamics. They cannot be derived from the domain model.
In your question, you wrote: "We also have a use case". A use case gives information about the dynamics, so maybe you can derive the sequence/interaction diagrams from the use case.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I want to know what kind of diagrams I should use in each step of a project lifestyle, for example in the first step I should do the use case diagram, but what diagrams should I do after this step, for example what diagrams I should use during the analyse of the project, the design, etc.
First of all you should decide which process model you want to use. Let it be Waterfall (not recommended), V-Model, Scrum, Unified Process, Rational Unified Process, etc.
Then you can start talking about first, second step and so on, because the steps depend on the process model that you use.
These diagrams you're referring to are also called artifacts, and you should only use them, if you need them and if they create value (more understanding for example), you should not use them just to have done it (only if it's an academic/school project and you want to learn).
If you want to improve your knowledge in that certain area, there are several good books out there, e.g. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development by Larman.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I have come across tools like visualparadigm demo which could automatically generate code from the class diagram which is modelled in UML. Since I have no industry experience, I am curious to know whether this is the way companies start working on their projects after the system is modelled in UML. since the skeleton of the classes needed is automatically generated, I assume it is a good way to save time. If this is not the way, then why is it so?
Also Can you provide me some other tools which can automatically generate code from UML class diagrams (prefer opensource).
Are there OOP software projects which do not get started with the class diagrams, so that this method can be of no use?
Most of UML are able to generate code from UML class diagram you just have to google it and you will find them.
Concerning the way companies start working, I guess it depends of the companies but from my experience companies try to avoid useless work.
If they spend some time on modeling it is because they can use it for something for example code generation, documentation, or just because its a client request. If companies do not find any interest in modelling they simply do not use it I guess that alot of OOP do not start with models.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
UML 1 uses the name Collaboration Diagram. UML 2 uses the name Communication Diagram. In this link you can find the definition and one nice example. Here you can find a nice reference about how to create them.
Unfortunately, I didn't find this diagram in the software I have been using lately: DIA. I think it is not available in WhiteStarUML either. There is a tutorial in the help, but I wasn't able to make it work. As WhiteStarUML is a fork of StartUML, maybe it is just not done yet.
WhiteStarUML Screenshot: there is a folder for Collaboration Diagram but not a file inside to double click it to create it (like the Class Diagrams or UseCase Diagrams)
What your favourite free tool to create those diagrams?
Again, free community edition of Visual Paradygm UML. Until you use one diagram for a project it even can be printed without water signs.
But the communication diagram is very simple, you could easily simulate it with some free diagraming tool. There are many of them, they are easy, simply try and find what you like - intuitivity is too personal thing.
It may not be intuitive but in WhiteStarUML ones creates diagrams (including Collaboration Diagram) using the context menu of the Model Explorer (right click on a package) or chosing from the main menu "Model - Add Diagram". In the Diagram Explorer you only see the existing diagrams.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
i am sorry for asking such a straight forward and simple question but there is a lot of confusion regarding the use of partition in activity diagrams like :
is it really necessary to create partitions?
since each organisation has a number of working units/sub-units,and eventually they will have roles to play,would we
need to create partitions in literally every activity diagram we draw
for any process flow?
e.g- suppose we have draw an activity diagram for online shopping .customers browse and search for items and later buy it .now there are very fewer roles here so we can clearly draw the diagram without partitions but still we can create them ,in both case they will represent the system so does it really make sense to create them.
The answer to both questions is No.
Partitioning is an optional feature for an activity diagram.
UML is most of all a means of communication. When partitioning adds useful information to the ddiagram, then you should include it. When it doesn't add anything to the message presented by the diagram, then you don't add it.