Alefgen Project Use Case Document
1. User Authentication
Actors: Property Owner, Tenant
Preconditions: User is not logged in.
Trigger: User accesses the login page.
Workflow:
1. User enters email or mobile number.
2. System sends a verification code (if using mobile) or
prompts for a password (if using email).
3. System verifies credentials.
4. On success, system grants access.
Postconditions: User is authenticated and directed to the
dashboard.
2. Identity Verification
Actors: Property Owner
Preconditions: User is authenticated and wants to list a
property.
Trigger: Property Owner initiates property listing.
Workflow:
1. System prompts user to submit identity documents.
2. Property Manager or automated service reviews and
verifies documents.
3. System notifies the owner upon successful
verification.
Postconditions: Owner’s identity is verified, allowing
them to list properties.
3. Property Listing Management
Actors: Property Owner, Property Manager
Preconditions: Property Owner is verified.
Trigger: Owner decides to list a new property or update
an existing one.
Workflow:
1. Owner enters property details, including photos,
location, price, and amenities.
2. System saves listing as “Pending Approval.”
3. Property Manager reviews listing details for quality
and compliance.
4. Upon approval, system publishes the listing.
Postconditions: Property is listed and visible to tenants
and guests.
4. Property Search and Filter
Actors: Tenant, Guest
Preconditions: User is on the search page.
Trigger: User initiates a search with specific criteria.
Workflow:
1. User selects search filters (e.g., price range, location,
bedrooms, amenities).
2. System applies filters and displays matching
properties.
3. User can view details and save properties of interest.
Postconditions: Matching properties are displayed to the
user.
5. Tenant Screening
Actors: Property Manager, Tenant
Preconditions: Tenant has shown interest in renting a
property.
Trigger: Tenant submits rental application.
Workflow:
1. System prompts tenant for screening information
(background check, credit score).
2. Tenant submits details, which are sent for screening.
3. System verifies tenant's background and e-stamps
the agreement if screening is successful.
Postconditions: Tenant screening is completed; property
manager receives a report.
6. Booking and Scheduling
Actors: Tenant
Preconditions: Tenant is interested in viewing a property
or scheduling maintenance.
Trigger: Tenant selects a property or requests a
maintenance appointment.
Workflow:
1. Tenant selects a date and time for booking.
2. System confirms availability and schedules the
appointment.
3. System sends reminders and booking details to both
tenant and owner.
Postconditions: Viewing or maintenance appointment is
scheduled.
7. Payment Integration
Actors: Tenant, Property Manager
Preconditions: Tenant has passed screening.
Trigger: Tenant proceeds to payment for rent or deposits.
Workflow:
1. Tenant chooses a payment method (credit/debit card
or bank transfer).
2. System securely processes the payment.
3. Confirmation is sent to the tenant and the property
manager.
Postconditions: Payment is completed, allowing the
tenant to proceed with the rental.
8. Rent Agreement Management
Actors: Tenant, Property Manager
Preconditions: Tenant has made the required payment.
Trigger: Tenant and Property Manager initiate the rental
agreement.
Workflow:
1. System generates a digital rental agreement with e-
stamp and digital signature options.
2. Tenant and Property Manager review and sign the
agreement.
3. System stores the signed agreement and sends
copies to both parties.
Postconditions: Agreement is finalized and stored for
future reference.
9. Maintenance Request
Actors: Property Owner, Property Manager
Preconditions: Property is already listed or set up for
maintenance-only services.
Trigger: Property Owner requests maintenance.
Workflow:
1. Owner submits a maintenance request, specifying
issue details.
2. System routes the request to the Property Manager.
3. Property Manager coordinates the maintenance task.
4. Upon task completion, system notifies the owner.
Postconditions: Maintenance request is fulfilled.
10. AI Chatbot Support
Actors: Property Owner, Tenant, Guest, AI Chatbot
Preconditions: User requires assistance with the
platform.
Trigger: User initiates a chat session with the AI Chatbot.
Workflow:
1. User selects the topic or enters a question.
2. AI Chatbot provides responses based on FAQs or
redirects to support resources.
3. If unresolved, chatbot escalates the issue to a human
agent.
4. Feedback is requested at the end of the chat for
future improvements.
Postconditions: User’s issue is resolved or escalated to a
human agent.