To analyze the British Swim School mobile app interface and identify its core objects, attributes, and relationships. The goal was to understand how the app organizes swim lessons, student accounts, payments, policies, and communication features into a clear conceptual model.
This exercise demonstrates my ability to translate interface observations into a conceptual object model. By identifying the system’s core objects and relationships, I clarified how the app supports parent tasks such as managing students, booking makeup lessons, tracking skills, handling payments, and accessing policies. This object-oriented thinking process helps create a stronger foundation for UX structure, navigation design, and future system improvements.
Parent or guardian profile that manages students, payments, activity, classes, and makeup lessons.
Child enrolled in swim lessons. Connected to skills, enrollment, absence records, and lesson level.
Swim class option organized by level, day, pool, and program type.
Skill-based category such as Tadpole, Swimboree, Seahorse, Starfish, Minnow, Turtle, Shark, and Adult Levels.
Physical swim school location, such as LA Fitness Cambridge.
Record of a missed class submitted by the user.
Replacement class connected to a student’s absence or schedule.
Student progress area showing swim abilities or development milestones.
Payment balance, payment history, and financial records.
Required agreements and previously accepted documents.
Communication options including call and email.
External links such as Instagram and Facebook.
Updates from the swim school.
External review action connected to Google.
User preferences and app-level configuration.
The User Account is the central object. It owns or manages Students, Billing & Payment, Activity, Classes, and Makeup Lessons.
Each Student connects to Enrollment, Skills, Absences, and Lesson Levels.
A Lesson depends on several filtering objects: Day, Pool Location, Level, and Program Type.
Policies, Contact, Billing, and Settings appear as support objects grouped under a broader account-management view.
This exercise demonstrates my ability to translate interface observations into a conceptual object model. By identifying the system’s core objects and relationships, I clarified how the app supports parent tasks such as managing students, booking makeup lessons, tracking skills, handling payments, and accessing policies. This object-oriented thinking process helps create a stronger foundation for UX structure, navigation design, and future system improvements.