Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Java Based RFID Attendance Management System Graduation Project Presentation


Published on

Java Based RFID Attendance Management System Graduation Project Presentation
Source code is only available when having permissions from the whole team members.

Published in: Business, Technology
  • Login to see the comments

Java Based RFID Attendance Management System Graduation Project Presentation

  1. 1. Java Based RFID Attendance Management System A graduation project for the future.. Supervised by Prof.Dr.Hesham Arafat Ali
  2. 2. Agenda ●Introduction ● A problem to solve and a solution. ● System purpose ● System features. ● Where? ● Used tools ●Phases ● Planning, gathering information phase ● Design, Application and Database Design ● Implementation ● Testing ●Future applicable extensions ●A Thank you! Word and Questions
  3. 3. Introduction Ibrahim Abdel Fattah Mohammed
  4. 4. Introduction: System Purpose ●The purpose of this project is to develop an automated class attendance checking system for each and every lecture room in the university.
  5. 5. Introduction: Where?
  6. 6. Introduction: Key Technology ●The primary technology to be used is Radio Frequency Identification technology or RFID ●A system of identification wherein an electronic device that uses radio frequency or magnetic field variations to communicate is attached to an item. ●Why RFID? 1. Alignment is not necessary. 2. High inventory speeds. 3. Variety of form factors. 4. Item-level tracking. 5. Rewritability (This depends on the type of the Tag).
  7. 7. Introduction: Used Tools ●RFID, The Key Technology ●Linux, The Base Operating System ●JAVA, Application logic and the middle-ware ●MySQL, The Back-end Database ●GWT, Google Web Toolkit
  8. 8. Planning & Analysis Eman Mahmoud Abdel Fattah
  9. 9. Planning ● We believe that the best way to get a good working application is to give enough time for planning and designing. ● In our planning phase,we passed through the following..
  10. 10. Know the scale and working environment ● large number of students ,class rooms and teaching stuff. ● Limited resources. Searching for suitable RFID-Reader to work efficiently with minimum cost. ● System has to be scalable
  11. 11. Analysis: Technical - H/W requirements: – RFID-Readers – Tags – Server machine - S/W requirements: – Linux Operating System – Database – Apache web server - Who uses the system: – Students – Teachers – Professors
  12. 12. System Analysis The system should be divided into 3 modules - The RFID module for using the RFID-Reader. - The Database module for recording the attendance. - The View module to view recorded attendance.
  13. 13. Analysis: Economic ● Initial costs ● RFID-Reader: 500 EGP for each Classroom ● RFID-Tag for each student ● Running costs ● Electricity cost ● Maintenance cost
  14. 14. Application & Database Design Eman Sa'ad El-Dien El-Zahy
  15. 15. Design As in the planning phase we have 3 modules - The RFID module - The Database module - The View module
  16. 16. RFID Designing Java classes which function is: ● When students pass through the RFID-Reader with their ID-cards,The RFID- Reader reads the ID of each student passes and sends it to the server for processing . ● The server takes the ID of the student, process it and record the attendance in the database.
  17. 17. Database ● Included two phases: 1- Designing the Database – creating tables that mirrors the structure of the environment and the relations between these tables. – Normalizing tables. 2- Designing Database Java classes: – Classes that records the attendance data in the database. – Classes that retrieves the attendance data to view it using the systems' GUI.
  18. 18. View ● Designing login form to check authentication. ● Designing needed forms for possible users of the system depending on the permissions given to each type of users (professor,TA,student).
  19. 19. The Environment Moustafa Mahmoud Al-Sherbiny
  20. 20. The Environment: Linux ● We use Linux as the base OS for our server ● In spite of that , Our Software is tested under Microsoft Windows. And can be deployed on any other platform that supports Java
  21. 21. The Environment: Why Linux? • Mainly , It is free – FREE of charge. – FREE source – Rapid development – More Secure. • Security –User Privileges –No Executables –No Registry • Stability. • Multi-User , Networked OS
  22. 22. The Environment: Java • Java is an Open Source Object Oriented Programming Language. • Platform independent • Secure • Simple • Multi-Threaded • Distributed
  23. 23. The Environment: MySQL • Relational database management system (RDBMS) • Providing multiuser access to a number of databases • Works on many different system platforms
  24. 24. The Environment: GWT Google Web ToolKit • A JAVA to JavaScript cross-compiler •It takes Java code and compiles it into JavaScript to be run in a browser with AJAX style • GWT-RPC : A technology used to remotely invoke code component from remote server
  25. 25. Implementation Amal Abdel Naby Al-Shihaby
  26. 26. Implementation: Reader API ● We create a class that will listen to the reader and if the reader read a tag it will capture this ID and the time of Attendance
  27. 27. View: Login Interface ● The client will send this information to the server using RPC to check if this user is authenticated.
  28. 28. View: Student Interface ● For student he can view only his attendance.
  29. 29. View: Professor Interface ● For professors ,each one can view attendance in his subjects.
  30. 30. View: Teacher Interface ● Switch on/off interface ● View student attendance ● View section attendance
  31. 31. Teacher: Reader Interface ● The teacher can switch on/off the reader from the interface
  32. 32. Model ● We create number of classes that will execute the query on the database and return the required data.
  33. 33. Controller ● Google Web Toolkit provides us with some of tools like RPC package. ● We used this package to connect the view with the model
  34. 34. Future Extensions Ibrahim Abdel Fattah Mohammed
  35. 35. Future Extensions ● Email integration and notification ● SMS integration and cooperation ● Cooperation with university's current system, proxy and email accounts ● Bullet-in boards, forums and presentations views. ● Classes Assignments ● Sections Cancellation
  36. 36. Question?
  37. 37. Thanks!