1 | P a g e

JABALPUR ENGINEERING COLLEGE, JABALPUR

MAJOR PROJECT REPORT ON

“E-Attendance Android Application”Submitted in Partial Fulfillment of the Requirements for the Degree of

BACHELOR OF ENGINEERING(Information Technology Engineering)

Guided by - Asst. Prof. Loveleen Kaur

Submitted by -Swati Upadhyay (0201IT131085)

Shrishti Jain (0201IT131074)

Ankita Singh (0201IT131017)

DEPARTMENT OF INFORMATION TECHNOLOGY ENGINEERINGSESSION 2016-2017

2 | P a g e

JABALPUR ENGINEERING COLLEGE, JABALPUR

ACKNOWLEDGEMENTWe express our sincere indebtness towards our guide Asst. Prof. Loveleen Kuar, Jabalpur Engineering College, Jabalpur (M.P.) for his invaluable guidance, suggestions and supervision throughout the work. Without his kind patronage and guidance the project would not have taken shape. We would also like to express our gratitude and sincere regards for his kind approval of the project, time to time counseling and advices.We owe sincere thanks to all the faculty members in the department of Information Technology Engineering for their kind guidance and encouragement time to time.

Lastly, We would like to thank our parents who have supported us throughout this work.

Date :

Place : Jabalpur

Swati Upadhyay

Shrishti Jain

Ankita Singh

3 | P a g e

4 | P a g e

JABALPUR ENGINEERING COLLEGE, JABALPUR

CERTIFICATE

This is to certify that the major project report entitled "E-Attendance

Android Application" submitted by Swati Upadhyay , Shrishti Jain and

Ankita Singh has been carried out under the guidance of Asst. Prof.

Loveleen Kuar, Jabalpur Engineering College, Jabalpur. The project

report is submitted in partial fulfillment of the requirements for the

degree of Bachelor of Engineering in Information Technology

Engineering from Jabalpur Engineering College, Jabalpur (M.P.).

Internal Examiner External Examiner

Date : Date :

5 | P a g e

6 | P a g e

JABALPUR ENGINEERING COLLEGE JABALPUR

CERTIFICATE

This is to certify that the major project report entitled "E-Attendance

Android Application" submitted by Swati Upadhyay , Shrishti Jain and

Ankita Singh has been carried out under my guidance and supervision.

The project report is submitted in partial fulfillment of the requirements

for the degree of Bachelor of Engineering in Information Technology

Engineering from Jabalpur Engineering College, Jabalpur (M.P.).

Asst. Prof. Loveleen Kuar Dr. Prashant Jain

Project Guide HOD, IT

7 | P a g e

8 | P a g e

JABALPUR ENGINEERING COLLEGE, JABALPUR

DECLARATION

We hereby declare that the project entitled - " E-Attendance Android

Application" which is being submitted as major project of 8th semester

in Information Technology Engineering department, JABALPUR

ENGINEERING COLLEGE, JABALPUR (M.P.) is authentic record

of our genuine work done under the guidance of, Asst. Prof. Loveleen

Kuar, Jabalpur Engineering College, Jabalpur.

Date :

Place : JabalpurSwati Upadhyay

Shrishti Jain

Ankita Singh

9 | P a g e

10 | P a g e

Table Of Contents

Abstract

1. Introduction...........................................................................................12

2. System analysis......................................................................................13

a.Existing system...............................................................................13

b. Proposed system............................................................................14

c. Registration and Login....................................................................14

d. Student Details...............................................................................14

e. Attendance......................................................................................14

f. Report Generation............................................................................14

3. Feasibility study.......................................................................................15

a. Economic feasibility study..............................................................15

b. Technical feasibility study..............................................................15

c. Social feasibility study....................................................................15

4. Literature Survey................................................................................................17

a. Technical Survey.....................................................................................17

b. Operational Survey..................................................................................17

c. Economic Survey......................................................................................17

5. System Requirement Specification......................................................................18

a. Overview..................................................................................................18

Study of the system..............................................................................................18

Number of module........................................................................................18

Module description.........................................................................................19

11 | P a g e

6. SDLC Methodologies............................................................................................21

a. Spiral Model..............................................................................................22

b. Advantages..............................................................................................23

7. Requirements......................................................................................................24

a. Software Requirements............................................................................24

b. Hardware Requirements................................................................................................24

8. System Design..........................................................................................25

a. DFD................................................................................................26

b. E-R Diagram....................................................................................28

9. . Experimantal Results..............................................................................30

10 Technologies used...................................................................................48

a. XML.................................................................................................48

b. Java Technologies…............................................................................................50

11.Testing.....................................................................................................56

a.Testing methodologies….......................................................................58

b.STLC…...................................................................................................61

12. Limitation & Future Enhancement..........................................................68

13. Conclusion...............................................................................................69

14. References...............................................................................................70

12 | P a g e

List Of Figures

i. Architectural Diagram.................................................................................................17

ii. Spiral Model...................................................................................................................20

iii. 0-Level DFD.........................................................................................24

iv. 1 Level DFD..........................................................................................24

v. 2 Level DFD................................................................................................................25

vi. ER Diagram.........................................................................................27

vii. Main Activity.......................................................................................28

viii. Scroll down........................................................................................29

ix. Log in...................................................................................................30

x. Check Attendance................................................................................31

xi. Check Attendance(II)...........................................................................32

