Teacher Evaluation Sheet

Name of Student: Sanket Kailas Patil

Enrolment No: 2200790164
Name of Program: Computer Technology Semester:- V
Course Title: Software Testing Code: -22518
Title of the Micro Project: Library Management System

Course Outcomes Achieved:-

• Apply various software testing methods.

• Prepare Test Cases for different types and levels of testing.
• Prepare Test Plan for an application.
• Identify bugs to create defect report of given application.
• Test Software for performance measures using automated testing tools.

Evaluation as per Suggested Rubric for Assessment of Micro-Project:

Sr.
Characteristic to be Poor Average Good Excellent
No.
assessed (Marks 1-3) (Marks 4-5) (Marks 6 - 8) (Marks 9-10)
(A) Process and Product Assesssment (Convert above total marks out of 6 marks)
1 Relevance to the Course
Literature Survey /
2
Information Collection
Completion of the Target as
3
per project proposal
Analysis of data and
4
Representation
5 Quality of Prototype / Model
6 Report Preparation
(B) Individual Presentation / Viva (Convert above total marks out of 4 marks)
8 Presentation
9 Viva
Micro – Project Evaluation Sheet:
Process Assessment Product Assessment
Part Project Part Individual Total
A – project Methodology B – Project Presentation / Marks 10
Name of Student Proposal (2 marks) Report / Working Viva (4 marks)
(2 marks) Model(2 marks)

Sanket Kailas Patil

Comments / Suggestions about team work / leadership / inter – personal communication :Good team
co-ordination and got many new things to learn

Any Other Comment :None

Name and designation of the faculty Member: Mr.G.M.Lodha Signature

1
 MAHARASHTRA STATE BOARD OF TECHNICAL
EDUCATION

SHRI H. H. J. B POLYTECHNIC,
CHANDWAD-423101 (Nashik)

MICRO PROJECT
Academic year 2023-24

TITLE OF PROJECT
Library Management System

Program: Computer Technology Program Code:CM

Course: Software Testing Course code: 22518

2
MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

Sr.No. Name of Student Roll No Enrollment No Seat No

1. Sanket Kailas Patil 39 2200790164

CERTIFICATE
This is to certify Sanket Kailas Patil of 5th Semester of Diploma in Computer Technology
of Institute, SHHJB POLYTECHNIC, CHANDWAD (Code: 0079) has completed the Micro-
Project satisfactorily in Subject Software Testing for the academic year 2024- 2025 as
prescribed in the curriculum.

Place: CHANDWAD

Date: / /2024

Subject Teacher Head of the Department Principal

(Mr.G.M.Lodha) (Mr.P.R.Sali) (Dr. V.A.Wankhede)

3
 INDEX

SR_NO. CONTENT PAGE NO.

Part A

1.0 Brief Introduction 5

2.0 Aim of Micro Project 5

3.0 Action Plan 5

4.0 Resources Required 5

Part B

1.0 Brief Description 6

2.0 Aim of Micro Project 6

3.0 Course Outcome Integrated 6

4.0 Actual Procedure Followed 6

5.0 Actual Resource Used 7

6.0 Outputs of the Micro-projects 7-21

7.0 Skill Developed 22

8.0 Applications of this Microproject 22

4
 PART A-Plan

Title of micro-project: Library Management System

1.0 Aim and Benefits of a Library Management System-

The aim of a Library Management System (LMS) is to streamline and enhance the
management of library operations, ensuring efficient handling of resources and user
interactions. By automating key processes such as cataloging, circulation, and user
account management, the LMS improves accuracy, reduces manual workload, and
enhances the overall user experience. The benefits of implementing an LMS are
substantial: it significantly boosts operational efficiency by automating routine tasks,
provides patrons with a user-friendly interface for easily accessing library resources, and
facilitates effective inventory management.

2.0 Course Outcomes Addressed-

a) Prepare Test Cases for different types and levels of testing.
b) Prepare Test Plan for an application.
c) Identify bugs to create defect report of given application.
d) Test Software for performance measures using automated testing tools.
e) Apply various software testing methods.

