How 1feycode/laboratory-management-system-for-haramaya-university works
This repository currently delivers specifications and architectural blueprints, not an implemented application. The diagram summarizes the planned asset-management product: users work through a role-aware web interface and REST API, with persistent records and documented asset, transfer, maintenance, and calibration workflows. Paths point to the repository’s specifications, not runtime code. Because no source excerpts or document contents beyond the README were provided, runtime relationships are shown as unverified (dashed) rather than asserted as implemented.
Main entry points: api-specification.md REST API · 03-frontend-architecture.md Web interface · 06-authentication-and-security.md Authentication and RBAC · 01-system-architecture.md System architecture
Components 13
User interaction
- Web interface
docs/architecture/03-frontend-architecture.md - QR scanning
docs/architecture/03-frontend-architecture.md
Planned services
- REST API
docs/api/api-specification.md - Authentication and RBAC
docs/architecture/06-authentication-and-security.md - Relational database
docs/architecture/04-database-design.md
Asset operations
- Asset registry
docs/workflows/asset-registration.mmd - Asset transfers
docs/workflows/asset-transfer.mmd - Maintenance work orders
docs/workflows/maintenance-request.mmd - Calibration tracking
docs/workflows/calibration-workflow.mmd
System specifications
- System architecture
docs/architecture/01-system-architecture.md - Backend architecture
docs/architecture/02-backend-architecture.md - API design
docs/architecture/05-api-design.md
Other components
- University staff
Connections 12
- University staff → Web interface: uses
- Web interface → REST API: sends requests
- Web interface → QR scanning: uses scanning
- Web interface → Authentication and RBAC: uses JWT
README.md - REST API → Authentication and RBAC: checks access
- REST API → Asset registry: supports registration
- REST API → Asset transfers: supports transfers
- REST API → Maintenance work orders: supports work orders
- REST API → Calibration tracking: supports tracking
- REST API → Relational database: persists records
- System architecture → Backend architecture: describes layers
README.md - API design → REST API: specifies routes
README.md