Use Case Tasks for Interview

Preparation
Use Case Task for Online Food Delivery Application

Identifying the Key Stakeholders

 Customers – Use the app to browse restaurants, order food, track delivery, and provide
feedback.
 Delivery Partners – Pick up orders from restaurants and deliver them to customers.
 Restaurants – Manage their menus, receive orders, and prepare food.
 Admin – Manage users, restaurants, complaints, delivery performance, and platform
efficiency.
 Technical Team – Ensure application functionality, maintain servers, and implement
features.

Requirement Elicitation Plan

 Customer Interviews – Understand ordering patterns and pain points.
 Restaurant Feedback – Explore restaurant-side operations.
 Competitor Analysis – Study Zomato, Swiggy, Uber Eats to gather best practices.
 A/B Testing – Test new features like filters, offers, etc.

Functional Requirements
 Customers can browse menus and apply filters.
 Customers must be able to view estimated delivery time.
 Restaurants can update item availability.
 Delivery partners can accept/decline deliveries.
 Admin can manage users and generate performance reports.

User Stories
 TITLE: Order Tracking - As a customer, I want to track my order live so that I know
when it will arrive.
 TITLE: Menu Management - As a restaurant, I want to update my menu in real time so
that customers don’t order unavailable items.
 TITLE: Delivery Notification - As a delivery partner, I want to be notified when a new
order is ready for pickup.
 TITLE: Complaint Resolution - As an admin, I want to track and respond to all
complaints to improve customer satisfaction.

Acceptance Criteria
 The user must have a registered account.
 Location access should be enabled for delivery tracking.
 Only verified restaurants can be onboarded.
 Real-time order status must be visible to the customer.
 Delivery personnel can mark an order as “Delivered.”

Use Case Task for Online Learning Platform

Identifying the Key Stakeholders

 Students – Use the app to enroll in courses, view lectures, and track progress.
 Instructors – Upload content, create quizzes, and monitor student performance.
 Admin – Monitor activity, moderate content, handle user issues.
 Technical Team – Maintain uptime, implement new features.

Requirement Elicitation Plan

 Student Surveys – Identify learning habits and problems.
 Instructor Interviews – Understand course creation workflows.
 Market Analysis – Review Coursera, Udemy, edX.
 Prototype Testing – Validate usability.

Functional Requirements
 Students must be able to enroll and access content.
 Instructors must be able to create structured content.
 Progress tracking must be available.
 Admin should be able to ban or approve content.

User Stories
 TITLE: Course Enrollment - As a student, I want to enroll in a course and track my
completion progress.
 TITLE: Upload Lecture Videos - As an instructor, I want to upload videos for each
module.
 TITLE: Certificate Generation - As a student, I want to download a certificate after
completing the course.
 TITLE: Report Generation - As an admin, I want to generate monthly user engagement
reports.

Acceptance Criteria
 Users must have verified emails.
 Courses should have structured modules.
 Progress bar must update on module completion.
 Instructors must be verified by admin.
 Only completed users should get certificates.
Use Case Task for Hotel Booking System

Identifying the Key Stakeholders

 Travelers/Guests – Book rooms, filter hotels by location and rating.
 Hotel Managers – Update room availability, pricing, and accept bookings.
 Admin – Validate listings, monitor fraud, and manage disputes.
 Tech Support – Ensure uptime and secure transactions.

Requirement Elicitation Plan

 User Interviews – Understand travel booking behaviors.
 Partner Hotel Meetings – Learn hotel-side challenges.
 Market Study – Research Booking.com, Airbnb, MakeMyTrip.
 Usability Testing – Test filter and booking flow.

Functional Requirements
 Guests can search and book rooms.
 Hotels can list, delist, and update rooms.
 Guests can rate and review after check-out.
 Admin can manage payment disputes.

User Stories
 TITLE: Search by Location - As a guest, I want to find hotels near a certain location.
 TITLE: Manage Availability - As a hotel, I want to mark rooms as unavailable during
renovation.
 TITLE: Payment Dispute - As an admin, I want to manage refund requests and disputes.
 TITLE: Booking Confirmation - As a user, I want to receive confirmation and hotel
details upon successful booking.

Acceptance Criteria
 Guests must log in to book.
 Only listed hotels should be shown.
 Payment gateway must be secure and provide confirmation.
 Booking must trigger email and SMS notification.
 Reviews should only be posted after a completed stay.
