You are on page 1of 41

INDEX

S.No.

TOPIC

1.

Introduction

1.1 Organization Profile 1.2 Project Overview 1.3 Purpose 1.4 Scope 1.5 Project Objectives 1.6 Introduction to wamp

2. Literature Review

2.1 Introduction 2.2 Literature Review of Requirement 2.3 Literature Review of Attendance management system 2.4 Literature Review of Software Development Process 2.5 Literature Review of

Attendance System 2.6 Literature Review of Tools

3. Problem Statement

3.1 Background of Problem 3.2 Statement of Problem 3.3 Existing system 3.4 Need for the system 3.5 Problem definition

4. Describing how you solved the problem

4.1 Data Flow Diagram 4.2 Internal Design 4.3 Entity Relationship Diagram 4.4 Use Case Description 4.5 External Design

5. Testing and Result

5.1 System Testing

6. Conclusion

6.1 Project Summary 6.2 Project And Limitation 6.3 Recommendation For Future project

7. References

Chapter 1 INTRODUCTION

1.1 ORGANISATION PROFILE

1.2 PROJECT OVERVIEW

Attendance Management System is a software developed for daily student attendance in schools, 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. The student attendance management system is a cost and time effective computerized system that maintains daily attendance of students on the basis of their attendance in theory and laboratory courses opted by them. The students are offered various theory and practical subjects depending upon the ongoing semester. The system maintains student details, the subjects opted by them, their attendance in a particular subject and details of the faculty member teaching them. The system also generates summary reports of all these details. Administrator is responsible for creating users, updating their details and maintaining the database. Every faculty has a unique login id and password, provided by the university/college through which it faculty updates the attendance. The intention of developing Attendance Management System is to computerized the tradition way of taking attendance. 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. 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 Application is built for automating the processing of attendance. It also enhances the speed of the performing attendance task easily. It also generates periodic reports to keep a check on the students who are regular & who are not. A Faculty has to login to the system & then in the attendance option they have to select appropriate class, semester and subject. So this will display the list of the students who are eligible to appear in this session. 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. This will add the selected students as present student in that particular session.

1.3 PURPOSE

The purpose of developing attendance management system is to computerized the tradition way of taking attendance. Another purpose for developing this software is to generate the report automatically at the end of the session or in the between of the session

1.4 SCOPE

The scope of the project is the system on which the software is installed, i.e. the project is developed as a desktop application, and it will work for a particular institute. But later on the project can be modified to operate it online.

1.5 Project Objectives

The project objectives are: i. ii. To study and analyze the existing attendance system in colleges or schools. To create a good requirement model of Attendance Management System for schools or colleges. iii. To design and build a prototype of Attendance Management System.

1.5 Introduction to WAMP

Before moving to the implementation of the project, it would help, to briefly go through the main features of the WAMP.

What is WAMP?

WAMP packages are a collection of free software that enables you to easily setup a web site on a server or PC running windows. Most packages use the principal software Apache, MySQL, and PHP. Some packages substitute Perl or Python for PHP.The name WAMP is derived from its four principal components Windows, Apache, MySQL, and PHP. You provide the windows OS and the package provide the other components. WAMP packages support most versions of the Microsoft's Windows operating systems. Apache is web server software that host web sites and make them accessible by web browsers. MySQL is a relational database engine. PHP is a scripting language that can be used for more than coding web pages. A WAMP created website can be setup to be accessed locally on your PC, across a network, intranet, and even the Internet. Most WAMP are not secure. Their security settings are not considered secure enough to prevent its sites from being hacked. Only use them locally until you learn how to make them safe and secure. There are numerous providers of WAMP packages. Each differs in their installation, administration, and included software. Some provide Perl or Python instead of PHP for the scripting language. On this web page I've include a short list of WAMP packages. There are many others available. In addition, there are Linux versions called LAMP and MAC versions call MAMP.

Uses for a WAMP


Developing websites. Personnel training in Apache, MySQL, PHP and other software supported by WAMP Running your own personnel WAMP compatible applications. Such as Wikipedia. Evaluating various Apache, MySQL, and PHP applications

WAMP has following main components named as: Apache MySQL