xii. Percentage view................................................................................33

xiii. Welcome activity..............................................................................34

xiv. Registration (II).................................................................................35

xv. Registration.......................................................................................36

xvi. About.................................................................................................37

xvii. Attendance list I................................................................................38

xviii. Attendance list II…...........................................................................39

xix. Welcome...........................................................................................40

xx. Select subject activity.........................................................................41

xxi. Attendance list III...............................................................................43

xxii. Attendance completion activity.........................................................44

13 | P a g e

xxiii. Attendance View................................................................................45

xxiv. Compiling and interpreting source code model.................................51

xxv. Template for test case........................................................................62

xxvi. Example for GUI test cases...............................................................63

xxvii. Example for positive test cases.......................................................64

xxviii. Example for Negative Test Cases...................................................65

10 | P a g e

11 | P a g e

AbstractE-Attendance is the android application developed to manage daily student attendance in colleges. The Mobile Phone Based Attendance System will help the lecturers to take attendance easily, securely and without errors. This system will be used to reduce the fake attendance and also reduce the waste of the time. Lecturer will be able to view the attendance by this App. After taking the attendance in the Android mobile, attendance will be send to the server.

The main objective of E-Attendance is creating and managing an Online directory of attendance where students and faculty can view and print their attendance and lectures taken respectively.

My aim for this project was to learn how to create an application in android, the Google operating system for mobile devices. The design of such an application is made in slightly modified Java. The purpose of the final application is to help students and faculty members. It is a system of databases that allows the user to have access their records. So I also used my knowledge of databases during my project.

12 | P a g e

1. IntroductionUsually attendance system calculated manually using computer but, this project using tablets. Education system in developing countries has been changing widely in last 10 years due to the development of the technology. Smart class, E-learning, Video conferencing are some of them. The core idea of this project is to implement some of the emerging Technologies like mobile computing and near field communications and advances in behavioral science studies to make a better educational system.

Android has a bad reputation among those who follow smart phones, for having too many version of OS floating around. The existing versions of android have bug fixes, advancements, and more programs. These timely releases provide better experience to the user, but it is a hassle for who can’t afford to keep updating their phone with newer versions. It is necessary to reboot the phone and there are chances that the devices won’t work properly after update because android releases OS specific and device specific updates.

Attendance Management System is a software developed for daily student attendance in schools, collages 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. 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

13 | P a g e

2.System AnalysisExisting system:

This existing system is not providing secure registration and profile management of all the users properly.

This manual system gives us very less security for saving attendance and various primitive operation on attendance.

The system is not very feasible for exporting reports as excel sheets and pdfs.

The system doesn’t provide facility to track all the activities of student and faculties.

The system doesn’t provide any facility to maintain any feedback option for users.

The system doesn’t provide users(students) to see their friends attendance.

Proposed System:

The objective of the design of a new system is to automate the current procedure of managing and controlling the information about the student details and to reduce the overhead of managing paper documents for every announcement and notices being made. The proposed system will keep the information on a central server while allowing users to access that information from their own Smartphone through the installed android application. There will be an optimized database on the server and an improved user interface on each client machine i.e. on the SIS app installed on the user Smartphone.

REGISTRATION AND LOGIN: Given that the user has downloaded the application, then the user should be able to register through the application by providing the details required for registration. Starting from 2nd year i.e. 3rd semester, it is required that user should register for the application at the beginning of every semester. After registration the user can login into the system by providing the user id and password.

14 | P a g e

STUDENT DETAILS: It includes three entities-

• Personal details

• Academic details

• Placement details

The students are expected to enter their personal details which will then be verified by the teachers. The personal details include residential address, email address, contact details (students as well as parents contact details) etc. The teachers are expected to enter the academic and placement details. Academic details include students CGPA. Placement details can only be entered in the final year and includes the company name where the student is placed and his pay package or if the student has opted for higher studies then the corresponding details will be entered.

NOTICE BOARD/EVENT NOTIFICATION: Notices can be posted by teachers from their respective login and can be viewed on a notice board section of the application with title for a notice associated with it. The notices for a particular class will be broadcasted to that class only.

ATTENDANCE: Subject teachers for each semester are required to enter the attendance details of students. The system should be able to generate attendance reports (for lectures and practicals) for individual student for each subject. These reports will be sent to the student as well as his parents periodically. The teacher can also view the attendance record of students during a particular interval. If the attendance of some student falls below the threshold value, then the particular student should be notified regarding the same.

REPORT GENERATION: It includes generation of attendance reports for lectures as well as practicals for individual student for each subject. Other reports such as academic details record etc. can also be generated. These reports can also be sent to the student as well as his parents if required.

15 | P a g e

3.Feasibility StudyThe main purpose of feasibility study is to consider each and every possible factor associated with the project and determine whether the investment of time and other resources yield desired results. It also includes determining the investments, manpower and costs incurred on this project. The following feasibility has used in this project.

Economic Feasibility

Economic analysis is the most frequently used method for evaluating the effectiveness of a new system. The project is economically feasible as it only requires a mobile phone with Android operating system.

The application is free to download once released into Android market. The users should be able to connect to internet through mobile phone and this would be the only cost incurred on the project.

The system being developed is economic with respect to School or Collage’s point of view. It is cost effective in the sense that has eliminated the paper work completely. 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. The result obtained contains minimum errors and are highly accurate as the data is required.

Technical Feasibility

To develop this application, a high speed internet connection, a database server, a web server and IDE (such as Eclipse) are required. The current project is technically feasible as the application was successfully deployed on android emulator.

The technical requirement for the system is economic and it does not use any other additional Hardware and software.

Social Feasibility

The application is socially feasible since it requires no technical guidance, all the modules are user friendly and execute in a manner they were designed to. The system working is quite easy to use and learn due to its simple but attractive interface. User requires no special training for operating the system

16 | P a g e

4.Literature Survey

TECHNICAL SURVEY:Evaluating the technical feasibility is the trickiest part of a feasibility study. This is because, at this point in time, not too many detailed design of the system, making it difficult to access issues like performance, costs on (on account of the kind of technology to be deployed) etc. A number of issues have to be considered while doing a technicalanalysis.

i) Understand the different technologies involved in the proposed system:Before commencing the project, we have to be very clear about what are the technologies that are to be required for the development of the new system.

ii) Find out whether the organization currently possesses the required technologies:

o Is the required technology available with the organization?

o If so is the capacity sufficient? For instance –

“Will the current printer be able to handle the new reports and forms required for the new system?”

Operational Survey:Proposed projects are beneficial only if they can be turned into information systems that will meet the organizations operating requirements. Simply stated, this test of feasibility asks if the system will work when it is developed and installed. Are there major barriers to Implementation? Here are questions that will help test the operational feasibility of a project:

▪ Is there sufficient support for the project from management from users? If the current system is well liked and used to the extent that persons will not be able to see reasons for change, there may be resistance.

17 | P a g e

▪ Are the current business methods acceptable to the user? If they are not, Users may welcome a change that will bring about a more operational and useful systems.

▪ Have the user been involved in the planning and development of the project?

▪ Early involvement reduces the chances of resistance to the system and in

▪ General and increases the likelihood of successful project.

Since the proposed system was to help reduce the hardships encountered. In the existing manual system, the new system was considered to be operational feasible.

Economic Survey:

Economic feasibility attempts to weigh the costs of developing and implementing a new system, against the benefits that would accrue from having the new system in place. This feasibility study gives the top management the economic justification for the new system.

A simple economic analysis which gives the actual comparison of costs and benefits are much more meaningful in this case. In addition, this proves to be a useful point of reference to compare actual costs as the project progresses. There could be various types of intangible benefits on account of automation. These could include increased customer satisfaction, improvement in product quality better decision making timeliness of information, expediting activities, improved accuracy of operations, better documentation and record keeping, faster retrieval of information, better employee morale.

18 | P a g e

5.System Requirement Specification

OVERVIEW

1. STUDY OF THE SYSTEM

In the flexibility of use the interface has been developed as graphics concepts in mind, associated through a browser interface. The GUI’s at the top level has been categorized as follows

1. Administrator Interface Design.

2. User Interface.

3. Reports.

4. General end-users.

The administrative user interface will maintain the different users details, the interface helps the administration with all the transactional states like which users sending the mails, and which users receiving whishing mails, users details information history. And the statistics of the system in difference stratagies.

2. Number Of Module The system after careful analysis has been identified to be presented with the following modules:

1.Admin Module

2.Registered Members Module(Student Or Faculty)

3. Reports Module

4. About App

3. Module Description

1.Admin Module

19 | P a g e

In this module the user can register an another admin. He can here also view all the application details of an applicant. he also can update status of an application. And he can also generate reports using report module.He can have the authority to delete moderators as well as add moderators.

2.Registered Members Module(Student Or Faculty)

The register members can post the articles. They can view their profiles and the articles list. How many articles are accepted by moderator and how many rejected. They can post the queries regarding the rejection of articles. The can receive the solution from the moderator to the rejection of articles.

3.Reports Module

In this Module the Administrator can generate the different types of Reports according to their access. The Reports can be generated in various formats as per users need and their access.

4.About App

The about app module will let user know about the application they are using along with the system requirements app will seek, best platform to be employed and various other application related module.

B . Architectural Diagram :

This App will run only on the Particular Network through Wi-Fi connection. After Completion of each process on the android device, the data will be sent to the PHP file on the web server through the network and data will stored on the MySql Database.

20 | P a g e

There are four modules in this Project.

There are1) Module 1: Authentication.2) Module 2: View and Edit Profile.3) Module 3: Reset Password.4) Module 4: Mark, Edit and View Attendance.

a. Module 1: Authentication Administrator, Teaching Staff, Student should Login to this Application first. Login will provide rights after the successful completion of verification of username and password with the database on the web server. Screenshot of the Login Screen is as shown in Fig. 2. Forget password option is also provided to change the new password by entering the Username, Name, Date of Birth, Phone No and E-Mail ID correctly.

b. Module 2: View and Edit Profile Administrator, Teaching Staff, Student can view their profile and edit their profile. Administrator can have additional rights to view and edit the Profile of Student, Staff and alumni. Administrator can also have rights to promote students. Head of the Department can have rights to Promote Students from one year to another year or semester, He can also change the Designation of the Staff and Change the allotted class for them too. Head of the Department, Administrator, Staff can have rights to view the class students, alumni student batch, profile of alumni student and student. Administrator can also create a new staff profile and student profile

c. Module 3: Reset Password Administrator, Teaching Staff, Student can change their Password for their Profile. They have to log out after the password is reset. Administrator can have additional rights to reset the password of student or staff. First login after reset of password by administrator, they have to give the new password. It is compulsory process. Screenshots of Reset Password are shown in Fig.8.

