Overview
VitalConnect is an academic capstone project: a healthcare-oriented software application carried through the full development lifecycle under academic supervision. Unlike the production platforms in this portfolio, it is presented here as coursework — its value is the disciplined process, not commercial deployment.
Problem
The capstone brief required demonstrating professional software practice end to end: eliciting and documenting requirements, designing an interface for real users, implementing and testing the system, and delivering documentation a future maintainer could pick up.
Users
- Healthcare-context end users defined in the capstone requirements
- Academic evaluators assessing process and deliverables
Goals
- Practice complete requirements analysis and documentation
- Design and test a usable healthcare-context interface
- Deliver a working, documented, deployed application
- Meet academic standards for process evidence
My role
Sole developer — requirements analysis, design, implementation, testing, documentation, and deployment within the academic timeline.
Product strategy
Treat the capstone like a client project: fixed scope, explicit requirements traceability, and deliverables that would survive a handoff.
Key features
- Documented requirements
- Formal requirements analysis translated into a traceable feature set.
- User-centered interface
- Interface design driven by the defined healthcare-context users.
- Testing & documentation
- Structured testing and maintainer-grade documentation as first-class deliverables.
Technical architecture
- Application architecture scoped to the capstone requirements
- Deployment demonstrating the full delivery cycle
Security & privacy
- Healthcare-context privacy considerations reflected in the design
- Academic project — no real patient data involved at any stage
Engineering challenges & decisions
Delivering the entire lifecycle within a fixed academic timeline.
Scope was controlled through documented requirements, and process artifacts were produced alongside the code rather than after it.
Lessons learned
- Process discipline — requirements, testing, documentation — is what separates a project that works from one that lasts.
- Academic constraints are a useful forcing function for scope control.
Future improvements
- Concepts from this capstone inform ongoing healthcare-platform work, including MyVital Harmony.