Design the Architecture for a Library Management System
Overview
What this challenge is about.
Read the 30-page replacement RFP. Author a 15-page architecture document covering the C4 model levels 1-3 (context, container, component) for the new system: web app, mobile app, public catalog, staff console, RFID self-checkout integration, and the inter-branch synchronization service. Design a normalized data model (around 25 entities) in dbdiagram.io. Draft an OpenAPI 3.1 sketch (top-level routes only) for the staff console + public catalog. Write 5 ADRs (e.g. PostgreSQL vs MongoDB, monolith vs modular monolith, REST vs GraphQL, sync vs event-driven inter-branch, hosted vs self-hosted search) using the Michael Nygard ADR template. Deliver the architecture document, C4 diagrams, data model, OpenAPI sketch, and the 5 ADRs.
The Brief
What you'll do, and what you'll demonstrate.
Design a web-based library management system architecture using the C4 model and document major decisions with ADRs for a public-tender process.
Earning criteria — what you'll demonstrate
- Apply the C4 model to a real multi-component system
- Design a normalized data model from an RFP
- Write Architecture Decision Records that survive procurement review
- Trade off architecture choices defensibly in writing
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Career mappings coming soon.