[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-665505-105":3,"detail-sidebar-cat-0-en-105":80,"doc-detail-665505-en":130},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":73,"head_meta":75,"extra_data":77,"updated_unix":79},105,"en","chapter-3-chapter-3-use-cases","Chapter 3 - Chapter 3 - Use Cases","","Chapter 3 explains how to identify and model functional requirements through use cases, linking them to user goals and system behavior. It outlines key activities from prior chapters, then demonstrates how analysts decompose a system into a set of use cases using two main techniques: the user goal technique and event decomposition. The chapter also introduces CRUD to validate and refine the use-case list, and teaches the notation and purpose of user case diagrams. Examples from RMO Tradeshow and Waiters on Call illustrate the process.",{"@graph":14,"@context":72},[15,34,55],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/document/","Document",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/document/technology/","Technology",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/document/chapter-3-chapter-3-use-cases/665505/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/chapter-3-chapter-3-use-cases/665505.png","ImageObject",300,407,{"name":42,"@type":43},"Aldword","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-30","2026-10-29",true,{"@type":52,"interactionType":53,"userInteractionCount":22},"InteractionCounter",{"@type":54},"ViewAction",{"@type":56,"mainEntity":57},"FAQPage",[58,64,68],{"name":59,"@type":60,"acceptedAnswer":61},"What is a use case and why is it important for functional requirements?","Question",{"text":62,"@type":63},"A use case is an activity the system performs, usually in response to a user request. Use cases define functional requirements by describing what the system must do for users.","Answer",{"name":65,"@type":60,"acceptedAnswer":66},"What are the two techniques for identifying use cases?",{"text":67,"@type":63},"The chapter presents the user goal technique and the event decomposition technique. Both are used to identify and structure possible use cases.",{"name":69,"@type":60,"acceptedAnswer":70},"How does CRUD help refine the list of use cases?",{"text":71,"@type":63},"CRUD is used to validate and refine the list of use cases. It helps ensure the identified use cases cover create, read, update, and delete behaviors where appropriate.","https://schema.org",{"og:url":32,"og:type":74,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":76,"canonical":32},"index,follow",{"doc_id":78,"site_id":7},665505,1793304528,{"code":4,"msg":81,"data":82},"success",[83,87,91,95,100,104,109,114,119,122,126],{"id":22,"doc_module":4,"doc_module_name":25,"category_name":84,"show_sort_weight":85,"slug":86},"Story & Novel",90,"story-novel",{"id":26,"doc_module":4,"doc_module_name":25,"category_name":88,"show_sort_weight":89,"slug":90},"Literature",80,"literature",{"id":33,"doc_module":4,"doc_module_name":25,"category_name":92,"show_sort_weight":93,"slug":94},"Exam",70,"exam",{"id":96,"doc_module":4,"doc_module_name":25,"category_name":97,"show_sort_weight":98,"slug":99},5,"Comic",60,"comic",{"id":101,"doc_module":4,"doc_module_name":25,"category_name":29,"show_sort_weight":102,"slug":103},6,50,"technology",{"id":105,"doc_module":4,"doc_module_name":25,"category_name":106,"show_sort_weight":107,"slug":108},7,"Healthcare",40,"healthcare",{"id":110,"doc_module":4,"doc_module_name":25,"category_name":111,"show_sort_weight":112,"slug":113},8,"Research & Report",30,"research-report",{"id":115,"doc_module":4,"doc_module_name":25,"category_name":116,"show_sort_weight":117,"slug":118},9,"Religion & Spirituality",20,"religion-spirituality",{"id":117,"doc_module":4,"doc_module_name":25,"category_name":120,"show_sort_weight":117,"slug":121},"World Cup","world-cup",{"id":123,"doc_module":4,"doc_module_name":25,"category_name":124,"show_sort_weight":123,"slug":125},10,"Lifestyle","lifestyle",{"id":127,"doc_module":4,"doc_module_name":25,"category_name":128,"show_sort_weight":96,"slug":129},19,"General","general",{"code":4,"msg":81,"data":131},{"doc_id":78,"user_id":132,"nickname":42,"user_avatar":133,"doc_module":4,"category_id":101,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":22,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":139,"language":140,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":141,"faqs":142,"seo_title":143,"seo_description":12,"update_tm":79,"read_time":144},2336478940917,"https://ap-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8","Chapter 3  \nUse Cases  \nChapter 3  \nSystems Analysis and Design in a Changing World 6th Ed  \nSatzinger, Jackson & Burd  \nChapter 3 Outline  \n􀁺 Use Cases and User Goals  \n􀁺 Use Cases and Event Decomposition  \n􀁺 Use Cases and CRUD  \n􀁺 Use Cases in the Ridgeline Mountain Outfitters Case  \n􀁺 User Case Diagrams  \nLearning Objectives  \n􀁺 Explain why identifying use cases is the key to defining functional requirements  \n􀁺 Describe the two techniques for identifying use cases  \n􀁺 Apply the user goal technique to identify use cases  \n􀁺 Apply the event decomposition technique to identify use cases  \n􀁺 Apply the CRUD technique to validate and refine the list of use cases  \n􀁺 Describe the notation and purpose for the use case diagram  \n􀁺 Draw use case diagrams by actor and by subsystem  \nOverview  \n􀁺 Chapter 2 provided an overview of systems analysis activities, functional and non-functional requirements, modeling, and information gathering techniques  \n􀁺 This chapter focuses on identifying and modeling the key aspect of functional requirements– use cases  \n􀁺 In the RMO Tradeshow System from Chapter 1 , some use cases are Look up supplier, Enter/update product information, Enter/Update contact information  \n􀁺 In this chapter’s opening case Waiters on Call, examples of use cases are Record an order, Record delivery, Update an order, Sign in driver, Reconcile driver receipts, Produce end of day deposit slip, and Produce weekly sales reports  \nUse Cases  \n􀁺 Use case—an activity that the system performs, usually in response to a request by a user  \n􀁺 Use cases define functional requirements  \n􀁺 Analysts decompose the system into a set of use cases (functional decomposition)  \n􀁺 Two techniques for Identifying use cases  \n􀁺 User goal technique  \n􀁺 Event decomposition technique  \n􀁺 Name each use case using Verb-Noun  \nUser Goal Technique  \n􀁺 This technique is the most common in industry  \n􀁺 Simple and effective  \n􀁺 Identify all of the potential categories of users of the system  \n􀁺 Interview and ask them to describe the tasks the computer can help them with  \n􀁺 Probe further to refine the tasks into specific user goals, “I need to Ship items , Track a shipment, Create a return”  \nUser Goal Technique Some RMO CSMS Users and Goals  \nUser Goal Technique: Specific Steps  \n1. Identify all the potential users for the new system  \n2. Classify the potential users in terms of their functional role (e.g. , shipping, marketing, sales)  \n3. Further classify potential users by organizational level (e.g. , operational, management, executive)  \n4. For each type of user, interview them to find a list of specific goals they will have when using the new system (current goals and innovative functions to add value)  \nUser Goal Technique  \nSpecific Steps (continued)  \n5. Create a list of preliminary use cases organized by type of user  \n6. Look for duplicates with similar use case names and resolve inconsistencies  \n7. Identify where different types of users need the same use cases  \n8. Review the completed list with each type of user and then with interested stakeholders","cbCaihVWNB3kzBPm","https://ap.wps.com/l/cbCaihVWNB3kzBPm","pdf",1657595,48,"English","# Chapter 3 Outline\n## Use Cases and User Goals\n## Use Cases and Event Decomposition\n## Use Cases and CRUD\n## Use Cases in the Ridgeline Mountain Outfitters Case\n## User Case Diagrams\n# Learning Objectives\n# Overview\n# Use Cases\n## User Goal Technique\n## User Goal Technique: Specific Steps\n## User Goal Technique (continued)","[{\"question\":\"What is a use case and why is it important for functional requirements?\",\"answer\":\"A use case is an activity the system performs, usually in response to a user request. Use cases define functional requirements by describing what the system must do for users.\"},{\"question\":\"What are the two techniques for identifying use cases?\",\"answer\":\"The chapter presents the user goal technique and the event decomposition technique. Both are used to identify and structure possible use cases.\"},{\"question\":\"How does CRUD help refine the list of use cases?\",\"answer\":\"CRUD is used to validate and refine the list of use cases. It helps ensure the identified use cases cover create, read, update, and delete behaviors where appropriate.\"}]","Chapter 3 - Chapter 3 - Use Cases | PDF",121]