[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-657649-105":59,"doc-detail-657649-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","modelling-scenarios-use-cases-structured-natural-language-and-uml-sequence-diagrams","Modelling Scenarios & Use Cases - Structured natural language and UML Sequence Diagrams","","Modelling Scenarios & Use Cases explains how to represent temporal interaction behaviors between agents using scenarios and UML sequence diagrams. It contrasts positive vs. negative and normal vs. exceptional scenarios, then shows structured natural language step sequences. The material further aligns scenarios with context diagrams, and introduces use cases, including relationships to scenarios and scope from product-level to system-level. Examples describe preconditions, postconditions, main and alternative success scenarios. Practical tips cover decomposition granularity, active voice, and user-focused intent rather than interface details.",{"@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":40,"@type":76,"position":81},"https://docshare.wps.com/document/research-report/",3,{"item":83,"name":65,"@type":76,"position":19},"https://docshare.wps.com/document/modelling-scenarios-use-cases-structured-natural-language-and-uml-sequence-diagrams/657649/",{"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/modelling-scenarios-use-cases-structured-natural-language-and-uml-sequence-diagrams/657649.png","ImageObject",300,407,{"name":92,"@type":93},"Malam Tenang","Person",{"url":74,"name":95,"@type":96},"DocShare","Organization","application/pdf","2026-10-30","2026-10-26",true,{"@type":102,"interactionType":103,"userInteractionCount":19},"InteractionCounter",{"@type":104},"ViewAction",{"@type":106,"mainEntity":107},"FAQPage",[108,114,118],{"name":109,"@type":110,"acceptedAnswer":111},"What is a scenario, and how can it be classified?","Question",{"text":112,"@type":113},"A scenario is a temporal sequence of interactions between agents. It can be positive vs. negative (what may happen vs. what should not happen) and normal vs. exceptional (normal sequences vs. desired sequences when deviating).","Answer",{"name":115,"@type":110,"acceptedAnswer":116},"How do structured natural language and UML sequence diagrams help modelling scenarios?",{"text":117,"@type":113},"Structured natural language expresses sequences as steps in the form \u003Cagent> \u003Cperforms an action>. UML sequence diagrams visualize participating agents and message exchanges, supporting clearer communication of interactions.",{"name":119,"@type":110,"acceptedAnswer":120},"What is the relationship between scenarios and use cases?",{"text":121,"@type":113},"The notes describe different relations, including 1 use case = 1 scenario or 1 use case = a set of scenarios. A common definition is that a use case is a set of scenarios describing sequences of interactions with the machine related to a single user’s goal.","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},657649,1793095874,{"code":4,"msg":5,"data":131},{"doc_id":128,"user_id":132,"nickname":92,"user_avatar":133,"doc_module":4,"category_id":39,"category_name":40,"doc_title":65,"doc_description":67,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":19,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":139,"language":140,"language_code":63,"site_id":62,"html_lang":63,"table_of_contents":141,"faqs":142,"seo_title":143,"seo_description":67,"update_tm":144,"read_time":36},962093532863,"https://ap-avatar.wpscdn.com/davatar_276721f389ce27ea32af1340a28f341c","Modelling Scenarios & Use Cases  \nEmmanuel Letier Department of Computer Science University College London [http://www.cs.ucl.ac.uk/people/E.Letier](http://www.cs.ucl.ac.uk/people/E.Letier)  \n1  \nScenarios  \n• Scenario = temporal sequence of interactions between agents  \n– positive scenario (what may happen)  \nvs. negative scenario (what should not happen)  \n– normal scenario (describe normal sequence of events) vs. exceptional scenario (describe desired sequence of events when one deviates from normal scenarios)  \n• Notations  \n– Structured natural language  \n– UML Sequence Diagrams  \n2   \nStructured natural language description  \nSequences of steps: \u003Cagent> \u003Cperforms an action>  \n1 . a member of the Public calls the emergency service  \n2 . a Control Assistant (CA) answers the calls and writes down the call details on a pre-printed form  \n3 . the CA identifies the incident location on a map book  \n4 . when the call is completed, the CA places the form on a conveyor belt  \n5 . the conveyor belt transports the form to the central collection point  \n6. ...  \n3  \nUML Sequence Diagrams (SD)  \nPublic  \nControl Assistant  \nForm Despatcher  \nResource Allocator  \nAmbulance Despatcher  \nAmbulance Station  \n\n| make UrgentCall\u003Cbr>| send\u003Cbr>IncidentForm\u003Cbr>|\n| --- | --- |\n\n• Modelling tips  \n– at RE level, don't decompose the Machine into components  \n– don't include guards on events, alternative branches, loops  \n• a scenario is one example of execution of the system  \n4  \nConsistency between Scenarios and Context Diagrams  \n• Agents in scenarios must correspond to agents the context diagram  \n• Agent interactions in scenarios must correspond to interfaces in the context diagram  \n5  \nUse Cases  \nComputer Aided Despatch Software  \nCall Handler  \nAllocator  \nAllocate Ambulance  \nSend Mobilization Instructions  \nUpdate Status Information  \nAmbulance Localisation System  \nMobile Data Terminal  \n• Useful to show the boundary of the Machine  \n-unlike context diagrams, it doesn’t show other interactions in the World & is vague about physical interfaces (shared phenomena)  \n• Contents of use cases must be described !  \n6   \nUse Cases  \n• Many different definitions of what a use case is  \n– Different relations to scenarios  \n• 1 use case = 1 scenario  \n• 1 use case = set of scenarios  \n– Different scopes  \n• product-level use cases: represent only interactions with the Machine ( [i.e. events](i.e. events) in the World outside the machine are not considered!)  \n• system-level use cases: represent interactions between agents in the World and with the Machine  \n• Most common definition (A . Cockburn)  \nA use case is a set of scenarios describing sequences of interactions with the machine related to a single  \nuser’s goal  \n7   \nExample of format for describing use cases  \nUseCase Encode Call Details  \nPreconditon an incoming call is waiting to be answered Postconditon a IncidentForm is created and passed to the relevant  \nAllocator  \nMain success scenario  \n1 . Call Handler (CH) responds to call  \n2 . CH encodes incident details  \n3 . CH validates incident location with map gazetteer  \n4 . CH terminates call  \n5 . CAD software assigns incident to relevant Allocator Alternative scenarios  \n2a. CH determines calls does not require intervention 2b. Caller or Phone network terminates call  \n.1 CH determines calls does not require intervention  \n.1a CH determines call could require intervention  \n...  \n8  \nUse Case Modelling Tips (1)  \n(based on A. Cockburn, Writing Effective Use Cases, Addison-Wesley, 2000)  \n• Use active voice to show who performs the action \u003Cactor> \u003Cperforms action>  \n– Bad: the call is terminated  \n– Good: the Call Handler terminates call  \n• Write use case from the user’s perspective, not from the software perspective  \n– Bad  \n1. Get card  \n2. Get PIN  \n3. Get transaction type 4. ...  \n– Good  \n1. costumer inserts card into ATM  \n2. costumer encodes PIN  \n3. ... 9   \nUse Case Modelling Tips (2)  \n(based on A. Cockburn, Writing Eff","cbCaijR0L1E3pfit","https://ap.wps.com/l/cbCaijR0L1E3pfit","pdf",143537,16,"English","# Scenarios\n## Structured natural language description\n## UML sequence diagrams (SD)\n# Consistency between Scenarios and Context Diagrams\n# Use Cases\n## Definitions and scope of use cases\n## Example format for describing use cases\n# Use Case Modelling Tips\n## Tips based on A. Cockburn (1)\n## Tips based on A. Cockburn (2)","[{\"question\":\"What is a scenario, and how can it be classified?\",\"answer\":\"A scenario is a temporal sequence of interactions between agents. It can be positive vs. negative (what may happen vs. what should not happen) and normal vs. exceptional (normal sequences vs. desired sequences when deviating).\"},{\"question\":\"How do structured natural language and UML sequence diagrams help modelling scenarios?\",\"answer\":\"Structured natural language expresses sequences as steps in the form \\u003cagent\\u003e \\u003cperforms an action\\u003e. UML sequence diagrams visualize participating agents and message exchanges, supporting clearer communication of interactions.\"},{\"question\":\"What is the relationship between scenarios and use cases?\",\"answer\":\"The notes describe different relations, including 1 use case = 1 scenario or 1 use case = a set of scenarios. A common definition is that a use case is a set of scenarios describing sequences of interactions with the machine related to a single user’s goal.\"}]","Modelling Scenarios & Use Cases - Structured natural language and UML Sequence Diagrams | PDF",1792985781]