d. Module 4: Mark, Edit and View Attendance Students can view their Attendance based on the date and period they chosen with the Subject Name, Attendance and Marked By. Administrator and Staffs can view the attendance of a class and a particular student on the particular period of the specified date. Staffs can mark and edit the attendance of the classes they are handling. The attendance marked by one staff is not allowed to edit by another staff. After the completion of Marking or Editing Attendance, the head counts will be displayed for the verification. Then, Attendance will be stored, It can also be saved as PDF on the Device Memory of the Staff’s Android device.

21 | P a g e

6.SDLC Methodologies

This document play a vital role in the development of life cycle (SDLC) as it describes the complete requirement of the system. It means for use by developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.

SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software Development and Enhancement. This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models.

As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.The steps for Spiral Model can be generalized as follows:

The new system requirements are defined in as much details as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.

A preliminary design is created for the new system.

A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.

A second prototype is evolved by a fourfold procedure:

1. Evaluating the first prototype in terms of its strengths, weakness, and risks.

2. Defining the requirements of the second prototype.

3. Planning an designing the second prototype.

4. Constructing and testing the second prototype.

At the customer option, the entire project can be aborted if the risk is deemed too great. Risk factors might involved development cost overruns, operating-cost miscalculation, or any other factor that

22 | P a g e

could, in the customer’s judgment, result in a less-than-satisfactory final product.

The existing prototype is evaluated in the same manner as was the previous prototype, and if necessary, another prototype is developed from it according to the fourfold procedure outlined above.

The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired.

The final system is constructed, based on the refined prototype. The final system is thoroughly evaluated and tested. Routine

maintenance is carried on a continuing basis to prevent large scale failures and to minimize down time.

The following diagram shows how a spiral model acts like:

Fig 1.0-Spiral Model

23 | P a g e

24 | P a g e

ADVANTAGES

Estimates(i.e. budget, schedule etc .) become more relistic as work progresses, because important issues discoved earlier.

It is more able to cope with the changes that are software development generally entails.

Software engineers can get their hands in and start woring on the core of a project earlier.

25 | P a g e

7.Software Requirements & Hardware Requirements

Software Requirements

a. The For Developing PC1) Java Development Kit (jdk1.6 or above).

2) Java Runtime Environment (jre1.6 or above).3) Eclipse IDE (Integrated Development Environment) with SDK (Software Development Kit).4) WAMP Server

b. For Mobile1) Operating System: Android 3.2 (Honeycomb) or above.2) Apps Required: Browser, PDF Reader.

Hardware Requirements

Processor : Pentium IV or updatedHard Disk : 40GB or moreRAM : 1GB or more

26 | P a g e

8.System Design

Data Flow Diagram

A graphical tool used to describe and analyze the moment of data through

a system manual or automated including the process, stores of data, and

delays in the system. Data Flow Diagrams are the central tool and the basis

from which other components are developed. The transformation of data

from input to output, through processes, may be described logically and

independently of the physical components associated with the system. The

DFD is also know as a data flow graph or a bubble chart.

DFDs are the model of the proposed system. The Basic Notation used to

create a DFD’s are as follows:

1. Dataflow: Data move in a specific direction from an origin to a

destination.

2. Process: People, procedures, or devices that use or produce (Transform)

Data. The physical component is not identified.

3. Source: External sources or destination of data, which may be People,

programs, organizations or other entities.

User/Administrator

System

1 Level DFD Login

ProcessAttendanceentry

26 | P a g e

4. Data Store: Here data are stored or referenced by a process in the

System.

0- level DFD:

Output

Student

Entry

Teacher

Entry

27 | P a g e

user

Loginprocess

Log in

Reportgeneration

Attendanceentry

attendance attendance

user

2-level DFD:

28 | P a g e

ER diagram :An entity relationship diagram (ERD) shows the relationships of entity sets stored in a database. An entity in this context is a component of data. In other words, ER diagrams illustrate the logical structure of databases.At first glance an entity relationship diagram looks very much likea flowchart. It is the specialized symbols, and the meanings of those symbols, that make it unique.

Common Entity Relationship Diagram SymbolsAn ER diagram is a means of visualizing how the information a system produces is related. There are five main components of an ERD:

Entities, which are represented by rectangles. An entity is an object or concept about which you want to store information.

Actions, which are represented by diamond shapes, show how two entities share information in the database.

Attributes, which are represented by ovals. A key attribute is the unique, distinguishing characteristic of the entity. For example, an employee's social security number might be the employee's key attribute.

Connecting lines, solid lines that connect attributes to show the relationships of entities in the diagram.

Cardinality specifies how many instances of an entity relate to one instance of another entity. Ordinality is also closely linked to cardinality. While cardinality specifies the occurrences of a relationship, ordinality describes the relationship as either mandatory or optional. In other words, cardinality specifies the maximum number of relationships and ordinality specifies the absolute minimum number of relationships.

ER Diagram UsesWhen documenting a system or process, looking at the system in multiple ways increases the understanding of that system. ERD diagrams are commonly used in conjunction with a data flow diagram to display the contents of a data store.ER Diagram of System :

29 | P a g e

Name

Teacher

Teacher_id StatusStudent_id

Month

Attendance

Subject

semes

