[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-665497-105":3,"detail-sidebar-cat-0-en-105":80,"doc-detail-665497-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","software-engineering-requirements-engineering-use-cases","Software Engineering - Requirements Engineering - Use Cases","","Slides on requirements engineering focusing on use cases, defining a use case as a set of scenarios linked by a common user goal and describing how use cases guide other artifacts such as analysis, design, implementation, and testing. Includes a running example of a Point of Sale (POS) system with domain terminology (sale, receipt, line item, payment, customer, cashier). Presents key concepts actor, use case, and scenario, plus use case formats: brief, casual, and fully dressed, emphasizing accuracy before precision.",{"@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/software-engineering-requirements-engineering-use-cases/665497/",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/software-engineering-requirements-engineering-use-cases/665497.png","ImageObject",300,407,{"name":42,"@type":43},"Aran","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-30","2026-10-29",true,{"@type":52,"interactionType":53,"userInteractionCount":33},"InteractionCounter",{"@type":54},"ViewAction",{"@type":56,"mainEntity":57},"FAQPage",[58,64,68],{"name":59,"@type":60,"acceptedAnswer":61},"What is a use case in requirements engineering?","Question",{"text":62,"@type":63},"A use case is a collection of related success and failure scenarios describing an actor using a system to support a goal.","Answer",{"name":65,"@type":60,"acceptedAnswer":66},"How do use cases relate to other software development artifacts?",{"text":67,"@type":63},"Use cases influence analysis, design, implementation, and test artifacts.",{"name":69,"@type":60,"acceptedAnswer":70},"What are the main use case formats mentioned?",{"text":71,"@type":63},"The slides list brief, casual, and fully dressed use cases, differing in level of detail and inclusion of supporting sections.","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},665497,1793304508,{"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":33,"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},137455076865,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","Dr. Michael Eichberg  \nSoftware Engineering Department of Computer Science Technische Universität Darmstadt  \nSoftware Engineering  \nRequirements Engineering  \n• The following slides are primarily based on the contents of the following books:  \n• Writing Effective Use Cases;  \nAlistair Cockburn; Addison-Wesley, 2001 • Applying UML and Patterns;  \nCraig Larman; Markt und Technik, 2005 • UML Distilled, Third Edition;  \nMartin Fowler; Addison-Wesley, 2004  \nRequirements Engineering  \n• Use Cases  \nA use case is a set of scenarios tied together by a common user goal.  \nExamples are:  \n(a)“sign up for the exam”,(b)“make a bank transfer”.  \nUse cases can not be used for all  \nkinds of requirements!  \nUse cases are text stories, widely used to discover and record requirements .  \nA use case encapsulates a set ofactions that are executed in a well defined order.  \nUse cases influence many other artifacts, e.g. analysis, design, implementation and test artifacts.  \nA Point of Sale (POS) System  \n(Point of sale system (POS System) =dt. Kassensystem)  \n Running Example-A POS System | 5   \n• POS systems are typically used in retail stores to record sales and to handle payments  \n• POS systems interface to various service applications to calculate taxes and for inventory control  \n• POS systems include computers, bar code scanners and software; the set of clients should vary, e.g. from thin-client web browser terminals, or rich client applications  \nThe running  \nexample scenario.  \nPoint of Sale Systems Domain Terminology  \n Running Example-A POS System | 6   \n• Sale-the exchange of a commodity for money  \n=dt. Verkauf  \n• Receipt =dt. Beleg  \n•(Sales) Line Item =dt.  \nEinzelposten / Belegposition  \n• Payment =dt. (Be)Zahlung /  \nVergütung  \n• Customer =dt. Kundin  \n• Cashier =dt. Kassiererin  \nUse cases are text stories, widely used to discover and record requirements .  \n Use Cases | 7   \nProcess Sale:  \nA customer arrives at a checkout with items to purchase. The cashier uses the POS system to record each item. The system presents a running total and lineitem details. The customer enters payment information, which the system validates and records. The system updates inventory. The customer receives a receipt from the system and then leaves with the items.  \nUse Cases-some Definitions  \n Use Cases | 8  \n• Actor  \n…something with behavior; e.g. a person, computer system or  \norganization.  \n• Use case  \n…is a collection of related success and failure scenarios that describe an actor using a system to support a goal.  \n• Scenario  \n[Also known as a “use case instance”.]  \n…a specific sequence of actions and interactions between actors and the system. It is one particular story using a system, or one path through the use cases .  \nUse Case Formats  \n Use Cases | 9  \n• Brief  \n(dt. kurz)  \nTerse one-paragraph summary, usually of the main success scenario (as seen above) .  \n• Casual  \n(dt. ungezwungen, zwanglos)  \nInformal paragraph format. Multiple paragraphs that cover various scenarios.  \n• Fully dressed  \n(dt. vollständig bearbeitet)  \nAll steps and variations are written in detail, and there are supporting sections, such as preconditions and success guarantees.  \nFocus on the accuracy of use cases before you focus on the precision.  \naccuracy =dt. Korrektheit  \nprecision =dt. Genauigkeit (~hier Detailgrad)  \n Use Cases | 10   \n• …identify all currently relevant use cases at a very high level (low precision, high accuracy)  \n• …work out the details  \n(add precision)","cbCaisMNJTtD9POh","https://ap.wps.com/l/cbCaisMNJTtD9POh","pdf",4295247,35,"English","# Use Cases\n## Key Definitions and Concepts\n## POS System Running Example and Terminology\n## Use Case Formats\n## Accuracy vs Precision","[{\"question\":\"What is a use case in requirements engineering?\",\"answer\":\"A use case is a collection of related success and failure scenarios describing an actor using a system to support a goal.\"},{\"question\":\"How do use cases relate to other software development artifacts?\",\"answer\":\"Use cases influence analysis, design, implementation, and test artifacts.\"},{\"question\":\"What are the main use case formats mentioned?\",\"answer\":\"The slides list brief, casual, and fully dressed use cases, differing in level of detail and inclusion of supporting sections.\"}]","Software Engineering - Requirements Engineering - Use Cases | PDF",88]