Scribd
Upload
4 views

Project

Uploaded by

Fãhãđ Ãľï Šhãh
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
4 views

Project

Uploaded by

Fãhãđ Ãľï Šhãh
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

LIBRARY MANAGEMENT

SYSTEM
An Efficient Solution for Book Tracking and Borrowing

GROUP MEMBERS: MUHAMMAD HAMZA (22MDBCS289)


FAHAD ALI SHAH (22MDBCS299)
MUHAMMAD AWAIS (22MDBCS307)
Table of Contents
Project proposal --------------------------------------------------------------------------------------------------1

Software Development Process---------------------------------------------------------------------------------2

Requirements of engineering-----------------------------------------------------------------------------------3

System design----------------------------------------------------------------------------------------------------4

Risk analysis-------------------------------------------------------------------------------------------------------5

Testing strategy------------------------------------------------------------------------------------------------------6

Project management-----------------------------------------------------------------------------------------------7

Timeline----------------------------------------------------------------------------------------------------------------8
1.1 Project Proposal
• Objective:
The LMS will help libraries manage books, users, and borrowing/returning records more
efficiently.
• Problem it Solves:
It simplifies the process of tracking books, reduces manual errors, and provides a faster
way to manage library activities.
• Stakeholders:
o Library staff (librarians).
o Library users (students, teachers, or members).

1.2 Software Development Process

• Model to Use: Agile Model


o Why Agile?
▪ The requirements for the system may change based on feedback from
librarians or users.
▪ Agile allows flexibility and iterative development for a better final product.

1.3 Requirements Engineering


Functional Requirements:
1. Users can search for books by title, author, or category.
2. Librarians can add, update, or delete book records.
3. The system allows users to borrow and return books.
4. Generate reports for borrowed books and late returns.
5. Users can check the availability of books.
Non-Functional Requirements:
1. The system should load pages within 2 seconds.
2. It must be secure to prevent unauthorized access.
3. The system should be accessible 24/7.
Constraints/Assumptions:
1. The library will have internet access for the system.
2. Users will need a valid library ID to access the system.

1.4 System Design


Use Case Diagram:

Class Diagram:

Sequence Diagram:
1.5 Risk Analysis
Risks and Mitigation:
1. Technical Risk: Difficulty in integrating with an existing database.
o Mitigation: Use simple and well-documented database tools like MySQL.
2. Schedule Risk: Delays in development due to unplanned changes.
o Mitigation: Set milestones and review progress weekly.
3. Financial Risk: Exceeding the budget for hosting or tools.
o Mitigation: Use free tools during development (e.g., XAMPP for local hosting).

1.6 Testing Strategy


Types of Testing:
1. Unit Testing: Test individual functions like "Search Books."
2. Integration Testing: Test how "Borrow Book" works with the database.
3. User Acceptance Testing: Librarians and users test the system to ensure it meets their
needs.
Example Test Cases:
1. Test Case 1:
o Input: Search for a book title “Harry Potter.”
o Expected Output: Display all Harry Potter books.
o Actual Result: [To be filled after testing].
2. Test Case 2:
o Input: Borrow a book already marked as unavailable.
o Expected Output: Show "Book not available."
o Actual Result: [To be filled after testing].

1.7 Project Management


Tasks/Phases:
1. Planning
2. Designing Use Case and Class Diagrams
3. Development of Core Features (Search, Borrow, Return)
4. Testing and Bug Fixing
5. Deployment

1.8 TIMELINE
Duration
Task Start Date End Date (calculated)
(hours)

Project Planning 24-Dec-2024 8am:9am 24-Dec-2024

System Design 24-Dec-2024 11am:12am 24-Dec-2024

Development 24-Dec-2024 1pm:2pm 24-Dec-2024

Testing 24-Dec-2024 3pm:4pm 24-Dec-2024

Final Review & Submit 24-Dec-2024 5pm:6pm 24-Dec-2024

You might also like