TeachesBelongs

S.codeSubject

studied

s.name

Teacher_idStudent

Student_id

Namesemester

course

30 | P a g e

9.Experimental Results Main Activity

31 | P a g e

Scroll Down

32 | P a g e

Log In

33 | P a g e

Check Attendance

34 | P a g e

Check Attendance (ii)

35 | P a g e

Percentage view

36 | P a g e

Welcome Activity

37 | P a g e

Registration Activity

38 | P a g e

Registration Activity(ii)

39 | P a g e

40 | P a g e

About Activity

40 | P a g e

Attendance List (i)

41 | P a g e

Attendance List(ii)

42 | P a g e

Welcome(ii)

43 | P a g e

Select Subject Activity

44 | P a g e

Attendance list (iii)

45 | P a g e

Attendance List(iv)

46 | P a g e

Attendance Completion Activity

47 | P a g e

Attendance View Activity

48 | P a g e

10.TECHNOLOGY DESCRIPTIONXMLIn computing, Extensible Markup Language (XML) is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. The W3C's XML 1.0 Specification[2]

and several other related specifications[3]—all of them free open standards—define XML.[4]

The design goals of XML emphasize simplicity, generality, and usability across the Internet.[5] It is a textual data format with strong support via Unicode for different human languages. Although the design of XML focuses on documents, the language is widely used for the representation of arbitrary data structures[6] such as those used in web services.Several schema systems exist to aid in the definition of XML-based languages, while programmers have developed many application programming interfaces (APIs) to aid the processing of XML data.

Key TechnologyThe material in this section is based on the XML Specification. This is not an exhaustive list of all the constructs that appear in XML; it provides an introduction to the key constructs most often encountered in day-to-day use.Character

An XML document is a string of characters. Almost every legal Unicode character may appear in an XML document.

Processor and applicationThe processor analyzes the markup and passes structured information to an application. The specification places requirements on what an XML processor must do and not do, but the application is outside its scope. The processor (as the specification calls it) is often referred to colloquially as an XML parser.

Markup and contentThe characters making up an XML document are divided into markup and content, which may be distinguished by the application of simple syntactic rules. Generally, strings that constitute markup either begin with the character < and end with a >, or they begin with the character & and end with a ;. Strings of characters that are not markup are content. However, in a CDATA section, the delimiters <![CDATA[ and ]]> are classified as markup, while the text

49 | P a g e

between them is classified as content. In addition, whitespace before and after the outermost element is classified as markup.

TagA tag is a markup construct that begins with < and ends with >. Tags come in three flavors:

start-tag, such as <section>; end-tag, such as </section>; empty-element tag, such as <line-break />.

ElementAn element is a logical document component that either begins with a start-tag and ends with a matching end-tag or consists only of an empty-element tag. The characters between the start-tag and end-tag, if any, are the element's content, and may contain markup, including other elements, which are called child elements. An example is <greeting>Hello, world!</greeting>. Another is <line-break />.4

AttributeAn attribute is a markup construct consisting of a name–value pair that exists within a start-tag or empty-element tag. An example is <img src="madonna.jpg" alt="Madonna" />, where the names of the attributes are "src" and "alt", and their values are "madonna.jpg" and "Madonna" respectively. Another example is <step number="3">Connect A to B.</step>, where the name of the attribute is "number" and its value is "3". An XML attribute can only have a single value and each attribute can appear at most once on each element. In the common situation where a list of multiple values is desired, this must be done by encoding the list into a well-formed XML attribute[note 1] with some format beyond what XML defines itself. Usually this is either a comma or semi-colon delimited list or, if the individual values are known not to contain spaces,[note 2] a space-delimited list can be used. <div class="inner greeting-box">Welcome!</div>, where the attribute "class" has both the value "inner greeting-box" and also indicates the two CSS class names "inner" and "greeting-box".

XML declarationXML documents may begin with an XML declaration that describes some information about themselves.

An example is <?xml version="1.0" encoding="UTF-8"?>.

Java Technology

50 | P a g e

Initially the language was called as “oak” but it was renamed as “Java” in 1995. The primary motivation of this language was the need for a platform- independent (i.e., architecture neutral) language that could be used to create software to be embedded in various consumer electronic devices.

Java is a programmer’s language. Java is cohesive and consistent. Except for those constraints imposed by the Internet environment,

Java gives the programmer, full control. Finally, Java is to Internet programming where C was to system

programming.

Importance of Java to the Internet

Java has had a profound effect on the Internet. This is because; Java expands the Universe of objects that can move about freely in Cyberspace. In a network, two categories of objects are transmitted between the Server and the Personal computer. They are: Passive information and Dynamic active programs. The Dynamic, Self-executing programs cause serious problems in the areas of Security and probability. But, Java addresses those concerns and by doing so, has opened the door to an exciting new form of program called the Applet.

Java can be used to create two types of programs

Applications and Applets: An application is a program that runs on our Computer under the operating system of that computer. It is more or less like one creating using C or C++. Java’s ability to create Applets makes it important. An Applet is an application designed to be transmitted over the Internet and executed by a Java –compatible web browser. An applet is actually a tiny Java program, dynamically downloaded across the network, just like an image. But the difference is, it is an intelligent program, not just a media file. It can react to the user input and dynamically change.

51 | P a g e

Features of Java Security

