This action might not be possible to undo. Are you sure you want to continue?
RAJIV GANDHI PROUDYOGIKI VISHAVIDYALAYA BHOPAL (M.P.) in partial fulfillment for the award of the degree of
BACHELOR OF ENGINEERING IN COMPUTER SCIENCE ENGG. Submitted By:
Anuj Gupta 0915CS081010 Kshama Agrawal 0915CS081013 Ajay Kujur 0915CS0810
Under the Guidance of Mr. D. D. Shrivastava CSE Deptt.
Department of Computer Science & Engineering
Institute of Information Technology & Management Gwalior (MP)
CERTIFICATE OF APPROVAL
The foregoing project entitled “Student Attendance Management System” Is here by approved as a certifiable study of engineering subjected carried out and presented in manner satisfactory to warrant it acceptance as a pre-Requisite to the degree for which it is submitted. It is understood by this Approval the undersigned do not necessarily endorse any conclusion of Opinion therein, but approve the project for which it is submitted.
HOD CSE Institute of Information Technology & Management, Gwalior
Principal Institute of Information Technology & Management, Gwalior
This is a certify that project entitled “Student Attendance Management System” is record of bona fide done by Anuj Gupta, Kshama Agrawal, Ajay Kujur under my guidance for partial Fulfillment of the requirements for the award of the degree of “Bachelor of Engineering” To the best of my knowledge, this project is original work and has not been submitted before for award of any other degree.
Mr. D. D. Shrivastava Institute of Information & Management, Gwalior
We sincerely and heartly thankful to the project in charge Ms. of CS & IT department for their encouragement to complete this project. B K Singh.D. D. Shrivastava their active & constant encouragement & also for the excellent & faithful discussion that has helped us during the course of the project. It gives us immense pleasure to express our sincere thanks to H. At the outside we would like to express our deep gratitude for project to Dr. Romina Sharma for her timely advise and kind cooperation of though times without his innovation guidance we would not been able to complete this project.ACKNOWLEGEMENT We are extremely grateful to Mr. D. Principal of INSTITUTE OF INFORMATION TECHNOLOGY & MANAGEMENT (IITM) for granting permission & providing the necessary facilities for successful completion of this project. Anuj Gupta Kshama Agrawal Ajay Kujur .O.
The information is sorted by the operators.1. updating any subject if necessary. This system will also help in evaluating attendance eligibility criteria of a student.Attendance Management System basically has two main modules for proper functioning.The scope of the project is the system on which the software is installed. and sending notice. school etc. It facilitates to access the attendance information of a particular student in a particular class. the project is developed as a desktop application.e. • First module is admin which has right for creating space for new batch. entry of new faculty. colleges and institutes. attendance system has remained one of the most important systems for evaluating the working time of students in any college or school.2 Scope: . this project is used to mark the number of days present/absent in any academic year of students in a college. Attendance can be taken in two ways: • On the basis of Subject and month. • On the basis of Class. • Second module is handled by the user which can be a faulty or an operator. In short. generating report. and it will work for a particular institute. which will be provided by the teacher for a particular class. 1. 1. i. Since ages. Introduction Attendance Management System is software developed for daily student attendance in schools.1 Overview:. User has a right of making daily attendance. . But later on the project can be modified to operate it online.
not properly storage of data.The purpose of developing attendance management system is to computerized the tradition way of taking attendance . due to which the people concerned with maintaining the attendance report have to face lot of problems like: problem of data security. So. to solve these problems we computerized the student attendance system. It is also a very tedious job and as manipulation of data is very easy it is error prone.1. Also. increases the work load. performance and user interface than the current system. . the purpose of the project is to develop a student attendance system. In the current system. which has better data security. the attendance is maintained manually.It is also used to generate the report automatically at the end of the session or in the between of the session. takes a lots of time etc.3 Purpose: .
2. 7. HTML. 3.Windows-7 2.2 Minimum Hardware Requirement:1.MS-Access. 4. Backend . Apache Tomcat etc. RAM -256 MB (Preferably 2GB or higher) Hard Disk -40 GB Processor -Intel Pentium 4 SVGA Monitor Keyboard Two Button Mouse Operating System -Windows XP Service Pack2 . System Requirements 2. 2. 2. 6. Operating System . Language – Java Servlets. Xara 3.1 Software Requirement:1. 5.
Literature Survey & Introduction of Methodology 3.In the present system all work is done on paper. This because majority of the records are stored as statements or in registers. these data can be accessed by anyone and even they can modify any important data. • Lots of paperwork: Existing system requires lot of paper work. . At the end of session the students who don’t have 75% attendance get a notice. •Less security: Security of data is less in manual systems. • Manual control: All calculations to generate report is done manually so there is greater chance of errors. We are not interested in generating report in the middle of the session or as per the requirement because it takes more time in calculation. The whole session attendance is stored in register and at the end of the session the reports are generated.3. • Time consuming: Every work is done manually so we cannot generate report in the middle of the session or as per the requirement because it is very time consuming. • Difficulty in report generating: We require more calculations to generate the report so it is generated at the end of the session and the student does not get a single chance to improve their attendance. Loss of even a single register/record led to difficult situation because all the papers are needed to generate the reports. Disadvantages of present working system:• Not User Friendly: The existing system is not user friendly because the retrieval of data is very slow and data is not maintained efficiently.1 Working of Present System: . Moreover.
A Faculty has to login to the system & then in the attendance option they have to select appropriate class.Proposed SystemThis Application is built for automating the processing of attendance. It also generates periodic reports to keep a check on the students who are regular & who are not. All the data is feted into the computer immediately and . So this will display the list of the students who are eligible to appear in this session. So this kind of various reports can be generated Characteristics of the proposed system• User Friendly:-The proposed system is user friendly because the retrieval and storing of data is fast and data is maintained efficiently. which provides user to deal with the system very easily. So now the faculty has to just select the students name from the manual attendance sheet according to their roll number and then submit the sheet. Office staff can also generate black list of students who have attendance less than 50% or80%. • Very less paper work:. Moreover the graphical user interface is provided in the proposed system. semester and subject. This will add the selected students as present student in that particular session. This system is very useful to the office staff also because they can generate various types of reports and submit them to respective faculties also or also can be submitted to the College Coordinator.reports can be easily generated in the proposed system so user can generate the report as per the requirement (monthly) or in the middle of the session. • Reports are easily generated:. User can give the notice to the students so he/she become regular. It also enhances the speed of the performing attendance task easily.The proposed system requires very less paper work.
The initialization step creates a base version of the system. • Computer operator control:.Computer operator control will be there so no chance of errors. the iteration step. . allowing software developers to take advantage of what was learned during development of earlier parts or versions of the system. however. The goal for this initial implementation is to create a product to which the user can react. and the Project Control List. Moreover work becomes very easy because there is no need to keep data on papers. So work can be done speedily and in time. Software Engineering ModelThe model employed to materialize the Student Attendance Management System is the iterative waterfall model. design modifications are made and new functional capabilities are added. Learning comes from both the development and use of the system. In software/systems development. At each iteration. where possible key steps in the process start with a simple implementation of a subset of the software requirements and iteratively enhance the evolving versions until the full system is implemented. The procedure itself consists of the initialization step. A common mistake is to consider "iterative" and "incremental" as synonyms. It should offer a sampling of the key aspects of the problem and provide a solution that is simple enough to understand and implement easily. they typically go hand in hand.reports can be generated through computers. which they are not. The basic idea is to develop a system through repeated cycles (iterative) and in smaller portions at a time (incremental). Moreover storing and retrieving of information is easy.
User has a right of making daily attendance. updating a subject if necessary.3. Attendance Management System basically has two main modules for proper functioning • First module is admin which has right for creating space for new batch. • Second module is handled by the user which can be a faulty or an operator. In this the teachers engaging different classes are required to submit the attendance of the students present in their class regularly. Detailed guidelines for its use are as under. Teachers will submit their attendance through this Student Attendance Management System. . and sending notice.2Introduction of Methodology:Student Attendance Management System has been developed in Institute for computerised attendance submission and it’s monitoring by Teachers. generating report. Students/Guardians also have access to view their attendance. any entry of new faculty. Head of Departments. Dean Academic Affairs and Director.
colleges and institutes.) 4. Teacher now mark the attendance of student who is present in class. Teachers have to enter their loginid and password in system. System Requirement Specification (S. The third module of the project allows the students to log into the system and view their current attendance statistics.S. also there is a provision to change login password. modifying branch information. and modifying student information.R. The scope of the project is the system on which the software is installed. This system will also help in evaluating attendance eligibility criteria of a student. modifying student information.1 Overview & Summary:Attendance Management System is a software developed for daily student attendance in schools. adding new student.2 Functional Requirements:The functional requirement of the project is defined under three modules. The purpose of developing attendance management system is to computerized the tradition way of taking attendance. the project is developed as a desktop application. The first module allows the system Administrator(admin) to log into his account and has the privileges to do multiple things some of the include adding a new branch. After that the id is verified and the records of student of particular semester are displayed on the screen. If facilitates to access the attendance information of a particular student in a particular class. No other privileges are given to the student. i. adding a new teacher.e. teachers can also change their password. The second module of the project defines itself in terms of being used by the Teachers. . 4. adding a new subject. and it will work for a particular institute.4.
Software requirementSoftware Interface: Student Attendance management System.3 Non-Functional Requirements: Hardware requirementsHardware Interface 1: The system should be embedded in the PC/Laptop. . Hardware Interface 2: 40 GB hard disk and 256 MB RAM.4.
their goals (represented as use cases). Design and Development 5. Faculty or Student. and any dependencies between those use cases. . GUI 2: Based on the users’ selection on the first screen he is navigated to the other screen on the basis of selection he/she made. 5.1 Design of Project:GUI 1: Main provides the basic navigation access to the user allowing him to choose his login type as Administrator. Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors. Roles of the actors in the system can be depicted.2 Use Case Diagram:A use case diagram in the Unified Modeling Language (UML) is a type of behavioral diagram defined by and created from a Use-case analysis. GUI 3: This screen is the users main work area from the navigation menu the user selects for the operation to be performed and is taken to the respective domain of the project. The main purpose of a use case diagram is to show what system functions are performed for which actor. Use Case diagrams are formally included in two modeling languages defined by the OMG: the Unified Modeling Language (UML) and the Systems Modeling Language (SysML).5.
Fig. Showing Use case Diagram .
3. not how the activities are accomplished. software. data structure or file organization. A Data Flow Diagram is logical model of the system and shows the flow of the data and the flow of logic so this all thing describes what takes place in a proposed system. We have noted that the DFD describes what the flow is rather then how they are processed. There may be a single DFD for the entire system or it may be exploded into various levels.5. The DFD a way of expressing the system in a graphical format in a modular design was developed by Larry Constrains. 2.3 Data Flow Diagram:A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system. It differs from the system flowchart as it shows the flow of data through processes instead of hardware. This DFD is also known as “Bubble Chart” has the purpose to classify the system requirement and to identify the major information that will be a program in system design. so it means the DFD doesn’t depend on the hardware. Context Free Diagram First Level DFD Second Level DFD . 1. DFD consist of a series of symbols joined together by a line.
1 .Fig.Context Free Diagram .
2 – First Level Diagram 5.Fig.5 Entity Relationship Diagram:- .
or mandatory • • The steps involved in creating an ERD are: • • • Identify the entities. The relationship is the interaction between the entities. For example. The cardinality defines the relationship between the entities in terms of numbers. or more simply. verbs are used to label the relationships. by the line connecting the entities. a sales rep could have no customers or could have one or many customers. entities would include not only customers. A relationship may be represented by a diamond shape. if you consider the information system for a business. In the example above. place or event for which data is collected. Determine all significant interactions. In either case. . and the relationships between entities. The entity is represented by a rectangle and labeled with a singular noun. within an information system. and orders as well. Analyze the nature of the interactions. the customer places an order. object. An entity may be optional: for example.An entity-relationship diagram is a data modeling technique that creates a graphical representation of the entities. but the customer's address. so the word "places" defines the relationship between that instance of a customer and the order or orders that they place. The three main components of an ERD are: • The entity is a person.
For example.Entity Relationship Diagram Notations Peter Chen developed ERDs in 1976. For example. Relationships Relationships illustrate how two entities share information in the database structure. Weak Entity Attributes are the properties or characteristics of an entity. an employee's social security number might be the employee's key attribute. . Key attribute A key attribute is the unique. Multivalued attribute A multivalued attribute can have more than one value. an employee entity can have multiple skill values. Entity An entity is an object or concept about which you want to store information. Since then Charles Bachman and James Martin have added some slight refinements to the basic ERD principles. distinguishing characteristic of the entity.
Showing Entity Relationship Diagram .Fig.
Showing Administrator Login Screen . Showing Basic Navigation Menu Fig.6. Snapshots of Project Fig.
Showing Administrator Home Screen Fig.Fig. Showing A Student Registration Page .
Showing A Branch Registration Page . Showing A Faculty Registration Page Fig.Fig.
Fig. Showing A Subject Registration Page .
Showing Faculty Login Screen . Showing Screen to Display Attendance Fig. Screen to Enter Student Attendance Fig.Fig.
Showing Student Login Screen .Fig. Showing Faculty Home Screen Fig.
Showing Student Home Screen .Fig.
Over a period of twenty years. This perception is perpetuated by users submitting problem reports that in reality are functionality enhancements to the system. over 80%. Software maintenance and evolution of systems was first addressed by Meir M.7. a famous and widely cited survey study by Lientz and Swanson. Lehman in 1969. his research led to the formulation of eight Laws of Evolution (Lehman 1997). As they evolve. In the late 1970s. Lehman demonstrated that systems continue to evolve over time. to improve performance or other attributes. Maintenance Software maintenance in software engineering is the modification of a software product after delivery to correct faults. They categorized maintenance activities into four classes: Adaptive – dealing with changes and adapting in the software environment Perfective – accommodating with new or changed user requirements which concern functional enhancements to the software Corrective – dealing with errors found and fixing it . exposed the very high fraction of life-cycle costs that were being expended on maintenance. they grow more complex unless some action such as code refactoring is taken to reduce the complexity. studies and surveys over the years have indicated that the majority. A common perception of maintenance is that it is merely fixing bugs. Key findings of his research include that maintenance is really evolutionary developments and that maintenance decisions are aided by understanding what happens to systems (and software) over time. of the maintenance effort is used for noncorrective actions (Pigosky 1997). However.
an estimate of the lifecycle costs. 7. the tailoring of the post delivery process. And this is the main cause of any problem during software evolution and maintenance. The implementation processes contains software preparation and transition activities. Studies show that contribution of end users are crucial during the new requirement data gathering and analysis. such as the conception and creation of the . Many subsequent studies suggest a similar magnitude of the problem. The software maintenance which can last for 5–6 years after the development calls for an effective planning which addresses the scope of software maintenance. the designation of who will provide maintenance. 7. Preventive – concerns activities aiming on increasing software maintainability and prevent problems in the future. and error correction consumed about 21%.2 Software maintenance processes:This section describes the six software maintenance processes as: 1.1 Software maintenance planning:The integral part of software is the maintenance part which requires accurate maintenance plan to be prepared during software development and should specify how users will request modifications or report problems and the estimation of resources such as cost should be included in the budget and a new decision should address to develop a new system and its quality objectives. So software maintenance is important because it consumes a large part of the overall lifecycle costs and also the inability to change software quickly and reliably means that business opportunities are lost. The survey showed that around 75% of the maintenance effort was on the first two types.
is the retirement of a piece of software. The problem and modification analysis process. The maintenance programmer must analyze each request. obtain all the required authorizations to apply the modifications. Finally. document the request and the solution proposal. 4. for example) is exceptional. If the software must be ported to another platform without any change in functionality. the last maintenance process. which is executed once the application has become the responsibility of the maintenance group. and is not part of daily maintenance tasks. finally. also an event which does not occur on a daily basis. by confirming the modified work with the individual who submitted the request in order to make sure the modification provided a solution. 5. The process considering the implementation of the modification itself. 3. and. and the follow-up on product configuration management. The process acceptance of the modification.maintenance plan. confirm it (by reproducing the situation) and check its validity. 2. this process will be used and a maintenance project team is likely to be assigned to this task. The migration process (platform migration. 6. . investigate it and propose a solution. the preparation for handling problems identified during development.
The primary concern is the compatibility of individual modules.1 System Testing:- Testing System testing is a critical aspect of Software Quality Assurance and represents the ultimate review of specification. The software must be executed several times in order to find out the errors in the different modules of the system. . but rather than integration of each module in the system. design and coding. Testing is the vital to the success of the system. A good test is one that has a probability of finding an as yet undiscovered error. Testing and validation are the most important steps after the implementation of the developed system. One has to find areas where modules have been designed with different specifications of data lengths. For this every module of the program is executed to find an error. The system testing is performed to ensure that there are no errors in the implemented system. Testing is a process of executing a program with the intent of finding an error. In unit testing step each module has to be checked separately. Nothing is complete without testing. System testing does not test the software as a whole.8. the examination of the specifications stating what the program should do and how it should perform under various conditions. To perform specification test. Unit testing focuses first on the modules in the proposed system to locate errors. In the code testing the logic of the developed system is tested. 8. This enables to detect errors in the coding and logic that are contained within that module alone. The purpose of testing is to identify and correct bugs in the developed system. Those resulting from the interaction between modules are initially avoided. type and data element name.
in order to find out the errors. because of the use of a number of hard disks.Validation refers to the process of using the new software for the developed system in a live environment i. Testing may be done at 4 levels: Unit Level Module Level Integration & System Regression .. The test has revealed that the new software for the agency is capable of handling the demands at the peak time. The proposed software has the required storage space available. In this phase the software developed Testing is exercising the software to uncover errors and ensure the system meets defined requirements. It will be come to know about the practical difficulties the system faces when operated in the true environment. Performance Time Testing: This test determines the length of the time used by the system to process transaction data. Storage Testing: This determines the capacity of the new system to store transaction data on a disk or on other files. new software inside the organization. there are some special tests conducted which are given below: Peak Load Tests: This determines whether the new system will handle the volume of activities when the system is at the peak of its processing demand. The validation phase reveals the failures and the bugs in the developed system. A specification test is conducted to check whether the specifications stating the program are performing under various conditions. Apart from these tests.e. the logic of the program can be examined. By testing the code of the implemented software.
1. Unit testing may use Test Drivers. which replace low-level modules.1. This testing includes testing of control paths.4 REGRESSION TESTING:Each modification in software impacts unmodified areas. Unit testing focuses on verification of the corresponding class or Screen. System testing is used to verify. logical decisions.1. and Test stubs. and error handling. 8. which results serious injuries to that software. interfaces. local data structures. So the process of re-testing for rectification of errors due to modification is known as regression testing.3 INTEGRATION & SYSTEM TESTING:- Integration testing is used to verify the combining of the software modules.2 MODULE LEVEL TESTING:- Module Testing is done using the test cases prepared earlier. boundary conditions.1. Integration testing addresses the issues associated with the dual problems of verification and program construction. Module is defined during the time of design. which are control programs to coordinate test case inputs and outputs. whether the developed system meets the requirements. 8.1 Unit Testing:- A Unit corresponds to a screen /form in the package. .8. 8. A stub is a dummy subprogram.
. The system solves the problem. Conclusion The Attendance Management System is developed using Java Servlets and fully meets the objectives of the system which it has been developed. The system has reached a steady state where all bugs have been eliminated. The system is operated at a high level of efficiency and all the teachers and user associated with the system understands its advantage. It was intended to solve as requirement specification.9.
java.sun. Java servlet programming bible . Access 2010 .Suresh Rajagopalan 4. Reference Books:1. Java servlet programming . Software Engineering – Roger Pressman Websites:1.www.Database Software and Applications .com/doc/servlet-essentials/ 3.office. Servlet Essentials . William Crawford 3.Jason Hunter. The complete Reference Java 2.com/en-us/access .microsoft.com/j2ee/tutorial/1_3fcs/doc/Servlets.html 2.novocode.Microsoft Office . Java Servlet Technology .10.
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 reading from where you left off, or restart the preview.