- INTRODUCTION STUDENT ATTENDANCE PORTAL is a web portal developed for daily student attendance in colleges and institutes. If facilitates to access the attendance information of a particular student in a particular class. The information is sorted by the operators, which will be provided by the teacher for a particular class. This system will also help in evaluating attendance eligibility criteria of a student. This system also provide paper less system. All staff maintain attendance of student, generate reports month wise, datewise.
The purpose of preparing of this document is to provide detail information of STUDENT ATTENDANCE PORTAL. This document describes the motive of entiresystem that is including in our project, its user, interactions, and end users. The requirements will be presented using textual descriptions to explain concepts, and different types of diagrams to illustrate complex interactions.
Our project is online attendance management system and the objectives are: 1.Reduces admin work by integrating the details of the students of all the three departments into a single database. 2.Manual work for information retrieval on attendance becomes less as the work becomes. 3.Easy access for students because they can view their attendance and make up for the shortage of attendance accordingly. 4.It is also time saving as manual work is less 5.There is less chance of error. 6.It eliminates duplicate data entry in time and attendance entries. 7.Auto-generation of various types of reports of student attendance.
The following project has much scope both in present as well as future. In present situation the system can be accessed both in luppies and mobile devices. The scope of the project any mobile device which has the acces to it's server on which the project has been deployed, ie, the project is developed as a web application, and it will work for a particular institute. But later on the project can be modified to operate for many institutes. In future the system can be automated using students fingerprint
There are some conventions are used during this document like Bold text is used for noticeable part. Under lined is used for key part. Numbering is used for defining sub categories or sub parts.
This document is prepared for its intended users who deals with it during system developing and future aspect phases, these are Developer: Developer uses this document for documentation and controlling project progress during whole life cycle of project. Tester: Tester uses this document for ensuring the goal of the project and attaining the diversion condition between intended and current phase of project. Project Manager: This project helps project manager to coordinates tasks of teams that are working on project; control their efforts for the project as well as timely reporting to top management. Maintenance Staff: This document provide the actual condition and processes that are carried out on the project so that the maintenance fields can be easily understandable and attain. End Users: This document describes end users i.e. what they actually want from the project, what their requirements are and how their requirements can be fulfilling.
This project has much scope both in present as well as future. In present situation the system can be accessed both in lappies and mobile devices (In the form of application). This project has provides a convenient and easier way to get the attendance paperlessly. The scope of the project any mobile device which has the access to its server on which the project has been deployed , i.e. the project is developed as a web application , and it will work for a particular institute. But later on the project can be modified to operate for many institute.
The main perspective of this project is to computerize the traditional way of taking attendance , and student can also monitor their attendance after the day, weakly and monthly.
This project is moving around 3 main modules Student , teacher , Admin. Student Module: Register and Login: Student first register to our website then he/shewill eligible to use our services, take part in our processes. View Attendance : Student can view attendance . Teacher Module: Register and Login: Teacher first register to our website thenhe/she will eligible to use our services, take part in our processes. Search Student: Teacher can search and get details of student according to their requirements. View Attendance: Teacher can view attendance. Manage Students: Teacher can able to add and remove the students.
Administrator:
Login: Admin login to get the status of processes that are running in entire system of this project. Add: Admin can add new students and teachers. Remove: Admin can remove students and teacher also and restrict any person. Update: Admin can modify any account details, offers and schemes, any details or information in web sites(even confidential information).
There are three users interact with the system and their characteristics are asfollows: ADMINSTRATOR: administrator is responsible for the maintenance of content over the web portal, he updates the current status and administrator takes the feedback from the various users and utilizes it for the betterment of services. STUDENTS: Customers are registered candidates and able to get the details of attendance other services that are provided by our system. TEACHER: Teacher is responsible for the maintenance of content over the web portal, he updates the current status .
The team has selected PHP language to implement theCode Behind functionality for web pages. The team will be using the VS code IDE to edit and create the web portal. The design constraint is that the computers at each place may not follow similar screen resolutions. This can lead to the web portal not having the impact it is planned to have.
Software requirements specification document. Extensive online help will be available at all times when using the system. This online help will guide the user, which may or may not be computer or Internet knowledgeable, through each aspect of the system.
It is assumed that the system will be able to interface with an email server in order to send a status email to contacts of the system.It is assumed that the system will interface with a MYSQL databas
This feature of allow administrator and teacher to manage attendance over the web portal. He can add or delete new categories, new sub categories and new students. Priority of this feature is high, because the system would be relatively useless if the projects are not updated
This feature are allow student to submit application of leave if any how student are absent.
This feature gives the automated calculated attendance at the end of the weak and months .
Description and Priority: This feature allows new user or customer to register on the web portal. The priority of this feature is high because only registered users can buy/sell properties from the web portal. Stimulus/Response Sequences: i. From the user home page the customer/company will click on the register link. ii. A new registration form will be open. iii. The user will complete the entries and clicks on the register button.
Description and Priority: This feature of allow administrator to manage the advertisement over the web portal. He can add new advertisement or delete/replace existing advertisement. The priority of this feature is moderated. Stimulus/Response Sequences: i. From the admin page the administrator click on the manage advertisement link. ii. A new manage advertisement page will be display. iii. Administrator will upload a new advertisement file. iv. He can delete select and click on delete button to delete the existing advertisement. v. The system will display a successful operation notification.
Description and Priority: This feature allows the system administrator to manage the customer support services He can accept or reject quotations, answer to thequeries through E-mail. Can see the feedback of the customers. Stimulus/Response Sequences: i. From the admin page the administrator click on the manage customer support services link. ii. A new manage customer support page will be display. iii. He will click on the edit button and all the fields will be open in the editable format.
There will be two “separate” user interfaces the web portal. One will be used by the administrator of the system to update and add content over the web portal. The second user interface is simply a different web page. The user interface for the system will be a web page on the Internet. A prototype will be created that represents the final interface for the system in terms of look and feel. The prototype can be accessed through a web link provided soon. The user interface will be limited to the types of controls that can be generated using HTML, JavaScript, and Cascading Style Sheets. The user interface code will be generated by individual developers.
The Hardware Interfaces of the system are handled by the Windows Server operating system. No hardware dependent code will be written by the development team.
Operating System: The software is being designed to run on Windows Server (version?). Windows Server (version?) includes the latest version of Apache Tomcat7.2.1. Web Server: The software is being designed to run on Apache Tomcat Server7.2.1. Database: The system will access the MYSQL database for providing the backend support for various features of the system. Libraries: The software will be created using the jar files. 4.4 Communications Interfaces: Web Interface: The application will be accessed over the Internet. All features will accessible through the web portal. Emails: The administrator can send status and answer emails to the customers.
Modem Connection: The users of this web page who have a 56Kbps modem connection to the Internet should expect to be able to load any page of within 10 to 20 seconds. Broadband Connection: The users of this web page who have a broadband connection should be able to load every page within 2 to 5 seconds. Client Hardware: The performance of the system will also depend on the client machine.
There are some risks too that come with when admin add new project then no any unauthorized builder can’t access details of the projects. And only register builder access the our customer details.
SEC-1 – The system shall only allow authorized users to access the login, lost password, and registration page. SEC-2 – The system shall require a login and password to gain access to the site.
Availability: The system must be available for use when it is needed during the critical months of updating the system. The web portal should have 99% uptime.
Reliability: Data, as entered, must be correctly stored in the database. In addition, the database should use transactions so that partial entries are not stored in the database. Because the user of the system may be inexperienced, each feature must work correctly 99% of the time. The logic required is not complex enough to allow for a lower expectation.
Usability: The system will be used by individuals of varying skill level and technical competence. The system shall be intuitive to use and have extensive online help documentation to walk users through the operations they are trying to perform.
Maintainability: The system will likely be developed by a different team at the same time. The code and design need to be documented well enough and designed such that a senior project team with the same amount of academic and experience can ramp up on the project within 4 weeks.