FIT2001 Lecture Notes - Lecture 4: Postcondition
13 Jun 2018
School
Department
Course
Professor
L4 - Investigating, understanding, and documenting system requirements:
Use Case Diagrams, Use Case Descriptions, & Activity Diagrams
Use Case Diagrams
What: a representation of a user's interaction with the system that shows the relationship
between the user and the different use cases in which the user is involved
Main elements:
- Primary/Secondary actor
- Use Case: an interaction between system and actor (VERB) eg. Open account
- Association: line indicating an actor makes use of functionality provided by use case
- System Boundary: box that defines scope of system
- Relationship: between two use cases
- Include: when one use case executes another use case automatically
- Extend: like superclass + subclass
- Generalisation
Use Case Description
What: provides the details of the functionality that the system will support and describes how the
actors will use the system in order to obtain a specific result of value.
Document Summary
L4 - investigating, understanding, and documenting system requirements: Use case diagrams, use case descriptions, & activity diagrams. )hat: a representation of a user"s interaction with the system that shows the relationship between the user and the different use cases in which the user is involved. Use case: an interaction between system and actor (cid:840)(erb(cid:841) eg. open account. Association: line indicating an actor makes use of functionality provided by use case. System boundary: box that defines scope of system. Include: when one use case executes another use case automatically. )hat : provides the details of the functionality that the system will support and describes how the actors will use the system in order to obtain a specific result of value. Brief summary of use case major actions eg. 1-5 (cid:840)1 = lowest priority, 5 = highest priority(cid:841) The action that causes this use case to begin eg.
