← All projects

IBM Business Analysis · End-to-End Academic Case Study · November 2026 · Rodrigo Garza García

Mobi-e-rides — End-to-End Business Analysis

Peer-to-Peer Bicycle and eBike Rental Platform

This case applies business analysis techniques to a proposed peer-to-peer bicycle and e-bike rental platform in Mexico City, linking stakeholder needs with prioritized requirements, traceability and solution models.

The business need

Customers need to find an available bike, make a reservation and pay. Employees need to record handovers and returns and keep availability up to date. The proposed launch uses a basic booking website with employee assistance at pickup and return.

End-to-end Business Analysis scope

The case brings together the main analysis activities needed to define a proposed solution:

A three-screen prototype and further stakeholder validation are proposed as next steps.

This is an academic design exercise adapted from the IBM exemplar. Interviews, observations, workshops, surveys and prototype testing have not been conducted. The outputs are proposed requirements and models.

Requirements and model connections

IDRequirementModel connection
REQ-01Easy bookingReserve bike; Customer and Rental records.
REQ-02Payment processingPay rental; payment_status in Rental.
REQ-03Bike availability trackingView and update availability; Bike status and the agreed rental period.

The three models

Explore and edit the three diagrams in Lucidchart.

Entity Relationship Diagram

Customer and Bike each have a one-to-many relationship with Rental, which stores the rental period and payment and rental status.
Three entities: Customer, Bike and Rental. The two dates define the agreed rental period. A bike must not have overlapping confirmed or active rentals. Open full-size ERD.

UML Use Case Diagram

Customer checks availability, reserves, pays and participates in return. Employee records handover and return and updates availability.
Two actors and six use cases. Customer and Employee both participate in return; the employee records receipt in the system. Associations show participation. Open full-size use case diagram.

Rental Process Flowchart

Select a bike and rental period, check availability, record details, pay, confirm, hand over, return and close the rental. Unavailable bikes and rejected payments lead to retry paths.
The proposed process includes two alternative paths: choose another bike or period, and retry payment. A rental is confirmed only after payment approval. Open full-size flowchart.

What I would validate next

I would review the requirements with customers and employees, clarify the handover and return information they need, and test the proposed booking journey with a simple prototype. Cancellation, refunds and detailed payment-provider integration would require further analysis.

Academic reference: IBM, Business Analysis and Modeling for an eBike Rental Startup, exemplar solution. Adapted using my stakeholder questions, requirements, priorities and models. Research and validation activities described as proposals have not been conducted.

Project deliverables

Project repository ↗ Open all three editable diagrams in Lucidchart ↗ Project report (PDF) ↗ View project diagrams ↓