Use Case Questions and Answers Guide
Use Case Questions and Answers Guide
'Preconditions' specify what must be true before a use case begins, while 'success guarantees' state what must be true after successful completion. Together, they define the start and end conditions of a use case, ensuring robustness in capturing system requirements .
The 'Main Success Scenario', also called the Basic Flow, outlines the primary path of successful interactions between actors and the system, capturing essential system functionalities necessary for fulfilling user goals .
The 'Fully Dressed' use-case format is more comprehensive as it details all steps, variations, and supporting sections. It includes alternative flows, extensions, and detailed descriptions that ensure all possible system interactions are covered .
Primary actors can be identified by asking questions such as who starts and stops the system, who uses the main features, and who interacts with the system first .
It is inaccurate to say use cases are solely within the Design discipline because they are actually part of the Requirements discipline. This means their primary role is to capture and agree upon what functionality is required, rather than how it will be designed or implemented .
The primary purpose of a use case in system design is to understand and describe functional requirements by detailing the scenarios tied to a user goal. They help in ensuring that all the necessary functionalities are captured from the end-user perspective .
The 'Technology and Data Variations List' is significant because it covers alternative input technologies and data formats, helping ensure that the use case remains relevant across different technological implementations. This makes the use case adaptable to varying technological scenarios .
Scenarios, being specific sequences of actor-system interactions that cover both success and failure paths, enhance the understanding of system interactions by providing detailed narratives of how various users might engage with the system. This detail helps in identifying potential issues and designing more robust systems .
An 'offstage actor' is an entity interested in the system's behavior but does not interact directly with it, whereas a 'supporting actor' is an external service that provides information or services to the system .
Actors in a use-case diagram help define the system boundary by representing entities outside the system that interact with it. This interaction delineates what is inside versus outside the system's scope, thus shaping its boundaries effectively .