Overview

Date: 15.09.2022

Objective: Weekly space for deep dive topics

Participants: (kindly only add your own names, not those of other participants)

Topic Proposals:

Presentations / Attachments

	File	Modified

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.

No files shared here yet.

Drag and drop to upload or browse for files

Identify our modules
1. Start with BlueSquare's graphic (one box = one module? one group = on module?)
2. Group at least FE & BE into one module, maybe even more
Cluster the modules according to JLN Process Groups (colors)
1. some modules will serve multiple Process Groups, let’s try to still find the primary process group
2. some modules will just have technical purposes
Assign our sources to modules
Homework: rearrange module pages accordingly and update them with property boxes

Remarks:

JLN are business activities will use several modules BUT many processes will use the same modules
A module is an element that is included in the assembly (backend/fronEnd) recipe (openimis.json) if this definition changes then will need to replace module terms we are using today → I fear that will bring a lot of confusion (Patrick)