Use Cases and User Stories in Software Analysis Study Guide PDF

10/18/24, 4:17 PM Use Cases and User Stories in Software Analysis Study Guide | Quizlet Use Cases and User Stories in Share Software Analysi...

10/18/24, 4:17 PM Use Cases and User Stories in Software Analysis Study Guide | Quizlet Use Cases and User Stories in Share Software Analysis Tonie_Munsayac Plus Created 10/18/24 Add course tag User story Use case Functional requirements Non-functional requirements See all Overview of Use Cases and User Stories Understanding User Stories User stories are tools used to capture software feature descriptions from an end-user perspective, focusing on who the user is, what they want, and why they want it. They provide a simplified description of requirements, allowing for better understanding and prioritization of features. The standard template for a user story is: As a , I want to so that , which helps clarify the user’s needs and the value of the functionality. Acceptance criteria for user stories are defined using the format: , which outlines the conditions for success in a specific scenario. Example: Given the customer has one credit account and one savings account, when they have logged in successfully, then the two accounts will be listed in account number order. https://quizlet.com/study-guides/use-cases-and-user-stories-in-software-analysis-780d8073-b1ab-46f3-8e3c-aa94cdfc6d3f 1/10 10/18/24, 4:17 PM Use Cases and User Stories in Software Analysis Study Guide | Quizlet The three critical aspects of a user story are: Who (the user role), What (the goal), and Why (the benefit), which are essential for understanding and implementing the story. Use Cases Defined A use case is an activity that the system performs in response to a user request, defining functional requirements of the system. Analysts decompose the system into a set of use cases through functional decomposition, which helps in understanding system interactions. Use cases are typically named using a Verb-Noun format, which clearly indicates the action and the object involved. There are two primary techniques for identifying use cases: User Goal Technique and Event Decomposition Technique, each serving different analytical needs. Use cases help in documenting the interactions between users and the system, ensuring that all functional requirements are captured effectively. Example of a use case: Process Payment , which describes the system's action in response to a payment request. Techniques for Identifying Use Cases https://quizlet.com/study-guides/use-cases-and-user-stories-in-software-analysis-780d8073-b1ab-46f3-8e3c-aa94cdfc6d3f 2/10 10/18/24, 4:17 PM Use Cases and User Stories in Software Analysis Study Guide | Quizlet User Goal Technique The User Goal Technique is widely used in the industry for its simplicity and effectiveness in identifying user needs. This technique involves identifying all potential user categories and interviewing them to understand the tasks they need the system to perform. Users are prompted to describe their goals, which can include actions like Ship items , Track a shipment , or Create a return. Steps in this technique include identifying users, classifying them by functional roles, and refining their goals into specific use cases. The process also involves creating a preliminary list of use cases organized by user type and resolving any duplicates or inconsistencies. This technique ensures that the system is designed with the end-user's needs in mind, leading to a more usable product. Event Decomposition Technique https://quizlet.com/study-guides/use-cases-and-user-stories-in-software-analysis-780d8073-b1ab-46f3-8e3c-aa94cdfc6d3f 3/10 10/18/24, 4:17 PM Use Cases and User Stories in Software Analysis Study Guide | Quizlet The Event Decomposition Technique is a more comprehensive method for identifying use cases by focusing on events that the system must respond to. An event is defined as something that occurs at a specific time and place, which the system should remember and respond to appropriately. For each identified event, a corresponding use case is named using the Verb-Noun format, describing the system's action in response to the event. This technique allows for a thorough understanding of system interactions and ensures that all potential use cases are considered. Benefits of this technique include a more complete set of use cases and a clearer understanding of system requirements based on real-world events. Example of an event: User Login , which triggers the use case Authenticate User. Benefits and Assumptions in Use Case Analysis Benefits of Event Decomposition Technique Provides a structured approach to identifying all relevant use cases based on real- world events, ensuring comprehensive coverage of system functionality. Helps in visualizing the interactions between users and the system, leading to better design decisions. https://quizlet.com/study-guides/use-cases-and-user-stories-in-software-analysis-780d8073-b1ab-46f3-8e3c-aa94cdfc6d3f 4/10 10/18/24, 4:17 PM Use Cases and User Stories in Software Analysis Study Guide | Quizlet Facilitates communication among stakeholders by providing clear descriptions of system behavior in response to events. Encourages thorough documentation of system requirements, which can be referenced throughout the development process. Aids in identifying potential edge cases and exceptions that may not be captured through user goals alone. Enhances the overall quality of the requirements by ensuring they are grounded in actual user interactions. Perfect Technology Assumptions Perfect Technology Assumptions refer to the ideal conditions under which a system is expected to operate without any constraints or limitations. These assumptions allow analysts to focus on the core functionalities of the system without being bogged down by technical limitations. Examples of events that should not be included initially due to these assumptions include system controls like User Authentication , Data Backup , and Error Handling , which may complicate the initial analysis. By setting aside these assumptions, analysts can better identify the essential use cases that drive user value and system functionality. This approach helps in prioritizing features that deliver the most significant benefits to users, ensuring a user-centered design process. Understanding these assumptions is crucial for effective requirements gathering and system design. https://quizlet.com/study-guides/use-cases-and-user-stories-in-software-analysis-780d8073-b1ab-46f3-8e3c-aa94cdfc6d3f 5/10 10/18/24, 4:17 PM Use Cases and User Stories in Software Analysis Study Guide | Quizlet Types of Events External Events External events are initiated by agents or actors outside the system, prompting a response from the system. Examples include customer transactions, information requests, and changes in external data. These events often lead to significant system interactions, such as processing orders or updating customer information. Understanding external events is crucial for designing user-centric systems that respond effectively to user needs. They can be tracked through checklists to ensure all potential interactions are considered. Temporal Events Temporal events are triggered by the passage of time, requiring the system to perform specific actions at designated intervals. Examples include generating management reports, operational reports, and payroll statements. These events ensure that the system maintains timely and relevant outputs for both internal and external stakeholders. https://quizlet.com/study-guides/use-cases-and-user-stories-in-software-analysis-780d8073-b1ab-46f3-8e3c-aa94cdfc6d3f 6/10 10/18/24, 4:17 PM Use Cases and User Stories in Software Analysis Study Guide | Quizlet Temporal events can be scheduled and automated to enhance efficiency and reduce manual intervention. Identifying these events is essential for systems that rely on regular updates and reporting. State Events State events occur when internal conditions change within the system, prompting a response or process. An example is reaching a reorder point for inventory, which triggers restocking processes. These events are critical for real-time systems where immediate responses are necessary to maintain operational flow. Understanding state events helps in designing systems that are responsive to internal changes, enhancing overall efficiency. They often require careful monitoring and analysis to ensure timely responses. Event Checklists External Event Checklist External events can be categorized based on the type of interaction they represent, such as transactions or information requests. Examples include: Customer purchases a product (transaction). Customer requests product details (information request). Customer updates their address (data change). Management requests production updates (information request). Utilizing checklists helps ensure comprehensive coverage of all potential external interactions. Temporal Event Checklist Temporal events can be categorized into internal and external outputs needed at specific times. Examples include: Internal management reports (summary or exception). Operational reports detailing transactions. External statements, bills, and reminders sent to customers. https://quizlet.com/study-guides/use-cases-and-user-stories-in-software-analysis-780d8073-b1ab-46f3-8e3c-aa94cdfc6d3f 7/10 10/18/24, 4:17 PM Use Cases and User Stories in Software Analysis Study Guide | Quizlet These checklists assist in identifying necessary outputs and ensuring timely delivery. Event Decomposition Technique Steps in Event Decomposition The event decomposition technique involves a systematic approach to identifying and analyzing events that require system responses. Key steps include: 1. Identify external events using checklists. 2. Identify state events and their corresponding use cases. 3. Identify temporal events and their required use cases. 4. Validate events against the perfect technology assumption to exclude unnecessary system controls. 5. Document the use cases associated with each identified event. This technique helps in breaking down complex systems into manageable components for analysis. Benefits of Event Decomposition Event decomposition provides a structured approach to understanding system interactions and requirements. It captures a broader range of events beyond user goals, including temporal and state events. Helps in identifying elementary business processes (EBPs) that are fundamental to system functionality. Ensures that the design focuses on user needs without being bogged down by system controls initially. Facilitates clearer communication among stakeholders regarding system requirements and functionalities. Perfect Technology Assumption Understanding the Perfect Technology Assumption The perfect technology assumption posits that systems operate under ideal conditions, ignoring potential failures or limitations. https://quizlet.com/study-guides/use-cases-and-user-stories-in-software-analysis-780d8073-b1ab-46f3-8e3c-aa94cdfc6d3f 8/10 10/18/24, 4:17 PM Use Cases and User Stories in Software Analysis Study Guide | Quizlet This assumption allows designers to focus on core functionalities without being distracted by system controls. Examples of system controls to exclude initially include: Backing up a database. User login processes. Restoring the database. This approach streamlines the design process, allowing for a more focused development of essential features. Implications of the Perfect Technology Assumption By not worrying about technological limitations initially, designers can prioritize user needs and system functionalities. It encourages a more innovative approach to system design, as potential constraints are addressed later in the process. This assumption can lead to more efficient and user-friendly systems, as the focus remains on delivering value to users. However, it is crucial to eventually incorporate necessary controls to ensure system reliability and security. Summary of Use Cases Identifying Use Cases Use cases represent the functions and activities that a system performs in response to user requests. Two primary techniques for identifying use cases are: 1. User goal technique: Focuses on end users and their specific goals. 2. Event decomposition technique: Focuses on events that require system responses. Understanding these techniques is essential for effective system design and ensuring user satisfaction. This product is enhanced by AI and may provide incorrect or problematic content. Please report any content that needs Use cases shouldreview.be documented clearly to guide development and testing processes. Study this material Flashcards https://quizlet.com/study-guides/use-cases-and-user-stories-in-software-analysis-780d8073-b1ab-46f3-8e3c-aa94cdfc6d3f 9/10 10/18/24, 4:17 PM Use Cases and User Stories in Software Analysis Study Guide | Quizlet Practice questions https://quizlet.com/study-guides/use-cases-and-user-stories-in-software-analysis-780d8073-b1ab-46f3-8e3c-aa94cdfc6d3f 10/10