Every time you that you download a “normal” program, you are risking a viral infection. Prior to Java, most users did not download executable programs frequently, and those who did scan them for viruses prior to execution. Most users still worried about the possibility of infecting their systems with a virus. In addition, another type of malicious program exists that must be guarded against. This type of program can gather private information, such as credit card numbers, bank account balances, and passwords. Java answers both these concerns by providing a “firewall” between a network application and your computer.

When you use a Java-compatible Web browser, you can safely download Java applets without fear of virus infection or malicious intent.

Portability

For programs to be dynamically downloaded to all the various types of platforms connected to the Internet, some means of generating portable executable code is needed .As you will see, the same mechanism that helps ensure security also helps create portability. Indeed, Java’s solution to these two problems is both elegant and efficient.

The Byte code

The key that allows the Java to solve the security and portability problems is that the output of Java compiler is Byte code. Byte code is a highly optimized set of instructions designed to be executed by the Java run-time system, which is called the Java Virtual Machine (JVM). That is, in its standard form, the JVM is an interpreter for byte code.

Translating a Java program into byte code helps makes it much easier to run a program in a wide variety of environments. The reason is, once the run-time package exists for a given system, any Java program can run on it.

Although Java was designed for interpretation, there is technically nothing

Java SourceJava byte code

JavaVM

52 | P a g e

about Java that prevents on-the-fly compilation of byte code into native code. Sun has just completed its Just In Time (JIT) compiler for byte code. When the JIT compiler is a part of JVM, it compiles byte code into executable code in real time, on a piece-by-piece, demand basis. It is not possible to compile an entire Java program into executable code all at once, because Java performs various run-time checks that can be done only at run time. The JIT compiles code, as it is needed, during execution.

Java Virtual Machine (JVM)

Beyond the language, there is the Java virtual machine. The Java virtual machine is an important element of the Java technology. The virtual machine can be embedded within a web browser or an operating system. Once a piece of Java code is loaded onto a machine, it is verified. As part of the loading process, a class loader is invoked and does byte code verification makes sure that the code that’s has been generated by the compiler will not corrupt the machine that it’s loaded on. Byte code verification takes place at the end of the compilation process to make sure that is all accurate and correct. So byte code verification is integral to the compiling and executing of JaOverall Description

Java .Class

Picture showing the development process of JAVA Program

Java programming uses to produce byte codes and executes them. The first box indicates that the Java source code is located in a. Java file that is processed with a Java compiler called javac. The Java compiler produces a file called a. class file, which contains the byte code. The .Class file is then loaded across the network or loaded locally on your machine into the

53 | P a g e

execution environment is the Java virtual machine, which interprets and executes the byte code.

Java Architecture

Java architecture provides a portable, robust, high performing environment for development. Java provides portability by compiling the byte codes for the Java Virtual Machine, which is then interpreted on each platform by the run-time environment. Java is a dynamic system.

Compilation of code

When you compile the code, the Java compiler creates machine code (called byte code) for a hypothetical machine called Java Virtual Machine (JVM). The JVM is supposed to execute the byte code. The JVM is created for overcoming the issue of portability. This machine is called Java Virtual Machine.

Compiling and interpreting Java Source Code

During run-time the Java interpreter tricks the byte code file into thinking that it is running on a Java Virtual Machine. In reality this could be a Intel Pentium Windows 95 or SunSARC station running Solaris or Apple Macintosh running system and all could receive code from any computer through Internet and run the Applets.

Java

SourcePC

CompilerJava Interprete

r (PC)Code Byte

code………..………..

………..

Macintosh Compiler (Platform

Independe nt)

Java Interprete

r (Macintos

h)SPARC JavaInterprete

(Spare)

54 | P a g e

Simple

Java was designed to be easy for the Professional programmer to learn and to use effectively. If you are an experienced C++ programmer, learning Java will be even easier. Because Java inherits the C/C++ syntax and many of the object oriented features of C++. Most of the confusing concepts from C++ are either left out of Java or implemented in a cleaner, more approachable manner. In Java there are a small number of clearly defined ways to accomplish a given task.

Object-Oriented

Java was not designed to be source-code compatible with any other language. This allowed the Java team the freedom to design with a blank slate. One outcome of this was a clean usable, pragmatic approach to objects. The object model in Java is simple and easy to extend, while simple types, such as integers, are kept as high-performance non-objects.

Robust

The multi-platform environment of the Web places extraordinary demands on a program, because the program must execute reliably in a variety of systems. The ability to create robust programs was given a high priority in the design of Java. Java is strictly typed language; it checks your code at compile time and run time.

Java virtually eliminates the problems of memory management and de- allocation, which is completely automatic. In a well-written Java program, all run time errors can –and should –be managed by your program.

55 | P a g e

11. TESTING Software Testing is the process used to help identify the correctness, completeness, security, and quality of developed computer software. Testing is a process of technical investigation, performed on behalf of stakeholders, that is intended to reveal quality-related information about the product with respect to the context in which it is intended to operate. This includes, but is not limited to, the process of executing a program or application with the intent of finding errors. Quality is not an absolute; it is value to some person. With that in mind, testing can never completely establish the correctness of arbitrary computer software; testing furnishes a criticism or comparison that compares the state and behavior of the product against a specification. An important point is that software testing should be distinguished from the separate discipline of Software Quality Assurance (SQA), which encompasses all business process areas, not just testing.

