Please enable JavaScript.
Coggle requires JavaScript to display documents.
UML - Coggle Diagram
UML
Kruchten's
Logical, One way is by its functionality. This shows how the system implements the purpose your client desires. How close to their requirements your software is.
The context is the services that should be provided to end users. the logical view usually involves the objects of the system. From these objects, you can create a UML class diagram that illustrates the logical view i.e. Class diagram, and State diagram
Scenarios, use cases or user tasks
Scenarios align with the use cases or user tasks of a system and show how the four other views work together. For each scenario, there's a script that describes the sequence of interactions between objects and processes.
These details are defined in the process view. This presents the processes implemented by the objects in the logical view. efficiency of the system or the interaction of the subprocesses. These all affect the performance and scalability of your system. NFRs +
the process view presents processes that correspond to the objects in a logical view. For example, the process view would show the execution order of your different objects. It would show the calls to methods defined by the logical view in the correct order i.e. Sequence diagram
The implementation of your software can be considered part of the development view. This implementation can be seen through the hierarchical structure (almost like UX flow) of the software.
The development view also considers elements like programming languages, libraries and tool sets. Essentially it is concerned with the details of software development and what is involved to support that. Besides code, this includes management details like scheduling, budgets and work assignments. Project management is essential in the development view.
Perhaps you need to use one server to host your database and others to host your web clients. You will need to plan how these different elements interact and deploy the system correctly. These details are expressed in the physical view
The physical view handles how elements in the logical process, and development views must be mapped to different nodes or hardware for running the system. A UML deployment diagram can express how the pieces of a system are deployed into hardware or execution environments
UML component diagram
-
-
-
-
Components are defined as independent, encapsulated units within a system. Each component provides an interface for other components to interact with it
UML deployment diagrams
Specification
gives an overview of artifacts and deployment targets, without referencing specific details like machine names. It focuses on a general overview of your deployment rather than the specifics
Instance
is a much more specific approach, which can map a specific artifact to a specific deployment target. In particular, the instance level diagram can identify specific machines and hardware devices
Most commonly, this approach is used to highlight the differences in deployments among development, staging, and release builds
Nodes are deployment targets that contain artifacts available for execution. They look like 3D boxes. Hardware devices are also displayed in the same way as nodes. The device tag on this node differentiates it from other types of nodes
UML activity diagram
The purpose of the activity diagram is to capture the dynamic behavior of the system. How control flows from one activity to another. The activity diagram allows you to map out the branching into alternative flows.
-
Partitions divide activities up into different categories, such as where it occurs, or the user role involved. For example, all of the video game activities concerning levels could be grouped in one partition, and all of the player activities could be grouped in another partition. Swim lanes are used in an activity diagram to display these partitions
-
-
How each element relates to one another,
UML package diagram
A package groups together elements of your software that are related. This elements can be related based on data, classes or user tasks