The simulation used five types of charts and UML-case diagram is a tool for modeling the dynamic aspects of the system, which in the modeling of behavior, class systems and subsystems play a major role.In each of these diagrams a lot of actors, use cases, and relationships between them.
UML-case diagram is widely used in various fields, especially where the need of a system in terms of the different variations of use or precedents.In most cases, it is assumed here modeling the context of the system, subsystem, or class, or modeling requirements that apply to the behavior of the selected items.
very important use case diagram is to specify, visualize and document the behavior of the system.Using it easier for developers to understand the system, subsystem, or class, as well as to look at the benefits of using external components for a particular context.This UML-diagram is of particular importance for testing executable systems with direct design, as well as a better understanding of their internal systems, especially in the reverse engineering.
structure precedent - is a great tool to look for an alternative to the main scenario, which leads to success.At every step, ask yourself the question again and again: "What else can happen?" And in particular, "What could go wrong?" It is best from the beginning to find out all the conditions of expansion that are possible.This will help avoid confusion in the future, while working on the consequences.
All the conditions for solving the problem, which is only possible, it is best to study from the beginning.This method will help to avoid being bogged down in a quagmire when working on the consequences.Therefore, if possible, consider the environment as much as possible, and this will cause further reduce errors.
The best option for a use case diagram is a graphical chart that shows its contents.It is something like a context diagram, which is used in the structural methods.For table shows the boundaries of the system, as well as its tangency with the outside world.
Chart precedents clearly displayed the actors, use cases, as well as the relationship between them:
- performance of the actors of a precedent;
- precedents involving other precedents.
about the contents of a precedent in UML modeling does not say anything, as a way of representing the chart shows it all.However, you can do without diagrams.Experts recommend the development of a precedent does not make too much effort to create the chart.It would be better if you concentrate on the text of the content.
case diagram UML, in addition to the relationship include, has other types, for example extend.It was his experts recommend avoiding.The reason lies in the fact that often the whole of the development team are paying a lot of time exploring different relationships between use cases.It is a waste of effort.After dealing with a text description of precedent is much easier, here it is hidden the true value of the technology.
