INTRODUCTION
CHAPTER-1
INTRODUCTION
1.1
Introduction
AIMS is a Windows based desktop application which will be used for efficient
management of Institute. This application has modular architecture. At the core of the
system centralized database will be used for access and storage. At the outset Attendance
System [1] each staff member and student will be able to mark their attendance through
thumb scanning. The device (Finger Print Capture) will captures the finger print and mark
each persons attendance in few seconds. Moreover in SMS Alerts API for SMS [2] will be
used to send messages for different purposes like SMS Notifications for meeting, holidays,
fee alerts and greeting messages on a single click. In student and employee information
administrator will have the provision to insert, view, and update and delete information of
the students and employee. In Institute information detail about the Institute like contact
details, number of students and employees and also information about the departments is
provided. System will also provide the facilities of generating different reports.
1.2
School Information Management System (SIMS) was the first IMS for schools. It
was initially developed by Philip Neal, a teacher at Lea Manor High School from 1982 to
1983. Bedfordshire County Council (Lea Manor's local education authority) then further
developed the product, which began being used by other schools in 1984.In 1988, a
commercial company, SIMS Ltd, was founded to further develop SIMS. SIMS Ltd was
acquired by Capita Group in 1994. [3]
Institute Management System (IMS) consists of tasks such as registering students,
attendance record keep, producing report cards and producing different reports for teachers
and parents.
1.3
Proposed System
Proposed system will have following modules: Attendance System, SMS Alerts,
Institute Information, Student Information, Employee Information and Reports. At the core
of the system will be centralized database for storage. So sub systems will be able to access
the data.
At the outset Attendance module, each staff member and student will be able to
mark their attendance through thumb scanning using USB finger print capture device.
Moreover in SMS Alert module API for SMS or GSM modem will be used to send
messages for different purposes like notifications for: meeting (teachers/parents),
holiday, fee alerts, and greeting messages etc.
Student information will store bio data, guardian and class information while
registering a new student. We can also search students and their results. Employee
information will store bio data, education, and experience information while registering a
new employee and also can search employees.
In Institute information detail about the Institute like contact details, number of
students and employees and also information about the departments is provided. Facility
of generating different reports like list of students/employees, attendance report of
students/employees, results and fee receipt will be provided.
1.3.1
Main Modules
In Automatic Attendance module each staff member and student
will mark their attendance through thumb scanning. A device (USB finger
print capture) will capture the finger print image, then matches the captured
image with already stored images. If match is found and verified then
attendance of that particular person will be marked. A fixed time will be set
for the attendance, like if any employee or student does not enter the
institute before that fixed time then his/her absence will be noted.
In SMS Alert module SMS APIs used that will send alerts through
SMS. To notify about the intimation for meeting to employees an SMS will
be sent to them, and also to the students parents if there is a parent meeting.
When any student will be absent from the institute without informing then
an SMS about the absence of student will be sent to his/her guardian.
Student record
Institute Name
Contact Numbers
Website
Number of Students
Number of Employees
Departments
Employee information: In Employee information we can:
1.4
List of Students.
List of Employees.
Attendance Report of Students.
Attendance Report of Employees.
Fee Slips.
Expected Outcome
1.5
1.6
No.
1.
2.
3.
Accepts data input from user and stores that data for later
retrieval
Maintaining records with accuracy
Activity Index
Activity
Comprehensive
analysis of topic
Specific Study
Design
Specifications
Duration
Deliverables
3 Weeks
Proposal
2 Weeks
SRS
4 Weeks
Mock-ups
Implementation of database and
4.
Implementation
5 Weeks
5.
Testing
2 Weeks
6.
Documentation
3 Weeks
User Manual
7.
Final Product
3 Weeks
GUI.
CHAPTER 2
REQUIREMENT ANALYSIS
CHAPTER-2
REQUIREMENT ANALYSIS
2.1
Requirement Analysis
Functional Requirements
The system should support management of academic, administrative
and other activities of the institute.
I.
Add user: Can add new user and assign login account to
access the system.
II.
2.1.2
Security
Security requirements are important factors in this system as classified
data will be stored in the database. User validation will be done during login to
insure that the user is valid and that the user only has access to his or her
permission data. General users will only have access through the user interface.
II.
III.
Ease of use
The system will be easily maintained by the developer or other
authorized trained person and it shall respond as fast as possible in generating
report and marking the attendance.
IV.
Deployment
System should be locally deployable for GPGC, preferably on a
windows platform.
V.
Platform
The system should be able to work on any of the common windows
operating system.
VI.
Data migration
Data can be easily migrated from the current system to a new
system.
2.2.
2.3
Use Cases:
i.
ii.
User Name
Password
i.
ii.
Login
Add New User
i.
ii.
UC-4
Search Student
Admin/User must login.
To search a particular student.
Login as Administrator or User.
10
Use Case ID
Use Case
Name
Actor
Description
Pre-Condition
UC-5
Register Employee
Admin
To register any new employee.
Login as Administrator.
UC-6
Employee Search
Admin
To search a specific employee.
Login as Administrator.
i. Employee main
ii. Employee search
Post Condition Employee searched
Data Flow
UC-7
Delete Employee Information
Admin
To Delete employees information.
Login as Administrator.
i. Employee main
ii. Employee information
Post Condition Information deleted
Data Flow
11
UC-10
Generate Reports
Admin
Admin can generate different reports
Login as Administrator.
i. Home
ii. Reports
Post Condition Report generated
Data Flow
12
Use Case ID
Use Case Name
Actor
Description
Pre-Condition
UC-11
Assign Subject
Admin
Admin can assign subjects to new students
Login as Administrator
i. Home
ii. Student Main
iii. Assign Subject
Post Condition Subject Added
Data Flow
UC-12
Update Institute Information
Admin
Admin can update the institute information
Login as Administrator
i.
ii.
Home
Institute Information
UC-13
View Results
User
User can view the results
Login as User
i. User Main
ii. Result
Post Condition Result Showed
Data Flow
13
2.4
14
15
2.5
16
CHAPTER 3
DESIGN
17
CHAPTER-3
DESIGN
3.1
UML Diagrams
3.1.1
Class Diagram
18
19
20
21
22
23
3.1.2
Sequence Diagrams
24
25
26
27
28
29
30
31
CHAPTER 4
TESTING
32
CHAPTER-4
TESTING
4.1
Testing
4.1.1 Test Cases
Steps:
1.
2.
3.
4.
5.
6.
7.
Run application
Login page
Enter username
Enter password
Click login
Navigate to main screen
Choose action
Status: Pass
33
Steps:
1.
2.
3.
4.
5.
6.
7.
Run application
Login page
Enter username
Enter password
Invalid username or password
Navigate to login page
reenter enter
Status: Fail
34
Steps:
1.
2.
3.
4.
Status: Pass
35
Steps:
1.
2.
3.
4.
5.
Status: Fail
36
Status: Pass
37
Status: Fail
38
Steps:
1.
2.
3.
4.
Status: Pass
39
Steps:
1.
2.
3.
4.
5.
Status: Fail
40
Steps:
Status: Pass
41
Steps:
Status: Fail
42
1.
2.
3.
4.
Status: Pass
43
Steps:
1.
2.
3.
4.
5.
Status: Fail
44
Login as administrator
Employee must be registered
EmployeeID:008080
Employee name: Waseem Ali
Test Data: Job type: office staff
Designation: head clerk
Gender: male
Steps:
1.
2.
3.
4.
5.
Status: Pass
45
Login as administrator
Employee must be registered
EmployeeID: 008080
Employee name: Waseem Ali
Test Data: Job type: office staff
Designation : voice principal
Gender: male
Steps:
1.
2.
3.
4.
5.
Status: Fail
46
Login as administrator
Must select one of them (1) For Student or (2) For Employee
Steps:
1.
2.
3.
4.
Status: Pass
47
Login as administrator
Must select one of them (1) For Student or (2) For Employee
Test Data: Message (please submit your subject result in admin office )
Steps:
Status: Fail
Status: Pass
48
Status: Fail
Steps:
1.
2.
3.
4.
Status: Pass
49
Steps:
1.
2.
3.
4.
5.
Status: Fail
Steps:
1.
2.
3.
4.
Status: Pass
50
Steps:
1.
2.
3.
4.
Status: Fail
51
CHAPTER 5
CONCLUSION &
FUTURE WORK
52
CHAPTER-5
CONCLUSION & FUTURE WORK
The system successfully registered Student and Employee. SMS Alerts were
successfully sent. The prototype successfully captured new fingerprints to be stored in the
database; scanned fingerprints placed on the device sensor. The performance of the system
was acceptable and would be considered for full implementation especially because of its
short execution time and reports generation. Everyone who tested the system was pleased
and interested in the product being developed for use in schools.
53
USER MANUAL
54
USER MANUAL
6.1
I.
Administrator
Login
Figure 29 - Login
II.
Institute Information
55
56
III.
Main
Figure 31 - Main
IV.
Student Main
57
58
V.
Student Registration
59
VI.
Update Student
60
VII.
Delete Student
61
VIII.
Search Student
62
IX.
Assign Subjects
63
X.
Results
Figure 38 - Results
64
XI.
Employee Registration
65
XII.
Update Employee
66
XIII.
Delete Employee
67
XIV.
Search Employee
68
XV.
SMS Alert
69
XVI.
Employee Attendance
XVII.
Student Attendance
70
71
XVIII.
Reports
Figure 46 Reports
XIX.
Settings
72
Figure 47 - Setting
73
6.2
User
I.
Main
74
REFERENCES
75
REFERENCES
[1] Saurabh Kumar; Uma Joshi; Bhupesh Kumar, Attendance Management
System (online).
Available at: http://www.iisjaipur.org/iiim-current08/mca_iv_sem_pro_eva/15.project%20attendence %20 managemnt % 20
system.pdf
[2] ViaNett, SMS API (online).
Available at: http://www.vianett.com/en/developers/sms-api-overview
[3] Chris Johnston (1999), Taxpayers lose in sale of software (online).
Available at: http://www.tes.co.uk/article.aspx?storycode=308303
76