3.0 Proposed Methodology-

The Library Management System (LMS) involves a structured approach to ensure a comprehensive
and effective solution. It begins with requirement gathering, where input is collected from
stakeholders, including librarians, patrons, and administrative staff, to identify their needs and
challenges. Following this, a design phase outlines the system architecture, user interface, and
database structure, prioritizing usability and functionality. The development phase employs agile
methodologies, allowing for iterative progress and the incorporation of user feedback.

4.0 Action Plan:-

Planned Start Planned Finish
Sr no. Details of activity
Date Date
1. Finalization of topic 22-08-2024 22-08-2024
2. Preparation of Abstract 30-08-2024 30-08-2024
3. Collection of data
4. Preparation of concept
5. Seminar / Presentation
6. Submission of Micro Project
5.0 Resources Required:-
Sr.No Name of Resource/Material Specification Quantity Remarks
1. Computer (Desktop/Laptop) i3,RAM 8GB 1 Available
2. Microsoft office word 2010 1 Available
3. Books - -
4. Websites - -
5. Software Notepad, Web 1 Available
Browser

5
 PART B-Plan

Title of micro-project: Library Management System

1.0 Brief Description:-

A Library Management System (LMS) is a software solution designed to streamline the

management of library operations, including cataloging, circulation, and user account
management. It enables librarians to efficiently track inventory, process check-outs and returns,
and maintain accurate records of borrowed materials. With a user-friendly interface, patrons can
easily search for resources, access digital content, and receive notifications about due dates and
new arrivals. The LMS also generates insightful reports to aid in decision-making and resource
allocation.

2.0 Aims/Benefits of Micro Project:

The aim of a Library Management System (LMS) is to streamline and enhance the management
of library operations, ensuring efficient handling of resources and user interactions. By
automating key processes such as cataloging, circulation, and user account management, the
LMS improves accuracy, reduces manual workload, and enhances the overall user experience.
The benefits of implementing an LMS are substantial: it significantly boosts operational
efficiency by automating routine tasks, provides patrons with a user-friendly interface for easily
accessing library resources, and facilitates effective inventory management.

3.0 Course Outcomes Achieved:

a) Prepare Test Cases for different types and levels of testing.
b) Prepare Test Plan for an application.
c) Identify bugs to create defect report of given application.
d) Test Software for performance measures using automated testing tools.
e) Apply various software testing methods.

4.0 Actual Methodology/Procedure Followed:-

The methodology followed for developing a Library Management System (LMS) involves a
systematic approach that begins with requirement gathering, where stakeholders such as
librarians and patrons provide input on their needs and challenges. This information guides the
design phase, which includes creating a detailed system architecture, database schema, and user
interface wireframes, focusing on usability and accessibility. Development is carried out using
agile practices, allowing for iterative progress and continuous feedback.

5.0 Actual Resources Used:-

Sr.No Name of Resource/Material Specification Quantity Remarks
1. Computer i3,RAM 8GB 1 Available
(Desktop/Laptop)
2. Microsoft office word 2010 1 Available
3. Books - -
4. Websites - -
5. Software Notepad, Web 1 Available
Browser

6
6.0 Output Of The Microproject.

• Problem Statement:
The Hostel Management System is developed for automating the activities of hostel. The
software will be great relief to the employees. This software will help user in case of reporting,
registration and searching the information about residents and rooms. The aim of the Hostel
Management System is to carry out the activities of Hostel in an efficient way. It will take the
operations of Hostel to an upper level by providing faster access to data and allowing addition,
upgradation, modification, and deletion of data in a very systematic and reliable manner.

• Purpose:
The purpose of this project to make an automated system to carry out different operations of a
hostel.
The system will provide the case, comfort of use to the staff of the hostel by performing all
work on computer system rather than following a paper pen approach. This approach helps
improving the reliability of data maintained and provides a fast and efficient for users of the
software. Hostel Management System is a customize and user friendly software for hostel
which provide Hostel information, Hostel room information and Hostel accounts information.
It helps admin to manage Student record, staff record & generating report of students etc..

