Anda di halaman 1dari 21




PROJECT TEAM MEMBERS A.MEENA ABDUL SHABBER D.LAVANYA 309126510010 309126510002 309126510032


Submitted by

A.Meena (309126510010)

Table of Contents:
1. Revision History 2. Introduction Purpose of the system Scope of the system Objective and success criteria of the project 3. Current System 4. Proposed System Overview Functional Requirements Non-functional Requirements 5. System Models Scenarios Use case model Object model Dynamic model 6. Glossary

Revision of History
Version R1.0 26/08/2012 Created by all team members Release composed of requirement analysis document.

This document addresses the requirements of Attendance Management System. The intended audience for this document are designers and the client of the project.

Targeted audience
Client, Developers.

1.1 Purpose of the system
The proposed system is entitled as Attendance management system of ANITS is developed to computerise all the attendance details of students in the college and the software must be user-friendly, simple, fast accessing of data. This system will be monitored by the Faculty members, Head of the Department, Principal and by the Administrator. The main function of this system is every faculty members engaged with different classes are required to submit the attendance of students present in the class. Faculty can submit the attendance details in Attendance management system and the details can be retrieved whenever necessary through it. The modifications on the attendance details are done by the administrator. Every student can view his/her attendance details online.

1.2 Scope of the system

Attendance management system enables the user to perform operations like addition of attendance details, updation of attendance details, adding and deletion of student record. It enables the user to use interface interactively.

1.3 Objectives and Success criteria of the project

The success of this project depends on the following objectives: Maintaining attendance record of every student. Maintaining student record of every student. Addition of student attendance by the faculty. Updation of every detail about the attendance and student record each student into the database.


3.1 Overview
The goal of Attendance Management System is to manage the attendance details of each and every student in the college. This software has the facility to store the attendance details of all students of every class and branch. One can enter into the Attendance Management System using their username and password, which is then verified in the database. Every faculty must submit the attendance details of the classes in which they are engaged with, and directly the modifications are updated onto the database. For any modifications in the attendance records, are done by the administrator. Admin can even add or delete student records. The required data can be retrieved easily. The interface will be user-friendly. Data is well protected and makes the data processing fast and easier.

3.2 Functional Requirements

The system supports three actors mainly, they are:

Faculty, who adds the attendance of each and every student Administrator, who modifies the attendance details if requested and adds or deletes
the student record.

Student, who can only view his/her attendance details. Attendance Management System, which contains all details about attendance, students and faculty. 3.2.1 Faculty
Logs in. Selects appropriate class and branch. Selects the subject title. Adds the attendance for each and every student. If any modifications are to be done on the attendance, requests to admin for modification.

Logs out. 3.2.2 Administrator

Logs in. Checks for the notifications. If any present, fulfils the requested notification Adds student record for new students.

Deletes student record if requested. 3.2.3 Student Enters roll number. Views his/her attendance record. 3.2.4 Attendance Management System Stores the updated information about the attendance details. Stores the attendance details of each and every student. Stores all login details about user.

3.3 Non-functional Requirements

3.3.1 Usability:
Usability is the ease of use and learnability of human made objects.

Attendance management system should be understandable by every user. User can easily interact with the system. 3.3.2 Reliability:
Reliability specifies the capability of the software to maintain its performance over time.

Always the attendance system should be available for the user. If the user enters wrong login details, then it must prompt the user to enter correct
login details.

3.3.3 Performance:
Performance requirements are concerned with quantifiable attributes of the system such as response time, throughput, availability and accuracy.

System should quickly respond for user request, that is, system must immediately
display the list of students along with their attendance details after he/she selects the class.

3.3.4 Supportability:
Supportability requirements are concerned with the ease of changes to the system after deployment. It means system must be able to support for up gradation.

3.3.5 Availability:
The system shall be available during normal college operating hours.

3.3.6 User Interface:

This works as an interface between the user and the system by properly guiding the user how to use it and perform operations. Both Admin and Faculty can change the data in the Attendance Management System, whereas, student can only view the data. Any sort of training is not required for using the system. .It is important that the system is easy to learn because even a layman need to use it efficiently. The input device is given to the keyboard and the output is viewed on the monitor.

3.3.7 Hardware Consideration:

The system shall use an Oracle or Access database, and run on any operating system.

3.3.8 Portability:
The Attendance Management System shall run in any Operating system environment that contains Java Runtime and the Microsoft Access database.

3.3.9 Maintainability:
The Attendance Management System is being developed in Java. Java is an object oriented programming language and shall be easy to maintain.

3.3.10 System Interfacing:

The system shall be a standalone product that does not require any system interfaces.

3.3.11 Error Handling:

Our system handles the errors in a very efficient manner. It can tolerate to wrong inputs and prompts the users to correct the inputs. It gives notifications as and when required, guiding the users to properly utilize it.

1. Viewing of attendance by the student: Ram starts the EZ school system. The website is now visible to ram. Ram then selects view attendance. Ram enters his registration number. He now views his attendance and exits. 2. Attendance addition by the faculty: Meena starts the EZ school system to post the attendance. She enters her log in details. She then selects the appropriate branch, class and subject. Now the list of student details along with the attendances is displayed and Meena updates the attendance detail of each and every student. After she successfully posts the attendance details, she logs out of the EZ-school. 3. Attendance modification by the admin: Harish, the administrator starts the EZ school system. He enters his log in details. Now Harish checks for any notifications, if there is any modification request sent by the faculty Meena, he successfully modifies the requested attendance. Harish then updates the attendance of the students those which are modified. He adds the details of the students who have newly joined in the college ,deletes the attendance records if any student leaves the college. After fulfilling all the requirements, Harish logs out of EZ schoolsystem.

