Phase 0 — Team Formation¶
This section defines the project team structure, communication workflow, and module ownership distribution for the CS340 Database Web Application.
Team Members¶
-
Shoug Alomran
-
Yara Albugami
-
Rose AlRakan
-
Raghad Abdulaziz
Communication Structure¶
Clear communication channels were established to ensure coordination and documentation consistency.
-
Primary Channel — WhatsApp
Used for rapid coordination, updates, and clarification during development.
-
Version Control — GitHub
Repository management for documentation and project artifacts.
-
Collaborative Drafting — Google Docs
Used for drafting reports and reviewing deliverables before final submission.
-
Meetings
Weekly coordination meetings, with additional meetings scheduled during major project milestones.
Project Plan Dashboard¶
Detailed responsibilities and phase-based task distribution are maintained in the interactive dashboard.
Roles & Tasks Dashboard:
Open the Roles Dashboard
The dashboard contains phase-by-phase responsibilities (Phase 2–5) per member and serves as the official source of task ownership.
Module Ownership (High-Level Distribution)¶
Each team member is responsible for a core system module to ensure accountability and structured development.
-
Rose AlRakan — User & Access Control Module
Authentication mechanisms, role-based access control (RBAC), and audit logging.
-
Raghad Abdulaziz — Family & Medical History Module
Family member relationships and structured medical history management.
-
Shoug Alomran — Risk Alerts & Analysis Module
Risk rule logic, alert generation, aggregation, and data analysis.
-
Yara Albugami — Appointments, Clinics & Awareness Module
Clinic browsing, appointment scheduling, and awareness content management.
Coordination Model¶
The team follows:
- Phase-based responsibility allocation
- Internal review before submission
- Cross-verification of schema, constraints, and documentation
This structure ensures accountability, technical accuracy, and consistency across all project phases.