The use case name is recommended to use a nominal, followed by a direct object, sometimes need more fully information names should always be user-centered, not the system-centric. The use case number is numbered as a hierarchy, and the name is used. Preparation date of YangTom
2005-4-6
Approved people approval date Approved personnel Approved date Major Participants are usually outside the system, and have nothing to do with the system. It is really important that participants play the role. Secondary Participant Participants define the role of users playing in the system interaction. Brief description. The role and purpose trigger event use case must be triggered by a protagonist, that is, each usage should be at least one. protagonist. The front condition refers to what state should be placed in the case when the use case is started. This state should be that the system can detect, the observable event flow basic event stream is a description of the general and expected paths in the use case. It is also known as the Happy Day scene, and the scene encountered most of the time; it will reflect the core value of the system; the optional event stream describes some cases of abnormal or occasional cases during the execution process. When the system should be placed, this state should also be that the system can detect, observable non-functional requirements include operating systems, development tools such as design constraints such as performance, reliability, availability, and scalability. It is best not to include these rules in the Business Rule Example Description, but these rules should be specified in some way so that the document can be used correctly and can be used. All related votes Single book Related Code Table Permission Scope Modify History Modify Version Description Modification Date
The use case model mainly includes the following two parts:
With an example (Use Case Diagram) Determine the correspondence between the participants, the use cases, and the correspondence between the systems, and the example diagram is described with an overview of the system function. Use the case specification (USE Case Specification) should have an example of using an example of the decisions corresponding to the details of the details of the use case.
The example is only a generally described various services that the system can provide in general, allowing us to have an overall understanding of the system. In object-oriented analysis design methods, the use case model is mainly used to express the functional needs of the system, and the examples are the core of the use case analysis technology.
After the use case model is complete, you can check the use case model to see if there is an omissit or error. It can be checked by the following aspects:
The complete existing use case model of functional requirements completely describes system functions, which is the flag we determine whether the model is used to end. If there is still a system feature that is not recorded in an existing usage model, then we need to abstract some new use cases to record these needs, or induct them in some existing cases. The biggest advantage of the model is easy to understand the use case model is that it should be readily understood by different involvement, so the most important guidelines for modeling is its understandability. The relationship between the particle size, number of models, and the model element should be determined by the guiding principle. Whether there is an inconsistency system is done by multiple system analysts, the model itself is also composed of multiple workpieces, so we must pay special attention to whether there is a place where there is a contradiction or conflict before and after different workpieces, avoiding models. Internal inconsistency. Inconsisons will directly affect the accuracy of demand definitions. Avoiding an unrestricted semantic demand definition should be ignorant, that is, different people should be consistent with the understanding of the same needs. In the description of the case, it should be avoided to define the need for ambiguity, that is, there is no meaning.
Reference: 1. Model Guide
