[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-655908-105":3,"detail-sidebar-cat-0-en-105":81,"doc-detail-655908-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":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","6-use-cases","6 - USE CASES","","Chapter 6 explains how use cases function as essential text stories for discovering and recording functional requirements. It outlines objectives for identifying and writing use cases using brief, casual, and fully dressed formats, applying tests to choose suitable cases, and linking use case analysis to iterative development. The chapter discusses how use cases influence other UP artifacts, introduces sample artifact relationships, and provides examples plus definitions of actors, scenarios, and use cases, including success and failure paths.",{"@graph":14,"@context":73},[15,34,56],{"@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/6-use-cases/655908/",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/6-use-cases/655908.png","ImageObject",300,407,{"name":42,"@type":43},"lugxt","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-30","2026-10-25",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",5,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"What are use cases in this chapter’s approach to requirements?","Question",{"text":63,"@type":64},"Use cases are text stories that capture how an actor uses a system to meet goals, thereby discovering and recording functional requirements.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"How do use case diagrams relate to use cases?",{"text":68,"@type":64},"Use case diagrams are optional for context, but use cases themselves are text; focusing on diagrams instead of use case text is a common mistake.",{"name":70,"@type":61,"acceptedAnswer":71},"What is the difference between an actor and a scenario?",{"text":72,"@type":64},"An actor is something with behavior (e.g., a cashier), while a scenario is a specific sequence of actions and interactions between actors and the system, representing a use case instance.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},655908,1793074492,{"code":4,"msg":82,"data":83},"success",[84,88,92,96,100,104,109,114,119,122,126],{"id":22,"doc_module":4,"doc_module_name":25,"category_name":85,"show_sort_weight":86,"slug":87},"Story & Novel",90,"story-novel",{"id":26,"doc_module":4,"doc_module_name":25,"category_name":89,"show_sort_weight":90,"slug":91},"Literature",80,"literature",{"id":33,"doc_module":4,"doc_module_name":25,"category_name":93,"show_sort_weight":94,"slug":95},"Exam",70,"exam",{"id":55,"doc_module":4,"doc_module_name":25,"category_name":97,"show_sort_weight":98,"slug":99},"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":55,"slug":129},19,"General","general",{"code":4,"msg":82,"data":131},{"doc_id":79,"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":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":107,"language":139,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":140,"faqs":141,"seo_title":142,"seo_description":12,"update_tm":143,"read_time":144},3985747862600,"https://ap-avatar.wpscdn.com/davatar_9964176cb1d06d4a9deccf72a44ae3dc","[UM](UML and Patterns.book)[L and Patterns.book](UML and Patterns.book) Page 61  \nThursday, September 16, 2004 9:48 PM  \nChapter  \n6  \nUSE CASES  \nThe indispensable first step to getting the things you want out of life: decide what you want.  \n—Ben Stein  \nObjectives  \n■ Identify and write use cases.  \n■ Use the brief, casual, and fully dressed formats, in an essential style.  \n■ Apply tests to identify suitable use cases.  \n■ Relate use case analysis to iterative development.  \nIntroduction  \nintermediate use case topics p. 493  \nUse cases are text stories, widely used to discover and record requirements. They influence many aspects of a project—including OOA/D—and will be input to many subsequent artifacts in the case studies. This chapter explores basic concepts, including how to write use cases and draw a UML use case diagram. This chapter also shows the value of analysis skill over knowing UML notation; the UML use case diagram is trivial to learn, but the many guidelines to identify and write good use cases take weeks—or longer—to fully digest.  \nWhat’s Next?  \nHaving introduced requirements, this chapter explores use cases for functional requirements. The next covers other requirements in the UP, including the Supplementary Specification for non-functional requirements.  \nInception  \nEvolutionary Requirements  \nUse Cases  \nOther Requirements  \nIteration 1 Requirements  \n61   \n[UM](UML and Patterns.book)[L and Patterns.book](UML and Patterns.book) Page 62  \nThursday, September 16, 2004 9:48 PM  \n6 – USE CASES  \nSample UP Artifact Relationships  \nDomain Model  \nBusiness Modeling  \nscope, goals, Vision  \nRequirements  \nFigure 6. 1 Sample UP artifact influence.  \nThe influence of UP artifacts, with an emphasis on text use cases, is shown in Figure 6.1. High-level goals and use case diagrams are input to the creation of the use case text. The use cases can in turn influence many other analysis, design, implementation, project management, and test artifacts.  \n62   \n[UM](UML and Patterns.book)[L and Patterns.book](UML and Patterns.book) Page 63  \nThursday, September 16, 2004 9:48 PM  \nEXAMPLE  \n6.1 Example  \nUML use case diagrams p. 89  \nInformally, use cases are text stories of some actor using a system to meet goals. Here is an example brief format use case:  \nProcess Sale: A customer arrives at a checkout with items to purchase. The cashier uses the POS system to record each purchased item. The system presents a running total and line-item details. The customer enters payment information, which the system validates and records. The system updates inventory.  \nThe customer receives a receipt from the system and then leaves with the items.  \nNotice that use cases are not diagrams, they are text. Focusing on secondary-value UML use case diagrams rather than the important use case text is a common mistake for use case novices.  \nUse cases often need to be more detailed or structured than this example, but the essence is discovering and recording functional requirements by writing stories of using a system to fulfill user goals; that is, cases of use.1 It isn’t supposed to be a difficult idea, although it’s often difficult to discover what’s needed and write it well.  \n6.2 Definition: What are Actors, Scenarios, and Use Cases?  \nFirst, some informal definitions: an actor is something with behavior, such as a person (identified by role), computer system, or organization; for example, a cashier.  \nA scenario is a specific sequence of actions and interactions between actors and the system; it is also called a use case instance. It is one particular story of using a system, or one path through the use case; for example, the scenario of successfully purchasing items with cash, or the scenario of failing to purchase items because of a credit payment denial.  \nInformally then, a use case is a collection of related success and failure scenarios that describe an actor using a system to support a goal. For example, here is a casual forma","cbCaibTDibFvt9yA","https://ap.wps.com/l/cbCaibTDibFvt9yA","pdf",2636484,"English","# Objectives\n# Introduction\n# What’s Next?\n# Inception\n# Evolutionary Requirements\n# Use Cases\n# Other Requirements\n# Iteration 1 Requirements\n# Sample UP Artifact Relationships\n# Example 6.1\n# Definition: What are Actors, Scenarios, and Use Cases?\n# Use Cases and the Use-Case Model","[{\"question\":\"What are use cases in this chapter’s approach to requirements?\",\"answer\":\"Use cases are text stories that capture how an actor uses a system to meet goals, thereby discovering and recording functional requirements.\"},{\"question\":\"How do use case diagrams relate to use cases?\",\"answer\":\"Use case diagrams are optional for context, but use cases themselves are text; focusing on diagrams instead of use case text is a common mistake.\"},{\"question\":\"What is the difference between an actor and a scenario?\",\"answer\":\"An actor is something with behavior (e.g., a cashier), while a scenario is a specific sequence of actions and interactions between actors and the system, representing a use case instance.\"}]","6 - USE CASES | PDF",1792964719,101]