[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-665483-105":3,"detail-sidebar-cat-0-en-105":81,"doc-detail-665483-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","information-systems-analysis-and-design-state-and-activity-diagrams","Information Systems Analysis and Design - State and Activity Diagrams","","Covers state and activity diagram concepts used to model an information system’s operating environment, interactions with external actors, and the lifetime of objects. Explains how transitions represent non-interruptible actions with an optional Event[Condition]/Action triple, while states capture longer-running activity or waiting. Defines events as triggers for actions and lists UML event types (change, signal, call, time). Describes state semantics (predicates, actions, eligible transitions) and introduces superstates (OR/AND) and nested abstraction.",{"@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/information-systems-analysis-and-design-state-and-activity-diagrams/665483/",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/information-systems-analysis-and-design-state-and-activity-diagrams/665483.png","ImageObject",300,407,{"name":42,"@type":43},"Cipher","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-30","2026-10-29",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 is the difference between transitions and states in UML state diagrams?","Question",{"text":63,"@type":64},"Transitions represent actions that occur quickly and are not interruptible, often modeled with an optional Event[Condition]/Action triple. States represent longer-running activities or waiting periods where predicates may hold and eligible outgoing transitions can fire when their events occur and conditions are true.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"How do events work as triggers for actions in these diagrams?",{"text":68,"@type":64},"An event is a happening the system must know about, and it can trigger actions carried out by actors or the system. UML distinguishes change, signal, call, and time events, each representing a different kind of occurrence.",{"name":70,"@type":61,"acceptedAnswer":71},"What are superstates, and how do OR and AND superstates differ?",{"text":72,"@type":64},"Superstates compose multiple nested states to improve readability and abstraction levels. In an AND superstate, all constituent states are on simultaneously, while in an OR superstate only one of the constituent states is on.","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},665483,1793304474,{"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":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":80,"read_time":144},687208528416,"https://ap-avatar.wpscdn.com/davatar_9964176cb1d06d4a9deccf72a44ae3dc","Information Systems Analysis and Design CSC340  \nIV. State and Activity Diagrams  \nState Diagrams  \nEvents and States  \nSuperstates  \nActivity Diagrams  \nPetri Nets  \n© 2002 Jaelson Castro and John Mylopoulos Statechart Diagrams-- 1  \nInformation Systems Analysis and Design CSC340  \nState Diagrams (Statecharts)  \n􀀁 These are state transition diagrams (with some interesting additions) which can be used to describe the operating environment of the system, interactions of the system with that environment, also the lifetime of some object (a person, a student,…) within or without the system.  \n􀀁 Transitions are supposed to represent actions which occur  \n“quickly” and are not interruptible. A transition can have an associated triple  \nEvent[Condition]/Action  \nall parts of this triple are optional.  \n􀀁 States are supposed to represent longer-running activities (or other things). What constitutes “quickly” and “longer-running”depends on the application.  \n© 2001 Jaelson Castro and John Mylopoulos State and Activity Diagrams-- 2  \nInformation Systems Analysis and Design  \nState Diagram for Purchase Order  \nCSC340  \nc~~ondition~~  \nstart  \n/get order  \nChecking  \nDo/check items  \nDispatching Do/package items  \naction  \nevent  \nItem received [some item not In stock]  \nWaiting  \n© 2001 Jaelson Castro and John Mylopoulos State and Activity Diagrams--3  \n\n| Information Systems Analysis and Design\u003Cbr>Events | CSC340 |\n| --- | --- |\n| 􀀁 An event is a happening that the system needs to know about.\u003Cbr>􀀁 For example, completing an assignment, failing an exam, or a system crash are all events.\u003Cbr>􀀁 An event may trigger an action by an actor or the system being developed.\u003Cbr>􀀁 In UML, there are four types of events:\u003Cbr>􀀂 Change events occur when a condition becomes true, e.g., when(balance \u003C 0);\u003Cbr>􀀂 Signal events designate the receipt of an explicit (real-time) signal from one object or actor to another;\u003Cbr>􀀂 Call events indicate the receipt of a call for an operation by an object or actor;\u003Cbr>􀀂 Time events mark the passage of a designated period of time, e.g., after(10 seconds)\u003Cbr>© 2001 Jaelson Castro and John Mylopoulos State and Activity Diagrams--4 |  |\n\nInformation Systems Analysis and Design  \nCourse Lifetimes  \nCSC340  \nofferNewCourse  \n/set count=0;create(CourseRoster)  \naddStudent[count\u003C10]  \n[Lochovsky98]  \nCancelled  \nClosed  \nOpen  \ncancel  \ncancel  \nquarterStarted  \n/delete(CourseRoster)   \n[count=10]  \nend state  \n© 2001 Jaelson Castro and John Mylopoulos State and Activity Diagrams--5  \n\n| Information Systems Analysis and Design\u003Cbr>States | CSC340 |\n| --- | --- |\n| 􀀁 A state represents a time period during which\u003Cbr>􀀂 A predicate is true, e.g., budget-expenses >0,\u003Cbr>􀀂 An action is being performed, e.g., check inventory for order items, or\u003Cbr>􀀂 Someone waits for an event to happen, e.g., arrival of a missing order item.\u003Cbr>􀀁 A state can be “on” or “off”.\u003Cbr>􀀁 When a state is “on”, all its outgoing transitions are eligible to fire. Fora transition to fire, its event must occur and its condition must be true. When a transition does fire, its action is carried out.\u003Cbr>􀀁 States can have associated activities. Special activity constructs include:\u003Cbr>􀀂 do/stateDiagramName(parameterList ) -- “calls” another state diagram;\u003Cbr>􀀂 entry/action--carry out the action when entering the activity;\u003Cbr>􀀂 exit/action--carry out the action when exiting;\u003Cbr>© 2001 Jaelson Castro and John Mylopoulos State and Activity Diagrams-- 6 |  |\n\nInformation Systems Analysis and Design  \nCourse Lifetimes, Again  \nCSC340  \n| Initialization |\n| --- |\n| do / Initialize |\n\naddStudent/  \ncount=0;CourseRoster .Create()  \naddStudent[count\u003C10]  \nOpen  \n[count=10]  \n| Cancelled | cancel | Closed |\n| --- | --- | --- |\n|  |  | do/FinalizeCourse |\n\n© 2001 Jaelson Castro and John Mylopoulos State and Activity Diagrams-- 7  \n\n| Information Systems Analysis and Design\u003Cbr>Superstates | CSC340 |\n| --- | --- |\n| 􀀁 State transition diagrams can be very hard to read once they gro","cbCaiosw1ISD4AZo","https://ap.wps.com/l/cbCaiosw1ISD4AZo","pdf",197519,11,"English","# State Diagrams\n## Events and States\n## Superstates\n# Activity Diagrams\n# Petri Nets","[{\"question\":\"What is the difference between transitions and states in UML state diagrams?\",\"answer\":\"Transitions represent actions that occur quickly and are not interruptible, often modeled with an optional Event[Condition]/Action triple. States represent longer-running activities or waiting periods where predicates may hold and eligible outgoing transitions can fire when their events occur and conditions are true.\"},{\"question\":\"How do events work as triggers for actions in these diagrams?\",\"answer\":\"An event is a happening the system must know about, and it can trigger actions carried out by actors or the system. UML distinguishes change, signal, call, and time events, each representing a different kind of occurrence.\"},{\"question\":\"What are superstates, and how do OR and AND superstates differ?\",\"answer\":\"Superstates compose multiple nested states to improve readability and abstraction levels. In an AND superstate, all constituent states are on simultaneously, while in an OR superstate only one of the constituent states is on.\"}]","Information Systems Analysis and Design - State and Activity Diagrams | PDF",28]