Modernized system - Entities MVP conceptual diagram

[OlgaPotiagalova]

System overview diagram is required for the MVP release plan to provide a visual representation of the high-level system architecture to help:

• interested parties (technical and non-technical)l to understand the structure and components of the system;
• reduce misunderstanding and ensure everyone is on the same page regarding the scope and functionality of the MVP;
• determine key components and interactions for planning the integration and testing effort;
• identify potential risks and bottlenecks related;
• be used as a reference for newer team members and future phases of the project.

Target: have something in front of people (for review) within a couple of weeks.

[severinbeauvais]

technical and non-technical people for MVP release what will things look like? are we still using COLIN? everyone to be on same page helpful for release plan not needed for entire system focus on Entities what stays in COLIN what moved to BCROS conceptual view

start with 2 systems: BCROS + COLIN (what belongs in each system) batch jobs? services? where are things stored type of platform (and db?)

explain, understandable to most, communication between each system how the systems play with each other what's available to users composition of systems what's important to know

communication with other systems?

start building what we know ask others to fill in unknown/missing pieces thor patrick kial mihai

powerpoint? visio? miro? should be easy to use should be available to misc users to update let's go with miro initially?

[severinbeauvais]

Existing diagrams

BCRS Application Logical Diagram V 4.0 Saved Aug 21 2018.pdf

App Hierachy

UI/API interactions

[OlgaPotiagalova]

Requirements:

• High-level, easy to be understood by technical and non-technical interested parties;
• Showing integration with legacy system, other parts of the modernized system and other external systems (partners specific to Entities);
• Showing data storage including types of data stored
• Access is not limited by licenses
• Can live on its own and can be easily embedded in documents

[severinbeauvais]

WIP: https://docs.google.com/presentation/d/17SCH4q4qsgq-N7LLCGPGGjsQsfBEaRowrQYc_vanQXQ/edit?usp=sharing

[vikas-gov]

Miro Link: https://miro.com/app/board/uXjVKsXk3ZU=/?share_link_id=702792431312

[severinbeauvais]

• what is COLIN still used for?
• what is LEAR used for?

[severinbeauvais]

There are some interesting Figma diagrams in the Architecture folder:

• Network Diagram
• Database/Data Flow

The above does not cover the requirements of this ticket, so we still need an Entities conceptual diagram.

Also, it might make sense to implement the Entities conceptual diagram in Miro/Figma... eventually. Right now, I'm finding it easier to work in Google Presentation (which is similar to Powerpoint) so I'll keep working on that.

[severinbeauvais]

I have updated the presentation and asked for feedback. This is a good place to take a little break from this and wait for others to review and provide feedback.

[severinbeauvais]

Waiting for Olga to show this to some business folks to answer some questions and solicit feedback.

[severinbeauvais]

~Sev will look this over with Mihai and try to fill in gaps~ then need to ask @lmcclung what she thinks.

Update: Mihai and I added and updated a few small things.