Name: Priyanka
Vishwakarma Roll No. : 53
Week No: 1 Date: From 13/01/2025 To 18/01/2025
Activities Planned: The primary objective for this week was to understand the overall project requirements
and research best practices for documentation and testing. I planned to study how a Library Management
System works, define testing strategies, and outline documentation requirements
Activities Executed: I went through the project's objectives, problem statement, and scope. Researched
different testing methods, including unit testing and integration testing, that would be needed later. I also
reviewed documentation formats used in similar projects
Reason for delay if any: N/A
Corrective Measure adopted: N/A
Remark: Research and requirement analysis were completed successfully. The documentation structure
and initial test plan were outlined.
Signature of the Guide: Marks: / 10
Week No: 2 Date: From 20/01/2025 To 25/01/2025
Activities Planned: Start drafting the initial sections of the project documentation, including the abstract,
introduction, and problem statement. Define the overall structure of the report.
Activities Executed: I prepared the abstract, explaining the purpose and scope of the Library
Management System. Wrote a detailed problem statement, highlighting issues faced in traditional library
management and how our system solves them. Outlined the objectives of the project and the technologies
used (Python,
Tkinter, SQLite).
Reason for delay if any: N/A
Corrective Measure adopted: N/A
Remark: The initial documentation draft was completed, setting a clear direction for the upcoming weeks.
Signature of the Guide: Marks: / 10
Week No: 3 Date: From 27/01/2025 To 1/01/2025
Activities Planned: Finalize the problem statement and begin documenting how the system works,
including
workflows for book management, user roles, and transactions.
Activities Executed: Improved the problem statement with more real-world examples and refined the
workflow diagrams for book issuing, returning, and fine calculations. Wrote an explanation of how users
interact with the system
Reason for delay if any: N/A
Corrective Measure adopted: N/A
Remark: The system workflow section was completed, making it easier for others to understand the
functionality of the system.
Signature of the Guide: Marks: / 10
Week No: 4 Date: From 3/01/2025 To 08/02/2025
Activities Planned: Document the system's key features and write use case scenarios explaining how
different users (librarians, students, and admins) interact with the system.
Activities Executed: Listed the major features of the system, including book tracking, user authentication,
fine calculation, and report generation. Wrote use case scenarios demonstrating different functionalities,
such as "A student searching for a book," "A librarian issuing a book," and "Admin generating reports."
Reason for delay if any: N/A
Corrective Measure adopted: N/A
Remark: The feature list and use case scenarios were documented successfully, helping to illustrate the
system's capabilities.
Signature of the Guide: Marks: / 10
Week No: 5 Date: From 10/02/2025 To 15/02/2025
Activities Planned: Begin preparing test cases for initial modules, including user authentication and book
[Link] test case formats
Activities Executed: Created a test case template, including test ID, description, expected outcome, actual
outcome, and status (pass/fail). Wrote test cases for login/logout, book addition, and user role validation.
Reason for delay if any: N/A
Corrective Measure adopted: N/A
Remark: Initial test cases were written and shared with the team for review
Signature of the Guide: Marks: / 10
Week No: 6 Date: From 24/02/2025 To 1/03/2025
Activities Planned: Execute test cases for authentication and book management modules and document any
bugs found
Activities Executed: Performed unit testing on login, registration, and book management functions. Found
a few bugs in form validation and reported them to the development team. Ensured database entries were
correctly updated when books were issued or returned.
Reason for delay if any: N/A
Corrective Measure adopted: N/A
Remark: Several small bugs were identified and reported. The testing process is going smoothly.
Signature of the Guide: Marks: / 10
Week No: 7 Date: From 3/03/2025 To 08/03/2025
Activities Planned: Extend testing to book issuing, returning, and fine calculation modules. Ensure that
overdue fines are correctly applied.
Activities Executed: Created test cases for book transactions, verifying that only available books can be
issued. Tested the fine calculation module, checking whether fines were applied correctly based on return
dates. Found an issue where fines were not being updated in real-time and reported it to the backend team.
Reason for delay if any: N/A
Corrective Measure adopted: N/A
Remark: Testing of transactions and fine calculations is mostly successful, with a few minor issues
identified.
Signature of the Guide: Marks: / 10
Week No: 8 Date: From 10/03/2025 To 15/03/2025
Activities Planned: Document all test results and ensure that reported bugs are fixed correctly.
Activities Executed: Prepared a bug report detailing all identified issues, their severity, and the resolution
status. Verified that previously reported bugs were fixed and re-tested those modules. Documented
successful test cases as part of the final testing report.
Reason for delay if any: N/A
Corrective Measure adopted: N/A
Remark: Most critical bugs have been resolved. The system is becoming more stable.
Signature of the Guide: Marks: / 10
Week No: 9 Date: From 17/03/2025 To 22/03/2025
Activities Planned: Write a user manual explaining how to use the system. Document the hardware and
software requirements for running the Library Management System.
Activities Executed: Created a step-by-step user guide for login, searching books, issuing books, returning
books, and checking fines. Listed the required system specifications, including minimum and recommended
configurations for running the application.
Reason for delay if any: N/A
Corrective Measure adopted: N/A
Remark: The user manual is clear and detailed, making it easy for new users to understand the system.
Signature of the Guide: Marks: / 10
Week No: 10 Date: From 24/03/2025 To 29/03/2025
Activities Planned: Perform integration testing to check how well the different modules (frontend, backend,
and database) work together. Report any remaining issues.
Activities Executed: Conducted end-to-end testing, ensuring smooth interactions between the frontend and
backend. Found minor Ul glitches and reported them. Ensured that database updates were correctly
reflected in the UI.
Reason for delay if any: N/A
Corrective Measure adopted: N/A
Remark: Integration testing was mostly successful. Minor Ul bugs need to be addressed.
Signature of the Guide: Marks: / 10
Week No: 11 Date: From 1/04/2025 To 05/04/2025
Activities Planned: Compile all documentation, including the project report, test reports, and bug tracking
report.
Activities Executed: Organized all documents, formatted the final project report, and included test
summaries. Highlighted major test findings and how they were resolved.
Reason for delay if any: N/A
Corrective Measure adopted: N/A
Remark: The final documentation is well-structured and ready for submission.
Signature of the Guide: Marks: / 10
Week No: 12 Date: From 08/04/2025 To 12/04/2025
Activities Planned: Conduct a final review of all documents, assist in deployment, and prepare for the
project presentation
Activities Executed: Reviewed and corrected minor errors in the documentation. Assisted the team in
deploying the application for demonstration. Helped in preparing the presentation slides and conducted a
final dry run before the official presentation.
Reason for delay if any: N/A
Corrective Measure adopted: N/A
Remark: The project was successfully deployed, and the final presentation went well. The system is fully
functional and ready for use.
Signature of the Guide: Marks: / 10
