Wiki source code of Checklist for Splitting Models
Last modified by Erik Bakker on 2023/08/23 15:33
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}}{{container layoutStyle="columns"}}((( | ||
| 2 | This micro-learning should help in determining when it may be useful to split models. | ||
| 3 | |||
| 4 | Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. | ||
| 5 | |||
| 6 | == 1. Prerequisites == | ||
| 7 | * Intermediate knowledge of the eMagiz platform | ||
| 8 | |||
| 9 | == 2. Key concepts == | ||
| 10 | In some cases, it can be useful for organizations to have multiple eMagiz models. More about such a multi-model environment is explained [[here>>doc:Main.eMagiz Academy.Fundamentals.eMagiz Multi-model.WebHome||target="blank"]]. | ||
| 11 | This microlearning contains a checklist with points that indicate when it may be useful to split models. | ||
| 12 | |||
| 13 | == 3. Splitting of models checklist == | ||
| 14 | |||
| 15 | * **1. Can systems in your model be grouped?** | ||
| 16 | //Check in your model whether there are evidently groups of systems whereby the interaction is limited to only these systems. For example, are these finance and transport management business processes into a single model? Or can you categorize systems per business department?// | ||
| 17 | ** No, no categorizations of systems can be made | ||
| 18 | ** Not sure whether systems can be categorized | ||
| 19 | ** Yes, several categorizations of systems can be made | ||
| 20 | * **2. What is the number of systems in your model?** | ||
| 21 | //The number of systems should represent the total number of systems that are present in your model. A high number of systems could indicate a situation where business processes are mixed and the interdependency of systems becomes large.// | ||
| 22 | ** 0-40 | ||
| 23 | ** 40-80 | ||
| 24 | ** >80 | ||
| 25 | * **3. What is the number of critical processes in your model?** | ||
| 26 | //A critical process is a complete set of flows that interact jointly in your model and which is deemed critical for business continuation of the client. Not that the number of critical streams is dependent on the size of an organization. Critical streams should be recognized as critical by the client.// | ||
| 27 | ** 1 | ||
| 28 | ** 2-4 | ||
| 29 | ** >4 | ||
| 30 | * **4. How many business owners are responsible for your model?** | ||
| 31 | //Business owners are the people that are responsible for the functionality of your model. These business owners are not direct users of the eMagiz platform but are more the ones that own the business process in the client organization. More business owner can indicate more diverging priorities, different release schedules, etc.// | ||
| 32 | ** 1 | ||
| 33 | ** 2-4 | ||
| 34 | ** >4 | ||
| 35 | * **5. How much time is involved in the daily monitoring of your model?** | ||
| 36 | //Daily monitoring concerns checking upon the functionality of your system, e.g. checking for errors. It does not include the time it takes to resolve those errors. More errors spread over many systems in the integration landscape means that specific domain knowledge is required for eMagiz users.// | ||
| 37 | ** 10-15 minutes per day | ||
| 38 | ** >30 minutes per day | ||
| 39 | ** >60 minutes per day | ||
| 40 | * **6. Is there a rhytm in the number of deployments that you have per sprint?** | ||
| 41 | //A release cycle is the sum of stages of development of a model ranging from its initial development to its release.// | ||
| 42 | ** Yes, there is a fixed rhythm including hotfixes | ||
| 43 | ** Yes, there is a fixed rhythm | ||
| 44 | ** No, there is no rhythm at all | ||
| 45 | * **7. Do you experience many delays in delivery of new and modified flows due to external and internal dependencies?** | ||
| 46 | //External and internal dependencies concern the communication with developers or stakeholders of the model. For example, do you have to wait a lot for a response of a developer or stakeholder before you can continue working on your model?// | ||
| 47 | ** Not really | ||
| 48 | ** It's increasing in the last 2 months | ||
| 49 | ** Basically a daily discussion and issue | ||
| 50 | * **8. Is there a good balance of time spent on technical debt versus time spent on functionalities within your sprint?** | ||
| 51 | //Technical debt represents additional rework that needs to be done.// | ||
| 52 | ** About 20/80 balance | ||
| 53 | ** About 10/90 balance | ||
| 54 | ** There is no balance | ||
| 55 | * **9. Do you have insight in your production incidents?** | ||
| 56 | //Production incidents are problems in your model that negatively impact the business.// | ||
| 57 | ** Yes, it is clear what production incidents there are and I have control over them | ||
| 58 | ** Yes, it is clear what production incidents there are but I do not have control over them | ||
| 59 | ** No, it is not clear what production incidents there are and I do not have control over them | ||
| 60 | |||
| 61 | == 4. Key takeaways == | ||
| 62 | Several key points can be used to indicate whether it is useful to split models in eMagiz. | ||
| 63 | |||
| 64 | == 5. Suggested Additional Readings == | ||
| 65 | |||
| 66 | There are no suggested additional readings on this topic.)))((({{toc/}}))){{/container}}{{/container}} |