There are many approaches to software testing, but effective testing of complex products is essentially a process of investigation, not merely a matter of creating and following routine procedure. One definition of testing is "the process of questioning a product in order to evaluate it", where the "questions" are operations the tester attempts to execute with the product, and the product answers with its behavior in reaction to the probing of the tester[citation needed]. Although most of the intellectual processes of testing are nearly identical to that of review or inspection, the word testing is connoted to mean the dynamic analysis of the product—putting the product through its paces. Some of the common quality attributes include capability, reliability, efficiency, portability, maintainability, compatibility and usability. A good test is sometimes described as one which reveals an error; however, more recent thinking suggests that a good test is one which reveals information of interest to someone who matters within the project community.

Introduction:

56 | P a g e

Software testing may be viewed as a sub-field of Software Quality Assurance but typically exists independently (and there may be no SQA areas in some companies). In SQA, software process specialists and auditors take a broader view on software and its development. They examine and change the software engineering process itself to reduce the amount of faults that end up in the code or deliver faster.

Regardless of the methods used or level of formality involved the desired result of testing is a level of confidence in the software so that the organization is confident that the software has an acceptable defect rate. What constitutes an acceptable defect rate depends on the nature of the software. An arcade video game designed to simulate flying an airplane would presumably have a much higher tolerance for defects than software used to control an actual airliner.

A problem with software testing is that the number of defects in a software product can be very large, and the number of configurations of the product larger still. Bugs that occur infrequently are difficult to find in testing. A rule of thumb is that a system that is expected to function without faults for a certain length of time must have already been tested for at least that length of time. This has severe consequences for projects to write long-lived reliable software.

A common practice of software testing is that it is performed by an independent group of testers after the functionality is developed but before it is shipped to the customer. This practice often results in the testing phase being used as project buffer to compensate for project delays. Another practice is to start software testing at the same moment the project starts and it is a continuous process until the project finishes.

Another common practice is for test suites to be developed during technical support escalation procedures. Such tests are then maintained in regression testing suites to ensure that future updates to the software don't repeat any of the known mistakes.It is commonly believed that the earlier a defect is found the cheaper it is to

57 | P a g e

fix it.

Unit tests are maintained along with the rest of the software source code and generally integrated into the build process (with inherently interactive tests being relegated to a partially manual build acceptance process).

The software, tools, samples of data input and output, and configurations are all referred to collectively as a test harness.

Testing Concepts

Testing

Testing Methodologies

➢ Black box Testing:➢ White box Testing.➢ Gray Box Testing.

Levels of Testing

➢ Unit Testing.➢ Module Testing.➢ Integration Testing.➢ System Testing.➢ User Acceptance Testing.

TCD (Test Case Documentation)

STLC

58 | P a g e

➢ Test Planning.➢ Test Development.➢ Test Execution.

➢ Result Analysis.➢ Bug-Tracing.➢ Reporting.

Microsoft Windows – Standards Manual Testing Automation Testing (Tools)

➢ Win Runner.➢ Test Director.

Testing:

The process of executing a system with the intent of finding an error. Testing is defined as the process in which defects are identified,

isolated, subjected for rectification and ensured that product is defect free in order to produce the quality product and hence customer satisfaction.

Quality is defined as justification of the requirements Defect is nothing but deviation from the requirements Defect is nothing but bug. Testing --- The presence of bugs Testing can demonstrate the presence of bugs, but not their absence Debugging and Testing are not the same thing! Testing is a systematic attempt to break a program or the AUT Debugging is the art or method of uncovering why the script /program

did not execute properly.

Testing Methodologies:

59 | P a g e

Black box Testing : is the testing process in which tester can perform testing on an application without having any internal structural knowledge of application.Usually Test Engineers are involved in the black box testing.

White box Testing : is the testing process in which tester can perform testingon an application with having internal structural knowledge.Usually The Developers are involved in white box testing.

Gray Box Testing : is the process in which the combination of black box and white box tonics’ are used.

60 | P a g e

STLC (SOFTWARE TESTING LIFE CYCLE)Test Planning:1.Test Plan is defined as a strategic document

which describes the procedure how to perform various testing on the total application in the most efficient way.

2.This document involves the scope of testing,3. Objective of testing,4. Areas that need to be tested,5. Areas that should not be tested,6. Scheduling Resource Planning,7. Areas to be automated, various testing tools

Test Development:1. Test case Development (check list)2. Test Procedure preparation. (Description of the Test cases).

Result Analysis:1. Expected value: is nothing but expected behavior Of application.2. Actual value: is nothing but actual behavior of application

Bug Tracing : Collect all the failed cases, prepare documents.

Reporting: Prepare document (status of the application)

Types Of Testing:

Smoke Testing: is the process of initial testing in which tester looks for the availability of all the functionality of the application in order to perform detailed testing on them. (Main check is for available forms)

61 | P a g e

Regression Testing: is one of the best and important testing. Regression testing is the process in which the functionality, which is already tested before, is once again tested whenever some new change is added in order to check whether the existing functionality remains same.Static Testing: is the testing, which is performed on an application when it is not been executed.ex: GUI, Document Testing

Dynamic Testing: is the testing which is performed on an application when it is being executed.ex: Functional testing.

Alpha Testing : it is a type of user acceptance testing, which is conducted on an application when it is just before released to the customer.

Beta-Testing: it is a type of UAT that is conducted on an application when it is released to the customer, when deployed in to the real time environment and being accessed by the real time users.

