The main objective of a development team is to create optimized applications, capable of satisfying the ever-changing needs of their users.
Modeling an application defines the structure and the expected behavior of a system. It helps understand its organization and detect simplification and reuse opportunities as well as manage potential risks.
A model is a simplification of reality. It allows you to better understand the system to develop.
A diagram is the graphical representation of a set of elements that build a system. To view the system from different perspectives, the Unified Modeling Language (UML) defines nine different diagrams. Each diagram represents a system state.
WINDEV, WEBDEV and WINDEV Mobile allow you to create the following nine types of UML models:
- Class diagram: describes the overall structure of a system.
- Use case diagram: represents the system features from the user's point of view.
- Object diagram: represents a set of objects and their relationships at a given time.
- Component diagram: describes the physical and static architecture of a computer application.
- Activity diagram: represents the behavior of a method or the progress of a use case.
- Sequence diagram: represents the chronological order of messages sent and received by a set of objects.
- Collaboration diagram: represents the structural organization of objects that send and receive messages.
- State-transition diagram: represents a sequence of states.
- Deployment diagram: shows the redistribution of the devices (nodes) used in a system as well as the association between the executable programs and these devices.
This help page presents an overview of the UML modeling. For more information about UML, see the specific documentation.