3. Inventarise and test necessary components and technologies. Divide into milestones and tickets (broadly).

• Using the information gathered during the previous ticket, create initial milestones and tickets. High-level only, for further grooming by the group (all relevant stakeholders).

Update:

• To communicate with RWS we're maintaining a (project management) board via RWS Azure DevOps. We have a user story for each milestone in this repo, which we use to track progress and plan sprints. All work details will be tracked in this repo and linked to.

• For visibility to ESCET developers, we'll maintain a summary of our repo/work as an issue in the official ESCET repository (see: eclipse/escet/escet#272 (closed)).

• With each contribution, we can summarise the work/information in this issue (272). Idea is to track detailed planning/documentation in our own repository for the time being, and summarise only relevant details for ESCET developers. Eventually, our fork should be merged and deleted, at which point we'll summarise and take along any relevant documentation/planning.