qa

Why did you choose this project?

Many libraries still use manual records or spreadsheets. This causes errors, difficulty tracking books, overdue items, and fines. I developed this system to automate library operations and improve efficiency.

What is the main aim of your project?

To develop a web-based Library Management System that automates book cataloguing, borrowing, returning, fine calculation, and role-based access control.

Why did you choose 3-tier architecture?

It separates the user interface, business logic, and database, making the system easier to maintain, secure, and scale.

A 3-tier web architecture is a way of organizing a web application into three separate layers, each with a specific responsibility.

What are your future ideas to improve or extend this project?

Future enhancements include:

  • Book reservation and waiting list functionality
  • Email and SMS reminders for due dates and overdue books
  • Barcode and RFID integration for faster book issuing and returning
  • Multi-branch library support
  • Advanced reporting and analytics with PDF/Excel export
  • Mobile application support
  • Online book search and reservation by members
  • Integration with digital libraries and e-books

Can you explain the functions

Functional Requirements

These describe what the system should do:

  • User login and authentication
  • Role-based access control
  • Book and category management
  • Member management
  • Book borrowing and returning
  • Automatic due date generation
  • Automatic fine calculation
  • Dashboard with library statistics
  • System settings management

What difficulties did you face while developing this project?

During development, I faced several challenges:

  • Designing the database relationships correctly
  • Implementing role-based access control securely
  • Ensuring book availability updates correctly during borrowing and returning
  • Implementing automatic fine calculation accurately
  • Preventing unauthorized page access
  • Testing different user roles and workflows

I overcame these challenges through careful database design, extensive testing, and debugging.

What technologies and tools did you use to complete this project?

Front-End Technologies

  • HTML
  • CSS
  • Bootstrap
  • JavaScript

Back-End Technologies

  • PHP

Database

  • MySQL

Development Tools

  • XAMPP
  • phpMyAdmin
  • Visual Studio Code

Why did you use PHP?

PHP is open-source, easy to learn, widely used for web development, and integrates effectively with MySQL.

Why did you use MySQL?

MySQL is reliable, supports relational databases, provides foreign key constraints, and works well with PHP.

Why is role-based access important?

It improves security by ensuring users can only access functions relevant to their role.

What is a foreign key?

A foreign key is a field that links one table to another and maintains referential integrity.

Example:
books.category_id → categories.id

What is normalization?

Normalization organizes data into related tables to reduce redundancy and improve consistency.

How is the fine calculated?

Fine = Overdue Days × Fine Rate Per Day

For example, if the fine rate is Rs. 20 per day and a book is returned 5 days late, the fine is Rs. 100.

Why did you choose a web application instead of a desktop application?

A web application can be accessed through a browser from multiple computers, requires no installation on client machines, and is easier to maintain and update.

What testing did you perform?

  • Access Control Testing
  • Workflow Testing
  • Fine Calculation Testing
  • Data Integrity Testing

Did you achieve your objectives?

Yes. All objectives mentioned in the project scope were successfully implemented and validated through testing.

What is the biggest contribution of your project?

The system replaces manual record-keeping with a digital platform that automates borrowing, returning, and fine management while providing real-time visibility of library operations.

Question they often ask at the end

“If you had another 6 months, what would you add?”

Answer:
“I would implement barcode/RFID support, email notifications, book reservations, reporting dashboards, mobile access, and multi-branch library management to make the system suitable for larger institutions.”

3. What objectives were achieved?

  • Digital book management
  • Automated borrowing and returning
  • Automatic fine calculation
  • Role-based access control
  • Real-time dashboard monitoring

What happens when a user borrows a book?

Answer:
The browser sends a request to PHP. PHP validates the request, updates the borrow record, decreases available copies, and stores the data in MySQL.

Why did you use MySQL?

Answer:
MySQL is open-source, reliable, easy to integrate with PHP, and supports relational database features such as foreign keys and transactions.

How many tables are in your system?

Answer:
Five main tables:

  • Users
  • Categories
  • Books
  • Borrows
  • Settings

Explain one-to-many relationship.

Answer:
One category can contain many books, but one book belongs to only one category.

12. Why did you normalize the database?

Answer:
To reduce data redundancy and improve data consistency.

13. How do users log in?

Answer:
Users enter their username and password. PHP verifies the password using password_verify() and creates a session.

16. How do you prevent unauthorized access?

Answer:
Role checking and session validation are performed on every protected page.

18. What can an Admin do?

Admin has full control over books, users, borrowing records, settings, and system management.

19. What can Students do?

Students can view books and their own borrowing history but cannot modify records.

20. Why implement role-based access control?

To improve security and ensure users access only the features relevant to their role.

Borrowing & Fine Management

21. How is the due date calculated?

The due date is automatically generated based on the borrow period configured in the Settings table.

22. How is the fine calculated?

Fine = Overdue Days × Fine Rate Per Day

24. What happens when a book is returned?

  • Updates return date
  • Calculates fine if overdue
  • Changes status to Returned
  • Increases available copies

What testing methods did you perform?

  • Access Control Testing
  • Workflow Testing
  • Fine Calculation Testing

27. How did you test fine calculation?

I manually calculated fines and compared them with system-generated values for different overdue periods.

28. What is Data Integrity Testing?

It ensures that borrowing and returning books update available copies correctly and that foreign key relationships remain valid.

29. Why did you choose PHP?

Answer:
PHP is open-source, easy to learn, widely supported, and integrates well with MySQL.

30. Why use Bootstrap?

Answer:
Bootstrap provides responsive and professional-looking user interfaces with minimal effort.

31. What is XAMPP?

Answer:
XAMPP is a local server environment containing Apache, MySQL, PHP, and phpMyAdmin for development.

What are the limitations of your system?

  • No book reservation feature
  • No email/SMS reminders
  • No barcode/RFID integration
  • No multi-branch support
  • No advanced reports

What future improvements would you add?

  • Barcode scanning
  • Email notifications
  • Book reservations
  • Multi-branch support
  • PDF/Excel reports
  • RFID integration

What is the most challenging part of your project?

Implementing the borrowing workflow and ensuring accurate fine calculation while maintaining correct book availability counts.

What is your project’s main contribution?

It digitizes library operations, reduces manual work, improves accuracy, and provides real-time access to borrowing and fine information.

Did you achieve all objectives?

Yes. All planned objectives were implemented and validated through testing.

Why should your system be adopted by libraries?

It reduces paperwork, improves efficiency, minimizes errors, provides real-time tracking, and simplifies library management.

These 40 questions cover about 90% of the questions typically asked in an MIT/IT viva for a Library Management System project.

These are very common viva questions. Here are strong answers tailored to your Library Management System project.