APACHE The Apache HTTP Server is web server software notable for playing a key role in the initial growth of the World Wide Web. Apache is developed and maintained by an open community of developers under the auspices of the Apache Software Foundation. The application is available for a wide variety of operating systems, including Unix, GNU, FreeBSD, Linux, Solaris, Novell NetWare, Mac OS X, Microsoft Windows, OS/2, TPF, and eComStation. Released under the Apache License, Apache is characterized as open source software. Apache supports a variety of features, many implemented as compiled modules which extend the core functionality. These can range from server-side programming language support to authentication schemes. Some common language interfaces support Perl, python and PHP. A sample of other features include SSL and TLS support, a proxy module, a URL rewriter, custom log files and filtering support. Apache features configurable error messages, DBMS-based authentication databases, and content negotiation. It is also supported by several graphical user interface (GUIs). Apache is primarily used to serve both static content and dynamic Web pages on the World Wide Web. Many web applications are designed expecting the environment and features that Apache provides. Apache is used for many other tasks where content needs to be made available in a secure and reliable way.

MySQL

MySQL is a relational database management system (RDBMS). MySQL has made its source code available under the terms of the GNU General Public License, as well as under a variety of proprietary agreements. MySQL is often used in free software projects that require a full-featured database management system. Though MySQL began as a low-end alternative to more powerful proprietary databases, it has gradually evolved to support higher-scale needs as well. Much of MySQLs appeal originates in its relative simplicity and ease of use, which is enabled by an ecosystem of open source tools such as phpMyAdmin that is ready-touse without manual configuration or setup.

Chapter 2 LITERATURE REVIEW

2.1 INTRODUCTION

A literature review is an analysis of published information that researchers have written on a certain topic. It is expressed according to issues or problems that the researchers wish to address.

2.2 LITERATURE REVIEW OF REQUIREMENT

A requirement described as a statement of what the system must do or what characteristic it must have. It is a function or characteristic of a system that is necessary, the quantifiable and verifiable behaviors that a system must possess and constraints that a system must work within to satisfy an organization's objectives and solve a set of problems.Similarly, requirement also defined as a condition or capability needed by a user to solve a problem or achieve an objective or must be met or possessed by a system to satisfy a contract, standard, specification, or other documents. Requirement is divided into two categories which are as follows: functional requirement non-functional requirement

Functional Requirements:-

The functional requirement of the project is defined under threemodules. The first module allows the system Administrator(admin) tolog into his account and has the privileges to do multiple things some of the include adding a new branch, adding a new subject, adding a new teacher adding new student, modifying student information ,modifying branch information , and modifying student information,also there is a provision to change login password .The second module of the project defines itself in terms of being used by the Teachers; Teachers have to enter their loginid and password in system. After that the id is verified and the records of student of particular semester are displayed on the screen. Teacher now mark the attendance of student who is present in class, teacherscan also change their password .The third
module of the project allows the students to log into the system and view their current attendance statistics. No other privileges are given to the student.

Non functional requirement:-

Hardware and Software Requirements: Minimum Required Hardware Configuration: Pentium III or more 64 MB of RAM or more

Required Software Configuration: Browser like Internet Explorer or other

2.3 Literature Review of Attendance System

According to Epstein & Sheldon, reducing the rates of student chronic absenteeism has been and continues to be a goal of many schools and school systems. In 1999, a student tracking system involving a database is being trialed in govenment and non-government schools Westen Australia (Bourke, Rigby & Burden, 2000). The student tracking system involved a set of processes, procedures and systems which can identify and monitor the location of students.

In the Torres Strait schools, they used a system called Student Information Management System (SIMS). The SIMS provides a good quality data regarding student attendance. This computer-based system collates individual class attendance records on a weekly basis.

The relationship between staff and parents was seen as vitally important by parents and principals. The student survey results indicated that attendance levels were significantly higher among students when teachers got in touch with their parents to talk about how they were going at school Therefore, in schools where students have attendance problems, school staff may need to go beyond the school building to involve parents in reducing absenteeism

2.4 Literature Review of Software Development Process

Software Development is an activity of creating a software system that when used, solves some users' problems, leverages their opportunities, or satisfies their needs. Classic software development follows a well-defined series of phases, traditionally called a waterfall model. More recently, software development is performed iteratively where development activities are repeated multiple times, resulting in a time series of successively more sophisticated products .

