why we have architectural documentation

TN: Robert, Patrick, Stefan, Stephan 25.2.25, 13-14h

referring Tickets / Links

• https://jira.telekom-mms.com/browse/IPCEICIS-2424
• https://jira.telekom-mms.com/browse/IPCEICIS-478
• Confluence: https://confluence.telekom-mms.com/display/IPCEICIS/Architecture

charts

we need charts, because:

• external stakeholders (especially architects) want to understand our product and component structure(*)
• our team needs visualization in technical discussions(**)
• we need to have discussions during creating the documentation

(*): marker: “jetzt hab’ ich das erste mal so halbwegs verstanden was ihr da überhaupt macht” (**) marker: ????

typed of charts

• schichtenmodell (frontend, middleware, backend)
• bebauungsplan mit abhängigkeiten, domänen
• kontext von außen
• komponentendiagramm,

decisions

• openbao is backend-system, wird über apis erreicht

further topics / new requirements

• runbook (compare to openbao discussions)
• persistenz der EDP konfiguartion (zb postgres)
• OIDC vs. SSI