Mastertutorial · Part 11
How are modern IT systems built?
With Christian Liebich40 minSystems & architecture
In short
A modern IT system is built in layers: use cases and user stories, system architecture, technology stack, data model, processes, UX/UI, operations and quality assurance. It does not start with code, but with understanding what the system should do for which role. It succeeds when developers, business and design break out of their silos, because culture and communication count as much as the tech stack.
The video is spoken in German and has integrated English subtitles. The podcast episode and the blog article are in German. This page summarises the episode in English.
The video is loaded from YouTube only after you click. Data is then transferred to YouTube.
What you take away
- Use cases first: the user stories for development are derived from them.
- Microservices scale better and allow parallel teams, but bring the challenges of distributed systems.
- Choosing the tech stack is risk management: neither too new nor outdated, and specialists must be available.
- Designs made before development make processes visible before the expensive programming starts.
Topics of this episode
- Use cases and user stories
- System architecture: monolith vs. microservices
- Technology stack: selection and risk
- Data modelling and multi-tenancy
- Processes and degree of digitalisation
- UX and UI
- Operations and DevOps: cloud, CI/CD, monitoring
- QA: test pyramid and penetration testing
Who it is for
For managers and decision-makers who do not develop themselves but have to understand what their development teams are working on.
This episode as
Related service
Solution & System Architecture
Target architecture, tech stack and reviews, so that your software stands on a foundation that still holds in five years.
Frequently asked questions
What is the difference between a use case and a user story?
A use case describes an interaction in abstract terms, for example “report a claim”. A user story is the concrete work instruction for development derived from it, usually with acceptance criteria.
Why microservices instead of a monolith?
Microservices allow better scaling and higher resilience, and teams can work on different parts of the software in parallel.
Why does UX/UI design matter before development starts?
Because designs make complex processes visible. Stakeholders understand the product before money is spent on programming.
