Assistant: Hello! How are you today?
User: Agent:
Beneficiary (Client)

Process Flows:
Login Flow

The Beneficiary submits login credentials (ID Number and Password) to the system.

The system checks these credentials against the Beneficiaries data store.

If the credentials are incorrect, an error message is sent back to the Beneficiary and the process ends.

If the credentials are correct, a success message is sent, and the Beneficiary can continue to other actions.

Book In/Out Flow

The Beneficiary makes a booking request (check-in or check-out).

The request is processed by checking room availability (if checking in) using the Bookings data store.

If a room is available, the booking status is updated in Bookings.

A confirmation message is sent back to the Beneficiary.

Request Meal Ticket Flow

The Beneficiary requests a meal ticket.

The system validates the booking status in Bookings.

If valid, a ticket is issued and recorded in Meal Tickets.

The Beneficiary receives the ticket as output.

Update Personal Details Flow

The Beneficiary submits updated personal details.

The system updates the record in Beneficiaries.

A confirmation message is sent back to the Beneficiary.

Data Flows:
Login credentials: Beneficiary → System → Beneficiaries (for validation)

Booking/meal ticket requests: Beneficiary → System → Bookings/Meal Tickets

Confirmation messages/tickets: System → Beneficiary

Updated details: Beneficiary → System → Beneficiaries

2. Organizer-Process Model (Administrator)
Agent:
Administrator (Organizer)

Process Flows:
Login Flow

The Administrator submits login credentials (Username and Password).

The system checks these credentials in the Users data store.

If incorrect, an error message is sent; if correct, access is granted.

Maintain Rooms Flow

The Administrator adds, edits, or deletes room records.

Room details are sent to the Rooms data store.

A confirmation message is returned.

Maintain Beneficiary Types Flow

The Administrator manages beneficiary types (add/edit/delete).

Type details are updated in the Beneficiary Types data store.

A confirmation message is returned.

Maintain Beneficiaries Flow

The Administrator manages beneficiary records (add/edit/delete).

Beneficiary details are updated in Beneficiaries.

A confirmation message is returned.

Generate Reports Flow

The Administrator requests a report (e.g., capacity, demographics).

The system queries Bookings, Beneficiaries, and Rooms.

The report is generated (CSV/PDF) and returned to the Administrator.

Manage Users Flow

The Administrator adds, edits, or deletes user accounts.

User details are updated in Users.

A confirmation message is returned.

Data Flows:
The beneficiary provides login credentials (ID Number and Password), which are sent to the system for verification against the Beneficiaries data store.

When the beneficiary submits a booking or meal ticket request, the system receives the request and accesses the relevant data stores (Bookings for check-in/out, Meal Tickets for meal ticket requests).

After processing a booking request, the system checks or updates the Bookings data store and, if necessary, checks room availability in the Rooms data store.

For meal ticket requests, the system validates the beneficiary’s booking status using the Bookings data store before issuing and recording a meal ticket in the Meal Tickets data store.

When the beneficiary updates personal details, the new information is sent to the system, which updates the Beneficiaries data store.

Throughout these processes, the system sends confirmation messages, error messages, or tickets back to the beneficiary as appropriate. in mermaid js v 10 syntax
User: Agent:
Beneficiary (Client)

Process Flows:
Login Flow

The Beneficiary submits login credentials (ID Number and Password) to the system.

The system checks these credentials against the Beneficiaries data store.

If the credentials are incorrect, an error message is sent back to the Beneficiary and the process ends.

If the credentials are correct, a success message is sent, and the Beneficiary can continue to other actions.

Book In/Out Flow

The Beneficiary makes a booking request (check-in or check-out).

The request is processed by checking room availability (if checking in) using the Bookings data store.

If a room is available, the booking status is updated in Bookings.

A confirmation message is sent back to the Beneficiary.

Request Meal Ticket Flow

The Beneficiary requests a meal ticket.

The system validates the booking status in Bookings.

If valid, a ticket is issued and recorded in Meal Tickets.

The Beneficiary receives the ticket as output.

Update Personal Details Flow

The Beneficiary submits updated personal details.

The system updates the record in Beneficiaries.

A confirmation message is sent back to the Beneficiary.

Data Flows:
Login credentials: Beneficiary → System → Beneficiaries (for validation)

Booking/meal ticket requests: Beneficiary → System → Bookings/Meal Tickets

Confirmation messages/tickets: System → Beneficiary

Updated details: Beneficiary → System → Beneficiaries

2. Organizer-Process Model (Administrator)
Agent:
Administrator (Organizer)

Process Flows:
Login Flow

The Administrator submits login credentials (Username and Password).

The system checks these credentials in the Users data store.

If incorrect, an error message is sent; if correct, access is granted.

Maintain Rooms Flow

The Administrator adds, edits, or deletes room records.

Room details are sent to the Rooms data store.

A confirmation message is returned.

Maintain Beneficiary Types Flow

The Administrator manages beneficiary types (add/edit/delete).

Type details are updated in the Beneficiary Types data store.

A confirmation message is returned.

Maintain Beneficiaries Flow

The Administrator manages beneficiary records (add/edit/delete).

Beneficiary details are updated in Beneficiaries.

A confirmation message is returned.

Generate Reports Flow

The Administrator requests a report (e.g., capacity, demographics).

The system queries Bookings, Beneficiaries, and Rooms.

The report is generated (CSV/PDF) and returned to the Administrator.

Manage Users Flow

The Administrator adds, edits, or deletes user accounts.

User details are updated in Users.

A confirmation message is returned.

Data Flows:
The beneficiary provides login credentials (ID Number and Password), which are sent to the system for verification against the Beneficiaries data store.

When the beneficiary submits a booking or meal ticket request, the system receives the request and accesses the relevant data stores (Bookings for check-in/out, Meal Tickets for meal ticket requests).

After processing a booking request, the system checks or updates the Bookings data store and, if necessary, checks room availability in the Rooms data store.

For meal ticket requests, the system validates the beneficiary’s booking status using the Bookings data store before issuing and recording a meal ticket in the Meal Tickets data store.

When the beneficiary updates personal details, the new information is sent to the system, which updates the Beneficiaries data store.

Throughout these processes, the system sends confirmation messages, error messages, or tickets back to the beneficiary as appropriate. in mermaid js v 10 syntax
Assistant: