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.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I'm very new at creating sequence diagrams. I've been watching countless videos of tutorials to make sure I understand the concept, however, the trouble starts when I have to implement a specific dice game between 2 players into a sequence diagram without making it too long and complicated. I say specific dice game since there's custom rules added to it. This leads to many alternative scenarios and loops. Do I only include the most important parts of the dice game?
Yes, only show what's needed. That would be parts where for example many objects communicate. You never show the full path (which is impossible anyway for almost all cases). SDs are not for graphical programming. They shall help to give you the ideas of certain collaborations. So create as many SDs as needed starting with just some basics. When questions come up you can use additional SDs to clarify these. Also relate SDs to the collaborations (being realizations of use cases). Depending on the tool you use there are different ways to do that (packing would be one of them).
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 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 3 years ago.
Improve this question
I'm learning about UML diagram and sequence diagram at the moment in one of my courses for my CS degree, and I wonder that if this is something that is common to use for developers or if this is just one of many approaches to analyse the design of the system.
I'm so used to the Waterfall model and wondering if there would be any benefits for switching my mindset.
Maybe the answer is obvious, but still think it would be interesting to hear from people that are more experienced in the area.
My first advice is not to mix concepts:
UML = modeling language.
Useful to describe/visualize the design of a system.
Waterfall model = design process.
Useful to describe in a linear-sequential manner the life cycle of a system.
This is a very short and non-deep description but ilustrates your question about the specific case of sequence diagrams, so in a real case scenario you probably will end using both like this:
-Requirement/Analysis: during this phase you will start creating some of the first UML Use case diagrams for your system.
-System Design: during this phase (or even earlier) you will start creating UML Sequence diagrams, UML Component diagrams and so on.
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
In the UML reference manual page 18
Full specifications of a final system:
An implementation model includes enough information to build the system. It must include not only the logical semantics of the system and the algorithms, data structures, and mechanisms that ensure proper performance, but also organizational decisions about the system artifacts
that are necessary for cooperative work by humans and processing by tools
What the highlighted sentence means?
It basically means that with UML modeling, you can go far beyond describing algorithms. You can (and should) put the technical information in context and describe what the system you describe is good for, how it will be used, for what purpose and by whom.
Perhaps because it's an obscure usage, you might be wondering about the use of the word "artifacts" here. In this context, it refers to any of the persisted entities in your design, which can include databases, files, archives, cloud-storage, tapes, printouts, etc. Basically any component in the system that has a lifetime or can serve as long-term memory.
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.