There are many views of software's development or development process though that has evolved over the years. What follows is a brief discussion of the theories of the software development process that recently used today. The first formal description of the software development process model is published in 1970 by Winston W. Royce. Refer Figure.

REQUIREMENT ANALYSIS AND SPECIFICATION

DESIGN

CODING

TESTING

IMPLEMENTATION AND MAINTANANCE

According to Royce (1970), firstly, developer must analyze user requirements. After that, make requirement specifications by clearly set out necessary features of system based on user requirement. Then, developer can design a suitable solution and do implementation by develop the proposed solution. In addition, developer must test the system to ensure that the solution solves the original problem and works in context. Lastly, developer must maintain the system.

2.5 Literature Review of Attendance System

According to Epstein & Sheldon reducing the rates of student chronic absenteeism has been and continues to be a goal of many schools and school systems. In 1999, a student tracking system involving a database is being trialed in govenment and non-government schools Westen Australia.The student tracking system involved a set of processes, procedures and systems which can identify and monitor the location of students. In the Torres Strait schools, they used a system called Student Information Management System (SIMS). The SIMS provides a good quality data regarding student attendance. This computer-based system collates individual class attendance records on a weekly basis (Bourke, Rigby & Burden, 2000). The relationship between staf and parents was seen as vitally important by parents and principals. The student survey results indicated that attendance levels were significantly higher among students when teachers got in touch with their parents to talk about how they were going at school (Bourke, Rigby & Burden, 2000). Therefore, in schools where students have attendance problems, school staf may need to go beyond the school building to involve parents in reducing absenteeism (Epstein & Sheldon, 2002).

2.6 Literature Review of Tools


I have decided to choose Macromedia Dreamweaver MX, and easyPHP 5.3.2 as tools in this study. The description of these tools is as follows:

Macromedia Dreamweaver MX Dreamweaver MX is poised to bring dynamic application development to the masses. Dreamweaver MX offers easy-to-use tools that can very quickly connect to databases and Web pages in a logical and visual manner. Dreamweaver can design interactive sites on Windows and Macintosh computers, but deploy the appropriate code to run the sites on UNIX, Linux, BSD, Windows, Macintosh, and dozens of other operating systems. It combining the power of the full HTML language and an interface that made publishers and designers feel at home, it brought cross platform HTML development to the world. With HTML in the hands of the masses, Web page design is available to anyone. This has pushed the elite HTML programmers to

move onward and upward to the next big thing. This big thing is creating sites that interact with the users. Dreamweaver MX supports five server technologies (JSP, CFML, ASP, PHP, and ASP.NET) with the capability to expand to new technologies through plug-ins. Dreamweaver MX offers the designer the ability to preview data in real-time within a document design. It makes life even easier by allowing the person designing the application logic to work on the database side while designers work on the page layout (Ray, 2002).

EasyPHP 5.3.2 Easy PHP is a software application written in dynamic PHP language that combines an Apache web server and MySQL database to create flexible web development tools. Apache is an open source web server. Web servers use hypertext transfer protocol (http) to enable a computer user to connect to the Internet. MySQL is an open source database that organizes information through tables and enables interactions between the user and the web through the creation of dynamic web pages.

Chapter 3 PROBLEM STATEMENT

3.1 Background of Problem

A generation ago, either in principle or in practice, attendance was not optional .Today often in principle and almost in practice, it is optional (Romer,1993). According to Lim, Sim and Mansor (2009), most educational institutions administrators are concerned about student irregular attendance. Shendell et al. (2004) defines it can affect student in overall academic performance. Romer (1993) found that attendance did contribute significantly to the academic performance of students. There is a slightly stronger relationship between attendance and performance. Also, Durden & Ellis (1995) conclude that attendance does matter for academic achievement. Thus, it makes student attendance mandatory in schools or colleges(Romer,1993), (Woltz,1955). Yet, almost everyone noticed that attendance in schools is far from perfect (Romer, 1993). There is a lack of school attendance data and a lack of consistency in the definition and measurement of non-attendance (Bourke, Rigby & Burden, 2000). Large schools or colleges are more likely to have problems with student attendance than small ones (Epstein & Sheldon, 2002). Everyday schools or colleges staff spends much time to handle student's attendance. There are many problems when recording data manually (Richard, 2005). Sometimes, the attendance's record books were missing. In real situation, it is hard for school or colleges staff to search student's record by looking at attendance's record books one by one. School staff usually spend much time to find the student's record especially when there are many classes in the school. Furthermore, parents may miss to get any information or letter from schools when their children didn't attend to school. According to Epstein & Sheldon (2002), high school staff's communications with parents about attendance can increased student attendance and reduced chronic absenteeism.

