Scribd
Upload
5 views

SOFT

Uploaded by

rej2559
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
5 views

SOFT

Uploaded by

rej2559
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

REQUIREMENT GATHERING:

The first step in developing an effective attendance management system is


comprehensive requirement gathering. This includes identifying both functional
and non-functional requirements. Functional requirements entail the system's
features and capabilities, such as face detection, recognition, and database
management. Non-functional requirements cover aspects like system performance,
security, and scalability.

Functional Requirements:
1. Face Detection: The system should accurately detect frontal faces in a classroom
environment.
2. Face Recognition: It must have the ability to recognize stored student faces with
an accuracy level of at least 30%.
3. GUI Display: The system should display the number of students present in real-
time on a graphical interface.
4. Database Matching: The system must match detected faces to those stored in the
database with a minimum accuracy of 30%.
5. Processing Time: The system should process an image within 10 minutes to
achieve the objective of recognition by the end of a lecture.

Non-functional Requirements:
1. Accuracy: The overall system accuracy, including face detection and
recognition, should meet or exceed industry standards.
2. Real-time Display: The graphical interface should reflect attendance changes in
real-time.
3. Processing Time Efficiency: The system must process images within a specified
time frame for practical application during lectures.
4. Security: The system should ensure the security and privacy of student facial
data stored in the database.
PROCESS MODEL SELECTION AND JUSTIFICATION:
Choosing an appropriate process model is crucial for project success. The selected
model should align with the project's unique requirements and constraints. For this
attendance management system, the Incremental Model is chosen and justified.

Justification:
1. Iterative Development: The Incremental Model supports iterative development,
allowing continuous improvement and adaptation to changing requirements.
2. Client Feedback: As the project involves complex functionalities like face
recognition, incremental development allows incorporating client feedback at
various stages.
3. Risk Management: Incremental development aids in risk management, as each
increment is a deliverable that can be tested and validated.
PROJECT SCHEDULING – TIMELINE CHARTS:
Project scheduling involves creating timeline charts to outline the tasks,
milestones, and deadlines. The Gantt chart below illustrates a tentative timeline for
the attendance management system project:
WORK BREAKDOWN STRUCTURE (WBS) (MODULE SPLIT-UP):
The Work Breakdown Structure (WBS) provides a hierarchical decomposition of
the project into phases, deliverables, and work packages. The WBS for the
attendance management system is structured as follows:

Delivery Based WBS:


Phase Based WBS:
USE CASE DIAGRAM
SEQUENCE DIAGRAM
Level 0:
1. Unit Testing:
• Objective: Verify the functionality of individual components or modules in the
system.
Test Cases:
➢ Face Detection Module:
• Verify the accuracy of the Histogram of Oriented Gradient (HOG) technique
in detecting frontal faces.
• Test with various face orientations, lighting conditions, and background
scenarios.
• Ensure the face detection module can accurately locate and extract facial
features.
➢ Face Recognition Module:
• Verify the accuracy of the deep learning-based face recognition algorithm.
• Test the module with a diverse set of student faces, including different
expressions, poses, and lighting conditions.
• Ensure the module can correctly match detected faces with the faces stored
in the database.
➢ Database Interaction:
• Verify the correct storage and retrieval of attendance records in the
PostgreSQL database.
• Test the database queries for adding, updating, and querying attendance data.
• Ensure the database operations are secure and efficient.
2. Regression Testing:
• Objective: Ensure that new changes or updates to the system do not break
existing functionalities.
Test Cases:
➢ Facial Recognition Accuracy:
• Perform regression testing on the face recognition module after any updates
or changes.
• Verify that the recognition accuracy remains within the 30% target.
• Test with a representative set of student faces, including those used in the
initial development.
➢ GUI Functionality:
• Verify that the graphical user interface (GUI) continues to display the
number of present students accurately after any UI updates.
• Test the responsiveness and usability of the GUI across different screen sizes
and resolutions.
• Ensure that the real-time attendance display remains functional.
➢ Database Integrity:
• Perform regression testing on the database operations to ensure data integrity
is maintained.
• Verify that the attendance records are correctly stored and retrieved after any
database schema or query changes.
• Test edge cases, such as handling database failures or connection issues.
3. Integration Testing:
• Objective: Verify the seamless integration and interaction between the different
components of the system.
Test Cases:
➢ End-to-End Attendance Tracking:
• Test the complete attendance tracking workflow, from image capture to
attendance display.
• Verify that the face detection, recognition, and database update processes
work together as expected.
• Ensure the end-to-end process meets the 10•minute processing time
requirement.
➢ Camera Integration:
• Test the integration of the mobile phone camera with the face detection and
recognition modules.
• Verify that the camera can capture images with sufficient quality for accurate
face detection and recognition.
• Ensure the camera integration is stable and reliable.
➢ GUI and Backend Integration:
• Verify the integration between the graphical user interface and the backend
components (face recognition, database).
• Test the real-time display of attendance data on the GUI.
• Ensure the GUI provides a seamless user experience.
4. Performance Testing:
• Objective: Evaluate the system's performance under various load conditions
and stress scenarios.
Test Cases:
➢ Scalability:
• Test the system's ability to handle a growing number of student records in
the database.
• Measure the response times and resource utilization as the database size
increases.
• Ensure the system can maintain acceptable performance with a large student
population.
➢ Concurrent Access:
• Simulate multiple users (e.g., instructors) accessing the system
simultaneously.
• Verify the system's ability to handle concurrent attendance marking and data
retrieval without performance degradation.
• Test the system's resilience to handle peak usage during high-traffic lecture
times.
➢ Image Processing Throughput:
• Measure the system's ability to process images within the specified
10•minute time frame.
• Test the processing time with various image resolutions and student
population sizes.
• Ensure the system can meet the target of processing 5 names per hour.

You might also like