In this example, we will document the high-level decision process by which an architect decides whether to develop software in-house to satisfy a business need or to buy a solution from a third party.
You should generally limit the number of activities in a diagram to around 10-15. If you want to go into more detail about a particular activity, create it using the Sub-Process tool, or press CTRL and double-click it to "decompose" it and enter into a sub-diagram where you can enter all of the "sub-activities" that are involved in it. For detailed information about working with and navigating in a hierarchy of processes, see Decomposing Processes.
You can use the Exclusive Gateway tool to create a split in the flow of activities to model situations where what is done depends on some condition. When your activities are more or less in place, create flows between them using the Sequence Flow tool. When communicating between pools, use the Message Flow tool. To show that your process terminates, use the End Event tool.