Eventstorming

Domain events

Low-level events

Idea : some of the high-level events might be synthetized/deduced from a combination of a low-level event and some contextual information (user who issued the related command, etc...). For example a FormFilled can be interpreted as a ProposalSaved if the formId is the one of the proposal form)

• FormFilled(author, formId, formValue)
• FormVersionAdded(formId, formDefinition)

High-level events

User

• AccountCreated

Speaker

• SpeakerBioSaved
• SpeakerInformationFilled
• SpeakerReceiptsUploaded
• SpeakerRoomBooked

Proposal

• ProposalSaved
• ProposalDrafted
• ProposalCancelled
• ProposalAcceptedByCommittee
• ProposalRefusedByCommittee
• UserVoted
• ProposalPutInWaitList // useful ?
• ProposalSelectedFromWaitList // idem ?

Talk

• TalkConfirmedBySpeaker
• TalkDeclinedBySpeaker
• TalkScheduled
• TalkUnscheduled
• InvitedTalkCreated

System

• VoteClosed
• C4POpened
• C4PClosed