Architects
in AI ERA.

Expense claims and reimbursements

Design a mobile solution that helps employees submit expenses and reviewers manage reimbursement requests.

1. An employee creates an expense claim with an amount, category, and description.
2. The employee submits the claim.
3. A reviewer approves or rejects it, with a reason where appropriate.
4. Both users can see the current status and decision history.

Business rule: An approved amount cannot exceed the claimed amount. Retrying a submission must not create duplicate claims.

Architecture focus: Monetary values, validation, approval transitions, and submission consistency. Payment processing and receipt scanning are optional.

Appointment coordination

Design a mobile solution that helps patients request appointments and clinics manage availability.

1. A patient browses available appointment slots.
2. The patient requests a slot.
3. The clinic confirms or declines the request.
4. The patient can see its status and cancel a confirmed appointment.

Business rule: A confirmed slot cannot be allocated to two patients. A cancelled appointment must update availability consistently.

Architecture focus: Scheduling, competing requests, changing availability, and consistent patient and clinic views. Use fictional patients; clinical advice, medical records, and video consultations are outside the required scope.

Solve a Mumbai property issue

Design a mobile solution to a property issue faced by people in Mumbai. Work from the specific problem assigned by the organizers and identify its users, such as renters, buyers, residents, owners, or housing societies.

The domain includes rental discovery and affordability, transparent total costs, listing accuracy and availability, and housing-society coordination. These are context for the domain; your assigned problem determines the scope.

1. A user discovers or reports a property-related need.
2. The user takes a meaningful action, such as making an enquiry, submitting a request, or reporting an issue.
3. Another role or service responds to that action.
4. The user can track the outcome, status, and latest information.

Business rule: Define and enforce a rule that protects the consistency of your chosen workflow. For example, a listing marked unavailable cannot accept a new viewing request, or a closed maintenance request requires explicit reopening before work resumes.

Architecture focus: Reliable property information, explicit workflow states, updates across user views, and recovery from stale or conflicting data. Use sample listings and data; live property integrations and maps are optional.

Campaign review and approval

Design a mobile solution that helps marketing teams prepare campaign proposals and coordinate approvals.

1. A marketer creates a campaign proposal with its objective, audience, channel, and budget.
2. The marketer submits it for review.
3. A reviewer approves it or requests changes.
4. The marketer can revise the proposal and track its approval or scheduling status.

Business rule: Only an approved campaign can be scheduled. Changing an approved proposal’s budget or audience must trigger another review.

Architecture focus: Revisions, approval validity, workflow state, and decision history. Actual ad publishing, external marketing integrations, and generated content are optional.