Compatibility testing : it is the testing process in which usually the products are tested on the environments with different combinations of databases (application servers, browsers…etc) In order to check how far the product is compatible with all these environments platform combination.

TCD (Test Case Document):

Test Case Document Contains

Test Scope (or) Test objective

Test Scenario

Test Procedure

Test case

62 | P a g e

This is the sample test case document for the Acadamic details of student project:

Test scope:

Test coverage is provided for the screen “Attendance register” form of a student module of university management system application

Areas of the application to be tested

Test Scenario:

When the office personals use this screen for the marks entry, calculate the status details, saving the information on student’s basis and quit the form.

Test Procedure:

The procedure for testing this screen is planned in such a way that the data entry, status calculation functionality, saving and quitting operations are tested in terms of Gui testing, Positive testing, Negative testing using the corresponding Gui test cases, Positive test cases, Negative test cases respectively

Test Cases:

Template for Test Case

63 | P a g e

T.C.No Description Exp Act Result

1

2

Enter username and password

Enter valid date to store in the database

True/false

Accurate/Valid data

True

Valid date

Home page

Data stored Successfully

Example for Gui Test cases:

T.C.No Description Expected value

Actual value

Result

1Check for all the features in the screen

The screen must contain all thefeatures

2Check for the alignment of the objects as per the validations

The alignment should be in proper way

64 | P a g e

2. Positive Test Cases :

The positive flow of the functionality must be considered Valid inputs must be used for testing Must have the positive perception to verify whether the requirements

are justified.

Example for Positive Test cases:

T.C.No Description Expected value

Actual value Result

1 Check forthe dateTime Auto Display

The date and time of the system must be displayed

2 Enter the valid Roll no into the student roll no field

It

should accept

Negative Test Cases:

Must have negative perception. Invalid inputs must be used for test.

65 | P a g e

Example for Negative Test cases:

T.C.No Description Expected value

Actual value Result

1 Try to modify The information in date

and time

Modificatio n

should not be allow

2 Enter invalid data in to the student details form, click on save

It

should not

accept invalid data,

66 | P a g e

12. Limitation & Future Enhancement

Limitations of the system: .

System works in all platforms and its compatible environments.

Advanced techniques are not used to check the authorization.

Future Enhancements:

It is not possible to develop a system that makes all the requirements of

the user. User requirements keep changing as the system is being used.

Some of the future enhancements that can be done to this system are:

As the technology emerges, it is possible to upgrade the system and

can be adaptable to desired environment.

Because it is based on object-oriented design, any further changes can

be easily adaptable.

Based on the future security issues, security can be improved using

emerging technologies.

Attendance module can be added

sub admin module can be added

67 | P a g e

13.ConclusionIt is an efficient method to store the attendance in the smart phone rather than wasting the paper. It also updates the students report directly on the server reducing the faculty’s time on logging from the computer.

The attendance management system will be used to lectures to take attendance easily, securely and is less error prone. Then this system is used to reduce the waste of the time for taking attendance to the students and we can save our manual calculations time. And then it will also reduce the fake attendance, then this system is user friendly .Because, we can put attendance to the students anywhere in the place. The paper work will be less to using this attendance management system.

This is a paperless work. It can be monitored and controlled remotely. It reduces the man power required. It provides accurate information always. Malpractice can be reduced. All years together gathered information can be saved and can be accessed at any time. The data which is stored in the repository helps in taking intelligent decisions by the management. So it is better to have an android application for student information management. All the stakeholders, faculty and management can get the required information without delay. This system is essential in the colleges/hostels and universities. 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. The system solves the problem. It was intended to solve as requirement specification.

We are planning to change this android application as an “E -Campus” for the College. I am planning to include profile picture for the Students, Teaching Staffs and Administrators. I am planning to include Declaration of Holiday on the Specified Date option for the Administrator and the Head of the Department. I am planning to change the Authentication with One Time Password, Face Recognition, Voice Recognition instead of Password to improve security of the Application. I am also planning to include login for Alumni to get the current news and events of the college and the current students of college can get the notes and ask Job related queries to them. I am also planned to include the chatting option which enables Student to post a question and the staff or the alumni can answer for that question based on the department. I am planning to change this Project based on QR (Quick Response) Code.

68 | P a g e

14.References

[1] http://opensourceforu.com[2] http://tutorialspoint.com[3] http://stackoverflow.com[4] http://stackexchange.com[5]Jeff Friesen, “Exploring the Basic APIs, Part1 and Part2” in Learn Java for Android Development, 2014, pp. 287-380.[6]Marko Gargenta and Masumi Nakamura, “Intents, Action Bar and More” in Learn Android, 2014, pp. 141-160.[7]Belén Cruz Zapata, “SDK Manager” in Android Studio Essentials, 2015, pp. 56.[8]Onur Cinar, “API Level” in Android Quick APIs Reference, 2015, pp. 10.[9]Rick Boyer and Kyle Mew, “Layouts” in Android Application Development Cookbook, 2016, pp. 25-41.[10]Phil Dutson, “Views” in Android Development Patterns, 2016, pp. 59-65.[11]Grant Allen, “Working with Files” in Beginning Android, 2015, pp. 287- 300.[12]Jason Morris, “Using Bundle Objects” in Android User Interface Development- Beginner-s Guide, 2011, pp.105.

70 | P a g e