Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🗺 Create a business architecture illustration #7

Open
janhalen opened this issue Jan 22, 2025 · 4 comments
Open

🗺 Create a business architecture illustration #7

janhalen opened this issue Jan 22, 2025 · 4 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@janhalen
Copy link
Collaborator

Create a very high level illustration showing a simplified dataflow

@janhalen janhalen added the documentation Improvements or additions to documentation label Jan 22, 2025
@janhalen janhalen self-assigned this Jan 22, 2025
@janhalen
Copy link
Collaborator Author

@TroelsRanum: After our meeting today my takeaway was that a more conceptual illustration is needed, that filters some of the technical realities and only shows a simplified version of potential dataflows in the solution.

I'll get started as soon as i can!

@TroelsRanum
Copy link

That would be very helpful when we are about to try and convince the right people to convince other people to board this ship. Thank you.

@janhalen
Copy link
Collaborator Author

janhalen commented Jan 30, 2025

Ok.. @TroelsRanum & @HenrikEmilArensEAatAarhus

I have a suggestion.. somwhat along these lines... but i might need some feedback on the naming of the elements, to make it easier to understand what is what 😄

flowchart LR
    a(("🏢 OS² Fagsystem")) --> l["🔄 data-workflow-engine"]
    b(("🏭 OS² Fagsystem")) --> l
    c(("🏗️ OS² Fagsystem")) --> l
    e(("🏛️ OS² Fagsystem")) --> l
    f(("🏠 Fagsystem")) --> l --> a
    l ---> g["📊 Target 1"] & h["📈 Target 2"]
    l --> j["🔀 KOMBIT<br> Distributor component"]
    j --> m(("💻 Fagsystem")) & n(("🖥️ Fagsystem")) & o(("📟 Fagsystem")) & p(("🖨️ Fagsystem"))

    style a fill:#F0E6E6,stroke:#D4BFBF,stroke-width:2px,color:#333333
    style l fill:#F0F0F0,stroke:#D4D4D4,stroke-width:2px,color:#333333
    style b fill:#E6F0E6,stroke:#BFD4BF,stroke-width:2px,color:#333333
    style c fill:#E6E6F0,stroke:#BFBFD4,stroke-width:2px,color:#333333
    style e fill:#F0E6F0,stroke:#D4BFD4,stroke-width:2px,color:#333333
    style f fill:#E6F0F0,stroke:#BFD4D4,stroke-width:2px,color:#333333
    style g fill:#F0E6EC,stroke:#D4BFC7,stroke-width:2px,rx:10,ry:10,color:#333333
    style h fill:#E6ECF0,stroke:#BFC7D4,stroke-width:2px,rx:10,ry:10,color:#333333
    style j fill:#E6F0EC,stroke:#BFD4C7,stroke-width:2px,rx:10,ry:10,color:#333333
    style m fill:#ECE6F0,stroke:#C7BFD4,stroke-width:2px,color:#333333
    style n fill:#E6F0F0,stroke:#BFD4D4,stroke-width:2px,color:#333333
    style o fill:#F0F0E6,stroke:#D4D4BF,stroke-width:2px,color:#333333
    style p fill:#F0E6F0,stroke:#D4BFD4,stroke-width:2px,color:#333333

    linkStyle 0 stroke:#E6B3B3,fill:none
    linkStyle 1 stroke:#B3E6CC,fill:none
    linkStyle 2 stroke:#B3CCE6,fill:none
    linkStyle 3 stroke:#CCB3E6,fill:none
    linkStyle 4 stroke:#E6CCB3,fill:none
    linkStyle 5 stroke:#B3E6E6,fill:none
    linkStyle 6 stroke:#E6B3CC,fill:none
    linkStyle 7 stroke:#B3CCE6,fill:none
    linkStyle 8 stroke:#CCE6B3,fill:none
    linkStyle 9 stroke:#E6B3CC,fill:none
    linkStyle 10 stroke:#B3E6E6,fill:none
    linkStyle 11 stroke:#E6E6B3,fill:none
Loading

@TroelsRanum
Copy link

TroelsRanum commented Jan 31, 2025

This looks like something that would make sense to most people. Good job!
I could rename some of them, but we might just do that when we know who we are going to show it. Then use the systems that they are familiar with?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants