[{"data":1,"prerenderedAt":72},["ShallowReactive",2],{"content-guides-eventstorming-systems":3},{"markdown":4,"frontMatterAttributes":5,"bodyRaw":8,"contributorPaths":9,"menuType":11,"contentName":12,"slug":13,"readingTime":14,"menu":15,"nextDocItem":60,"previousDocItem":50},"\u003Cp>Next are external systems that your process uses or integrates with. A classic example is a payment\nprocessor. The example user sign-up flow delegates the work of validating and accepting payment to a\npayment processor like PayPal or Stripe.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"\u002Fassets\u002Fexternal\u002Fguides\u002Feventstorming\u002Fassets\u002Fdiagrams\u002Fsticky-notes-systems.png\" alt=\"Adding external systems helps to visualize dependencies\">\u003C\u002Fp>\n\u003Cp>EventStorming participants are often confused what constitutes a "system." Is a system what you're\nbuilding? Or, is it another internal tool or microservice? The following definition may help.\u003C\u002Fp>\n\u003Cblockquote>\n  \u003Cp>\n    An External System is whatever we can put the blame on\n  \u003C\u002Fp>\n  \u003Cdiv>\n    - Alberto Brandolini, \u003Ca href=\"https:\u002F\u002Fleanpub.com\u002Fintroducing_eventstorming\">Introducing EventStorming\u003C\u002Fa>\n  \u003C\u002Fdiv>\n\u003C\u002Fblockquote>\n\n\u003Cp>An external system can be anything you depend on that you do not directly control, like a 3rd party\nSaaS application. A system can also be something that you or your organization own and operate but\nis outside of the application you're modeling, like a user management system.\u003C\u002Fp>\n\u003Cp>In the example above, the payment processor is a 3rd party system that we integrate for payments.\nThe QR code generator could be an external system that another team in the company builds and runs.\nThe QR code generator could also be a microservice that our team has built but that we treat as a\n3rd party system for the "user onboarding" flow.\u003C\u002Fp>\n",{"title":6,"order":7},"Step 6 - External systems",60,"Next are external systems that your process uses or integrates with. A classic example is a payment\nprocessor. The example user sign-up flow delegates the work of validating and accepting payment to a\npayment processor like PayPal or Stripe.\n\n![Adding external systems helps to visualize dependencies](\u002Fassets\u002Fexternal\u002Fguides\u002Feventstorming\u002Fassets\u002Fdiagrams\u002Fsticky-notes-systems.png)\n\nEventStorming participants are often confused what constitutes a \"system.\" Is a system what you're\nbuilding? Or, is it another internal tool or microservice? The following definition may help.\n\n\u003Cblockquote>\n  \u003Cp>\n    An External System is whatever we can put the blame on\n  \u003C\u002Fp>\n  \u003Cdiv>\n    - Alberto Brandolini, \u003Ca href=\"https:\u002F\u002Fleanpub.com\u002Fintroducing_eventstorming\">Introducing EventStorming\u003C\u002Fa>\n  \u003C\u002Fdiv>\n\u003C\u002Fblockquote>\n\nAn external system can be anything you depend on that you do not directly control, like a 3rd party\nSaaS application. A system can also be something that you or your organization own and operate but\nis outside of the application you're modeling, like a user management system.\n\nIn the example above, the payment processor is a 3rd party system that we integrate for payments.\nThe QR code generator could be an external system that another team in the company builds and runs.\nThe QR code generator could also be a microservice that our team has built but that we treat as a\n3rd party system for the \"user onboarding\" flow.\n",[10],"content\u002Fcontributors\u002Fbrian-zambrano.json","LIST","EventStorming","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fsystems","2 min",[16],{"title":12,"content":17},[18,26,32,38,44,50,57,60,66],{"title":19,"order":20,"youtubeVideoID":21,"time":22,"path":23,"id":24,"link":25},"Introduction",1,"FG4UOoEJvBc","5 min","introduction","introduction.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fintroduction",{"title":27,"order":28,"time":14,"path":29,"id":30,"link":31},"Step 1 - Invitations",10,"invitations","invitations.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Finvitations",{"id":33,"title":34,"order":35,"time":14,"path":36,"link":37},"events.md","Step 2 - Crowdsource events",20,"events","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fevents",{"title":39,"order":40,"time":14,"path":41,"id":42,"link":43},"Step 3 - Sequence events",30,"timeline","timeline.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Ftimeline",{"title":45,"order":46,"time":14,"path":47,"id":48,"link":49},"Step 4 - People",40,"people","people.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fpeople",{"title":51,"order":52,"time":53,"path":54,"id":55,"link":56},"Step 5 - Hotspots",50,"1 min","hotspots","hotspots.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fhotspots",{"title":6,"order":7,"time":14,"path":58,"id":59,"link":13},"systems","systems.md",{"title":61,"order":62,"time":53,"path":63,"id":64,"link":65},"Step 7 - Pivotal events",70,"boundaries","boundaries.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fboundaries",{"id":67,"title":68,"time":69,"path":70,"link":71},"learn-more.md","Learning more","4 min","learn-more","\u002Fcontent\u002Fguides\u002Feventstorming\u002Flearn-more",1792578865907]