System modeling of software Engineering: Design use case model

This paper mainly introduces the design process of use case model, first design use case model from system layer, then refine each use case of system layer recognition, design more detailed use case model. The use-case model is the starting point of the development process and drives the modeling process. The following is a case study of the use case model of office automation (OA) to explain the design process of the case model. The use case model includes a document use case diagram and a use case description.

Handling the use case model of the dispatch

1. Document use case diagram

Before the design of the use case model, it is necessary to identify the activists and use cases, the activists and the use case recognition before the use case model can be established.

1.1 Identification of the active person

The activity is the starting point of the system analyst and the user communication, is also the project obtains the follow-up product the key. The activity can be the person who uses the system function, also can be the software system and the hardware equipment, the external kind that the information exchange with the system, all can be classified as the activity of the system. After in-depth communication with system users, the system analyst is clear about system scope, system function and external related things. The identification of the activity needs to be repeated several times, by asking the user to identify the active person. For example: WHO/what is interested in the results of system operation, will change the data in the system, get information from the system, and interact with the system. The system activists can be identified by further analysis of the users with these requirements.

1.2 Recognition process

External entities interacting with the system include drafters, reviewers, reviewers, issuers and distributors. The drafters may be identified as the author of the Dispatch, the auditor may be able to set up an audit for the issuer, the reviewer can be identified as a post reviewer, the issuer is generally the relevant leadership, can be identified as a issuing issuer, the distributor can be identified as a distributor.

1.3 Use case identification

A new draft issued by the drafting of a new dispatch and saved in the system

The author of the dispatch modifies the dispatch and saves the operation. Modify the use case of the dispatch

The issuing auditor approves the editorial audit opinion and saves it in the system to audit the issued use case.

The issuing reviewer reviews the editorial review comments and maintains the system to review the issued use cases.

Issued by the issuer issued a dispatch editor issued comments and stored in the system to issue the use case

The Distributor distributes a dispatch to register the distribution and save it in the system distributing the use case

The drafting person sends the archives to the archive room to send the dispatch to the archive case

1.4 Use case diagrams