Design View Summary
The design view is developed by the analysis section (with example view), which is a premise that the demand transformation into code. The pan-design view includes a class diagram (StateCharts). Here is the "Practical Object" of Mark Priestley. Oriented Design With UML "Summary" Summary My translation version, discuss with you, learn.
The design model summarizes the association between objects and objects in Interaction DiaGram, which gives a detailed description of the target system. The design model mainly includes a class diagram and a state diagram.
The L-class diagram draws the relationship between classes and classes, and the characteristics of the class include attributes and operations.
l Association describes a link to an instance of a class associated with a class. Multiple (Multip
li
How many objects that are defined can be connected.
l General is that a class can be a special form of another class. Subclass inheritance characteristics from superclass, instances of subclasses can replace superclars (editorials).
The status map is prepared for classes that have different behaviors according to different states. The state diagram gives the correct order of events (Event), and results caused in an event order on one object.
l The state diagram shows a transaction that occurs when an object may be status and state transition, and an event that triggers a transaction.
L guard condition (Guard Conditions) can be used to remove uncertain conditions in the state diagram. (Editor Press: Since an event may result in two result status, in order to eliminate this uncertainty, in the state map, the extension condition is indicated, which is called Guard Conditions.
After getting the requirements, the demand analysis is started to obtain an example view, and the use case view here can be referred to as a general purpose view, which may include examples, sequence diagrams, collaboration graphs, and scenes, and then obtain classes and classes according to the analysis. The relationship between, draws a class diagram, and draws a state diagram of the dependent state. This gives a complete design model that can go to the next implementation step.