Hence, by creating attendance system is one of the best solutions to address this problem. The system should help faculty to take attendance for student. It must make the process of taking the attendance easier, faster and secure as compared to conventional method. The conventional method of taking attendance by calling names or signing on paper is very time consuming, inefficient, and insecure (Ervasti, Isomursu, & Kinnula, 2009), (Lim, Sim & Mansor, 2009). It is a one way that helps teachers or school staf reducing the taken time to carry out routine processes and enable them connected with parents by sending real-time information on their children's attendance immediately if students are not-attended to school more than the limit. Thus, teachers has more time for teaching. (Ervasti, Isomursu, & Kinnula, 2009).

3.2 Statement of Problem


Based on background of problem, several problems have been identified. i. To set up the first requirement models of student attendance monitoring systems in secondary school. The requirement model must meet the user needs, goals and constraints. ii. The conventional method of taking attendance is very time consuming, inefficient and insecure. So, attendance system can assist to solve the problem of conventional method. It is important to identify characteristics, features, relations and design implications to design a good SAMS. iii. User acceptance testing is important to validate user's understanding and satisfaction to the developed system. User acceptance can be test by showing prototype to user under study. Hence, a prototype should be design and develop.

3.3 Existing System


In existing system all the information is handled manually,and so that it is tedious to manage all the records of faculty,students and the courses details.For a minor changes in records administrator has to manage all the files related to that record. The work flow in the existing system is explained in the following points: Existing courses recorded in the files or registered and for any query Admin has to check all the records. Information is stored in many registered,so the same information is to be written so many times.

Faculties or Students details are managed manually and at different records files.If there is any minor change to be done, we have to change the records at many places. Generating reports is tedious work when we do it manually. There are many files to store the records and so while generating reports all file is search.

3.4 Need for the system


The current system is unable to handle information and data as the size of the records expands day by day. The current system finds it difficult to maintain information of the registered and not registered courses, assets of the organization, staff details etc.

Some of the major problems that arise in the current system are: There are limited storage capacities of the registers maintaining records of the institute assets and other information as it expand day by day. It is easier to maintain the records in computer as only one time insertion is required for the information and that record automatically available for other purposes. Information about courses that is the existing courses is not managed efficiently manually as after some duration of course the new Course will also treated as the existing course and records are updated at different files while in proposed system this will done Automatically. There is always updating in software and the records are also maintained,but manually it may be erroneous to update the records so, it becomes important to automate the system in such a way that all the processes are performed by the proposed system.

3.5 Problem definition:

Manually organized files and registers are used to store information related to existing courses ,new courses ,faculty details and student details taking attendance other information. In the absence of an attendance management system it is hard to organize , maintain and taking attendance.

Chapter 4 DESCRIBING HOW YOU SOLVED THE PROBLEM (Design and Implemenation)

4.1 Data Flow Diagram


A DFD, also known as a bubble chart has the purpose of clarifying system requirements and identifying major transformations that will become programs in system design. So, it is the starting point of the design place that functionally decomposes the requirements specification down to the lowest level of detail. A DFD consists of a series of bubbles joined by data flows in the system. It is very useful to make user understand the working of the system. Symbols used in DFD: SYMBOL MEANING

the

External entity (any source or destination of the data which is external to the system).

Process (How flow of data is transformed).

Data Flow (It is actually data in motion).

Data store (Data at rest or temporary repository of data).

0-level DFD

ADMIN

Login update information

STUDENT ATTENDANCE MANAGEMENT SYSTEM

login respond

FACULTY

1-level DFD

1 LOGIN LOGIN

2 ADD FACULTY DETAILS ADMIN

FACULTY_MASTER,FACULTY_ EXPERTISE,BATCH_FACULTY

3 ADD STUDENT DETAILS STUDENT_MASTER

4 ADD NEW COURSE

4.2 Database Design:

