The Level 0 DFD, also known as a Context Diagram, provides a high-level view of the system. It represents the entire system as a single process, showing how data flows between entities (like users or other systems) and the main system. This diagram doesn’t delve into internal system details but focuses on the system's overall functions.

1. Depicts the entire system as one unit.
2. No internal process details are shown.
3. Highlights the external entities and how they exchange data with the system.

The key components of a Level 0 DFD are:

• Entities: Actors that interact with the system. They could be individuals, systems, or organizations that send or receive data from the system.
• Single Process: The entire system is represented as a single process or a large bubble/circle.
• Data Flows: Arrows connecting entities and the main process, representing the flow of data between the system and its actors.

In the case of LivSmart, a Smart Community Living System, the Level 0 DFD represents the system as a single process. External actors like Residents, Managers, and Security Guards provide inputs (such as service requests), and the system responds with outputs (such as notifications and announcements).

• Figure 1: Level 0 DFD for LivSmart using Visual Paradigm.

• Figure 2: Level 0 DFD for LivSmart (Hand Drawn).

• Entities: Resident, Manager, Security Guard, Secretary.
• Single Process: LivSmart.
• Data Flow: Represents the movement of data between the process and entities.

• Residents → LivSmart: Residents send service requests.
• LivSmart → Residents: LivSmart provides status updates on the submitted requests.
• Managers → LivSmart: Managers handle resident needs and receive updates or notifications regarding tasks.
• LivSmart → Managers: The system sends notifications about updates.
• Security Guards → LivSmart: Security guards submit security logs to monitor building and resident access.
• LivSmart → Security Guards: The system processes security updates.
• Secretary → LivSmart: The secretary updates system information regarding community activities or changes.
• LivSmart → Secretary: The system processes this information to ensure smoother operation.

---

The Level 1 DFD provides a more detailed view of the system by decomposing the single process from the Level 0 DFD into multiple sub-processes. These processes represent the key functions that the system performs and provide insight into the system’s internal operations. Unlike the Level 0 DFD, the Level 1 DFD highlights how data flows between internal processes and data stores.

1. Provides more detail about how the system operates internally.
2. Shows multiple processes and their interactions with each other.
3. Includes data stores, showing where information is kept within the system.
4. Useful for system developers, engineers, and analysts to understand the system’s finer details.

The key components of a Level 1 DFD are:

• Processes: The specific tasks or functions performed within the system, represented by bubbles or circles.
• Data Stores: Repositories where the system stores data, such as databases or files.
• Data Flows: Arrows that connect processes and data stores, representing how information moves through the system.
• Entities: External actors that interact with the system, such as residents or managers, by sending data to or receiving data from the processes.

In the case of LivSmart, a Smart Community Living System, the Level 1 DFD breaks down the system’s functionality into processes like managing events, registering parking, handling complaints, and providing security. Each of these processes interacts with specific data stores (like Event Files or Security Logs) and external actors (such as Residents, Security Guards, or Managers).

• Figure 3: Level 1 DFD for LivSmart using Visual Paradigm.

• Figure 4: Level 1 DFD for LivSmart (Hand Drawn).

• Processes:

  • Register: Verifies and stores personal information of users and grants access credentials.
  • Login: Authenticates users via credentials and provides access based on their role.
  • Access Dashboard: Displays a role-specific dashboard with tasks, updates, and notifications.
  • Manage Service Request: Allows residents to submit service requests and receive status updates from managers.
  • Manage Event: Enables managers or secretaries to create, update, and notify residents about events.
  • Register Event: Records resident participation in events and manages event capacity.
  • Manage Bill Payments: Records and verifies resident bill payments, updating billing history.
  • Manage Announcement: Enables managers and secretaries to post community-wide announcements.
  • Register and Manage Parking: Verifies and records resident parking registrations and availability.
  • Verify: Verifies credentials for residents and visitors, ensuring secure access to parking areas.
  • Manage Security: Logs security events, verifies credentials, and tracks visitor access.
  • Manage Complaint: Processes and tracks complaints, providing updates to residents.
  • Manage Feedback: Collects and stores resident feedback for management review.
  • Book Amenities: Enables residents to book available community amenities and confirms bookings.

• Data Stores:

  • User Info File: Stores personal information of users for authentication and profile management.
  • Service Request File: Logs service requests, tracking their progress and updates.
  • Bill Payment File: Maintains records of bill payments, including transaction history and status.
  • Event File: Stores community event details for managers and secretaries to manage.
  • Event Registration File: Tracks resident participation in events and manages capacity.
  • Announcement File: Logs community-wide announcements for resident dashboards.
  • Parking Registration File: Records parking slot registrations and availability information.
  • Security Log File: Stores security logs for visitor entries, incidents, and access control.
  • Complaint File: Logs complaints from residents, tracking resolution status and updates.
  • Feedback File: Stores resident feedback on services and amenities for management review.

• Entities: Resident, Manager, Security Guard, Secretary.

• Data Flow: Represents the movement of data between processes and data stores.

• Residents → Register: Residents submit personal details for registration, and the system verifies the information, storing it in the User Info File.
• Residents → Login: Residents input their credentials, which are verified against the User Info File for authentication.
• Users → Access Dashboard: After a successful login, residents, managers, secretaries, and security guards access their customized dashboards, which display tasks and relevant data from files like Service Request File, Complaint File, and Bill Payment File.
• Residents → Manage Service Request: Residents submit service requests, which are logged in the Service Request File. Managers monitor and update the request status.
• Secretary → Manage Event: Secretaries create and managers manage community events, which are logged in the Event File. Event registrations are tracked in the Event Registration File.
• Residents → Register Event: Residents register for events, and their participation is recorded in the Event Registration File.
• Residents → Manage Bill Payments: Residents make payments, which are logged and stored in the Bill Payment File. Payment statuses are updated in real-time.
• Manager → Manage Announcement: Managers create announcements, which are stored in the Announcement File and displayed on resident dashboards.
• Residents → Register and Manage Parking: Residents submit parking registration requests, and the availability and registration details are recorded in the Parking Registration File.
• Security Guard → Manage Security: Security guards log visitor entries, access control events, and security incidents in the Security Log File.
• Residents → Manage Complaint: Residents submit complaints, which are stored in the Complaint File. Managers or secretaries review and update the status.
• Residents → Manage Feedback: Residents provide feedback on community services or events, which is stored in the Feedback File.
• Residents → Book Amenities: Residents request to book amenities like gyms or parking. Booking details are stored in the Amenity Booking File.