• Abstarct:

The Hostel Management System (HMS) is a software solution designed to optimize hostel
management by automating processes like room booking, billing, and maintenance tracking.
This intuitive platform enhances communication between administrators and residents,
streamlining operations and reducing manual errors. Key features include online booking,
payment processing, and resident management tools, all aimed at improving efficiency and
user experience. Ultimately, the HMS fosters a supportive living environment, promoting
collaboration and satisfaction for both staff and residents.

• Introduction:

The Hostel Management System (HMS) is designed to streamline operations for efficient
management of hostel facilities. By automating processes like room allocation, billing, and
maintenance requests, the HMS reduces administrative workload and errors, while enhancing
communication with residents. This project aims to create a user-friendly software solution that
improves operational efficiency and fosters a positive living environment, incorporating
features such as online booking, payment processing, and maintenance tracking. Ultimately,
the HMS addresses common challenges in hostel management, promoting collaboration and
satisfaction for all users.

• Unit Testing:

Unit testing for a Hostel Management System (HMS) involves systematically verifying the
functionality of individual components to ensure they operate correctly. Each module, such as

7
user authentication, room management, payment processing, maintenance requests, and
resident management, should have specific test cases. For instance, tests can validate user login
credentials, check room availability, process payments, and manage maintenance requests.
These tests help identify bugs early, improve code quality, and enhance overall system
reliability. By ensuring each unit works as intended, the HMS can provide a seamless
experience for both administrators and residents. Ultimately, effective unit testing contributes
to a robust and efficient hostel management solution.

• Integration Testing

Integration testing for the Hostel Management System (HMS) focuses on verifying the
interactions between different modules to ensure they work together seamlessly. Key areas of
testing include:

1. User Authentication and Room Booking: Test the process where a user logs in and
successfully books a room. Ensure that the booking is reflected in the room management
module.
2. Payment Processing and Room Allocation: Validate that once a payment is processed,
the room allocation is updated correctly and that the user receives a confirmation.
3. Maintenance Requests and Resident Management: Check that maintenance requests
created by residents are accurately logged and displayed in the management dashboard.
4. Reporting Module: Test that data from various modules (e.g., bookings, payments, and
maintenance) integrates correctly into the reporting tools for generating summaries and
analytics.
5. Notification System: Ensure that notifications about bookings, payments, and
maintenance requests are sent appropriately to users and admins.

• Alpha Testing for Hostel Management System

Alpha testing aims to verify the functionality of the Hostel Management System before beta
testing. Key areas include user registration, room booking, check-in/check-out, billing, and
admin functions. Testing will be conducted in a dedicated environment using manual and use
case testing. Key test cases will focus on critical functionalities and defect tracking will be
managed via a tool like JIRA. The testing phase will last 2 weeks, with exit criteria set at
resolving all critical defects and achieving over 90% test pass rate.

• Beta Testing for Hostel Management System

Beta testing involves real users testing the Hostel Management System in a production-like
environment to gather feedback and identify any remaining issues. Focus areas include user
experience, functionality, and performance across various devices. Participants will include a
select group of end-users who will report bugs and provide suggestions. The testing phase will
last approximately 3 weeks, and feedback will be collected through surveys and direct
communication. The goal is to ensure the system meets user expectations and is ready for full
deployment.

8
• White Box Testing Overview

White box testing involves examining the internal structures or workings of the Hostel
Management System, focusing on code quality and logic. Testers design test cases based on
knowledge of the code, algorithms, and control flow, ensuring comprehensive coverage of all
paths, conditions, and loops. This method helps identify hidden errors, security vulnerabilities,
and performance issues. It typically includes unit testing, integration testing, and code reviews.
The primary goal is to validate the logic and correctness of the implementation before moving
to higher levels of testing.

• Black Box Testing Overview

Black box testing focuses on evaluating the Hostel Management System's functionality
without any knowledge of the internal code or architecture. Testers assess the system based
on requirements and specifications, verifying input-output behavior, user interfaces, and
overall usability. This method is used to identify discrepancies between expected and actual
results, as well as usability issues. It includes functional testing, system testing, and
acceptance testing. The primary goal is to ensure that the software meets user needs and
performs as intended.

