My contribution
- Planned and managed code refactoring, component upgrades, and removal of deprecated dependencies.
- Coordinated regression testing and user acceptance to ensure feature parity.
- Managed communication and training for researchers and animal care staff.
Outcome
Delivered a secure and responsive application with improved performance and long-term support readiness.
Overview
Prior to this effort, SUBS ran on .NET 6 and Angular 15—platforms approaching end of support and lacking newer security and UX improvements. The upgrade positions SUBS on supported frameworks (backend .NET 8, frontend Angular 18) to reduce risk, improve responsiveness, and ensure long-term maintainability.
Guiding principle: maintain all existing business functionality while moving to modern frameworks; adopt new features selectively after stability is confirmed.
In Scope
- Backend framework upgrade to .NET 8
- Frontend framework upgrade to Angular 18
- Validation of existing processes, reports, and integrations
- Performance benchmarking & tuning
- Change communications and user readiness
Out of Scope
- Brand-new features unrelated to the upgrade
- Full UX redesign beyond Angular 18 updates
- Re-engineering business processes or net-new integrations
Per approved requirements.
Objectives
- Ensure system continuity before .NET 6 end-of-support (Nov 2024)
- Improve security, performance, and maintainability on .NET 8/Angular 18
- Preserve all current capabilities with minimal downtime during cutover
Objectives summarized from the Business Requirements.
What Changed
- Backend: migrated to .NET 8 for support, security updates, and runtime performance
- Frontend: migrated to Angular 18 for a modern, consistent, responsive UI
- Quality: test strategy covering regression, performance, and security
Future-state benefits and features.
Timeline
- • Requirements & technical assessments — Summer 2024
- • TEST environment upgrade & regression — late Summer 2024
- • STAGE promotion & performance tuning — Fall 2024
- • Production cutover window — late Fall 2024
- • Warranty/support & post-implementation review — through year-end
Milestones aligned to the end-of-support driver and validated environments.
Risks & Constraints
- Compatibility with legacy integrations and services must be retained
- Data integrity during migration and promotions
- Network/performance baselines must meet or exceed current SLAs
Key constraints and impacts.
- Fixed timeline due to .NET 6 end-of-support; minimal downtime allowed
- Clear stakeholder communications & change management to avoid disruption
- Documented deployment & rollback plan for a reversible cutover
Assumptions & readiness items.
Project Team Roles Managed
- Project Manager (my role)
- Product Owner / Business Alignment
- Business Analyst
- .NET / Angular Developers
- Application Analyst / DevOps (environments & deployments)
- QA & Performance Testing
- Security & Compliance Advisor
- OCM / Training & Communications
Results
- SUBS upgraded to supported frameworks with improved security and performance
- All core processes, reports, and integrations validated with no loss of functionality
- Users experienced a consistent, responsive UI with minimal disruption
- Clear runway for future enhancements on a modern, maintainable stack
Results aligned to Business & Functional Requirements.