Object-Oriented Program
1. Requirements Analysis 2. Overall design 3 . Detailed design stage 4. realization stage
1. Requirement analysis stage:
mainly use case diagrams, until class analysis diagrams. The class diagram is the source of the source code. The main function of a use case is represented by a sequence diagram. The states of the use case can be identified by the state diagram, note that the activity diagram should be refined to the same level as the sequence diagram. According to different users draw different
Same use case diagram. Draw deployment diagrams according to different physical locations; classify programs according to different types of users to obtain component diagrams. The collaboration diagram is obtained from the sequence diagram, and a simple class analysis is performed to obtain a class analysis diagram. Sequence diagram messages become operations
, the information in the message becomes an attribute.
2. The overall design
is the system computer level that the user sees, including the interface. The complete sequence diagram of each use case, including the main function, the backup function, the abnormal event, the error input and the error handling and other sequence diagrams, each branch has a sequence diagram. with a live
The animation merges all sequence diagrams, and uses a diamond box when encountering branches to obtain the complete function of the use case. Refine the use case diagram, compare the activity diagram of each use case, get the same part, and decompose it into use cases; for complex function use cases, decompose it into multiple use cases
Contains use cases. Modular extensions to some functions are called extension use cases. Inheritance can be used for users and use cases. Obtain collaboration diagrams from sequence diagrams and perform simple class analysis, especially entity classes. Added classes: interface class, transaction management class.
Draw a system state diagram (with active expressions), draw a class state diagram for important classes, and get new attributes and operations from them. Redraw sequence diagrams, activity diagrams and collaboration diagrams for the added classes. Analyze class diagrams. Refine the state diagram. The state diagram is the main,
The application class diagram is the center of gravity. It draws a detailed use case diagram for all users and illustrates the interface with other systems. Draw the overall design diagram of the system, according to the application class diagram and sequence activity diagram. Build a UML overall model.
3. Detailed design
stage The internal structure of the program and the detailed class diagram of the implementation plan are mainly focused on adding control classes. The structure of the program is obtained from the class diagram, and the process of the program is obtained from the sequential activity diagram (C++). Redraw sequence diagrams, collaboration diagrams, and activity diagrams with control classes. .use
Collaboration diagrams functionalize operations and variable properties with return values. Gives an activity expression for a class state diagram. The events of the state diagram are the messages of the sequence diagram, the operations of the class, and the active expressions are the implementation of the transition events, and therefore the implementation of the operations of the class.
Decompose the activity diagram, according to a certain operation. Unlike active expressions. Turn the application class diagram into a design class diagram, use a specific language, and divide the subsystems: class diagram, activity diagram (module diagram), component diagram, and deployment diagram. align the class into the component,
Put components into a deployment graph. Build a complete model of programming.
Fourth, the realization phase to establish concurrent views.