[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-665499-105":59,"doc-detail-665499-en":130},{"code":4,"msg":5,"data":6},0,"success",[7,13,18,23,28,33,38,43,48,51,55],{"id":8,"doc_module":4,"doc_module_name":9,"category_name":10,"show_sort_weight":11,"slug":12},1,"Document","Story & Novel",90,"story-novel",{"id":14,"doc_module":4,"doc_module_name":9,"category_name":15,"show_sort_weight":16,"slug":17},2,"Literature",80,"literature",{"id":19,"doc_module":4,"doc_module_name":9,"category_name":20,"show_sort_weight":21,"slug":22},4,"Exam",70,"exam",{"id":24,"doc_module":4,"doc_module_name":9,"category_name":25,"show_sort_weight":26,"slug":27},5,"Comic",60,"comic",{"id":29,"doc_module":4,"doc_module_name":9,"category_name":30,"show_sort_weight":31,"slug":32},6,"Technology",50,"technology",{"id":34,"doc_module":4,"doc_module_name":9,"category_name":35,"show_sort_weight":36,"slug":37},7,"Healthcare",40,"healthcare",{"id":39,"doc_module":4,"doc_module_name":9,"category_name":40,"show_sort_weight":41,"slug":42},8,"Research & Report",30,"research-report",{"id":44,"doc_module":4,"doc_module_name":9,"category_name":45,"show_sort_weight":46,"slug":47},9,"Religion & Spirituality",20,"religion-spirituality",{"id":46,"doc_module":4,"doc_module_name":9,"category_name":49,"show_sort_weight":46,"slug":50},"World Cup","world-cup",{"id":52,"doc_module":4,"doc_module_name":9,"category_name":53,"show_sort_weight":52,"slug":54},10,"Lifestyle","lifestyle",{"id":56,"doc_module":4,"doc_module_name":9,"category_name":57,"show_sort_weight":24,"slug":58},19,"General","general",{"code":4,"msg":60,"data":61},"ok",{"site_id":62,"language":63,"slug":64,"title":65,"keywords":66,"description":67,"schema_data":68,"social_meta":123,"head_meta":125,"extra_data":127,"updated_unix":129},105,"en","use-case-based-requirements","Use Case-based Requirements","","Use Case-based Requirements outlines how to document stakeholder functional requirements using use cases supported by textual descriptions and UML use case diagrams. It introduces UML as a modeling notation for object-oriented “blueprints,” explains the value of diagrams for communicating with both technical and non-technical stakeholders, and shows how use cases guide later design and testing. The chapter also covers scenario-based requirements elicitation by collecting stakeholder stories and mapping them into actor/use case specifications, then defines core use case elements and their relationship to scenarios.",{"@graph":69,"@context":122},[70,84,105],{"@type":71,"itemListElement":72},"BreadcrumbList",[73,77,79,82],{"item":74,"name":75,"@type":76,"position":8},"https://docshare.wps.com","Home","ListItem",{"item":78,"name":9,"@type":76,"position":14},"https://docshare.wps.com/document/",{"item":80,"name":30,"@type":76,"position":81},"https://docshare.wps.com/document/technology/",3,{"item":83,"name":65,"@type":76,"position":19},"https://docshare.wps.com/document/use-case-based-requirements/665499/",{"url":83,"name":65,"@type":85,"image":86,"author":91,"headline":65,"publisher":94,"fileFormat":97,"inLanguage":63,"description":67,"dateModified":98,"datePublished":99,"encodingFormat":97,"isAccessibleForFree":100,"interactionStatistic":101},"DigitalDocument",{"url":87,"@type":88,"width":89,"height":90},"https://docshare.wps.com/thumbnails/use-case-based-requirements/665499.png","ImageObject",300,407,{"name":92,"@type":93},"4398046744996","Person",{"url":74,"name":95,"@type":96},"DocShare","Organization","application/pdf","2026-10-30","2026-10-29",true,{"@type":102,"interactionType":103,"userInteractionCount":81},"InteractionCounter",{"@type":104},"ViewAction",{"@type":106,"mainEntity":107},"FAQPage",[108,114,118],{"name":109,"@type":110,"acceptedAnswer":111},"What is the purpose of documenting requirements with use cases?","Question",{"text":112,"@type":113},"It provides a structured way to capture stakeholder functional requirements using textual descriptions and use case diagrams, which helps later design, testing, and user manual writing.","Answer",{"name":115,"@type":110,"acceptedAnswer":116},"Why is UML introduced in this chapter?",{"text":117,"@type":113},"UML is presented as the diagrammatic notation that includes use case diagrams for requirements and other diagram types useful for object-oriented analysis and design.",{"name":119,"@type":110,"acceptedAnswer":120},"How does scenario-based requirements elicitation work?",{"text":121,"@type":113},"It gathers stakeholder expectations by asking questions tied to descriptive stories, mapping collected scenarios into a specification represented by actors and use cases.","https://schema.org",{"og:url":83,"og:type":124,"og:title":65,"og:site_name":95,"og:description":67},"article",{"robots":126,"canonical":83},"index,follow",{"doc_id":128,"site_id":62},665499,1793304512,{"code":4,"msg":5,"data":131},{"doc_id":128,"user_id":132,"nickname":92,"user_avatar":66,"doc_module":4,"category_id":29,"category_name":30,"doc_title":65,"doc_description":67,"doc_content":133,"file_id":134,"file_url":135,"file_type":136,"file_size":137,"view_count":81,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":138,"language":139,"language_code":63,"site_id":62,"html_lang":63,"table_of_contents":140,"faqs":141,"seo_title":142,"seo_description":67,"update_tm":129,"read_time":143},4398046744996,"By Laurie Williams, Associate Department Head and Professor North Carolina State University Department of Computer Science  \nUse Case-based Requirements  \nThis chapter gives an overall introduction to documenting requirements using use cases. In this chapter, we will explain the following:  \n• the symbols found in a use case diagrams  \n• the relationships between the symbols in a use case diagram  \n• the textual description of a use case, the use case flow of events  \nIt is quite likely that you have written code in an object-oriented language, such as Java or C++ . In these object-oriented languages, you have come to create your programs in terms of classes where each class has its own data (via variables/attributes) and its own behavior (via the class methods) . In your programs, you create instances of these classes, called objects. As your program runs, these objects interact with each other to implement the system functionality.  \nIn this chapter we will discuss a means of documenting your stakeholder functional requirements in a way that will more easily lead you to discover what classes you will need to implement. This approach is called the use cases approach (Jacobson, Christerson et al., 1992) . When you document your requirements using use cases, these use cases are then valuable during the next steps in your project development – such as in the design and testing activities. Also, it will be easier to write your user manual if you have documented your requirements by means of use cases.  \nWhen we document requirements using use cases, we use textual description along with use case diagrams. The use case diagram is a part of the Unified Modeling Language (Rumbaugh, Jacobson et al., 1999), more commonly referred to as UML. In this chapter, we will first introduce you to UML. Then, we will show you how to document your requirements using use cases.  \n1 An Introduction to UML  \nUML is a modeling language or graphical/diagrammatic notation for object-oriented programming – a way to express the “blueprints” of your system. Within UML, there are several types of diagrams. Some of them are:  \n• Use case diagrams for requirements  \n• State diagrams for object-oriented analysis  \n• Class diagrams and sequence diagrams for object-oriented design  \nAs a software engineer, you need to become well-versed in these UML diagrams. As you head towards your professional life, your peers will simply assume that you know these diagrams. When you brainstorm together, your co-workers will quickly draw one of these diagrams on a whiteboard without explaining the symbols or notations, fully expecting that you understand. Or, you might receive UML-based requirements, analysis, or design documents that you will need to work with.  \n[agile.csc. ncsu.edu-SEMaterials-UseCaseRequirements.pdf](agile.csc. ncsu.edu-SEMaterials-UseCaseRequirements.pdf)  \nUse Case-based Requirements  \nOnce you know UML, you can also communicate with your peers using the diagrams too. You know the old adage,“A picture is worth a thousand words.” You can spend a few moments reviewing a use case, class, or sequence diagram and have a pretty good understanding of what even large programs do. UML diagrams are also very understandable to non-technical stakeholders. So, these diagrams are useful for validating requirements.  \n2 Scenario-based Requirements Elicitation  \nBefore jumping into use cases themselves, we will first describe a scenario, which is a subset of a use case. A scenario is a sequence of actions that illustrates behavior. A scenario may be used to illustrate an interaction or the execution of a use case instance.(Rumbaugh, Jacobson et al., 1999) Scenarios are used in a scenario-based requirements elicitation, a technique of asking questions related to a descriptive story in order to ascertain the design requirements. For example, consider the following scenario for the Monopoly game:  \nPlayer 1 lands on Blue 3. This house is owned by Player 2, and the rent i","cbCailegJ6aRwiaJ","https://ap.wps.com/l/cbCailegJ6aRwiaJ","pdf",586481,23,"English","# Use Case-based Requirements\n## An Introduction to UML\n## Scenario-based Requirements Elicitation\n## Elements of a Use Case\n## Use Case Is Made Up of Scenarios","[{\"question\":\"What is the purpose of documenting requirements with use cases?\",\"answer\":\"It provides a structured way to capture stakeholder functional requirements using textual descriptions and use case diagrams, which helps later design, testing, and user manual writing.\"},{\"question\":\"Why is UML introduced in this chapter?\",\"answer\":\"UML is presented as the diagrammatic notation that includes use case diagrams for requirements and other diagram types useful for object-oriented analysis and design.\"},{\"question\":\"How does scenario-based requirements elicitation work?\",\"answer\":\"It gathers stakeholder expectations by asking questions tied to descriptive stories, mapping collected scenarios into a specification represented by actors and use cases.\"}]","Use Case-based Requirements | PDF",58]