Database design involves in identifying the data elements and defining the data structures appropriate to hold them. It may also specify the data storage and outlines that are required to access them. The data structures in this system are tables, grouped in the database. The structure of the various tables is as follows.

Table No. Table Name

: :

1 BATCH TABLE

Field B_id Batch_name

Type int(10) Varchar(10)

Key Primary key -

Description Batch ID Duration of batch

Table No. Table Name

: :

2 SEM MASTER TABLE

Field Sem_id Sem_name

Type int(10) Varchar(50)

Key Primary key -

Description Semester ID Name of semester

Table No. Table Name

: :

3 SEM SUBJECT MASTER TABLE

Field Sem_id

Type int(10)

Key -

Description Foreign key of sem master table Subject ID University subject ID Name of subject Theory record Lab record

Subject_id Univ_subject_id Subject_name Theory Lab

int(10) Varchar(20) Varchar(50) tinyint(1) tinyint(1)

Primary key -

Table No. Table Name

: :

4 FACULTY MASTER TABLE

Field Fac_id Fac_name Address Email Mobile_no Qualification

Type int(10) Varchar(50) Varchar(255) Varchar(50) Varchar(15) Varchar(255)

Key Primary key -

Description Faculty ID Name of faculty Address of faculty Email of faculty Mobile no of faculty Qualification of faculty

Table No. Table Name

: :

5 FACULTY TABLE

Field Fac_id

Type int(10)

Key Primary key

Description Foreign key of faculty master table Foreign key of sem subject master table

Sub_id

int(5)

Primary key

Table No. Table Name

: :

6 BATCH FACULTY TABLE

Field Sr_no Fac_id

Type Int(10) Int(10)

Key Primary key -

Description Serial no Foreign key of faculty master table Foreign key of batch table Foreign key of sem master table Foreign key of sem subject master table

B_id

Int(10)

Sem_id

Int(10)

Subject_id

Int(10)

Table No. Table Name

: :

7 STUDENT MASTER TABLE

Field Stud_id Name Roll_no Permanent_address

Type Varchar(15) Varchar(50) Varchar(50) Varchar(255)

Key Primary key -

Description student ID Name of student Rollno of student Permanent address of student Corresponding address of student Mobile no of sudent Landline no of student Email of student Foreign key of batch table Date of birth 10th % of student 10th board of student 10th pass year of student 12th % of student 12th board of student 12th pass year of student Graduate percentage Stream name College of student

Corr_address

Varchar(255)

Mobile _no Landline_no

Varchar(15) Int(15)

Email B_id

Varchar(50) int(10)

d.o.b X% x_board X_pass_year

Varchar(20) double(5,2) Varchar(50) Year(4)

Xii% Xii_board Xii_pass_year

Double(5,2) Varchar(50) Year(4)

Grad% Stream College

Double(5,2) Varchar(50) Varchar(255)

University Grad_pass_year

Varchar(255) Year(4)

University of student Grad pass year of student Current mca %

Current_mca%

Double(5,2)

Table No. Table Name

: :

8 STUDENT ATTENDANCE TABLE

Field

Type

Key

Description

Stud_id

Varchar(15)

Primary key

Foreign key of student master table Date of attendance Foreign key of slot master table Foreign key of faculty master table Foreign key of sem subject master table Theory attendane Lab attendance

Date Slot_id

Date Varchar(10)

Primary key Primary key

Fac_id

Int(10)

Subject_id

int(10)

Theory_attn lab_attn

tinyint(1) Tinyint(1)

Table No. Table Name

: :

9 SLOT MASTER TABLE

Field

Type

Key

Description

Slot_id Time

Varchar(10) Varchar(50)

Primary key -

Slot ID Duration of lecture

4.3 Entity Relationship (E-R) Diagram


The entity-relationship (E-R) data model is based on a perception of a real world that consists of a collection of basis objects, called entites and of relationships among these objects. An entity is a thing or object in the real world that is distinguishable from other objects. For example, each person is an entity and bank accounts can be considered as entities. A relationship is an association among several entities. The set of all entities of the same type and the set of relationships of the same type are termed an entity set and relationship set respectively. The overall logical structure (schema) of a database can be expressed graphically by an E-R diagram, which is built up from following components: Rectangles, which represent entity sets. Ellipses , which represents attributes. Diamonds, which represents relationships among entity sets. Lines, which link attributes to entity sets and entity sets to relationships. Each component is labeled with the entity or relationship that it represents.

