[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-657624-105":59,"doc-detail-657624-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","synthesis-of-state-machines-from-multiple-interrelated-scenarios-using-dependency-diagrams","Synthesis of State Machines from Multiple Interrelated Scenarios Using Dependency Diagrams","","Requirements specification is a key phase in software development, where system behavior is captured through multiple interrelated scenarios. Many existing approaches translate scenarios into state machines in isolation, despite the fact that scenario relationships lead to different resulting models. The work introduces dependency diagrams and provides rules and steps to synthesize state machines from several scenarios, using these diagrams as support throughout design and implementation.",{"@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/synthesis-of-state-machines-from-multiple-interrelated-scenarios-using-dependency-diagrams/657624/",{"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/synthesis-of-state-machines-from-multiple-interrelated-scenarios-using-dependency-diagrams/657624.png","ImageObject",300,407,{"name":92,"@type":93},"dabgoudw","Person",{"url":74,"name":95,"@type":96},"DocShare","Organization","application/pdf","2026-10-29","2026-10-26",true,{"@type":102,"interactionType":103,"userInteractionCount":14},"InteractionCounter",{"@type":104},"ViewAction",{"@type":106,"mainEntity":107},"FAQPage",[108,114,118],{"name":109,"@type":110,"acceptedAnswer":111},"Why do the authors treat scenario relationships as important for state machine synthesis?","Question",{"text":112,"@type":113},"Different relationships between scenarios produce different state machines. The authors therefore emphasize representing these relationships instead of translating each scenario separately.","Answer",{"name":115,"@type":110,"acceptedAnswer":116},"What are dependency diagrams used for?",{"text":117,"@type":113},"Dependency diagrams are a newly introduced diagram type that represent classified relationships and dependencies among scenarios, serving as input for synthesizing state machines.",{"name":119,"@type":110,"acceptedAnswer":120},"How do scenarios and state machines provide different perspectives on system behavior?",{"text":121,"@type":113},"A scenario corresponds to a single trace of behavior for a complete set of objects, while a state machine describes the complete behavior of a single object. Together they provide an orthogonal view, and transforming scenarios into state machines enables leveraging both benefits.","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},657624,1792985395,{"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":14,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":39,"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":46},3985747860484,"https://ap-avatar.wpscdn.com/davatar_276721f389ce27ea32af1340a28f341c","Synthesis of State Machines from Multiple Interrelated Scenarios Using Dependency Diagrams  \nSimona VASILACHE  \nDepartment of Computer Science, University of Tsukuba  \nTsukuba, Ibaraki 305-8573, Japan  \nand  \nJiro TANAKA  \nDepartment of Computer Science, University of Tsukuba  \nTsukuba, Ibaraki 305-8573, Japan  \nABSTRACT  \nRequirements specification is one of the most important phasesin developing a software application. In defining the behavior of a system, requirements specifications make use of a number of scenarios that are interrelated in many ways. Most of the current approaches, even though giving directions on how to translate them into state machines, treat each scenario separately. Because different relationships between scenarios result in different state machines, we believe it is significant to emphasize and represent these relationships. In order to illustrate them we propose a new type of diagrams named dependency diagrams. We offer a set of rules and steps for the synthesis of state machines from multiple inter-related scenarios, based on the initial scenarios and on the newly introduced dependency diagrams, as a means to describe the requirements specifications and to offer support during the design and implementation phases of developing a system.  \nKeywords: requirements specification, dynamic modeling, scenarios, state machines.  \n1. INTRODUCTION  \nRequirements analysis represents a crucial phase in the software development process. The main task of the requirements analysis is to generate specifications that describe the behavior of a system unambiguously, consistently and completely [1] . Several object-oriented methodologies and notations (like OMT [2], UML [23]) make use of scenarios as a means of capturing requirements specifications, as well as a means of communication between users and software developers. A scenario is a sequence of events that occurs during one particular execution of a system [1], it is one particular “story” of using a system.  \nDuring the recent years, scenarios have gained considerable popularity. However, we believe that they have not yet received the attention they actually deserve and they have not been used up to their entire potential. Their usefulness lies not only in the ability to capture requirements, but also in their applicability when used in conjunction with other models. We specifically refer to what is called \"behavior models\", that is models that describe the behavior of a system.  \nState machines (particularly statecharts, originally introduced by D. Harel [3]), represent a compact and elegant way of describing the aspects concerning the behavior of a system.  \nThey can be used not only for behavioral requirements specifications, but also for detailed design models close to implementation [4] .  \nWhile scenarios represent a single trace of behavior of a complete set of objects, state machines represent the complete behavior of a single object. Together, they provide an orthogonal view of a system. By transforming scenarios into state machines, we can take advantage of the benefits offered by both of these concepts.  \nScenarios are generally not independent of each other; various relationships and dependencies connect them. We make a classification of these relationships and in order to represent them we propose a new type of diagrams. We call these diagrams dependency diagrams.  \nBased on these dependency diagrams and on the given scenarios, we give rules and steps of synthesis of state machines from multiple interrelated scenarios. We will describe in this paper the newly introduced diagrams and our method of synthesis.  \nThe remainder of the paper is organized as follows: section 2 offers an overview of scenarios and state machines. In section 3 we make a classification of the relationships that can exist between various scenarios and we describe the dependency diagrams. Section 4 illustrates the synthesis of state machines from multiple scenarios. Section 5 ","cbCaiiZfNsoV6neg","https://ap.wps.com/l/cbCaiiZfNsoV6neg","pdf",359998,"English","# Introduction\n## Sequence Diagrams and State Machine Diagrams\n## Scenarios as Sequence Diagrams\n## State Machine Diagrams\n# Dependency Diagrams and Scenario Relationships\n## Classification of Relationships Between Scenarios\n# Synthesis of State Machines from Multiple Scenarios\n## Synthesis Rules and Steps\n# Discussion and Related Work\n## Issues\n## Related Work\n# Conclusions","[{\"question\":\"Why do the authors treat scenario relationships as important for state machine synthesis?\",\"answer\":\"Different relationships between scenarios produce different state machines. The authors therefore emphasize representing these relationships instead of translating each scenario separately.\"},{\"question\":\"What are dependency diagrams used for?\",\"answer\":\"Dependency diagrams are a newly introduced diagram type that represent classified relationships and dependencies among scenarios, serving as input for synthesizing state machines.\"},{\"question\":\"How do scenarios and state machines provide different perspectives on system behavior?\",\"answer\":\"A scenario corresponds to a single trace of behavior for a complete set of objects, while a state machine describes the complete behavior of a single object. Together they provide an orthogonal view, and transforming scenarios into state machines enables leveraging both benefits.\"}]","Synthesis of State Machines from Multiple Interrelated Scenarios Using Dependency Diagrams | PDF"]