Design a Smart Public Park Lost Child Alert App with Object-Oriented Design

Designing a Smart Public Park Lost Child Alert App using Object-Oriented Design (OOD) principles involves breaking down the system into logical objects, their attributes, and how they interact with each other. Here’s a blueprint for such an application:

1. System Overview

The primary function of the Smart Public Park Lost Child Alert App is to help park-goers quickly locate lost children and notify park authorities in real-time. The app uses GPS, Bluetooth, and geofencing technologies to track children, alert guardians, and ensure their safety.

2. Identified Objects and Class Structure

Class 1: Child

This object represents the child being monitored by the app. The child can be tracked based on their location and a security tag worn (e.g., wristband or ID).

• Attributes:

  • childID: Unique identifier for each child.

  • name: Name of the child.

  • age: Age of the child.

  • guardianContact: Emergency contact information for the guardian.

  • location: Real-time GPS location of the child.

  • status: Current status of the child (e.g., “Lost”, “Safe”, etc.).

  • alertStatus: Tracks whether an alert has been triggered.

• Methods:

  • updateLocation(): Updates the child’s GPS location.

  • triggerAlert(): Sends an alert when the child goes missing.

  • resetAlert(): Resets the alert after the child is located.

Class 2: Guardian

The Guardian class represents the parent or caretaker of the child. The guardian will receive alerts about the child’s location.

• Attributes:

  • guardianID: Unique identifier for the guardian.

  • name: Guardian’s name.

  • contactNumber: Contact phone number.

  • email: Guardian’s email address.

  • children: List of children under the guardian’s supervision.

• Methods:

  • receiveAlert(): Receives an alert when the child is lost.

  • sendAlertConfirmation(): Confirms if the alert has been acknowledged by the guardian.

Class 3: ParkAuthority

The Park Authority is responsible for managing and responding to lost child alerts. They oversee the park’s security and ensure children are quickly reunited with their guardians.

• Attributes:

  • authorityID: Unique identifier for each park authority staff member.

  • name: Name of the authority staff.

  • contactNumber: Phone number to contact the authority.

  • alertQueue: List of active lost child alerts.

• Methods:

  • receiveAlert(): Receives a lost child alert from the system.

  • locateChild(): Attempts to locate the child using available data (GPS, Bluetooth, etc.).

  • sendHelp(): Dispatches a staff member to the location of the child.

  • closeAlert(): Closes the alert once the child has been located.

Class 4: Geofence

The Geofence class is used to define the safe areas of the park. If a child moves outside of these areas, it triggers an alert.

• Attributes:

  • fenceID: Unique identifier for each geofence.

  • location: GPS coordinates that define the safe zone.

  • radius: The radius of the safe zone.

  • parkID: The park to which the geofence belongs.

• Methods:

  • isChildOutsideFence(): Checks if the child has left the designated safe area.

  • createGeofence(): Creates a new geofence around a particular area in the park.

  • deleteGeofence(): Removes a geofence.

Class 5: NotificationService

The NotificationService is responsible for notifying the guardian, park authority, and other relevant parties about the status of the child.

• Attributes:

  • serviceID: Unique identifier for each notification service.

  • message: The notification message.

  • recipient: The person (guardian, authority) who should receive the notification.

• Methods:

  • sendNotification(): Sends a notification message to the guardian or park authority.

  • logNotification(): Logs notifications sent for tracking purposes.

3. App Flow and Use Cases

1. Monitoring the Child:

   • The Child object’s GPS is continuously updated by the app.

   • A Geofence is created around the park with the safe zones, where children are expected to stay.

   • If a child moves outside of the safe zone, an alert is triggered.

2. Alert Triggering:

   • When the system detects the child has left the designated area, the Child object’s triggerAlert() method is called.

   • The NotificationService object sends an alert to the Guardian and ParkAuthority.

3. Guardian’s Response:

   • The Guardian receives the notification and can confirm receipt by using the sendAlertConfirmation() method.

   • If the child is found, the Guardian can update the child’s status via the app, which updates the Child object’s status to “Safe.”

   • The ParkAuthority can also receive the alert, dispatch a staff member, and track the child’s location in real time.

4. Park Authority’s Role:

   • Once an alert is received, the ParkAuthority object may take action using the locateChild() method, determining if additional steps are necessary.

   • The authority may use available park security to locate the child and send a team using the sendHelp() method.

4. Interaction Between Objects

• The Child object communicates with Geofence to detect if the child is outside of a safe zone.

• When the child is outside the safe zone, the NotificationService will alert both the Guardian and ParkAuthority.

• The Guardian interacts with the Child and NotificationService to confirm and acknowledge the alert.

• The ParkAuthority uses the Child‘s data and coordinates to assist in locating the child.

5. Additional Features

• Real-Time Tracking: Allow the ParkAuthority to have access to real-time location data of the lost child, which is updated every few seconds.

• SOS Button: A button on the app that the guardian can press to immediately notify the park authority if the child is lost or in danger.

• Child’s Photo: The app can store a recent photo of the child, which will be sent with the alert to help authorities locate them.

• Location Sharing: The guardian can share the child’s last known location with other guardians within the app, creating a community of park-goers who can assist in locating the child.

6. Technologies Used

• GPS: For real-time location tracking.

• Bluetooth: To track the child’s proximity to nearby devices in the park (e.g., park entrances, exits).

• Geofencing: To define safe zones and trigger alerts if the child exits these areas.

• Push Notifications: For sending alerts to guardians and park authorities in case of an emergency.

• Database: To store child, guardian, and park authority profiles, alert logs, and other relevant information.

7. Conclusion

This Smart Public Park Lost Child Alert App designed with object-oriented principles focuses on real-time alerts, user interaction, and efficient use of geolocation and Bluetooth technologies. It enhances the safety of children in public parks and ensures quick responses from guardians and park authorities. By following OOD, the system can be easily extended with additional features, ensuring scalability and maintainability.