1. Embedded Systems Software Engineering
Jarosław Kuchta
Embedded Systems Software Engineering
Use case modeling
GUT - INTEL 2015/16
Embedded Systems Software Engineering

2. Embedded Systems Software Engineering
Basic concepts
use case – an abstract unit of functionality that system delivers to the user
actor – a role or a coherent set of roles that a human, a hardware device, or even another system plays when interacting with the system
GUT - INTEL 2015/16
Embedded Systems Software Engineering

3. Embedded Systems Software Engineering
Examples
Actors:
Operator
Supervisor
Use cases
Measures
Calibration
Operating
GUT - INTEL 2015/16
Embedded Systems Software Engineering

4. Embedded Systems Software Engineering
Use case diagram
Measures
Operator
Supervisor
Operating
Calibration
GUT - INTEL 2015/16
Embedded Systems Software Engineering

5. Embedded Systems Software Engineering
Use case kinds
overview / detailed
only generic use cases
specific use cases with interactions
essential / real
used in analysis
used in design
GUT - INTEL 2015/16
Embedded Systems Software Engineering

6. Embedded Systems Software Engineering
Use case model
Generic information
Actors list (actors class diagram)
Use case diagram
Main scenarios (interactions)
GUT - INTEL 2015/16
Embedded Systems Software Engineering

7. Many actors in one use case
Operator
Supervisor
Operation
Game session
Player 2
GUT - INTEL 2015/16
Embedded Systems Software Engineering

8. Embedded Systems Software Engineering
Actor hierarchy
Generic user
User
Specific users
Operator
Supervisor
GUT - INTEL 2015/16
Embedded Systems Software Engineering

9. Use cases relationships
<<include>>
Base use case explicitly incorporates the behavior of another use case at a location specified in the base. The included use case never stands alone, but is only instantiated as part of some larger base that includes it.
<<extend>>
Base use case implicitly incorporates the behavior of another use case at a location specified indirectly by the extending use case. The base use case may stand alone, but under certain conditions, its behavior may be extended by the behavior of another use case.
generalization-specialization
Generalization among use cases is just like generalization among classes. Child use case inherits the behavior and meaning of the parent use case; the child may add to or override the behavior of its parent; and the child may be substituted any place the parent appears
GUT - INTEL 2015/16
Embedded Systems Software Engineering

10. Relationships examples (1)
Order placement
«include»
Delivery terms
Login
«extend»
Registration
User management
Account creation
Account edition
Password reset
GUT - INTEL 2015/16
Embedded Systems Software Engineering

11. Relationships examples (2)
User
User
Login
Login
Operator
Admin
Login
GUT - INTEL 2015/16
Embedded Systems Software Engineering

12. Relationships examples (2)
Admin
User management
Account creation
Account edition
Password reset
Admin
Account creation
Account edition
Password reset
GUT - INTEL 2015/16
Embedded Systems Software Engineering

13. Embedded Systems Software Engineering
Scenario
Main event sequence
Sub-activities
Exceptional situations
GUT - INTEL 2015/16
Embedded Systems Software Engineering

14. Embedded Systems Software Engineering
Text scenario (1)
Order placement:
Customer authentication
Order negotiation
Order authorization
GUT - INTEL 2015/16
Embedded Systems Software Engineering

15. Scenario – interaction diagram
Control Panel
Active Directory
Controller
User
2: ok:= Authorization()
1: Login()
3a:[not ok] Invalid login
4: Get Status()
5: Menu
GUT - INTEL 2015/16
Embedded Systems Software Engineering

16. Embedded Systems Software Engineering
Use case model usage
User interface design
Application logic design
Testing
GUT - INTEL 2015/16
Embedded Systems Software Engineering

17. Embedded Systems Software Engineering
Bibliography
Grady Booch, James Rumbaugh, Ivar Jacobson: Unified Modeling User Guide (book, PDF)
GUT - INTEL 2015/16
Embedded Systems Software Engineering