Most project reports need the same five diagrams: use case, ER, data flow, class and sequence. Here is the full set for 9 classic projects, ready to open, change for your own project in plain English, and download as PNG or PDF for your report.
Use case diagram โ Who uses a college library system and what each of them can do: members, the librarian and the system administrator.
ER diagram โ The database of a library system: books and their copies, authors, members, loans, reservations and fines, with keys and cardinality.
Data flow diagram โ How data moves through a library system: members and the librarian, the main processes, and the data stores they read and write.
Class diagram โ The main classes of a library system with attributes, methods and UML relationships.
Sequence diagram โ The steps when a member borrows a book: checks, loan record and the copy status update.
Online Examination System
Use case diagram โ What students, examiners and the administrator do in an online examination system.
ER diagram โ Database design for online exams: courses, exams, questions and options, attempts, answers and results.
Data flow diagram โ Data flows in an online exam system from question setting to published results.
Class diagram โ Classes for an online exam system, with question types by inheritance and grading logic.
Sequence diagram โ A student taking an online exam: start, auto-save, submit and grading.
Hotel Room Booking System
Use case diagram โ Guests, front desk staff and the hotel manager in an online room booking system, with the payment gateway as an outside actor.
ER diagram โ Database for hotel bookings: room types, rooms, guests, bookings, payments and stays.
Data flow diagram โ How booking data flows between guests, the payment gateway, staff and the hotel's data stores.
Class diagram โ Main classes of a hotel booking system, including room types and a payment interface.
Sequence diagram โ Booking a hotel room online, from the availability search to the confirmation email.
Student Result Management System
Use case diagram โ Students, teachers, the exam cell and parents in a college result and attendance system.
ER diagram โ Database for marks, attendance and results: students, subjects, semesters, marks and attendance records.
Data flow diagram โ Marks and attendance flowing from teachers to published results for students and parents.
Class diagram โ Classes for results and attendance, with a grading policy that can change.
Sequence diagram โ From marks entry to students seeing results: validation, grade calculation and exam cell approval.
Online Shopping System
Use case diagram โ Customers, sellers, the admin and outside services in an online shopping website.
ER diagram โ The core e-commerce schema: customers, addresses, products, categories, carts, orders, order items, payments and reviews.
Data flow diagram โ Order data flowing between the customer, seller, payment gateway, courier and the shop's data stores.
Class diagram โ Classes for an online shop: customer, cart, order, payment strategies and order states.
Sequence diagram โ Checkout on a shopping website: stock check, payment and order confirmation.
Hospital Management System
Use case diagram โ Patients, receptionists, doctors, lab technicians, pharmacists and the admin in a hospital management system, with the payment gateway as an outside actor.
ER diagram โ The database behind a hospital management system: patients, doctors and departments, appointments, admissions to wards and beds, prescriptions, lab tests and bills.
Data flow diagram โ How data moves through a hospital: registration, appointments, diagnosis and prescriptions, lab results, pharmacy, billing, payments and daily reports.
Class diagram โ Classes for a hospital management system: Person with Patient, Doctor and Staff, departments, appointments, admissions with wards and beds, prescriptions, lab tests, bills and payments.
Sequence diagram โ Booking a doctor's appointment online: finding a free slot, holding it for five minutes, paying the consultation fee and getting an SMS confirmation.
Railway Reservation System
Use case diagram โ Passengers, the ticket counter clerk and the admin in a railway reservation system, with the payment gateway handling payments and refunds.
ER diagram โ The database of a railway reservation system: trains, coaches and seats, stations and routes, passengers, bookings with a PNR, tickets, payments, cancellations and refunds.
Data flow diagram โ How a railway reservation system handles a booking: search, passenger details, payment, seat or waiting-list allocation, e-ticket with PNR, cancellation and refund.
Class diagram โ Classes for a railway reservation system: trains, coaches, seats, stations, routes and stops, passengers, bookings with a PNR, tickets, payments and refunds.
Sequence diagram โ Booking a train ticket online, from the train search to the e-ticket by SMS and email, including the waiting list and failed payments.
ATM System
Use case diagram โ What a customer and a technician do at an ATM, with the bank's core banking system authorising every transaction.
ER diagram โ The database of an ATM banking system: customers, accounts, debit cards, ATMs and their cash cassettes, transactions, cash refills by technicians and an audit log.
Data flow diagram โ How a cash withdrawal flows through an ATM system: card and PIN check, balance and daily limit, cash dispensing, account update, receipt, logging and cash refills.
Class diagram โ Classes for an ATM system: the ATM and its card reader, keypad, screen, cash dispenser and receipt printer, the bank, accounts, cards, customers and transaction types.
Sequence diagram โ An ATM cash withdrawal step by step: card and PIN, balance and limit check, debit, cash dispensing and receipt, with a blocked card after three wrong PINs and a reversal if the dispenser fails.
Online Food Ordering System
Use case diagram โ Customers, restaurants, delivery partners and the admin in an online food ordering app, with the payment gateway as an outside actor.
ER diagram โ The database of an online food ordering system: customers and addresses, restaurants, menu categories and items, carts, orders, payments, delivery partners, coupons and ratings.
Data flow diagram โ How an online food order flows: menu and order, payment, the restaurant's acceptance, delivery assignment and live tracking, ratings and sales reports.
Class diagram โ Classes for an online food ordering app: users (customer, restaurant owner, delivery partner), restaurants, menus, carts, orders and order items, payments, coupons and ratings.
Sequence diagram โ Placing a food order in an app: checkout, payment, the restaurant's acceptance, assigning a delivery partner, live tracking and delivery, with a refund if the restaurant rejects it.
Which diagram goes where in the report
Use case diagram โ the requirements chapter: who uses the system and what they can do.
Data flow diagram (Level 0 and 1) โ system design: how data moves between users, processes and data stores.
ER diagram โ database design: tables, keys and how they relate.
Class diagram โ detailed design: classes, attributes, methods and relationships.
Sequence diagram โ detailed design: the steps of one important action, such as placing an order.
Questions
Is it free for students?
Opening and copying these diagrams is free and needs no account. Changing one with AI or making your own uses credits: 3 a day without an account, 20 to start with a free account.
Can I use a different project, not one of these?
Yes. Describe your own system in plain English, for example "a hostel management system where students apply for rooms and the warden allocates them", and choose the diagram type.
Can I put the diagrams in my Word report?
Yes. Download a diagram as PNG, SVG or PDF and insert it into your report. A Word export with every diagram and its explanation is part of Pro.
Will every college accept these diagrams as they are?
Check your college's format and your guide's notes. Treat these as a correct starting point and change names and details to match your own project.