SAMSReport
SAMSReport
SUBMITTED TO
KBC, North Maharashtra University,
Jalgaon.
In the Partial Fulfilment of the Requirements of the Degree
BCA
SUBMITTED BY:
Mr. abc xyz.
Email id: [email protected]
This is to certify that Your Name Here a student of BCA from KCES’SInstitute of
Management and Research, Jalgaon has completed the project work entitled
“Student Attendance Management System” He has submitted satisfactory
project report in partial fulfillment of the requirement for the degree of IMCA
during academic year 2024-2025.
It is the original work and sincerely completed. I am fully satisfied with his
performance.
SR. Page
NO.
Particulars No.
1 Introduction
1.1 Background
1.2 Objective of the Project
1.3 Scope of the Project
1.4 Goals of Proposed System
1.5 Project Requirements
1.6 Technologies Used
1.7 Constraint’s
2 Feasibility Study
2.1 Technical Feasibility
2.2 Economic Feasibility
2.3 Schedule Feasibility
3 System Analysis
3.1 Working of Present System
3.2 Proposed System
3.3 E-R Diagram
3.4 Process Modeling
3.5 Use Case Model
4 System Design
4.1 Testing
4.2 Database Table
5 Screenshots
6 Conclusion
7 Bibliography / References
1. Introduction
Admin Panel: SAMS will feature an admin panel that enables administrators to
manage user accounts, add faculty members, define subjects and timetables,
and oversee overall system functionality.
Reporting: The system will provide robust reporting capabilities, allowing users
to generate attendance reports for specific date ranges, classes, or students,
thus facilitating data-driven decision-making.
The goals of the Student Attendance Management System (SAMS) are aligned
with the overarching objective of modernizing attendance tracking processes
within educational institutions and fostering a digital ecosystem that enhances
efficiency, transparency, and accountability. The project aims to achieve the
following goals:
Hardware Requirements:
Server:
Minimum: Dual-core processor
Recommended: Quad-core processor or higher
RAM: Minimum 4GB (8GB recommended)
Storage: SSD recommended for better performance
Client Devices:
Desktop or laptop computers for administrators and faculty members
Mobile devices (optional) for accessing the system remotely
Network Infrastructure:
Stable internet connection for accessing the system
Local area network (LAN) or wide area network (WAN) for internal connectivity
Software Requirements:
Operating System:
Server: Linux (e.g., Ubuntu Server, CentOS) or Windows Server
Client: Windows, macOS, or Linux
Browser Compatibility:
Ensure compatibility with modern web browsers such as Google Chrome,
Mozilla Firefox, Safari, and Microsoft Edge.
Programming Languages:
PHP: Server-side scripting language for backend development.
JavaScript: Client-side scripting language for interactive features.
HTML: Markup language for creating web pages.
CSS: Style sheet language for styling web pages.
Database Management System (DBMS):
Web Server:
Apache HTTP Server or Nginx: HTTP servers for hosting the web application.
Development Tools:
Git: Version control system for tracking changes in the codebase and
collaboration.
Operating System:
Linux (e.g., Ubuntu, CentOS) or Windows Server for hosting the application
server.
Client devices may use Windows, macOS, or Linux operating systems.
1.7 Constraints Summary
User Acceptance: Ensuring user acceptance and adoption of the system among
faculty members and administrators may require comprehensive training and
support mechanisms.
2. Feasibility Study
The feasibility study for the Student Attendance Management System (SAMS)
assesses the project's viability and potential for success from various
perspectives.
Use Case Modeling: Developing use case diagrams and scenarios to illustrate
the interactions between users and the system, helping to identify essential
functionalities and user roles.
Risk Assessment: Identifying potential risks and challenges that may affect the
success of the project, such as technical constraints, resource limitations, and
security vulnerabilities.
At the beginning of each class, faculty members call out students' names, and
students respond with their attendance status. Faculty members then record
this information on paper sheets, which are later compiled and stored for
administrative purposes. Attendance records may be prone to errors, such as
illegible handwriting or incorrect entries, leading to inaccuracies and
inconsistencies in attendance tracking.
Use Case Diagrams: Use case diagrams illustrate the interactions between
users (administrators, faculty members) and the system, identifying various
use cases such as adding faculty, managing classes, and marking attendance.
Activity Diagrams: Activity diagrams depict the flow of activities within SAMS,
including steps such as login authentication, adding faculty members, selecting
classes, marking attendance, and generating reports.
State Diagrams: State diagrams represent the different states that entities
within the system can transition through, such as the states of attendance
(present, absent, late) or the states of user authentication (logged in, logged
out).
Start
Login
Check Id and
Password NO
Yes
Check Login
Type
Admin
A
Flow Chart Diagram for teacher
User Interface Design: The user interface of SAMS will prioritize usability,
accessibility, and intuitiveness. Modern web design principles and frameworks
like Bootstrap may be utilized to create a responsive and visually appealing
interface.
Blackbox Testing
Whitebox Testing
Attendance Table
Class Table
ClassArm Table
SessionTerm Table
Student Table
The completion of this project would not have been possible without the
assistance of the following.
www.stackoverflow.com
www.php.net
www.javaTpoint.com
www.getbootstrap.com
www.google.com