Page tree
Skip to end of metadata
Go to start of metadata

Programme title: "Tackling complex business domains with Event Storming and Domain Driven Design"


Programme description (i.e. what it is about, history - why these particular subjects, programme aim, benefits of attending the programme):

Event storming is a workshop-based method to quickly find out what is happening in the domain of a software program. Compared to other methods it is extremely lightweight and intentionally requires no support by a computer. The result is expressed in sticky notes on a wide wall. The business process is "stormed out" as a series of domain events which are denoted as orange stickies. It was invented by Alberto Brandolini in the context of domain-driven design (DDD). Event storming can be used as a means for business process modeling and requirements engineering. The basic idea is to bring together software developers and domain experts and learn from each other. To make this learning process easier, event storming is meant to be fun. The name was chosen to show that the focus should be on the domain events and the method works similar to brainstorming or agile modeling's model storming. Source: Wikipedia.

Benefits: better understanding of domains modelled in the developed software; software systems more suitable to real problems; 

Why: Event Storming is a relatively new idea that is gaining more and more supporters.

Structure: 4 x 4h interactive sessions


To be delivered by: Bottega IT (https://bottega.com.pl/index_en)

                                   

Dates of delivery: 26-29 Oct 2020


Platform: Zoom, Miro


Affiliation (WP/Task): WP9 T2


Authors (created by) (i.e. who created the content, if applicable): Bottega IT


Who will attend (target audience): Programmers, Testers, Team Leaders, Analysts, Designers


Resources available can be accessed after the programme (location):


Webinar evaluation/feedback (link):


Schedule


Session

Title

Aim (what do you expect to be able to do after, i.e. apply, review, introduce, etc)

Date

Duration

Session 1





Session 2





Session 3





Session 4






Planning a session

Session One


Session Section

Resources Resources (tools, applications, link to a respective wiki page)

Content (what will happen)

Duration

Facilitated by

Reception (prior to the start of a webinar)





Welcome





Introductions





Main body of the webinar





Q & A





Closing (what next?)










Session Two

Session Section

Resources (tools, applications, link to a respective wiki page)

Content (what will happen)

Duration

Facilitated by

Reception (prior to the start of a session)





Welcome





Introductions





Main body of the session





Q & A





Closing (what next?)










Session Three

Session Section

Resources (tools, applications, link to a respective wiki page)

Content (what will happen)

Duration

Facilitated by

Reception (prior to the start of a session)





Welcome





Introductions





Main body of the session





Q & A





Closing (what next?)










Session Four

Session Section

Resources (tools, applications, link to a respective wiki page)

Content (what will happen)

Duration

Facilitated by

Reception (prior to the start of a session)





Welcome





Introductions





Main body of the webinar





Q & A





Closing (what next?)










  • No labels