Week 4 Day 02 Childcare Domain Generated by Gemini Code Assist

Application and User Lifecycle

Defining user creation triggers, lifecycles, and the NoSQL data structure for the application.

1. User Creation and Lifecycle

The user creation process and lifecycles are driven by the operational needs of the center (such as enrollment and employment), while the Firebase database structure must support a NoSQL document-based architecture to handle the flexible data requirements of children and staff.

A

Parents and Families

Creation Trigger: The account is created during the "Online Enrollment" phase. This occurs when a parent interacts with "customizable digital registration forms" to register their interest or apply for a spot.

Lifecycle:

  • Prospect/Waitlist: The user exists in a holding state, receiving "automated waitlist notifications" when spots open.
  • Active: Once a spot is secured, the parent becomes an active user engaging in "two-way messaging," receiving "newsletters," and viewing "real-time updates".
  • Alumni/Archived: When the child graduates or leaves, the account is archived, but data may be retained for records.
B

Children (Data Subject)

Creation Trigger: A child profile is created by the Parent during the document collection phase (e.g., uploading immunization records) or by the Administrator upon intake.

Lifecycle:

  • Applicant: Data is limited to intake forms and health history (e.g., "Allergy lists").
  • Enrolled: The profile becomes active for daily tracking, including "milestone tracking" (fine motor skills, social behavior) and "medication administration".
  • Graduated: The profile is closed, but "student portfolios" and health records are preserved.
C

Educators and Staff

Creation Trigger: Accounts are created by an Administrator when a staff member is hired. This is essential to enable "scheduling" and "performance tracking".

Lifecycle:

  • Onboarding: The user is set up with credentials to access the system.
  • Active Duty: The user interacts daily via "staff timecards (check-in/out)," submits "time-off requests," and manages "digital lesson plans".
  • Terminated/Inactive: Access is revoked, but attendance logs are kept for "legal ratios" and compliance audits.
D

Administrators

Creation Trigger: Created at the system deployment phase or by a "Super Admin" when the center purchases the software.

Lifecycle:

  • Continuous active status responsible for "operational duties," "maintaining rigorous records," and "workforce management".

2. Lifecycle Flows

Detailed visual flows for the core entities in the system.

1. Student Lifecycle Flow

This flow covers the journey from a parent registering, enrolling a child, the approval process, ongoing data enrichment, and eventually offboarding.

Key Data Transitions:

  • Data starts in an enrollment_forms collection.
  • Upon approval, essential data moves to the children collection (status: 'onboarding').
  • Parents add more medical/personal details to the children collection (status becomes 'active').
Student Lifecycle Flow Student Lifecycle Diagram

2. Staff Lifecycle Flow

This flow involves the administrator setting up staff access, the staff performing daily duties, HR-related tasks (leave/performance), and the exit process.

Key Data Entities:

users (for auth/roles), staff_profiles (for detailed info), classrooms (for assignment), daily_logs, leave_requests.

Staff Lifecycle Flow Staff Lifecycle Diagram

3. Syllabus Lifecycle Flow

This flow focuses on the creation and management of the syllabus data entity itself.

Key Data Entities:

Firebase Storage buckets (for PDFs), Firestore syllabus collection.

Syllabus Lifecycle Flow Syllabus Lifecycle Diagram

4. Consolidated Lifecycle Diagram

Consolidated Lifecycle Diagram Consolidated Lifecycle Diagram