Software Code Development for Model Deployment
Turns a model into specified, tested, documented, deployable software.
Tech stack
Modules
5 modules · 120 hours
M1 · Define requirements
22 h · PC1, PC2- Software Requirements Specification
- Functional and non-functional requirements: latency, throughput, availability, security, cost
- Technical specifications and limitations of the target system
- Evaluating the design of data flows and structures
- Interface and schema contracts
- Traceability matrix
Lab: Produce a complete SRS and reviewed data-flow design for a model-serving system
Course material for this module is in production.
M2 · Evaluate model and concurrency design
22 h · PC3, PC4- Reviewing core algorithmic model design for deployability
- High-Level Design: solution and rationale, assumptions, constraints, dependencies, interfaces
- Parallel programming constraints of the target system
- Concurrency models
- Thread safety
- Statelessness and idempotency
Lab: Write and defend an HLD including a concurrency and constraint analysis
Course material for this module is in production.
M3 · Convert specifications into reusable code
34 h · PC5, PC6, PC7- Low-Level Design: programming structures, coding standards, checklists
- Modular and reusable component design
- Determining component reuse suitability
- Serving with FastAPI
- Request/response schemas with Pydantic
- Configuration and secrets
- Dependency injection
- Packaging and containerisation
- Code-generation tooling
- Stakeholder documentation and validation walkthroughs
Lab: Implement a documented, containerised, schema-validated inference service and validate it with stakeholders
Course material for this module is in production.
M4 · Unit testing and defect management
28 h · PC8, PC9, PC10- Test design and the test pyramid
- Unit test case creation and execution
- Fixtures, mocking, parametrisation
- Coverage measurement
- Performance and load testing
- Defect taxonomy and triage
- Root-cause analysis
- Corrective action
- Recording corrective actions to improve future design
- Refactoring for performance
Lab: Build a test suite with a coverage gate; log, classify and remediate seeded defects; optimise the hot path
Course material for this module is in production.
M5 · Approval and release
14 h · PC11- Organisational approval process for code designs
- Pull-request and sign-off workflow
- Release notes and versioning
- Deployment readiness checklist
- Handover documentation
Lab: Submit optimised, tested code through a formal approval gate to release
Course material for this module is in production.