REPRESENTATIONS:

The following representation are used for representing the relationships:

1 Entity 1

relation

&

* Entity 2

Here, the relationship type shown is one to many from Entity 1 to Entity 2.

ENTIY RELATIONSHIP DIAGRAM

Qualification

Fname Address

Fac_id faculty Mobile no. Email type

username

password

LOGIN details Stud_id

Name Batchid

Course has takes Add new

Students details

Address

Mobile no. Add new

Fac_id Slots Lab_attn Attendance details teachs Sub_id

ADMIN

Theory_attn Add new

Lab Subject details

Theory

Semid

Subid

Sub_name

4.4 Use Case Description

Use case description is a detailed specification of a use case. Use case specification is used to textually describe the sequence of steps of each interaction between the actor and the use case (Whitten et.al., 2001).

There are many use case description for this requirement model; like login, verifying, reg, manage student info, insert info, search, register class, get notification, register student, manage student info, view attendance, manage attendance, manage absent reason, update info, logout, and forum.

Figure shows the simple use case diagram for attendance management system

USE CASE DIAGRAM

ADD STUDENT RECORD

MODIFY STUDENT RECORD

LOGIN

ADMIN UPDATE ATTENDANCE

FACULTY

VIEW ATTENDANCE RECORD

4.5 EXTERNAL DESIGN

Chapter 5 TESTING

5.1 System Testing

System testing is a critical aspect of Software Quality Assurance and represents the ultimate review of specification, design and coding.Testing is a process of executing a program with the intent of finding an error. A good test is one that has a probability of finding an as yet undiscovered error. The purpose of testing is to identify and correct bugs in the developed system. Nothing is complete without testing.Testing is the vital to the success of the system.In the code testing the logic of the developed system is tested. For this every module of the program is executed to find an error. To perform specification test, the examination of the specifications stating what t h e p r o g r a m s h o u l d d o a n d h o w i t s h o u l d p e r f o r m u n d e r v a r i o u s conditions.Unit testing focuses first on the modules in the proposed system to locate errors. This enables to detect errors in the coding and logic that are cont ai ned wi t hi n t hat m odul e al one. Thos e res ul t i ng f rom t he interaction between modules are initially avoided. In unit testing step each module has to be checked separately. System testing does not test the software as a whole, but rather than integration of each module in the system. The primary concern is the co m pat i bi l i t y of i ndi vi dual m odul es. One has t o fi nd areas wh ere m od ul es have been desi gned wi t h di ffer ent speci fi c at i ons of dat a lengths, type and data element name. Testing and validation are the most important steps after theimplementation of the dev eloped system. The system testing is performed to ensure t h a t there are no e r r o r s i n t h e i m p l e m e n t e d system. The software must be executed several times in order to find out the errors in the different modules of the system Validation refers to the process of using the new software for the developed system in a live environment i.e., new software inside the organization, in order to find out the errors. The validation phase reveals the failures and the bugs in the developed system. It will become to know about the practical difficulties the system faces when operated in the true environment. By testing the code of the implemented software, the logic of the program can be examined. A specification test is conducted to check whether the specifications stating the program are performing under various conditions. Apart from these tests, 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 test has revealed that the new software for the agency is capable of handling the demands at the peak time. Storage Testing: This determines the capacity of the new system to store transaction data on a disk or on other files. The proposed software has the required storage space available, because of the use of a number of hard disks. Performance Time Testing: This test determines the length of the time used by the system to process transaction data .In this phase the software developed Testing is exercising thesoftware to uncover erro rs and ensure the system meets definedrequirements. Testing may be done at 4 levels: Unit Level Module Level Integration & System Regression

UNIT TESTING
A Unit corresponds to a screen /form in the package. Unit testing focuses on verification of the corresponding class or Screen. This testing includes testing of control paths, interfaces, local d a t a structures, logical decisions, boundary conditions, and error handling.Unit testing may use Test Drivers, which are control programs to co-ordinate test case inputs and outputs, and Test stubs, which replace low-level modules. A stub is a dummy subprogram.

MODULE LEVEL TESTING


