System modeling of Software Engineering: Design Interface class model

This paper introduces the design process of interface class model. The interface class model describes the interface between the system activists and the system, the interface class is in the representation service layer of the system structure, and the interface class model is described by class Diagram and package diagrams. Firstly, the design method of interface class model is introduced briefly, then the class diagram of subsystem is designed, and the package diagram of system and subsystem is finally designed.

1. Design method

To design the interface class model, we should first recognize the interface class and then recognize the relationship between the interface classes. The interface class is the "visual area" of the application and the isolation layer between the system and the outside world. Interface classes can be identified using use cases, and use cases to drive interface class design. The user interface is directly connected to the use case, and the user initiates and terminates the use case through the user interface. Because the user interface is directly user-oriented, the design process should be repeated with the user to discuss, fully understand the user's requirements, the use case map to the user interface, according to the needs of the user to the appropriate combination of use cases. There are two kinds of relationships between interface classes: One is the composition relationship and the other is the dependency relationship. A specific window is composed of many components, the window and the component is formed between the relationship, one window into another window, which is a dependency between the two windows.

2. Class Diagram

We recognize the interface class of the system instance from the high-rise window and draw the interface class diagram of the main window of the system. We use the OA system in the dispatch of the interface class as an example, we in the "Software Engineering system modeling article" Design entity Class Model "has identified 7 use cases: New to send a document, modify the dispatch, audit issued, review the Dispatch, issue a dispatch, distribution, send a dispatch to the archives." In the Dispatch menu, you can define 7 menu items corresponding to the 7 use cases, the main window interface class diagram is shown in the following diagram, and the Menusfile class (Dispatch menu) defines the following 8 actions.

Create () Creating a dispatch menu

Createsfile () The action is invoked when the "new draft" menu item is selected

Changesfile () This action is invoked when the Modify a dispatch menu item is selected

Auditsfile () This action is invoked when the "Audit dispatch" menu item is selected

Checksfile () This action is invoked when the "Review dispatch" menu item is selected

Signsfile () The action is invoked when the "issue a dispatch" menu item is selected

Enresfile () This action is invoked when the "Distribute a dispatch" menu item is selected

Sendsfile () This action is invoked when the "Send document Archive" menu item is selected

Through the analysis of the relationship between the dispatch interface classes is a dependency relationship, that is, menusfile classes rely on Frmdraftsfile, frmsfilelist, Frmauditsfilelist, Frmchecksfilelist, Frmsignsfilelist, frmenresfilelist and frmsendsfile,frmsfilelist depend on the Frmdraftsfile class, Frmauditsfilelist relies on the Frmauditsfile class, Frmchecksfilelist relies on the Frmchecksfile class, and the Frmsignsfilelist class relies on FrmSignSFile, The Frmenresfilelist class relies on the Frmenresfile class.