Instructions: Part 1: It is now time to increase the details provided by the to-be model. The to-be model just provides a strategic view over the project. With the detailed to-be, you aim to provide all the details necessary to realise the project That includes, in particular, describing the sub-processes and identifying all activities and actors Model any sub-processes necessary to fully describe the project. You can use expanded or global sub-processes As a rule of thumb, detailed to-be models should not have more than three levels of detail (process/sub-process/sub-sub-process). Having too many levels of detail is usually excessive and results in overly complex and incomprehensible models Do not forget to reuse sub-processes whenever they appear across more than one process You can now use several bpmn files. You should not have more than three files Part 2: It is now time to use pools and lanes to identify actors Revise your use of events. Consider adding events necessary to fully explain the project Consider the whole diversity of events that can be used Do not forget to also model relevant data objects Part 3: It is now time to model uncommon process behaviour. Focus on what may fail and what can be done differently Add exceptions and compensation activities to processes and activities wherever necessary Focus on what may fail and what has to be done to overcome a failure. You may have to use your imagination if the project description does not provide many details Define a strategy for improving the clarity of the detailed to-be model. Make it clear how the different parts are interconnected (using events and naming conventions)