Module Testing is done using the test cases prepared earlier. Module is defined during the time of design.

INTEGRATION & SYSTEM TESTING


Integration testing is used to verify the combining of the software modules. Integration testing addresses the issues associated with the d u a l p r o b l e m s o f v e r i f i c a t i o n a n d p r o g r a m c o n s t r u c t i o n . S y s t e m testing is used to verify, whether the developed system meets the requirements.

REGRESSION TESTING
Each modification in software impacts unmodified areas,which results serious injuries to that software. So the process of re -testing for rectification of errors due to modification is known as regression testing

Chapter 6 CONCLUSION

6.1 PROJECT SUMMARY

Requirement model is used to model out the user's requirement. The requirement model in this study can easily be understood and referred by other system developers or designers. It can be a guideline to create a Attendance Management System in secondary schools ,colleges or in any related area. It is consisted of use case diagram, a prototype for the system has been build. In order to define a good requirement model for Attendance Management System for secondary school, several tasks has been followed: 1. Review some theories or principles regarding software development and attendance system. 2. Make data collection to get user requirements. 3. Analyzed user requirement and demonstrate it through models. 4. Build a prototype or ER diagram based on requirement model. 5. Construct user acceptance testing to get feedback from them.

In this study, each chapter describes and demonstrates several tasks detailed: Chapter one describes about project overview. Chapter two describes about literature review of software development phase, methods, tools and etc. Chapter three describes about problem statement or existing work of required attendance and how this project help the users. Chapter four describes about design and implementation. Chapter five describes testing used in this project

6.2 Problem and Limitation

During this study, the main problem and limitation occur is Attendance Management System contains many faculty, admin, students, and many other involve in this. Therefore, there are a little bit complicated to develop and design the system.

6.3 Recommendation for Future Project

In the future, it is good to design and develop requirement model of web application which can manage whole part in college include faculty attendance, time table, examination results, update lecture status ,co-curriculum activity and so on.

REFERRENCES

W,Jason Gilmore,Beginning PHP and MYSQL,fourth edition SOFTWARE ENGINEERING,Roger Pressman,fourth,fifth edition Bennett, S., Skelton, J., & Lunn, K. (2001). UML: Schaums Outlines Bourke, C. J., Rigby, K., & Burden J. (2000). Better Practice in School Attendance: Improving the School Attendance of Indigenous Students. Commonwealth of Australia, 1-62 Carroll, M.P., & Hawkins, C.M. (2002). Web Based Analysis. SM'02, 220225. ACM 1-58113-506-8/02/0006 Christel, M.G., & Kang, K.C. (1992). Issues in Requirements Elicitation. Technical Report CMU/SEI-92-TR-012 ESC-TR-92-012. Dennis, A., Wixom, B.H., Tegarden, D. (2005). System Analysis and design with UML Version 2.0. (2nd ed). New York: John Wiley & Sons. Durden, G. C. & Ellis, L. V. (1995). The Efects of Attendance on Student Learning in Principles of Economics, The American Economic Review, Papers and Proceedings of the Hicker, A.M., & Davis, A.M. (2004). A Unified Model of Requirements Elicitation. Journal ofManagement Information Systems, 20(4), 65-84. Hundredth and Seventh Annual Meeting of the American Economic Association Washington, 85(2), 343-346. Elmagarmid, A.K., & McIver,,W.J., Jr. (2001). The Ongoing March Toward Digital Government. IEEE Computer, 34(2), 32-38. Epstein, J. L., & Sheldon, S. B. (2002). Present and Accounted for: Improving Student Attendance Through Family and Community Involvement. Educational Research and Improvement. 95(5)

Kendall, K.E. (1992). System Analysis and Design (2nd ed). New Jersey: Prentice-Hall, Inc.

Lim, T. S., Sim, S. C. & Mansor, M. M. (2009). RFID Based Attendance System Nunamaker, Jr., J.L., Chen, M., & Purdin, Titus, D.M. (1990). Systems Development in Information Systems Research. Journal ofManagement Information System, 7(3), 89-106. Palmer, J. W. (2002). Web Site Usability, Design, and Performance Metrics, Information System Research, 13(2), 151-167.

Reference sites http://www.w3schools.com http://www.roseindia.net.com http://www.dotnetspider.com http://www.wampserver.com