Flashcards
Domain Analysis and Modelling - Use Cases
Cards in this deck (22)
- 1What is a Use Case?The specification of a set of a actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system
- 2What is a Use Case used for?Describing the functional requirements of a system
- 3How are Use Cases shown?In Use Case Diagrams
- 4What do Use-case diagrams contain?Actors - represent users of a system (inc. human users and other systems)
Use Cases - represent functionality or services provided by a system to users - 5Example of a Use case diagram between cashier and POS system?
- 6What is a system boundary?
- 7What is an actor?
- 8What is the role of a use case?
- 9What are the communications involved?
- 10What is the association involved?
- 11What can the meaning of association be refined with?1. Multiplicity
2. Direction
3. Labels - 12Explain Multiplicity1. Cashier may be involved in up to one interaction to "Process CC payment"
2. 1 cashier participates in "Process CC payment"
3. >1 CC systems involved to process CC payment
4. CC System may be involved in many interactions to "Process CC payment"
- 13Explain directionIndicates who initiates communication
- 14How Use Cases are related to each other?1. Generalization - one use case is a special case of another
2. Includes - included use case embodies common behaviour
3. Extends: Extending use case adds behaviour - 15Specilization/Generalization of actors?One actor can be a specialization of another
- 16And of use cases?
- 17What does includes allow?Reuse of functionality by multiple use
cases
- 18What does extends involve?Indicates that one use case adds or replaces behaviour of another
1. They must have an associated extension point
2. May have a condition
- 19Use Case Diagram guidelines?1. Use cases should begi nwith a verb (i.e. generate report)
2. Actors should be named as singular (student)
3. Do not show behaviour in a UCD, depict only system functionality
4. Actors are roles, NOT instances - 20Qualities of a good use case?1. Starts with a request from actor to system, ends with production of all answers to the request
2. Defines interactions related to function
3. Takes into account actor point of view
4. Focuses on interaction, not internal system activity
5. Not describe GUI in detail
6. Easy to read - 21Software to run cell phone, use cases vs internal functions?Use cases:
Call someone
Receive call
Send message
Memorize number
Internal function:
Transmit/receive data
Energy (battery)
User I/O (display, keys)
Phonebook mgt. - 22Advantages of Use Cases?1. Simple, everyone understands them
2. Gives concise view of what system must do for users/stakeholders
3. Defines the boundaries of a system
4. Facilitate agreement with customers/users and stakeholders
5. Places requirements in context
6. Captures workflow
Information
- Description
- Flashcards on Domain Analysis and Modelling - Use Cases, created by zacklife on 20/01/2016.
- Created by
- zacklife
- Views
- 0
- Rating