Example Use Case Modeling Modeling with

A simple description and advantages of the use case modeling

Use case from the outside peripheral systems and user perspective, examine and analyze the behavior of the system to be developed, and by the participants (which may be an end user may also be a peripheral system) Features described interactions between the system and the system to provide both - --- this interactive relationship between participants and system features that use case. Analysis and use case modeling software is through research on the requirements, the specific functional requirements of the working procedure of Example abstract model use case. There are two cases with modeling product. The first is the use case diagram, a second product is described.

Example use has the advantage Modeling:

It provides tools to capture the functional requirements of
The system helps the range into more easily manageable chunks
It provides tools to communicate with users and other system functions associated personnel concerned. A use case is readily appreciated that the various common language related art
It provided for determining the distribution, tracking, control and management system means development activities (in particular, iterative development and incremental development activities)
Auxiliary estimated project scope, schedule and investment
It provides a benchmark for defining test plans and test cases
It provides a benchmark for the help system and user manuals and documentation systems development
It provides tools for requirements traceability
It provides a starting point for determining the data object or entity
It provides functional specifications and system design user interface description
It provides a definition of database access requirements (add, modify, delete, and read) means
It provides a framework for the drive system development projects

Second, the key terms used to describe:

　　Use Case Modeling: How to use the service, people who initiate business events, as well as the appropriate course of these events to the system modeling system functions

　　Use case diagram: describes the interaction between the graphics system and external users and other systems. Embodiment described with FIG who will use the system, what the user wishes to interact with the system

　　Functional Decomposition: split into a sub-component system activities

　　Use Case Description: business events and how users interact with the system to complete the task of text description

　　Use case: a sequence of steps related behavior, either automatically or be manually, and its object is to complete a single business task

　　Participants: it represents everything needs to interact with the system to exchange information

　　Timing events: System events triggered by the time

Three participants, the relationship between the embodiments with

1. This is the association relationship between the most commonly used, by solid lines with arrows will be described.

2. Generalization can be cited as a plurality of sub-use cases, which is a generalization cases be use cases, similar to the relationship between these and the generalization class. In a generalization of the embodiment, denoted by the sub-embodiment of embodiment with a special form of the parent, the embodiment may be inherited from the parent with the behavior and properties. A graphical representation of generalization hollow solid arrows, the arrow points to the parent class.

3. Relationship comprising comprising: means in which a use case (referred to as the base case) act contains another use case (referred comprising use cases). Results of a base case comprising a case and depend embodiment comprises. But the two can not access each other's property. Inclusion relationship graph is a dotted arrow plus <> with arrow pointing embodiment comprises.

4. The use case extension extend relationship may be defined as: increment base case extended, expanded relationship between Talia. Simply put, when a specific condition occurs, the extended use cases of behavior will be executed. Expanded relationship graph is a dotted arrow plus << >>, arrows point the base case.

Fourth, the system according to the concept used in modeling

There are two cases with modeling product. The first embodiment is a diagram that graphically as the system will be described by way of embodiments and the relationship among the participants (users). Use case diagram exchange the scope of business events in the system must handle at the top. The second product is described, filled each service event, and describes in detail how the user interacts with the system.

example

Participants

Relationship (association, expanded relationship includes relationships, dependencies, inheritance)

Fifth, the step of establishing the use case model

Define the system
Determining actors and use cases
Use case describes the relationship between participants and
Confirm model

Sixth, use case diagrams my engineering practice

My practice is a gateway things intelligent search engine

1, extraction Abstract use case

Account management, personal information management, search management, collections management.

2, to determine the scope of use cases High level use case

Account management: registration, login, quit.

Personal Information Management: including modifications to save personal information, attention / take off.

Search management: issuing search, return information and make recommendations.

Collection Management: Collection Gateway, collection company website.

3、Expanded use case

Account cancellation: Delete the current account information

Link function: given the appropriate link on the recommendation of the gateway company information.