• Test Plan for Hostel Management System

1. Test Plan Identifier:

HPMS-TP-001

2. Introduction:
This test plan outlines the testing strategy, scope, objectives, resources, schedule, and
deliverables for the Hostel Management System. The system is designed to manage user
registrations, room bookings, check-ins/check-outs, billing, and various administrative
functions.

3. Objectives and Tasks:

• Validate user registration functionality.

• Test room availability checks and allocations.
• Ensure check-in/check-out processes work as intended.
• Verify billing calculations and payment processing.
• Check user login, profile updates, and booking history retrieval.
• Validate admin functionalities including user management and report generation.

9
 • Test the notification and feedback submission systems.
• Ensure error handling is accurate for invalid inputs.

4. Scope:

• In Scope:
o User registration and login processes.
o Room booking and management functionalities.
o Billing and payment processes.
o User profile management.
o Notifications and feedback mechanisms.
o Admin functionalities.
• Out of Scope:
o Integration with external payment gateways.
o Mobile application interface.
o Performance testing.

5. Resources:

• Test Team:
o Test Lead: [Name]
o Test Engineers: [Names]
• Tools:
o Test Management Tool: [e.g., JIRA, TestRail]
o Automation Tool (if applicable): [e.g., Selenium, Postman]
o Reporting Tool: [e.g., Excel, Custom Dashboard]

6. Schedule:

Task Duration Start Date End Date

Test Planning 1 week 15-07-24 22-07-24
Test Case Design 1 week 22-07-24 29-07-24
Test Execution 2 weeks 29-07-24 12-08-24
Bug Fixing & Retesting 1 week 12-08-24 19-08-24
Test Closure 3 days 19-08-24 13-09-24

7. Test Strategy:

• Manual Testing: Perform detailed manual testing for user interfaces and
functionalities.
• Automated Testing: Utilize automated testing for regression tests in future releases.

8. Deliverables:

10
 • Test Plan Document
• Test Case Document
• Test Execution Report
• Defect Report
• Test Closure Report

9.Test Cases For Hostel Management:

Test Descripti Input Expected Status

Case on Output Actual
ID Output
Name: John User Logged pass
Doe, Email: in
User
User john@exampl
TC001 registered
Registration e.com,
successfully.
Password:
abc123
Name: Jane User Fail
User Smith, Email: registered
Error: Email
Registration john@exampl successfully
TC002 already
(Email e.com,
exists.
Duplication) Password:
xyz456
Room Date: 2024-09- List of Pass
Available available
TC003 Availability 15, Number of
Guests: 2 rooms listed. rooms
Check
Room Type: Room Room Pass
Room
TC004 Single, Date: allocated Allocated
Allocation
2024-09-15 successfully.

Room Messgae: Pass

Room Type: Error: No
Allocation No Rooms
TC005 Double, Date: rooms
(No Available
2024-09-20 available.
Availability)

Check-in Room Status: Pass

User ID: 001, successful, Occupied
Check-in
TC006 Room ID: room status
Process
101 updated to
'Occupied'.

11
 Message: Pass
Check-in Room Not
Room ID: Error: Room
TC007 (Invalid Found
999 not found.
Room ID)
Check-out Error: User Fail
successful, not found.
Check-out
TC008 User ID: 001 room status
Process
updated to
'Available'.
User ID: 001, Message: Pass
Total Total
Billing Duration: 5
TC009 Amount: Amount:
Calculation days, Room
$250 $250
Rate: $50
User ID: 001, Payment Pass
Billing Payment Successful
Payment
TC010 (Payment processed
Method:
Method) successfully.
Credit Card
Email: Login Error: Invalid Fail
john@exampl successful, email or
TC011 User Login e.com, user password.
Password: dashboard
abc123 displayed.
Email:
john@exampl Message: Pass
User Login Error: Invalid
e.com, Invalid Email
TC012 (Invalid email or
Password: or Password
Credentials) password.
wrong
password
No booking Fail
View Booking history
TC013 Booking User ID: 001 history displayed,
History displayed. even though
bookings exist
Room ID: Maintenance Message: Pass
Room Request
101, Issue: request
TC014 Maintenance Submitted
Leak in submitted
Request
faucet successfully.
Action: Add User Added Pass
Admin User User, Name: User added
TC015
Management Admin User, successfully.
Role: Admin

