Use Case
It is a system-independent view, and the high-level shape of the system is not specifically implemented. Includes all roles in the system, using cases, and USE case block diagrams, may also include some sequence or collaboration block diagrams.
Character. External entities interact with the system.
Use Cases. The system's high-level function block.
Use the case documentation. Detailed describes the process of using the case, including any error handling. Link to an external file.
Use case block diagram. Display roles, use cases and their interactions.
Intertion block diagram. Displays an object or class involved in using a case process.
package. Role / Use Case Group.
¨ Customer / Analyst / Project Administrator: Use the usecase, class, documentation to determine the high-level view of the system. Pay attention to system role rather than implementation details.
¨ All: Describe the event process through UseCase.
¨ QA: Write test scripts.
¨ Technician: Write user documentation.
¨ Customer / Analyst: Confirm that all requirements are captured.
¨ Developers: See which advanced components containing the system, how is the system logic.
Logical
Pay attention to how to implement the functions proposed in the case. It provides a detailed graphic of the system, which describes how the components are associated. Ligical block diagram Focus on the system logical structure, in this view, you want to mark the system components, check the information and features of the system, check the relationship between components, and determine the classes and packages that can be reused.
class.
Class block diagram. Used to browse classes, class properties and operations and their relationships in the system.
Intertion block diagram. Used to display classes participating in the case time process.
State Transition block diagram. Display the dynamic behavior of the object.
package. A set of related classes.
Two steps of logical view:
Analysis class. - Understand the system structure rather than language specific details.
Design class. Class with a specific language detail.
¨ Developers: Use class and class box graph information to determine which business requirements will be implemented. What class has been generated.
¨ QA: See which blocks in the system need to test, and use the ST block diagram to display a specific class.
¨ Project administrator: Determine the system constructor reasonably through class and block diagram, and estimate the complexity of the system.
¨ Subjector: The overall structure of the system, guarantee the system structure document, considering reusing, flexible adaptation of demand.
Component
Contains information of the model code base, executing files, runtime, and other components. The component is the actual module of the code.
Components. The actual module of the code.
Component block diagram. Display components and their relationships, understand compilation correlation and compilation order.
package. Related component groups. The purpose is to reuse. ¨¨ Code Control / Compilation Deployment Application: Determine the compilation order.
¨ Developer: Displays the class that has been generated and included in each code base.
DEPLOYMENT
Pay attention to the actual deployment of the system, handle fault tolerance, network bandwidth, fault recovery and response time. Can be different from the logical structure of the system.
process. It is a thread executed in your own memory space.
processor. Any machine with processing functions. Each process is running in one or several processors.
equipment. Includes any machine that does not have a function, such as a printer.
¨ Publish Application Personnel / All: Understand system deployment.
