It helps to identify someone to be in charge of recording things on the SNAP sheets so that they can grow as things come out in general conversation during Boris.Īs you discuss the flow and the interactions with the system you can add information to each bounded context’s sheet.
What backlog stories need to be created to account for the work?.
What are the major risks for the bounded context?.
What data elements should the bounded context include?.
What External Systems integrate with the bounded context?.
What APIs need to be built for the Bounded context?.
The backlog for the product will be created based upon the items identified. The SNAP exercise should be done for each bounded context and call out APIs, data needed, UIs, and risks that would apply to that bounded context. SNAP takes the understanding from the Boris diagram to understand the specific needs of every bounded context under the new proposed architecture. Add in the lines for how it is communicated with in the flow. Using a new sticky note of a different color, indicate if there are external systems as part of the flow. Add in the lines for what systems are talking to it. Indicate if a queue is needed by adding them in a new sticky note of the same color for a queue/topic. notifications, monitoring, balancing, accounting, etc)?
What are some of the cross cutting integrations that need to be included (e.g.
Should the communication be through events or web services?.
What are the inputs and outputs for this bounded context?.
Add arrows to indicate if it is pushing or pulling. If the event message payload is discussed, push to use the smallest message possible with the least number of unique keys to identify a unique bounded context through a synchronous web service lookup (“lean events, rich APIs”)ĭraw a line from system to system as they talk, using different colors for synchronous and asynchronous communication. From a happy path perspective, how should the “to be” bounded contexts communicate with each other? From a non-happy path perspective, how should the “to be” system communicate with each other during a failure? Tip: If mapping more than one slice through the system, use different colored arrows for each.
0 kommentar(er)