12
 Report Type: Report Pass
Occupancy, Report generated
Report
TC016 Date Range: generated
Generation
2024-09-01 to successfully.
2024-09-30
Event: Notification Pass
Notification sent
Notification Check-in
TC017 sent
System Reminder,
successfully.
User ID: 001
Feedback pass
User ID: 001, Feedback Submitted
Feedback
TC018 Feedback: submitted
Submission
Great stay! successfully.

Password No email Fail

Password Email: received, no
reset email
TC019 Reset john@exampl error message
sent
Request e.com displayed.
successfully.
Password Message: Pass
Email: Email not
Reset Error: Email
TC020 nonexisting@ found
(Invalid not found.
example.com
Email)
Pass
User ID: 001, Room Message:
Room Type
TC021 New Room upgraded Room
Upgrade
Type: Deluxe successfully. Upgraded

Amenities Amenities Pass

View Listed
Room ID: listed (Wi-Fi,
TC022 Available
101 Breakfast,
Amenities
etc.).
Profile Pass
User ID: 001, Profile updated
User Profile
TC023 New Phone: updated Successfully
Update
123-456-7890 successfully.
Message: Pass
Booking Booking
Cancel Booking ID:
TC024 cancelled Canceled
Booking 005
successfully.

13
 • Defect Report: •

Defect Test Defect Seve Status Steps to Expected Actual Remarks

ID Case Description rity Reproduce Result Result
ID
DEF00 TC002 System High Open 1. Go to User Error: User Needs
1 allows Registration. Email register urgent
duplicate 2. Enter an already ed fix.
email existing email exists. successf
registration (john@example. ully
com). with the
3. Submit the duplicat
form. e email.
DEF002 TC008 Check-out fails High Open 1. Go to Check-out Check-out Error: Investigate
for a valid user page. successful, User not user
ID 2. Enter a valid room status found retrieval
User ID (e.g., 001). updated to logic..
3. Submit the 'Available'.
form..

DEF003 TC011 User login fails High Open 1. Go to Login Login Error: Investigate
with correct page. successful, Invalid authenticat
credentials. 2. Enter Email: user email or ion
john@example.co dashboard password process.
m, Password: displayed. .
abc123.
3. Click Login.
DEF004 TC013 Booking Mediu Open 1. Log in as User Booking No Check
history not m ID (e.g., 001). history booking history
displayed for 2. Navigate to displayed history retrieval
logged-in user. Booking History. correctly. displayed logic.
, even
though
bookings
exist.
DEF005 TC019 Password reset High Open 1. Go to Password Password No email Investigate
email not sent Reset. reset email received, email
for valid email. 2. Enter a sent no error sending
registered email. successfully message process.
3. Submit the displayed
request.

• Defect Report:

14
Defect details:
Defect ID: DEF001
Title: System allows duplicate email registration.
Project: Hostel Management System
Module: Login System
Severity: High
Status: Open
Detected By: John
Detected On: September 17,2024
Assigned To: Smith
Reported On: September 17,2024

Environment Details:
Browser: Chrome 92.0.4515.159
Operating System: Windows 10
Device: Laptop
Notes: This defect affects the user experience and might deter users and System allows
duplicate email registration this impacts the user login to system.

Approval and Acknowledgement

Test Manager: John doe
Development Lead: Cherry
Date of Approval: September 17,2024
Steps to Reproduce:
1. Go to User Registration.
2. Enter an existing email (john@example.com).
3. Submit the form
Expected Result : Error “ Email already exists”.
Actual Result: User registered successfully with the duplicate email.

15
16