Registration & Application Platform
Architecture and workflows for programme registration, membership applications and awards.
- Solution evaluation
- Build vs buy
- Implemented workflows
- Registration
- System boundaries
- Integrations
The challenge
Make registration work across system boundaries.
Programme intake, membership and awards sit across systems. The first job is to decide what to build, what to buy and where the boundaries are.
Product & engineering
What I delivered
Architecture and implementation of programme registration, membership application and scholarship workflows.
- 01
Registration workflows
Architecture and implementation of registration and application flows.
- 02
Integration design
Integration outline across programme, membership and award systems.
System design
How the pieces connect
- 01
Programmes
Registration and application workflows.
- 02
Evaluation
Build-versus-buy and vendor decisions.
- 03
Boundaries
System responsibilities and contracts.
- 04
Integrations
Membership, awards and scholarships.
Product interface
- Angular
Services & interfaces
- Spring
Data & search
- PostgreSQL
- DynamoDB
Platform & delivery
- Flyway
- AWS
- Lambda
- Bedrock
Evaluation-led system boundaries and integration contracts, validated through implemented registration workflows.
Outcome & evidence
What the work produced
Delivered outcome
Delivered registration workflows and architectural recommendations.
Scope & context
The client and internal programme names are omitted.