Use Case Task for E-Commerce Application

Identifying the Key Stakeholders

 Customers – Browse products, place orders, track delivery, and post reviews.
 Sellers – List products, manage inventory, and handle orders.
 Admin – Verify sellers, manage users, resolve disputes.
 Delivery Partners – Deliver products to the customers.
 Tech Team – Maintain site reliability, enhance user experience.

Requirement Elicitation Plan

 Customer Surveys – Understand shopping behavior and preferences.
 Seller Interviews – Identify pain points in order and inventory management.
 Competitor Analysis – Study Amazon, Flipkart, Myntra.
 Usability Testing – Test cart, filters, and payment flows.

Functional Requirements
 Users must be able to search, filter, and order products.
 Sellers must be able to list, edit, and remove products.
 Customers must be able to track their orders.
 Admin can suspend accounts for policy violations.
 Payment integration must support refunds.

User Stories
 TITLE: Product Filtering - As a customer, I want to filter products by price, brand, and
rating.
 TITLE: Add to Cart - As a customer, I want to add products to a cart before final
purchase.
 TITLE: Manage Listings - As a seller, I want to add and manage my product catalog.
 TITLE: Refund Handling - As an admin, I want to process and approve customer refund
requests.

Acceptance Criteria
 Customers must register or log in to place an order.
 Each order should have a unique tracking ID.
 Products must be categorized for efficient browsing.
 Sellers can view stock levels in real-time.
 Refunds must be processed within 7 business days.
Use Case Task for Banking Application

Identifying the Key Stakeholders

 Customers – Perform transactions, check balances, and manage accounts.
 Bank Staff – Assist with customer issues and approvals.
 Admin – Monitor system security, fraud, and compliance.
 Tech Team – Ensure data security and feature updates.

Requirement Elicitation Plan

 Focus Groups – Gather feedback from banking customers.
 Stakeholder Meetings – Involve compliance officers and risk managers.
 Competitor Analysis – Review SBI, ICICI, HDFC applications.
 Security Audit Reports – Understand system vulnerabilities.

Functional Requirements
 Customers can check account balance and transaction history.
 Customers can transfer money via NEFT/IMPS/UPI.
 Admins can freeze suspicious accounts.
 Bank staff can approve loan or KYC requests.
 System must log all actions securely.

User Stories
 TITLE: Fund Transfer - As a user, I want to transfer funds securely to another account.
 TITLE: View Transactions - As a customer, I want to see my transaction history for the
last 6 months.
 TITLE: Loan Approval - As a bank officer, I want to review and approve personal loan
requests.
 TITLE: System Security - As an admin, I want to track and get alerts for any suspicious
activity.

Acceptance Criteria
 User must be authenticated via OTP or biometrics.
 Transactions should complete within a defined time limit.
 KYC must be verified before account activation.
 Loan approvals require dual-level verification.
 Account activity logs must be tamper-proof.
Use Case Task for Healthcare Management System

Identifying the Key Stakeholders

 Patients – Book appointments, view prescriptions, access reports.
 Doctors – Manage appointments, view patient history, prescribe medication.
 Receptionists – Schedule patient visits and manage billing.
 Admin – Ensure compliance, manage system access, and view reports.
 Tech Team – Ensure system uptime and data protection.

Requirement Elicitation Plan

 Patient Feedback – Identify issues in appointment scheduling.
 Doctor Interviews – Streamline EHR (Electronic Health Record) usage.
 Benchmarking – Study apps like Practo, Apollo 247.
 HIPAA Compliance Review – Ensure legal data practices.

Functional Requirements
 Patients can book, reschedule, or cancel appointments.
 Doctors can view patient records and update diagnoses.
 Prescriptions must be digitally generated and downloadable.
 Admins can generate reports on visits, prescriptions, and revenue.
 System must have role-based access controls.

User Stories
 TITLE: Appointment Scheduling - As a patient, I want to book an appointment with my
preferred doctor.
 TITLE: Prescription Download - As a patient, I want to download my prescription for
offline use.
 TITLE: Medical Record Update - As a doctor, I want to update a patient’s diagnosis after
consultation.
 TITLE: Report Generation - As an admin, I want to download monthly analytics of
patient visits.

Acceptance Criteria
 Only registered users can access patient data.
 All changes to health records must be timestamped.
 Doctor access is limited to their assigned patients.
 Prescriptions should be stored in PDF format.
 Appointments should send SMS/Email reminders.