Peer review for proposal - Group 11

[tmh2408]

1. Project Originality

Strong:
Your database-first ICU monitoring concept is genuinely unique. Most existing systems treat the database as passive storage, but you elevate MySQL into the core logic engine through triggers, procedures, and partitioning.

Suggestion:
To enhance originality even further, consider adding adaptive or personalized alerting, such as baseline-adjusted thresholds or lightweight anomaly detection. This keeps the scope manageable while strengthening innovation.

2. Database and Tech Choices

Strong:
The choice of MySQL 8 with triggers, views, partitioning, and optimized indexing fits the real-time ingestion workload very well. Pairing it with WebSockets and a structured API makes your stack coherent and suitable for continuous monitoring.

Suggestion:
Clarify how you divide responsibilities between MySQL and the backend. For example: “Alert generation occurs entirely in DB triggers, while acknowledgment logic is handled by the backend.” This prevents duplicated logic and improves maintainability.

3. Clarity of the Proposal

Strong:
Your proposal is highly readable, with a complete breakdown of entities, workflows, and a clear week-by-week development plan. It is easy for graders to visualize what the final system will look like.

Suggestion:
Including a few simple user stories would make the system even clearer. For instance: “As a doctor, I can view a patient’s vitals history and modify their thresholds.” This helps anchor the technical requirements to real clinical behavior.

4. Feature Evaluation

Strong:
The proposed features—real-time vitals ingestion, alert triggers, stored procedures, dashboards, and role-based access—are both realistic and sufficiently advanced to showcase your database engineering skills.

Suggestion:
Since the system targets high-frequency inserts, briefly address performance considerations such as limiting trigger complexity or optimizing table schemas. This demonstrates awareness of potential scaling issues.

5. Positive Feedback

Strong:
Overall, this is a polished, technically ambitious proposal with excellent planning and team role clarity. The reproducible demo scenarios and strong focus on database engineering make it one of the most compelling submissions.

Suggestion:
No major improvements needed here; just ensure your final deliverables include the ERD and example queries to maintain the same level of clarity and completeness.