Presentation on NCCA Student Attendance System

1. Presentation onNCCA Student Attendance System By : Rajeshkumar S. Gone Hussain A. Pipwala

2. Topics • Existing System • Limitations of Existing System • Proposed System • Objectives • Project Profile • Development Environment • Ajax • Process Model • Module Specification • Data Flow Diagram • Abbreviation • Data Dictionary • Complexities and Its Solutions • Data Table • Design (User Interface) • Testing • Bibliography

3. Existing System • Present attendance process is running fully manually with a more or less use of computer • An Attendance master is maintain for the purpose of keeping regular attendance of every students • For any manipulation or any report generation is made by calculating attendance of all students.

4. Limitation of existing system Before using NSAS ,Narmada College of computer Application was using manual system, the following is some limitation of manually system   • Require keeping all duplicates of documents properly  • Probability of Data Redundancy  • Probability of Inconsistent Data • All time check Contact Details for sending message

5. Require counting percentage of attendance of Students • Require checking which Subject under which Faculty • It’s a time consuming way.  • There is no accuracy in maintain details of different students attendance.  • There are chances of mistakes in calculation and all the kind of entries.   • It takes time to search manually and report the records.

6. Proposed Systems properties • The System will provide user friendly interface to the users • Computerized Attendance System • Day wise Reports • Subject wise Reports • Student Attendance Reports • Computer generated report

7. Basic functionality of NSAS system Admin Module • The System will provide user friendly interface to the admin. • The admin will be able to easily browse the site & obtain the desired information of Students & Faculties. • Admin can easily register Faculty on the system • Admin can view Category wise insurance just selecting any of the categories.  • Admin can maintain promote & detain procedure. • Admin can assign subject to any faculty. • System can be able to help generate various reports that become helpful to administrator.

8. Faculty Module • Faculty can login into system and use all the features provided on Faculty section. • Faculty can make attendance easily. • Faculty can view and edit personal details. • Faculty can search any student details in brief. • Faculty can configure his/her own details like Username, Password etc.  • Faculty can forgot login details by Email. • System can be able to help generate various reports that become helpful to administrator

9. Leave Module • User can login into system and use all the features provided on Leave section. • User can view and edit personal details. • User can easily input leaves details. • User can search any student details in brief. • User can configure his/her own details like Username, Password etc. • User can get login details by Email. • System can be able to help generate various reports that become helpful to administrator.

10. Module wise Functions

11. Objectives • Conversion from Manual system to computerized system • Data Access Rapidly • More Accurate Data • Data Integrity • Less chances of unauthorized access • Various Report generation parameter wise

12. Easy to enter records and maintain them. • Search facility is easy for the operator to keep track of records • No chances of any calculation mistakes because it all calculations is being done automatically by the system very accurately. • Email facility is to get login details of faculties. • Very simple and very convenient to use.

13. Project Profile • Project Title : NCCA Student Attendance System(NSAS) • Developed For : Narmada College of Computer Application, Bharuch. • Team Members : Rajeshkumar S. Gone Hussain A. Pipwala • Front End : Java Server Page(JSP) • Back End : My SQL • Server : Apache Tomcat Server • Documentation Tool : Microsoft Word 2007

14. Development environment • Hardware used for Development • Processor : Genuine Intel(R) CPU ( 1.6 GHz) • Memory : 2 GB • Free Space on Disk : 80 GB • Monitor : Samsung Color Monitor 17” Inch • Java Enabled Browser : Mozilla Firefox, Google Chrome • Printer : Brothersoft Color Printer • Internet Connection : 256 kbps speed • Software Specification • Front End Software : Dreamviewer 8, Editplus 3 • Back End : Wamp Server 2.0(for MySQL) • Operating System : Microsoft Windows 7 • Server • Apache Tomcat Server

15. Ajax • for validating online forms. • Real-time Form Validation using Ajax • This example uses the JavaScript XMLHttpRequest object and server-side scripting to check that the Email address entered is valid (at least that it matches a particular regular expression) and that the Age lies between 16 and 100.

16. Cont… • As the form is completed, the values are passed immediately to the server as POST variables, the server calculates a result, passing back an XML file which is then parsed to trigger various actions on the page as you will see.

17. If you enter an invalid Email address, or a value for Age outside the specified range, a red warning message will appear and form will not be able to be submitted. Similarly, when you enter a valid value the message will be green. When all fields have been validated the form will be able to be submitted.

18. Cont… • The Email field input is tested using Ajax when theonChange event is triggered (when the input value changes and the focus moves to another element). We could have also usedonBlur but that's more resource-intensive as it's called even when the value hasn't been modified. • The Age field is checked whenever it's onKeyUp event is triggered - every time a key is pressed and released while the focus is on that element.

19. Process model • As a process model we have used “PROTOTYPE MODEL”. • WHY PROTOTYPE MODEL? • There are some limitations of “Linear Sequential Model”. • Real project rarely follow the sequential flow that the model proposes. Although the linear model can accommodate iteration, in does so indirectly. As a result, changes can cause confusion as the project team proceeds.  • It is often difficult for the customer to state all requirements explicitly. The linear sequential model requires this and has difficult accommodating the natural uncertainty that exists at the beginning of many projects.

20. Cont… • The customer must have patience. A working version o the program(s) will not be available until late in the project time-span. A major blunder, if undetected until the working program is reviewed, can be disastrou • In this model we also have to wait for others. Because of this we cannot complete our work in specific period of tim • Each of these problems is real. So we use prototype model in our project, as our project is real one.

21. Cont… • As a process model we have use “PROTOTYPE MODEL”.

22. Module specification Admin module • This module allows admin to add new faculty for handling his/her personal details and students details. And will create user id with personal profile and other information. The module get the various information about the faculty starts with username, password, and email address and so on. User id is used to log in the system for accessing. When new faculty gives the username which already exists, then his/her username is not accepted. Admin is also having the rights to detain any student. Which will reflects in all the database

23. Cont… Faculty Module • This module trying to login to system using user id and password. And allow saving his students detail which will direct reflects in database. This module allows faculty to update his personal details.

24. Cont… Leave Module  • This module allows the faculty to view his personal details and he/she is allowed to add detail about the leaves of ant student date wise.

25. Data Flow Diagram

40. Abbreviation

41. Data Dictionary

44. Data Table studentMaster

45. facultyMaster

46. subjectMaster

47. leaveMaster

48. attendance

49. Complexities and Its Solutions Efficiency of coding

50. Cont…