Documente Academic
Documente Profesional
Documente Cultură
MANAGEMENT SYSTEM
PROBLEM STATEMENT
◊ CSE -- 132
◊ ECE -- 132
◊ IT -- 66
◊ EEE – 66
1st 7 5
2nd 7 5
3rd 6 4
4th 6 4
5th 6 4
6th 6 5
7th 4 4
8th 3 4
75% is the Compulsory attendance for a student else a short attendance report is
generated.
So a list of students along with their daily attendance for class, subjects offered and
faculty members is to be maintained.
The faculty members of respective subjects provide attendance details to the data
entry operator who all details into the system database. This process is carried out
daily by the faculty members and the data entry operator. Attendance is updated on
all weekdays except Saturdays and Sundays. Once the data entry operator has
updated the attendance, he/she would not be allowed to change the attendance
again.
The students and faculty members can also login the system to view and generate
reports for student information, subjects opted by them and their attendance in any
subject.
The system will generate monthly attendance reports and the reports should be
printable.
SOFTWARE
REQUIREMENT
SPECIFICATIONS
(SRS)
TABLE OF CONTENTS
1. INTRODUCTION
1.1 Purpose
1.2 Scope
1.4 References
1.5 Overview
2. OVERALL DESCRIPTION
2.1 Product Perspective
2.1.7 Operations
2.4 Constraints
3. SPECIFIC REQUIREMENTS
3.1 External Interface Requirements
Login Screen:
Validity Checks
Sequencing Information
Validity Checks
Sequencing Information
Validity Checks
Sequencing Information
Validity Checks
Sequencing Information
Validity Checks
Sequencing Information
Validity Checks
Sequencing Information
3.5.1 Security
3.5.2 Maintainability
3.5.3 Portability
1. INTRODUCTION
The student attendance management system is a software developed for daily
attendance of students in colleges. It facilitates the access of attendance information
of a particular student belonging to a particular class. The attendance information is
provided to the DEO by the faculty teacher for a particular class and subject. The
software system also helps in evaluating the examination eligibility criteria for a
student in the sense that only those students with attendance above 75% are
allowed to be eligible for the semester exams.
1.1 PURPOSE
This specification document describes the capabilities that will be provided by the
software application “Student Attendance Management System”. The purpose of
developing this attendance management system is to computerize the traditional
way of taking attendance in classes and also manage student and teachers’
information along with their classes and subjects.
Another purpose for developing the software is to generate the reports automatically
whenever required-in between the semesters or after the semester.
1.2 SCOPE
The scope of the project is the system, on which the software is installed, i.e., the
project is developed as a desktop application, and it will work for a particular college.
But later on, the project can be modified to operate it online.
INFO: Information
1.4 REFERENCES
1.5 OVERVIEW
The rest of the SRS document describes the various system requirements,
interfaces, features and functionalities in detail.
2. OVERALL DESCRIPTION
None.
• STUDENT INFO SCREEN: for capturing and displaying the details of all
students enrolled for the course in different years, their name, enrollment
number, branch, semester and courses opted by them.
• FACULTY INFO SCREEN: for capturing and displaying the details of all
faculty members-their name, department, qualification, experience, salary,
teaching subject/s and class/es.
Screen resolution of at least 800*600 required for proper and complete viewing of
screen and support for printer is also required for printing of reports.
None.
At least 64 MB and 2 GB space on hard disk will be required for running the
application successfully.
2.1.7 OPERATIONS
The Administrator at client site will be responsible for manually deleting old/non
required data. Database backup and recovery will also be handled by administrator.
The terminals at client site will have to support hardware and software interfaces
specified in the above sections.
The system will allow access to only authorized users with specific roles
(administrator, DEO, student, faculty member). Depending upon the role, he/she will
be able to access only specific modules of the system.
• DEO will be able to add/modify/delete info about different subjects that are
offered and opted by students in a particular semester and branch.
2.4 CONSTRAINTS
Since DBMS is MS Access 2000, which is not very powerful, it will not be able to
store a very huge number of records.
Due to limited features of DBMS being used, database auditing and performance
tuning features will not be provided.
Not required.
3. SPECIFIC REQUIREMENTS
LOGIN SCREEN:
This is the first screen displayed. It will allow users to access different screens based
on their role. Various fields will be: Username, Password, Role (Administrator,
Student, Faculty member, DEO).
This screen will be accessible to user with any role. It will allow the user to enter the
Batch Year for which the user wants to access student info.
This screen will be accessible to user with role DEO. It will allow the user to
add/modify/delete any info about new/existing student/s. Various fields on the screen
will be: Student name, enrollment no., branch, address, phone no., etc...
This screen will be accessible to user with any role. It will allow the user to enter the
semester number for which user wants to access the subject info.
This screen will be accessible to user with any role. It will allow the user to enter the
department name for which user wants to access the faculty member info.
This screen will be accessible to user with role DEO. It will allow the user to
add/modify/delete any info about new/existing faculty member/s. Various fields on
the screen will be: Faculty member name, department, designation, qualification,
experience, salary, teaching subject, etc...
This screen will be accessible to user with any role. It will allow the user to enter the
Batch Year for which the user wants to access the individual or list of students’
attendance info.
This screen will be accessible to user with role DEO. It will allow the user to
add/modify/delete any info about new/existing student attendance. Various fields on
the screen will be: Student info, Subject info, Daily attendance, etc...
This screen will be accessible to user with any role. It will allow the user to enter the
Batch Year for which the user wants to view and print student attendance info.
None
VALIDITY CHECKS
• Only user with role Administrator will be authorized to access the User
Accounts Maintenance module.
SEQUENCING INFORMATION
User account for a particular user has to be created in order for the system to be
accessible to that user. At system startup, only a default user account for
‘Administrator’ would be present in the system.
If any of the above validations/sequencing flow does not hold true, appropriate error
messages will be prompted to the user for doing the needful.
The system will maintain info. about various students enrolled in the course in
different years. The following info. will be maintained for each student:
Student name, enrollment no., enrollment year, branch, address, phone no.
VALIDITY CHECKS
• Only user with role DEO will be authorized to access the Student Info
Maintenance module.
SEQUENCING INFORMATION
Student info for a particular student will have to be entered in the system before any
attendance info can be entered for that student.
If any of the above validations/sequencing flow does not hold true, appropriate error
messages will be prompted to the user for doing the needful.
The system will maintain info. about various subjects offered to the students of
particular semester and branch of the course. The following info. will be maintained
for each subject:
Subject name, code, credits, type (theory or practical), branch, and semester.
VALIDITY CHECKS
• Only user with role DEO will be authorized to access the Subject Info
Maintenance module.
SEQUENCING INFORMATION
Subject info for a particular branch will have to be entered in the system before any
student attendance for that semester can be entered.
ERROR HANDLING/RESPONSE TO ABNORMAL SITUATIONS
If any of the above validations/sequencing flow does not hold true, appropriate error
messages will be prompted to the user for doing the needful.
The system will maintain info about various faculty members belonging to different
departments teaching the course. The following info will be maintained for each
faculty member:
VALIDITY CHECKS
• Only user with role DEO will be authorized to access the Faculty Member Info
Maintenance module.
SEQUENCING INFORMATION
Faculty member info for a particular branch can be entered in the system only after
the subject info and student info have been entered.
If any of the above validations/sequencing flow does not hold true, appropriate error
messages will be prompted to the user for doing the needful.
The system will maintain info. about various students enrolled in the course along
with their subject choice and their daily attendance in that particular subject. The
following info will be maintained for each student:
VALIDITY CHECKS
• Only user with role DEO will be authorized to access the Student Attendance
Info Maintenance module.
• Attendance once written cannot be updated and if less than 75%, then
student will not be eligible for semester-end exams.
SEQUENCING INFORMATION
Student attendance info for a particular branch can be entered in the system only
after the subject info and student info have been entered.
If any of the above validations/sequencing flow does not hold true, appropriate error
messages will be prompted to the user for doing the needful.
The attendance info reports will be generated for every student enrolled in the
program either for an individual or the whole list of students of a particular batch
year. This report will be generated in the following format:
Attendance Table:
VALIDITY CHECKS
User with any role DEO is authorized to access the Student Attendance Report
Generation module.
SEQUENCING INFORMATION
Student attendance info reports for a particular student can be generated by the
system only after the whole student and their subjects info have been entered.
If any of the above validations/sequencing flow does not hold true, appropriate error
messages will be prompted to the user for doing the needful.
None.
None.
3.5.1 SECURITY
The application will be password protected. Users will have access to enter correct
username, password and their role in order to access the application.
3.5.2 MAINTAINABILITY
3.5.3 PORTABILITY
The application will be easily portable on any windows-based system that has MS
Access 2000 installed.
None.
USE-CASE DIAGRAM
Student
DEO Maintain Student Information
Log in
Administrator
Faculty Member
Generate reports Maintain Faculty Information
° Login
USER DATABASE
Enter user id
and password invalid
valid
Update details
Prompt to edit
account
DE O D A TA B A S E
G et s uc c es s /error m es s age
for info. updation
° View and Generate Reports
USER DATABASE
User can be
a Student or Teacher
4: Check login
Edit
: Administrator : Database
5: Giving details
6: Entering details
7: Updating details
Accepting
: Data Entry : Database
Details
Operator
1: Getting Details
2: Accepting Details
4: Storing Data
5: Update Details
User can be
a Student or Teacher
Student Details
: User Display Screen
: Database
User can be
a Student or Teacher
Employment details
: User : Database
display screen
1: Generate report
2: Getting attendance details
3: Searching for details
4: Generating reports
5: Display report
6: Printing report
COLLABORATION
DIAGRAMS
° Login
Login
4: Check login
10: Update details
3: Get login details
Login Login Details/Change
Checker password
° User Account Maintenance
2: Getting details
6: Entering details
: Database
° Accepting Details
5: Update Details
Accepting
Details
° View Subject Details
3: Searching For Semester Details
8: Searching For Branch Detail
13: Searching for Subject Details
Student Details
Display Screen
: Database
° View Faculty Details
: Database
° Generating Reports
4: Generating reports 3: Searching for details
: Database
6: Printing report
5: Display report
Printing
1: Generate report reports
Display Attendance
Report
: Administrator
CLASS DIAGRAM
STUDENT INFO
LOGIN SUBJECT INFO
NAME
USER ID SUBJECT NAME
ENROLLMENT NO.
PASSWORD CREDITS
ENROLLMENT YEAR
CODE
SEMESTER
LOGINCHECKER() SEMESTER
BRANCH
CHANGEPASSWORD() BRANCH
ADDRESS
ADDUSER() PHONE NO.
DELETEUSER() ADD()
MODIFY()
ADD()
DELETE()
MODIFY()
DELETE()
FACULTY MEMBER
INFO
NAME
DEPARTMENT
DESIGNATION REPORT GENERATION
QUALIFICATION
EXPERIENCE GENERATEREPORT()
SALARY
ATTENDANCE INFO
ADD() DAILY ATTENDANCE
MODIFY()
DELETE() ADD()
MODIFY()
STATE TRANSITION
DIAGRAM
Verification
System Login
Login Use
checker Screen
Enter login id and password Access granted
Logging out
Report
Generation
Logging out
System Exit
DATA FLOW DIAGRAMS
° LEVEL-0
° LEVEL-1
E-R DIAGRAM