the extension use case adds new behavior to the base use case
Diagram Description:
Association:
Depend on:
Generalization:
Contains:
Extended:
Two. Role: Describe the needs of the user (emphasizing the function, the performer of the function, the system in
Example
Defining system boundaries determines the boundaries between the system's interior and exterior.
The main character represents the role played by the external object. An object can assume several roles, so it can be represented by several leading roles.
Communication relationships are used to clarify the participation of the main character in the use case.
A
Recently has been learning the basic knowledge of UML, after watching the video, and did not have a good summary, in the process of drawing found a lot of problems, the following is the process of reading their own summary of the UML use case diagram of a little knowledge, share with you.
First, the concept
A use
Use case diagram (Use Case daigrams)
The Use Case view of UML is the view of the external feature description of software products. It describes the demand for software products from t
Background
Previous: Using Visual Studio 2010 from Analysis to implementation (2)--using activity diagram to refine business processes
The brother who is unfamiliar with the use case diagram please refer to: http://www.ibm.com/developerworks/cn/rational/r-usecase-atm/
The Visual Studio 2010 development team's role i
control. Describes the performer "Customer" using the "withdraw" use case.The use of connectors (uses connector) can be selective at each endpoint with multiple values, such as showing that a client may only perform one withdrawal transaction at a time. But banks can perform many withdrawal transactions at the same time. The multiplicity setting is set separately on both ends of the purpose connector.Use
The previous blog summarized the use case diagram, in which the relationship between use cases is only included, because the relationship between use cases is not particularly profound. This is also because the UML use
Case modeling is a part of UML modeling and the most basic part of UML. The main function of case modeling is to express the functional requirements or behaviors of the system. To put it bluntly, it is to explain what the system is, so you don't have to worry about how to work. I think the use case chart is the best pi
As mentioned in the previous article on the relationship in the use case diagram, the use case diagram describes user requirements, describes system functions from the user's perspective, and points out the executors of various fu
A use case diagram is a diagram that describes the functions of a system by actors, use cases, and relationships.
Participant: A person who directs a system, or a system-related thing or system.
A simple understanding of use case
In the software development process, the software design stage plays an important role. A good design can improve the development efficiency. The design use case diagram clearly shows the user's operation behavior. The use case diagram
The use case diagram mainly includes use cases, activists, and relationships.
Use Cases: A description of the sequence of actions that the system, subsystem, or class interacts with external participants, including various normal sequences and error sequences.
The use case diagram in UML describes user requirements, describes system functions from the user's perspective, and points out the executors of various functions, emphasizing who is using the system and what functions the system executors are performing. It is mainly used in the requirement analysis stage to describe the functional requirements of the system to
Three elements of use case diagram design
1. Participants
2. Use Cases
3. Relationship
1. The relationship between participants is generalized (inherited.
2 Relationship between participants and Use Cases
A solid arrow indicates the relationship between active and pass
The use case diagram is used to describe the relationship between users, requirements, and system functional units. It shows a system functional model diagram that can be observed by external users.
[PURPOSE]: help the development team understand the functional requirements of the system in a visual manner.
The
Use case diagram Structure
1Roles: Personnel roles-people and events;
Roles are not necessarily limited to people. They can also be things or things.
2. Use Case: function description;
Each use
confirmation, preferably with the user representative to confirm the signature.(2) "Review requirements Document" Activities, can not be omitted, the need for system analysis, designers to fully understand, analyze the requirements, confirm that the requirements analysis described clearly, and do not go beyond the scope.(3) "Create and publish a requirement baseline" activity, which solidifies the requirements and requires the creation of a demand tracking matrix.Next, we will focus on demand a
Use Case Diagrams are used to determine the scope of requirements. These requirements are the basis for design and development. The use case diagram treats the system as a black box and understands the system from the perspective of external executors. As shown in Figure 12.
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.