Podcast
Questions and Answers
What distinguishes a state event from a temporal event?
What distinguishes a state event from a temporal event?
- A state event has a predictable duration.
- A state event occurs due to external factors.
- A state event can be defined by a specific point in time.
- A state event is triggered by an internal change within the system. (correct)
Which of the following best describes an actor in the context of use-case notations?
Which of the following best describes an actor in the context of use-case notations?
- An actor is a specific action taken by the system.
- An actor is an internal component of the system controlling processes.
- An actor exclusively refers to software applications interacting with the system.
- An actor represents a user or an external entity that interacts with the system. (correct)
What do use cases primarily illustrate?
What do use cases primarily illustrate?
- The timeframes within which system processes must occur.
- The functionalities and interactions of users with a system. (correct)
- The design and architecture of system components.
- The limitations and constraints of a system.
How does the identification of use cases begin?
How does the identification of use cases begin?
Which of the following is NOT a type of use case mentioned?
Which of the following is NOT a type of use case mentioned?
What defines a use case's story?
What defines a use case's story?
Which component is essential for defining functional requirements of a system?
Which component is essential for defining functional requirements of a system?
Which statement is true regarding state events?
Which statement is true regarding state events?
What is the primary purpose of a use case in system design?
What is the primary purpose of a use case in system design?
What defines an external event?
What defines an external event?
Which of the following best describes an elementary business process (EBP)?
Which of the following best describes an elementary business process (EBP)?
Which statement is true regarding temporal events?
Which statement is true regarding temporal events?
What role does an actor play in relation to a use case?
What role does an actor play in relation to a use case?
How do use cases and scenarios relate to each other?
How do use cases and scenarios relate to each other?
Why is analyzing domain classes necessary in system design?
Why is analyzing domain classes necessary in system design?
What is the first action taken by the Customer in the rental process?
What is the first action taken by the Customer in the rental process?
What does the Clerk do after receiving the membership identification from the Customer?
What does the Clerk do after receiving the membership identification from the Customer?
What occurs after the Clerk records the item identification into the system?
What occurs after the Clerk records the item identification into the system?
If a credit payment is used, which step must occur before completing the transaction?
If a credit payment is used, which step must occur before completing the transaction?
What happens if the Customer has unpaid late charges and refuses to pay them?
What happens if the Customer has unpaid late charges and refuses to pay them?
Which of the following is NOT a responsibility of the Clerk during the rental process?
Which of the following is NOT a responsibility of the Clerk during the rental process?
What does the Clerk provide to the Customer after the transaction is completed?
What does the Clerk provide to the Customer after the transaction is completed?
During what phase of the rental process does the Customer present their membership identification?
During what phase of the rental process does the Customer present their membership identification?
What must be included in the functional requirements of a system?
What must be included in the functional requirements of a system?
Which best describes a use case description?
Which best describes a use case description?
In the 'buy a product' scenario, what information does the customer need to provide when paying?
In the 'buy a product' scenario, what information does the customer need to provide when paying?
What happens if credit card authorization fails in the buying process?
What happens if credit card authorization fails in the buying process?
What is typically included in a written use case?
What is typically included in a written use case?
What does the generalization relationship in use cases represent?
What does the generalization relationship in use cases represent?
What is the role of the actor in a use case diagram?
What is the role of the actor in a use case diagram?
Why should use case names be kept simple?
Why should use case names be kept simple?
Which of the following describes exceptional flows in use case modeling?
Which of the following describes exceptional flows in use case modeling?
In the step-by-step breakdown of assigning staff to a campaign, what is the first action of the actor?
In the step-by-step breakdown of assigning staff to a campaign, what is the first action of the actor?
What does the system do after the actor selects the relevant campaign?
What does the system do after the actor selects the relevant campaign?
In what scenario is it typically unnecessary to include the 'Start Up' and 'Shut Down' use cases?
In what scenario is it typically unnecessary to include the 'Start Up' and 'Shut Down' use cases?
What is one key guideline for use case modeling regarding actors?
What is one key guideline for use case modeling regarding actors?
Which of the following statements correctly describes the difference between a use case diagram and a flow chart?
Which of the following statements correctly describes the difference between a use case diagram and a flow chart?
Which of the following is an example of a naming convention that should be avoided in use cases?
Which of the following is an example of a naming convention that should be avoided in use cases?
When defining use cases, what is the significance of including secondary actors?
When defining use cases, what is the significance of including secondary actors?
What must customers do before renting additional items?
What must customers do before renting additional items?
What should be done if the credit payment fails due to insufficient credit?
What should be done if the credit payment fails due to insufficient credit?
In a use case diagram, what does the stereotype «include» signify?
In a use case diagram, what does the stereotype «include» signify?
What is the purpose of a low-fidelity incomplete use case draft?
What is the purpose of a low-fidelity incomplete use case draft?
What is indicated by the «extend» relationship in use cases?
What is indicated by the «extend» relationship in use cases?
In terms of responsibilities, what does the system do after the customer pays?
In terms of responsibilities, what does the system do after the customer pays?
What is typically involved in the actor intentions for a rental transaction?
What is typically involved in the actor intentions for a rental transaction?
What does the relationship of an actor representing behavior for reuse indicate?
What does the relationship of an actor representing behavior for reuse indicate?
Flashcards
Event
Event
An occurrence at a specific time and place that can be described.
Event Decomposition
Event Decomposition
A technique to identify use cases by focusing on the events a system needs to respond to.
Elementary Business Process (EBP)
Elementary Business Process (EBP)
A task performed by one person in one place, in response to a business event, that adds value and leaves the system in a consistent state.
Scenario
Scenario
Signup and view all the flashcards
Actor
Actor
Signup and view all the flashcards
Use Case
Use Case
Signup and view all the flashcards
External Event
External Event
Signup and view all the flashcards
Temporal Event
Temporal Event
Signup and view all the flashcards
State Event
State Event
Signup and view all the flashcards
Use Case Diagrams
Use Case Diagrams
Signup and view all the flashcards
System Use Cases
System Use Cases
Signup and view all the flashcards
Identifying Use Cases
Identifying Use Cases
Signup and view all the flashcards
Procedure
Procedure
Signup and view all the flashcards
Functional Requirements
Functional Requirements
Signup and view all the flashcards
Written Use Cases
Written Use Cases
Signup and view all the flashcards
Use Case Description
Use Case Description
Signup and view all the flashcards
Alternative Courses (in Use Cases)
Alternative Courses (in Use Cases)
Signup and view all the flashcards
Actor's Goal in Use Case Scenario
Actor's Goal in Use Case Scenario
Signup and view all the flashcards
Robo-Actor
Robo-Actor
Signup and view all the flashcards
Buy a Product' Scenario
Buy a Product' Scenario
Signup and view all the flashcards
Membership Verification
Membership Verification
Signup and view all the flashcards
Item Recording
Item Recording
Signup and view all the flashcards
Calculating Total Charge
Calculating Total Charge
Signup and view all the flashcards
Payment Processing
Payment Processing
Signup and view all the flashcards
Customer Membership Information
Customer Membership Information
Signup and view all the flashcards
Generating Receipt
Generating Receipt
Signup and view all the flashcards
Membership Status Tracking
Membership Status Tracking
Signup and view all the flashcards
Inventory Management
Inventory Management
Signup and view all the flashcards
Summary Use Case
Summary Use Case
Signup and view all the flashcards
«include» Relationship
«include» Relationship
Signup and view all the flashcards
«extend» Relationship
«extend» Relationship
Signup and view all the flashcards
Summary Use Case
Summary Use Case
Signup and view all the flashcards
«include» Relationship
«include» Relationship
Signup and view all the flashcards
Extend relationship
Extend relationship
Signup and view all the flashcards
Generalization relationship
Generalization relationship
Signup and view all the flashcards
Study Notes
Use Case Diagrams/Documentation
- Use cases are techniques for documenting system requirements.
- They illustrate how users interact with a system.
- A scenario is a sequence of steps.
- An actor is a user's role in relation to the system.
- A use case is a set of scenarios tied together by a common user goal.
Objectives
- Use events to identify use cases defining requirements.
- Analyze events and resulting use cases.
- Understand how problem domain classes define requirements.
- Analyze domain classes needed in a system.
Use Case Diagrams
- Use Cases are techniques for capturing functional system requirements.
- They capture typical user-system interactions.
- A scenario describes typical interactions between a user and a system, modeling user goals.
- An actor is a role a user plays related to the system.
- A use case consists of scenarios tied together by a shared user goal.
Events and Use Cases
- An event is an occurrence at a specific time and place.
- Event decomposition is an analytical technique to identify use cases.
- It involves first focusing on events a system responds to, then examining system responses.
- Elementary Business Processes (EBPs) are tasks performed by one person, responding to a business event that adds value and leaves the system consistent.
- Each EBP is a use case triggered by a business event.
- A use case is an activity the system carries out in response to an event.
Types of Events
- External events originate outside a system, often initiated by an external agent or actor (e.g., a student wanting to register).
- Temporal events occur when a system reaches a specific point in time (e.g., producing result slips at the end of a semester). Systems should automatically process such events.
- State events originate from actions occurring within a system, triggering further processing (e.g., auto-backup upon system failure).
External Event Checklist
- External agent wants something, leading to a transaction.
- External agent needs information.
- Data change necessitates update.
- Management requests information.
Temporal Event Checklist
- Internal outputs are needed.
- Management reports (summary or exception) are required.
- Operational reports (detailed transactions) are required.
- Internal statements and documents (including payroll) are required.
- External outputs (e.g., statements, status reports, bills, and reminders) are needed.
Use-Case Notations: Actors
- Actors represent external entities interacting with the system.
- Actors can be users, external systems, or the physical environment.
- Each actor has a unique name and an optional description.
- Examples include Passengers, GPS satellites, etc.
Use-Case Notations: Use Case
- A use case represents a class of functionality provided by a system as an event flow.
- Use cases are shown as ellipses.
User/Actor
- Users and their goals help in understanding required functionality for use cases.
Use Case Diagrams
- Use cases show actors and the use cases they use/execute/interact with.
- Use cases illustrate functional requirements in a system.
Identifying Use Cases
- Use cases are based on system processes, which are complete end-to-end.
- The identification begins with the requirement definition, focusing on process-oriented requirements and actions resulting from external or temporal events.
- Information-oriented requirements highlight the data or time triggers necessary for information collection or generation.
Studying That Suits You
Use AI to generate personalized quizzes and flashcards to suit your learning preferences.