STUDENT ATTENDANCE MANAGEMENT SYSTEM Submitted by
SHUBHANGI S DESAI ANIL H PATEL
Submission Date: 14th June 2010
Sector 23 Near Gh-6 Bus stand, Gandhinagar
1.1 1.2 Profile Project Detail
2. 3.1 3.2 3.3 3.4 3. 4.1 4.2 4.3 5. 6. 7. 8. 9. 10. 12. Existing System
Limitations of the Existing System
Proposed System Advantages of Proposed System Feasibility Study Operational Feasibility Technical Feasibility Economic Feasibility Environment Specifications Fact finding Techniques Requirement Specifications Development Strategies E-R Diagram Data Flow Diagram Data Base Schema
Desai (Roll No : 11) Anil H. Office Staff and Faculties
Developed By :
Shubhangi S. Patel (Roll No : 34)
.Project Title :
Student Attendance Management System
Developed For :
S K Patel Institute of Management & Computer Studies
Development of fully functional Desktop Application system that maintains all the attendance of institute’s MCA program Students and generates desired attendance reports.
If facilitates to access the attendance information of a particular student in a particular class. Another purpose for developing this software is to generate the desired reports automatically at the end of the session or in the between of the session as they require.PROJECT DETAILS
• What is Attendance Management System?
Attendance Management System is software developed for daily student attendance in schools.
• Purpose & Scope:The intention of developing “Attendance Management System” is to computerized the tradition way of taking attendance. This project is basically a desktop application which means self contained software runs on the system on which it has been installed under the user control and it will work for a particular institute or college only.
. This system will also help in evaluating attendance eligibility criteria of a student. The information is sorted by the operators. colleges and institutes. which will be provided by the teacher for a particular class.
For this application we have provided the following modules and features. Admin ○ Add & Modify details of student faculty subject (if required) Office Staff ○ Generate various types of reports ○ Send notice to black listed Students Faculty ○ Attendance on basis of subject day by day ○ Check various generated Reports
The type of the system any institute uses always plays an important role in management of the institute. the easier would be the management tasks
Since the existing Attendance Management System of the Institute is totally working manually. All the Information’s are handled manually in the registers or other documents.
The process of the work is mainly divided in two parts. And then at the end of the session or semester attendance is calculated manually & reports are generated. efficiency and accuracy of the system. first is to take attendance on sheet & enter details into the registers. Better the form.
there is always a possibility of occurrence of errors means accuracy is less which may lead in many problems
. So the wastage of time occur the most over here. This process is a tedious process when there are many records ➢ Each & every organizations want their work to be done accurately. time makes a huge sense. ➢ There are large amount of data. accessing any data from the manual system is very difficult. these data can be accessed by anyone and even they can modify any important data. ➢ Security of data is less in manual systems. they have very efficient employees who can work accurately. Therefore. Moreover. nobody can afford wasting precious time. This employee could be used for some other productive work for organization.LIMITATIONS OF THE EXISTING SYSTEM
➢ The Current system is completely manual. in today’s do or die world. But. This because majority of the records are stored as statements or in registers. ➢ Daily reports of the system are done manually so it is more time consuming & one person of the organization is reserved with this work so it is also wastage of the human resource. In today’s circumstances where there is cut-throat competition. The employee would have to go through each and every record sequentially until they find the required data. For this purpose.
This Application is built for automating the processing of attendance. It also enhances the speed of the performing attendance task easily.
A Faculty has to login to the system & then in the attendance option they have to select appropriate class. So this kind of various reports can be generated
. This will add the selected students as present student in that particular session. semester and subject. 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. It also generates periodic reports to keep a check on the students who are regular & who are not. Office staff can also generate black list of students who have attendance less than 50% or 80%. So this will display the list of the students who are eligible to appear in this 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.
So it saves the time utmost. This also saves a lot of time. The work becomes easy for the employees and thus. some amount of human resources is saved. ➢ Complexity of the work can be reduced by using the system which was not possible in manual or semi-automated system. Accurate information can be achieved within a short span of time ➢ Data can be accessed easily and randomly.ADVANTAGES OF THE PROPOSED SYSTEM
➢ A Computer can work more efficiently then compared to a human being. ➢ Data accuracy is maintained.
. ➢ Data is protected with the help of login system. unauthorized persons cannot access the data. Because of this login system.
It is cost effective in the sense that has eliminated the paper work completely. The result obtained contains minimum errors and are highly accurate as the data is required. User requires no special training for operating the system.FEASIBILITY STUDY
• Feasibility Study
A feasibility study is a short.
. The system is also time effective because the calculations are automated which are made at the end of the month or as per the user requirement. focused study.
➢ Behavioral Feasibility
The system working is quite easy to use and learn due to its simple but attractive interface. which aims to answer a number of questions • • • Does the system contribute to the overall objectives of the Organization? Can the system be implemented using current technology and within given cost and schedule constraints? Can the system be integrated with systems which are already in place?
➢ Economically Feasibility
The system being developed is economic with respect to School or Collage’s point of view.
➢ Technical feasibility
The technical requirement for the system is economic and it does not use any other additional Hardware and software.
According to the requirements the system should minimum generate following kinds of reports. List of report is give below
Semester wise Attendance Daily Attendance Attendance for extra class Subject wise attendance Leave reports ○ Approved ○ Not approved ○ Medical leaves Black listed below 50% Black listed below 75%
ENTITY RELATIONSHIP DIAGRAM
-An entity-relationship diagram is a data modeling technique that creates a graphical representation of the entities. place or event for which data is collected. but the customer's address. The relationship is the interaction between the entities.
The steps involved in creating an ERD are: • • •
. if you consider the information system for a business. or mandatory Identify the entities. In either case. or more simply. Analyze the nature of the interactions. within an information system. the customer places an order. a sales rep could have no customers or could have one or many customers. and the relationships between entities. entities would include not only customers. object. A relationship may be represented by a diamond shape. so the word "places" defines the relationship between that instance of a customer and the order or orders that they place. by the line connecting the entities. verbs are used to label the relationships. For example. The cardinality defines the relationship between the entities in terms of numbers. In the example above. The three main components of an ERD are: • The entity is a person. An entity may be optional: for example. The entity is represented by a rectangle and labeled with a singular noun. Determine all significant interactions. and orders as well.
an employee entity can have multiple skill values.
Multivalued attribute A multivalued attribute can have more than one value.
Key attribute A key attribute is the unique. an employee's social security number might be the employee's key attribute. For example. For example. Since then Charles Bachman and James Martin have added some slight refinements to the basic ERD principles. distinguishing characteristic of the entity.
Entity An entity is an object or concept about which you want to store information. Weak Entity Attributes are the properties or characteristics of an entity.Entity Relationship Diagram Notations
Peter Chen developed ERDs in 1976. Relationships Relationships illustrate how two entities share information in the database structure.
Entity Relationship Diagram
data structure or file organization. Second Level DFD
. First Level DFD 3. DFD consist of a series of symbols joined together by a line. We have noted that the DFD describes what the flow is rather then how they are processed.
1. There may be a single DFD for the entire system or it may be exploded into various levels. software. 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. 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. The DFD a way of expressing the system in a graphical format in a modular design was developed by Larry Constrains.DATA FLOW DIAGRAM
A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system. not how the activities are accomplished. It differs from the system flowchart as it shows the flow of data through processes instead of hardware. so it means the DFD doesn’t depend on the hardware. Context Free Diagram 2.
Context (Zero) level diagram
First level diagram
. A data dictionary contains a list of all files in the database. Without a data dictionary. and the names and types of each field. the number of records in each file. a database management system cannot access data from the database. however. Most database management systems keep the data dictionary hidden from users to prevent them from accidentally destroying its contents.DATA DICTIONARY
In database management system Data Dictionary is a file that defines the basic organization of a database. Data dictionaries do not contain any actual data from the database.
7. 3. NO 1. Login Table
Description: Login table stores details for authentication
SR. 2. NO 1. FIELD NAME faculty_id faculty_name contact_details Username DATA TYPE varchar2(5) varchar2(50) varchar2(40) Varchar2(30) Foreign Key DESCRIPTION Primary Key
. 5. 2.1. 2 3. 4. 4. FIELD NAME stud_id Stud_name Address contact_details Course Semester Batch DATA TYPE varchar2(5) varchar2(40) varchar2(50) varchar2(12) varchar2(3) number varchar2(9) eg : 2009-2012 DESCRIPTION Primary Key
3. NO 1. 6. Faculty details
Description: Stores faculties’ details
SR. FIELD NAME Username Password Usertype DATA TYPE varchar2(30) varchar2(20) varchar2(10) DESCRIPTION Primary Key
2. 3. Student details
Description: Stores students’ details
2 3.4. Office staff details
Description: Stores office staff members’ details
SR. NO 1. FIELD NAME staff_id member_name designation Username DATA TYPE varchar2(5) varchar2(50) varchar2(40) Varchar2(30) Foreign Key DESCRIPTION Primary Key
2 3. FIELD NAME attend_id Date Time DATA TYPE varchar2(5) date/time varcahr2(10) DESCRIPTION Primary Key
.5. Subject details
Description: Stores attendance details for the extra classes taken
SR. 2 3. FIELD NAME sub_code sub_name semester DATA TYPE varchar2(5) varchar2(50) varchar2(5) DESCRIPTION Primary Key
7. 4. 5. NO 1. Extra Class Attendance details
Description: Stores attendance details for the extra classes taken
SR. NO 1. sub_code varchar2(5) DESCRIPTION Primary Key
6. 2 3. FIELD NAME attend_id Date Time faculty_id present_students DATA TYPE varchar2(5) date/time varcahr2(10) varchar2(5) varchar2(MAX) All the present students’ id are stored as a string Eg : “1-2-5-8-1011” 6. NO 1. Attendance details
Description: Stores attendance details
4. 5. Leave details
Description: Stores leave details
SR. 5. : Medical or General Approved – True Not Approved – False DESCRIPTION Primary Key
8.e. FIELD NAME Leave_id Date From_date to_date Stud_id Type Status DATA TYPE varchar2(5) date/time Date/time Date/time varchar2(5) varchar2(10) Boolean i. 6. 2 3. NO 1.
varchar2(5) varchar2(MAX) All the present students’ id are stored as a string Eg : “1-2-5-8-1011”