4.2Use case model:

The following are the use cases initiated by the faculty: Logs into Attendance management system. Selects branch. Selects class. Adds attendance to every student. Requests for any modifications.

The following are the use cases initiated by the admin: Logs into Attendance management system. The requested modification by the faculty is fulfilled by the admin. Adds student record.

Deletes student record.

The following are the use cases initiated by the Attendance management system: Updatesthe modified attendance. Checks the login details. Updates attendance record. Updates student record.

Use case Diagram:

It describes the system from an external point of view.

Flow of events:
1. Name: Login Participating Actor: Faculty Entry condition: Enter the log in details Flow of events: Faculty starts the system and opens the EZ school system, the homepage is now displayed, promping to enter her login details or get registerd . He enters his login details and the information is sent to anits attendance management system for verification. It acknowledges back by displaying next page if the details are valid. Otherwise it prompts to first register them by entering the details such as name, DOB, gender, age, password, qualification, branch, and so on. After entering the required information, it is then send to anits attendance management system for verification. Antis attendance system then acknowledges the faculty by displaying a next page.

Exit condition: Faculty successfully logs into the ez school site and starts the required tasks.

2. Name: Attendance addition Participating Actor: Faculty Entry condition: subject selection Flow of events: The system prompts the faculty to select branch and class. Now it prompts to select the subject like English, OOSE, Maths, Microprocessors, etc. Faculty responds to the system by selecting one subject name for example say OOSE. The system sends that particular subject information to the anits attendance system for verification. Anits attendance system then responds to the request of the user by displaying the list of students related with that subject i.e OOSE. Faculty then adds the Attendance to the students related with that subject.

Exit condition: Teacher logs out after having posted the attendance.

3. Name: Request for modification Participating Actor: Faculty, Admin Entry condition: Faculty sends requests to the admin Flow of events: While adding the attendance details, if faculty needs to modify the attendance of the students, then he sends the request to admin for modification. The attendance must be updated before the modification is done. Admin gets the notification and modifies the requested attendance.

Exit condition: Admin modifies the attendance and updates in database.

4. Name: Add/Delete a student record Participating Actor: Admin Entry condition: Admin logs into the system Flow of events: Admin starts the system, homepage is displayed prompting to enter his login details. He enters the login id and password, and the information is sent to anits attendance management system for verification. It acknowledges him back by displaying next page if the details are valid, otherwise displays a message invalid details. Admin adds record of those students who joined recently and updates the details into data base. Similarly, admin deletes the student record whenever necessary.

Exit condition: Admin saves the modification done to the particular section students, updates into data base and logs out.

5. Name: Roll no Participating Actor: Student Entry condition: Enter a roll number Flow of events: Student starts the system, homepage is displayed and prompts to enter his roll no.

Student enters his roll no. The information is sent to the database and if it is valid then the database responds by displaying next page. Otherwise it displays a message invalid roll no.

Exit condition: Student enters into Anits attendance management system.

6. Name: View attendance Participating Actor: Student Entry condition: views the attendance Flow of events: Student enters the roll no and the information is sent to the database. The database responds by displaying the next page containing attendance, if the attendance is updated. Otherwise the database responds by displaying a new page containing a message attendance not updated.

Exit condition: Students view required attendance details and exits.

4.3 Object model

The object model describes the structure of the system in terms of objects, attributes, associations, and operations. The classes that are identified from the above use case diagram are: Faculty: Attributes: Name of the facuty and an id(number) is given for each faculty. Operations: He/She has the right to only to add attendance. Ez school system: Attributes:It has a name and an id being assigned to this class. Operations: This class can perform getdetails and transferdetails . Student: Attributes: Every student is assigned with a name and a roll number. Operations: He has the right only to views his attendance. Login: Attributes: This class is assigned with a login id and a password. Branch: Attributes: Every branch is assigned with a name and also the year.

Class: Attributes: Each class has a name and also a section being assigned to it . Attendance record: Attributes: This class has the student name, roll number, subject, year of study, branch in which he studies, number of days he attended the class and his % of attendance. Operations: This class does the action of displaying the attendance. Admin: Attributes: Admin is assigned with a name and an id(number). Operations:He can perform the actions such as add,modify,delete and maintain records. Registration: Attributes: This class maintains the name of the faculty members,there log in Details, designation and their date of birth. Anits attendance management system: Attributes: This class is assigned with a name and an id(number). Operations: It can perform the actions such as verifying,transfering,and getting the details of the students. New student record: Attributes: This class maintains the name,rollnum,branch,year,class in which the student is admitted. Student record: Attributes: It has the name, subject, and % of attendance the student acquired.

Class Diagram:
It is used to describe the structure of the system.

4.4 Dynamic model

The dynamic model describes the internal behaviour of the system. They are represented with interaction diagrams, statechart diagrams, and activity diagrams.

Sequence Diagrams:
It describes the behaviour as a sequence of messages exchanged among a set of objects.

1. For Addition of attendance and modifications:

1. For student:

2. Collaboration Diagram: Faculty posting the attendance

Student viewing his attendance details

State chart Diagram:

It describes the behaviour of the system in terms of states of an individual object and possible transitions between states. 1. Attendance addition:

2. Updation of attendance

3. Viewing of Attendance

Activity Diagrams:
It describes the behaviour of the system in terms of activities. 1.Faculty