This action might not be possible to undo. Are you sure you want to continue?
ATTENDANCE MANAGEMENT SYSTEM OF ANITS COLLEGE
PROJECT TEAM MEMBERS A.MEENA ABDUL SHABBER D.LAVANYA 309126510010 309126510002 309126510032
IV/IV B.TECH C.S.E-A OBJECT ORIENTED SOFTWARE ENGINEERING LAB
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
. The intended audience for this document are designers and the client of the project.Revision of History Version R1. Preface This document addresses the requirements of Attendance Management System. Targeted audience Client. Developers.0 – 26/08/2012 Created by all team members Release composed of requirement analysis document.
Faculty can submit the attendance details in Attendance management system and the details can be retrieved whenever necessary through it. fast accessing of data. Every student can view his/her attendance details online. CURRENT SYSTEM None . 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.2 Scope of the system Attendance management system enables the user to perform operations like addition of attendance details. 2. This system will be monitored by the Faculty members. Head of the Department. INTRODUCTION 1. adding and deletion of student record.3 Objectives and Success criteria of the project The success of this project depends on the following objectives: Maintaining attendance record of every student.1. simple. Updation of every detail about the attendance and student record each student into the database. 1. It enables the user to use interface interactively. Principal and by the Administrator. Maintaining student record of every student. The modifications on the attendance details are done by the administrator. updation of attendance details. 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. Addition of student attendance by the faculty.
1 Overview The goal of Attendance Management System is to manage the attendance details of each and every student in the college. Adds the attendance for each and every student. Attendance Management System. they are: Faculty. For any modifications in the attendance records.3. and directly the modifications are updated onto the database. If any present. 3. Checks for the notifications. The required data can be retrieved easily. Selects the subject title. which is then verified in the database. 3. students and faculty. Selects appropriate class and branch. Admin can even add or delete student records. This software has the facility to store the attendance details of all students of every class and branch. 3. . PROPOSED SYSTEM 3. requests to admin for modification. are done by the administrator.2 Functional Requirements The system supports three actors mainly. which contains all details about attendance. who adds the attendance of each and every student Administrator. fulfils the requested notification Adds student record for new students. Student. Data is well protected and makes the data processing fast and easier.2.2 Administrator Logs in. who modifies the attendance details if requested and adds or deletes the student record.1 Faculty Logs in. One can enter into the Attendance Management System using their username and password. who can only view his/her attendance details. If any modifications are to be done on the attendance. Every faculty must submit the attendance details of the classes in which they are engaged with. Logs out. The interface will be user-friendly.2.
1 Usability: Usability is the ease of use and learnability of human made objects. then it must prompt the user to enter correct login details.3 Student Enters roll number. Views his/her attendance record.3. system must immediately display the list of students along with their attendance details after he/she selects the class. that is.3.3 Non-functional Requirements 3. Deletes student record if requested.3 Performance: Performance requirements are concerned with quantifiable attributes of the system such as response time. 3. If the user enters wrong login details. 3. Attendance management system should be understandable by every user. availability and accuracy.4 Supportability: Supportability requirements are concerned with the ease of changes to the system after deployment. User can easily interact with the system.2.3. . 3. It means system must be able to support for up gradation. throughput. System should quickly respond for user request. Always the attendance system should be available for the user. Stores the attendance details of each and every student. 3. Stores all login details about user. 3.2 Reliability: Reliability specifies the capability of the software to maintain its performance over time.2.4 Attendance Management System Stores the updated information about the attendance details. 3.3.
11 Error Handling: Our system handles the errors in a very efficient manner.3.3. 3. Java is an object oriented programming language and shall be easy to maintain. 3. 3. and run on any operating system.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.It is important that the system is easy to learn because even a layman need to use it efficiently. 3.3. Both Admin and Faculty can change the data in the Attendance Management System. 3.7 Hardware Consideration: The system shall use an Oracle or Access database.3. whereas. student can only view the data.10 System Interfacing: The system shall be a standalone product that does not require any system interfaces.3.5 Availability: The system shall be available during normal college operating hours.8 Portability: The Attendance Management System shall run in any Operating system environment that contains Java Runtime and the Microsoft Access database. . Any sort of training is not required for using the system. The input device is given to the keyboard and the output is viewed on the monitor. .3.3. 3.3. guiding the users to properly utilize it. It gives notifications as and when required. It can tolerate to wrong inputs and prompts the users to correct the inputs.9 Maintainability: The Attendance Management System is being developed in Java.
3. the administrator starts the EZ school system. Now the list of student details along with the attendances is displayed and Meena updates the attendance detail of each and every student. He now views his attendance and exits.2Use case model: The following are the use cases initiated by the faculty: Logs into Attendance management system.deletes the attendance records if any student leaves the college. She then selects the appropriate branch. class and subject. He adds the details of the students who have newly joined in the college . Harish then updates the attendance of the students those which are modified. 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. . 4. she logs out of the EZ-school. he successfully modifies the requested attendance. After she successfully posts the attendance details. The website is now visible to ram. He enters his log in details.4. Ram enters his registration number. Selects branch. Viewing of attendance by the student: Ram starts the EZ school system. After fulfilling all the requirements. 2. Adds student record. if there is any modification request sent by the faculty Meena. Requests for any modifications. Adds attendance to every student. Selects class. Attendance addition by the faculty: Meena starts the EZ school system to post the attendance. Now Harish checks for any notifications.1Scenarios: 1. Ram then selects view attendance. She enters her log in details. Attendance modification by the admin: Harish. Harish logs out of EZ schoolsystem. SYSTEM MODEL 4.
Updates attendance record. Use case Diagram: It describes the system from an external point of view. . Deletes student record. The following are the use cases initiated by the Attendance management system: Updatesthe modified attendance. Checks the login details. Updates student record.
gender. . Now it prompts to select the subject like English. Exit condition: Teacher logs out after having posted the attendance. The system sends that particular subject information to the anits attendance system for verification. it is then send to anits attendance management system for verification. and so on.e OOSE. branch.Flow of events: 1. It acknowledges back by displaying next page if the details are valid. 2. He enters his login details and the information is sent to anits attendance management system for verification. qualification. etc. promping to enter her login details or get registerd . Microprocessors. Exit condition: Faculty successfully logs into the ez school site and starts the required tasks. Otherwise it prompts to first register them by entering the details such as name. Faculty then adds the Attendance to the students related with that subject. age. password. OOSE. Anti’s attendance system then acknowledges the faculty by displaying a next page. 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. DOB. Faculty responds to the system by selecting one subject name for example say OOSE. Maths. Anits attendance system then responds to the request of the user by displaying the list of students related with that subject i. Name: Attendance addition Participating Actor: Faculty Entry condition: subject selection Flow of events: The system prompts the faculty to select branch and class. After entering the required information. the homepage is now displayed.
Name: Add/Delete a student record Participating Actor: Admin Entry condition: Admin logs into the system Flow of events: Admin starts the system. Similarly. Admin Entry condition: Faculty sends requests to the admin Flow of events: While adding the attendance details. then he sends the request to admin for modification. otherwise displays a message “invalid details”. if faculty needs to modify the attendance of the students. admin deletes the student record whenever necessary. homepage is displayed and prompts to enter his roll no. Exit condition: Admin saves the modification done to the particular section students. Name: Roll no Participating Actor: Student Entry condition: Enter a roll number Flow of events: Student starts the system. It acknowledges him back by displaying next page if the details are valid. and the information is sent to anits attendance management system for verification.3. . 5. Admin gets the notification and modifies the requested attendance. updates into data base and logs out. Name: Request for modification Participating Actor: Faculty. 4. homepage is displayed prompting to enter his login details. He enters the login id and password. Admin adds record of those students who joined recently and updates the details into data base. Exit condition: Admin modifies the attendance and updates in database. The attendance must be updated before the modification is done.
Operations: This class can perform getdetails and transferdetails . The information is sent to the database and if it is valid then the database responds by displaying next page. The database responds by displaying the next page containing attendance.3 Object model The object model describes the structure of the system in terms of objects. 4. Student: Attributes: Every student is assigned with a name and a roll number. attributes. Student enters his roll no. 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. Branch: Attributes: Every branch is assigned with a name and also the year. . Otherwise it displays a message “invalid roll no”. associations. Operations: He/She has the right to only to add attendance. Otherwise the database responds by displaying a new page containing a message “attendance not updated”. Ez school system: Attributes:It has a name and an id being assigned to this class. Exit condition: Student enters into Anits attendance management system. Operations: He has the right only to views his attendance. 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. if the attendance is updated. 6. Exit condition: Students view required attendance details and exits. Login: Attributes: This class is assigned with a login id and a password.
designation and their date of birth. Attendance record: Attributes: This class has the student name. Operations:He can perform the actions such as add. subject. Admin: Attributes: Admin is assigned with a name and an id(number).class in which the student is admitted.year.delete and maintain records. Operations: It can perform the actions such as verifying.there log in Details. branch in which he studies. Student record: Attributes: It has the name. roll number. Registration: Attributes: This class maintains the name of the faculty members. year of study. Operations: This class does the action of displaying the attendance. Anits attendance management system: Attributes: This class is assigned with a name and an id(number).rollnum.and getting the details of the students. .transfering. number of days he attended the class and his % of attendance. Class: Attributes: Each class has a name and also a section being assigned to it . subject. New student record: Attributes: This class maintains the name.modify.branch. and % of attendance the student acquired.
and activity diagrams.Class Diagram: It is used to describe the structure of the system. .4 Dynamic model The dynamic model describes the internal behaviour of the system. 4. statechart diagrams. They are represented with interaction diagrams. Sequence Diagrams: It describes the behaviour as a sequence of messages exchanged among a set of objects.
For Addition of attendance and modifications: .1.
1. For student: .
Collaboration Diagram: Faculty posting the attendance Student viewing his attendance details .2.
State chart Diagram: It describes the behaviour of the system in terms of states of an individual object and possible transitions between states. Attendance addition: . 1.
Updation of attendance 3. Viewing of Attendance .2.
1.Faculty .Activity Diagrams: It describes the behaviour of the system in terms of activities.
Admin 3.2.Student .
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.