Mico
Mico
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)
Comments / Suggestions about team work / leadership / inter – personal communication (if any)
1
MAHARASHTRA STATE BOARD OF TECHNICAL
EDUCATION
SHRI H. H. J. B POLYTECHNIC,
CHANDWAD-423101 (Nashik)
MICRO PROJECT
Academic year 2024-25
TITLE OF PROJECT
2
MAHARASHTRA STATE BOARD OF TECHNICALEDUCATION
CERTIFICATE
This is to certify 1) Gauri Vijay Bagul
of 5thSemester of Diploma in Computer Technologyof Institute, SHHJB POLYTECHNIC,
CHANDWAD (Code: 0079) has completed the Micro-Project satisfactorily in Subject
Software Testing (22518)for the academic year 2024- 2025as prescribed in the curriculum.
Place: CHANDWAD
Date: / /2024
INDEX
3
Part A
1. Brief Introduction 6
3. Action Plan 5
Part B
1. Brief Description 6
6 Introduction 7
7 Abstract 7
9 Test Cases 9
11 Skill Developed 12
PART A-Plan
4
1.0Aim/Benefits of the Micro-Project-The aim of a Time Table Management System
(TTMS) project is to automate and streamline the scheduling process for educational
institutions or organizations, ensuring efficiency, accuracy, and user-friendliness. By
minimizing manual effort and quickly identifying conflicts, the system facilitates the
creation of conflict-free timetables that are easily accessible to students, teachers, and
administrators. Key benefits include enhanced organizational efficiency, real-time
updates, centralized data management, and improved communication. Additionally, the
TTMS optimizes resource allocation and provides valuable analytics for decision-making,
ultimately leading to increased productivity and satisfaction within the institution.
PART B-Plan
5
1.0 Brief Description: A Time Table Management System (TTMS) is designed to
automate and optimize the scheduling process within educational institutions. It streamlines
the creation and management of class schedules, ensuring that timetables are conflict-free and
easily accessible for students, teachers, and administrators. The system allows for real-time
updates, centralized data management, and efficient resource allocation, significantly
reducing the manual effort involved in scheduling. By enhancing communication and
providing valuable insights through reporting, a TTMS improves overall organizational
efficiency and user satisfaction, making it an essential tool for modern educational
environments.
2.0 Aims/Benefits of Micro Project: The aim of a Time Table Management System
(TTMS) project is to automate and streamline the scheduling process for educational
institutions or organizations, ensuring efficiency, accuracy, and user-friendliness. By
minimizing manual effort and quickly identifying conflicts, the system facilitates the
creation of conflict-free timetables that are easily accessible to students, teachers, and
administrators. Key benefits include enhanced organizational efficiency, real-time
updates, centralized data management, and improved communication. Additionally, the
TTMS optimizes resource allocation and provides valuable analytics for decision-making,
ultimately leading to increased productivity and satisfaction within the institution
6
1) INTRODUCTION:
This defines the project being developed along with the description of existing systems of
similar type. Here the need for the new system,its future prospects and currently available
systems of similar types have been defined which therefore presents a brief overview of the
system being developed in termsof its differences with the previously available systems and
the newly embedded functionalities.
2) ABSTRACT:
The Time Table Management System (TTMS) project is designed to automate and optimize
the scheduling of classes, resources, and personnel in educational institutions. The system
addresses the challenges of manual timetable creation, which often leads to conflicts,
inefficiencies, and administrative burdens. By employing a user-friendly interface and robust
algorithms, the TTMS enables administrators to generate conflict-free timetables that
accommodate the needs of students and faculty. The project encompasses requirements
gathering, system design, development, testing, deployment, and user training to ensure
seamless integration into existing workflows. With real-time updates and easy accessibility,
the TTMS enhances communication and resource allocation, ultimately improving the overall
educational experience for all stakeholders involved.
2) TEST PLAN:
Testing Methodology:
Timetable management software helps design timetables and mark attendance for teachers
and students. It helps to regulate proper schedules and allocate faculty according to their
availability by outlining the classes, sections, and other details fed into the system.
Unit Testinig
Unit testing for a timetable management system involves testing individual components to
ensure they function correctly. This includes verifying the creation of timetable entries,
detecting scheduling conflicts, and managing user roles effectively. Each unit test checks
specific functionalities, such as confirming that valid entries are saved and that conflicts are
identified when overlapping classes are added. Testing frameworks like JUnit for Java or
unittest for Python can be employed to automate these tests. By conducting thorough unit
testing, developers can identify and fix issues early, ensuring a reliable and efficient system
that meets user requirements.
System Testing
System testing for a timetable management system validates the entire application to ensure
it meets requirements and performs as expected. This includes functional testing for features
like schedule creation and conflict resolution, performance testing under load, usability
testing for user experience, and security testing to protect user data. Comprehensive system
7
testing helps identify integration issues and bugs before deployment, ensuring a reliable and
efficient timetable management solution.
Performance Testing
Performance testing for a timetable management system evaluates how the application
behaves under various load conditions to ensure it can handle the expected number of users
and data volume. This includes testing response times for key functionalities, such as creating
and updating schedules, and assessing system stability during peak usage. Load testing
simulates multiple users accessing the system simultaneously to identify any performance
bottlenecks, while stress testing determines the system's breaking point. By conducting
thorough performance testing, the team can ensure that the timetable management system
remains responsive, reliable, and scalable, ultimately enhancing the user experience.
Security Testing
Security testing for a timetable management system focuses on identifying vulnerabilities that
could be exploited by unauthorized users. This involves evaluating user authentication
processes, ensuring proper access controls are in place, and testing for potential security flaws
such as SQL injection or cross-site scripting. Additionally, security testing verifies that
sensitive data, like user information and timetable details, is adequately protected through
encryption and secure storage practices. By conducting thorough security assessments, the
team ensures that the system is resilient against threats, safeguarding user data and
maintaining trust in the application's integrity.
Alpha testing
Alpha Testing is conducted internally by the development team in a controlled environment
to identify bugs and usability issues before releasing the software to external users. This
phase focuses on refining features and ensuring the system functions as intended.
Beta testing
Beta testing on the other hand, involves releasing the application to a limited number of end-
users outside the organization. This phase gathers real-world feedback, allowing users to test
the system in various scenarios and report any issues. Together, these testing phases help
ensure the timetable management system is robust, user-friendly, and ready for a wider
audience.
Object-Oriented Testing
object-oriented testing for a timetable management system checks how well different objects,
like schedules, users, and courses, work together. It starts with unit testing, which verifies that
each object's methods and properties function correctly.
8
2) TEST CASES :
Test Case ID Prerequisites Input Data Expected Actual Result Remark
Output data
TC-1 User logged in Create new Timetable Timetable passed
as admin timetable for created created
Class A, successfully
Subject X
TC-2 Timetable Modify Timetable Timetable passed
exists timetable for updated updated
Class A to add successfully
Subject Y
TC-3 User logged in Create Error Error failed
as admin timetable with message: displayed
overlapping "Schedule
classes conflict
detected"
TC-4 User logged in View Display Class Timetable passed
as student timetable for A timetable displayed
Class A
TC-9 User logged in Add a new Subject added Subject added passed
as admin subject not successfully
already in the
system
9
Test Summary Plan for Time Table Management System
1. Objective
The objective of the testing phase is to ensure that the Time Table Management System (TTMS)
functions correctly, meets all requirements, and provides a user-friendly experience. This involves
validating all functionalities, identifying bugs, and ensuring overall system reliability and
performance.
2. Scope of Testing
- Functional Testing: Verify that all system functionalities operate as intended, including timetable
creation, modification, viewing, and deletion.
- Usability Testing: Assess the user interface for ease of use and accessibility for different user roles
(admin, student, teacher).
- Performance Testing: Evaluate system performance under various loads, ensuring it can handle
multiple users accessing timetables simultaneously.
- Security Testing: Test the system for vulnerabilities, ensuring that user data is protected and access
controls are effective.
3.Testing Methodology:
- Manual Testing: Conduct exploratory testing to assess user experience and functionality.
- Automated Testing: Utilize automated scripts for regression testing and repetitive tasks to improve
efficiency.
4. Test Environment:
- Hardware: Standardized PCs/laptops for testing.
- Software: TTMS application, web browsers, database management system.
- Network: Reliable internet connection for online functionalities.
5. Testing Tools
- Bug Tracking: JIRA or Bugzilla for tracking issues.
- Test Management: TestRail or similar tools for managing test cases and documentation.
- Automation Tools: Selenium or JUnit for automated tests.
6.Test Schedule
- Planning Phase: 1 week for planning and preparation.
- Execution Phase: 2 weeks for functional and usability testing.
- Performance Testing: 1 week following functional testing.
- Bug Fixing: Ongoing during execution phase with a dedicated week for final fixes.
7. Deliverables
- Test Cases Document: Comprehensive list of all test cases executed.
- Test Reports: Summary of testing results, including pass/fail rates.
- Defect Log: List of identified bugs and their status.
- Final Test Summary Report: Overview of the testing process, results, and recommendations.
8. Risk Assessment
- Potential delays in bug fixing due to complexity.
- User acceptance challenges if the interface is not intuitive.
- Performance issues under high load if not adequately tested.
10
DEFECT REPORT
Defect id TTMS-36
Description The system fails to save changes made to the timetable. Upon
clicking the "Save" button after editing, users encounter an error
message: "Unable to save changes." This defect prevents users from
updating their schedules, impacting operational efficiency.
Expected Result The system should successfully save the changes made to the
timetable, and a confirmation message ("Changes saved
successfully") should appear.
Actual Result After clicking "Save," the following error message is displayed:
"Unable to save changes." No changes are saved, and the user is
returned to the editing screen.
Severity Major
Priority High
Assigned to Mr.G.M.Lodha
11
DECISION TABLE
12
design timetables and mark attendance for teachers and students.
regulate proper schedules and allocate faculty according to their
availability by outlining the classes, sections, and other details fed into the
system.
8.0 Conclusion: In conclusion, the timetable management system project highlights the
importance of effective software testing. It ensures schedules are accurate, user-friendly, and
free from conflicts. Testing validates functionality, improves user experience, and maintains
data integrity. By implementing robust testing practices, the system becomes reliable and
efficient for all users, ultimately enhancing the overall management of timetables.
13