Android Attendance Management System
Android Attendance Management System
Android Attendance Management System
It helps the users to maintain theirs various details. The main advantage of
using this application is it reduces the time of generating time table to all over the
classes and staffs details are maintained. The process in this project is to be
organized to College Staff and Subject, Class batch wise, And Also Maintained by
Student Attendance details organized by staff directly Responsibility of the vision
of my captured Student details, Class based Attendance hour wise organized
mobile application. The Project Coding is based Several Tools is used to develop
the this mobile application (java jdk ) are so well connected that the protect
resembles to the computerization of the Web services operation of the firm. The
database design and coding techniques has highly enhanced and optimized. This
makes the application an overall user friendly and easy for naive users.
It helps the clients to keep up theirs different points of interest. The principle
favorable position of utilizing this application is it decreases the season of
producing time table to everywhere throughout the classes and staff's subtle
elements are kept up. The procedure in this undertaking is to be sorted out to
College Staff and Subject and Class cluster savvy ,And Also Maintained by
Student Attendance subtle elements composed by staff specifically Responsibility
of the vision of my caught Student points of interest ,Class based Attendance hour
wise, Staff login maintained Timetable vision For Staff wise Generated Report
displayed and Class ,Department Wise Reports are displayed based on User Login
Preferences composed versatile application
MODULES DESCRIPTION
SYSTEM ANALYSIS
EXISTING SYSTEM
The most important drawback of the existing system is that Staff has
to totally depend on the Student Attendance Book at the time of need.
Another demerit of the existing system is that the process of
obtaining the Time Table is not an easy task.
PROPOSED SYSTEM
The system will overcome all the ambiguity. The project provides the
flexible, reliable, simple and most powerful system to get the list of Time Table
from Staff wise and Department with Class Wise Report Generated. The project
consists of three users namely admin, Staff, Student, This applications organized
based user login Preferences can register their details and through mobile
application the users can find the easily and request for their help.
3.SYSTEM REQUIREMENTS
DEVELOPMENT ENVIRONMENT
The configuration given below is the Hardware handled for the system
development.
TOOLS REQUIRED
Eclipse Luna version 3.7
Android sdk : Android 5.0 Platform
Android adt plug-in.
3.2.1 FRONT END TOOLS
JAVA (PROGRAMMING LANGUAGE)
Java is a programming language originally developed by James Gosling at
Sun Microsystems (which has since merged into Oracle Corporation) and released in
1995 as a core component of Sun Microsystems' Java platform. The language
derives much of its syntax from C and C++ but has a simpler object model and
fewer low-level facilities. Java applications are typically compiled to byte code (class
file) that can run on any Java Virtual Machine (JVM) regardless of computer
architecture. Java is a general-purpose, concurrent, class-based, object-oriented
language that is specifically designed to have as few implementation dependencies
as possible. It is intended to let application developers "write once, run anywhere"
(WORA), meaning that code that runs on one platform does not need to be
recompiled to run on another. Java is currently one of the most popular
programming languages in use, particularly for client-server web applications, with
a reported 10 million users.
JAVA PLATFORM
JAVA VERSIONS 7
The Java language has undergone several changes since JDK 7.0 as well as
numerous additions of classes and packages to the standard library. Since J2SE 7.0,
the evolution of the Java language has been governed by the Java Community
Process (JCP), which uses Java Specification Requests (JSRs) to propose and specify
additions and changes to the Java platform. The language is specified by the Java
Language Specification (JLS); changes to the JLS are managed under JSR 901.
Android is a Linux-based operating system for mobile devices such as smartphones and
tablet computers. It is developed by the Open Handset Alliance led by Google. Google purchased
the initial developer of the software, Android Inc., in 2005. The unveiling of the Android
distribution in 2007 was announced with the founding of the Open Handset Alliance, a
consortium of 86 hardware, software, and telecommunication companies devoted to advancing
open standards for mobile devices. Google releases the Android code as open-source, under the
Apache License. The Android Open Source Project (AOSP) is tasked with the maintenance and
further development of Android.
Android has a large community of developers writing applications that extend the
functionality of the devices. Developers write primarily in a customized version of Java. Apps
can be downloaded from third-party sites or through online stores such as Google Play (formerly
Android Market), the application store run by Google. As of February 2012 there were more than
450,000 apps available for Android, and the estimated number of applications downloaded from
the Android Market as of December 2011 exceeded 10 billion
Features
Media support for common audio, video, and still image formats (MPEG4, H.264, MP3,
AAC, AMR, JPG, PNG, GIF)
Application Framework
Developers have full access to the same framework APIs used by the core applications.
The application architecture is designed to simplify the reuse of components; any application can
publish its capabilities and any other application may then make use of those capabilities (subject
to security constraints enforced by the framework). This same mechanism allows components to
be replaced by the user.
Content Providers that enable applications to access data from other applications (such as
Contacts), or to share their own data
A Notification Manager that enables all applications to display custom alerts in the status
bar An Activity Manager that manages the lifecycle of applications and provides a common
navigation back stack For more details and a walkthrough of an application, see the Notepad
Tutorial.
Libraries
Android includes a set of C/C++ libraries used by various components of the Android
system. These capabilities are exposed to developers through the Android application framework.
Some of the core libraries are listed below:
System C library - a BSD-derived implementation of the standard C system library (libc), tuned
for embedded Linux-based devices
Media Libraries
Packet Videos Open CORE; the libraries support playback and recording of many
popular audio and video formats, as well as static image files, including MPEG4, H.264, MP3,
AAC, AMR, JPG, and PNG
Surface Manager
Manages access to the display subsystem and seamlessly composites 2D and 3D graphic
layers from multiple applications
LibWebCore
A modern web browser engine which powers both the Android browser and an
embeddable web view
SGL
3D libraries
An implementation based on OpenGL ES 1.0 APIs; the libraries use either hardware 3D
acceleration (where available) or the included, highly optimized 3D software rasterizer
Free Type
SQLite
Android Runtime
Android includes a set of core libraries that provides most of the functionality available in
the core libraries of the Java programming language.
Every Android application runs in its own process, with its own instance of the Dalvik
virtual machine. Dalvik has been written so that a device can run multiple VMs efficiently. The
Dalvik VM executes files in the Dalvik Executable (.dex) format which is optimized for minimal
memory footprint. The VM is register-based, and runs classes compiled by a Java language
compiler that have been transformed into the .dex format by the included "dx" tool.
The Dalvik VM relies on the Linux kernel for underlying functionality such as threading
and low-level memory management.
Linux Kernel
Android relies on Linux version 2.6 for core system services such as security, memory
management, process management, network stack, and driver model. The kernel also acts as an
abstraction layer between the hardware and the rest of the software stack.
VERSION HISTORY
Android has seen a number of updates since its original release, each fixing
bugs and adding new features. Each version is named, in alphabetical order, after a
dessert. They are
v1.6 Donut
v2.0/2.1 Eclair
v2.2.x Froyo
Android Linux-based system, so as to modify Android, the user must know the
commands on the Linux system, and should log on as administrator.
ANDROID SDK
Android applications are packaged in .apk format and stored under /data/app
folder on the Android OS (the folder is accessible only to root user for security
reasons). APK package contains .dex files (compiled byte code files called Dalvik
executables), resource files, etc
WEB SERVICE
"Big Web services" use Extensible Markup Language (XML) messages that
follow the SOAP standard and have been popular with the traditional enterprises. In
such systems, there is often a machine-readable description of the operations
offered by the service written in the Web Services Description Language (WSDL).
WEB API
Web API is a development in Web services (in a movement called Web 2.0) where
emphasis has been moving away from SOAP based services towards representational state
transfer (REST) based communications. REST services do not require XML, SOAP, or WSDL
service-API definitions. Web APIs allow the combination of multiple Web services into new
applications known as mashups.
When used in the context of Web development, Web API is typically a defined set of
Hypertext Transfer Protocol (HTTP) request messages along with a definition of the structure of
response messages, usually expressed in an Extensible Markup Language (XML) or JavaScript
Object Notation (JSON) format.
STYLES OF USE
Web services are a set of tools that can be used in a number of ways. The
three most common styles of use are RPC, SOA and REST.
Service-oriented architecture
JSON
Object (an unordered collection of key: value pairs with the ':' character
separating the key and the value, comma-separated and enclosed in curly
braces; the keys must be strings and should be distinct from each other)
null (empty)
SCHEMA
FEATURES OF SQLITE
SQLite implements most of the SQL-92 standard for SQL but it lacks some features. For
example it has partial support for triggers, and it can't write to views (however it supports
INSTEAD OF triggers that provide this functionality). While it supports complex queries, it still
has limited ALTER TABLE support, as it can't modify or delete columns.[9]
SQLite uses an unusual type system for a SQL-compatible DBMS. Instead of assigning a
type to a column as in most SQL database systems, types are assigned to individual values; in
language terms it is Dynamically Typed. Moreover, it is weakly typed in some of the same ways
that Perl is: one can insert a string into an integer column (although SQLite will try to convert the
string to an integer first, if the column's preferred type is integer). This adds flexibility to
columns, especially when bound to a dynamically typed scripting language. However, the
technique is not portable to other SQL products. A common criticism is that SQLite's type system
lacks the data integrity mechanism provided by statically typed columns in other products. The
SQLite web site describes a "strict affinity" mode, but this feature has not yet been added.
However, it can be implemented with constraints like CHECK(typeof(x)='integer').
Several computer processes or threads may access the same database concurrently.
Several read accesses can be satisfied in parallel. A write access can only be satisfied if no other
accesses are currently being serviced. Otherwise, the write access fails with an error code (or can
automatically be retried until a configurable timeout expires). This concurrent access situation
would change when dealing with temporary tables. This restriction is relaxed in version 3.7 when
WAL is turned on enabling concurrent reads and writes.
Due to its small size, SQLite is well suited to embedded systems, and is also
included
Apple's iOS (where it is used for the SMS/MMS, Calendar, Call history and Contacts
storage)
Symbian OS
Nokia's Maemo
Google's Android
RIM's BlackBerry
Linux Foundation's MeeGo.
WINDOWS XP
Windows XP is a line of proprietary operating systems developed by Microsoft
for use on general-purpose computer systems, including home and business
desktops, notebook computers, and media centers. The letters "XP" stand for
experience. Windows XP was first released on October 25, 2001, and over 400
million copies are in use, according to a January 2006 estimate by an IDC analyst. It
is succeeded by Windows Vista, which was released to volume license customers on
November 8, 2006 and worldwide to the general public on January 30, 2007.
Windows XP is known for its improved stability and efficiency over previous
versions of Microsoft Windows. It presents a significantly redesigned graphical user
interface, a change Microsoft promoted as more user-friendly than previous versions
of Windows. Windows XP had been in development since early 1999, when Microsoft
started working on Windows Neptune, an operating system intended to be the
"Home Edition" equivalent to Windows 2000 Professional. Windows file protection
protects core system files from being over written by application installations.
If a file is overwritten, windows file protection will restore the correct version.
By safeguarding system files, windows XP professional mitigate many of the most
common system failures encountered in earlier versions of windows. A system
service that helps users installs, configure, track, update and remove software
programs correctly which helps to minimize user downtime and increase system
stability.
In windows XP professionals, EFS can provide multiple users access to an
encrypted document. Turned on by default, the built-in Windows Firewall helps
increase computer security from startup to shutdown. It reduces the risk of network
and internet-based attacks. Easily manage security resources with this single,
unified view of key settings, tools, and access to resources.
LINUX
Linux was originally developed as a free operating system for Intel x86-based personal
computers. It has since been ported to more computer hardware platforms than any other
operating system. It is a leading operating system on servers and other big iron systems such as
mainframe computers and supercomputers: more than 90% of today's top 500 supercomputers
run some variant of Linux, including the 10 fastest. Linux also runs on embedded systems
(devices where the operating system is typically built into the firmware and highly tailored to the
system) such as mobile phones, tablet computers, network routers, televisions and video game
consoles; the Android system in wide use on mobile devices is built on the Linux kernel.
The development of Linux is one of the most prominent examples of free and open
source software collaboration: the underlying source code may be used, modified, and distributed
commercially or non-commerciallyby anyone under licenses such as the GNU General
Public License. Typically Linux is packaged in a format known as a Linux distribution for
desktop and server use. Some popular mainstream Linux distributions include Debian (and its
derivatives such as Ubuntu), Fedora and openSUSE. Linux distributions include the Linux
kernel, supporting utilities and libraries and usually a large amount of application software to
fulfill the distribution's intended use.
A distribution oriented toward desktop use may include the X Window System and an
accompanying desktop environment such as GNOME or KDE Plasma. Other distributions may
include a less resource intensive desktop such as LXDE or Xfce for use on older or less powerful
computers. A distribution intended to run as a server may omit all graphical environments from
the standard install and instead include other software such as the Apache HTTP Server and an
SSH server such as OpenSSH. Because Linux is freely redistributable, anyone can create a
distribution for any intended use. Applications commonly used with desktop Linux systems
include the Mozilla Firefox web browser, the LibreOffice office application suite, and the GIMP
image editor.
UNIX
The Unix operating system was conceived and implemented in 1969 at
AT&T's Bell Laboratories in the United States by Ken Thompson, Dennis Ritchie,
Douglas McIlroy, and Joe Ossanna.
It was first released in 1971 and was initially entirely written in assembly
language, a common practice at the time. Later, in a key pioneering approach in
1973, Unix was re-written in the programming language C by Dennis Ritchie (with
exceptions to the kernel and I/O).
UBUNTU
Ubuntu is a computer operating system based on the Debian Linux distribution and
distributed as free and open source software, using its own desktop environment. It is named
after the Southern African philosophy of Ubuntu ("humanity towards others").
Ubuntu is designed primarily for use on personal computers, although a server edition
also exists.Ubuntu is sponsored by the UK-based company Canonical Ltd., owned by South
African entrepreneur Mark Shuttleworth.
Canonical generates revenue by selling technical support and services related to Ubuntu,
while the operating system itself is entirely free of charge. The Ubuntu project is committed to
the principles of free software development; people are encouraged to use free software, improve
it, and pass it on.
FEATURES
Ubuntu is a fork of the Debian project's codebase. The original aim of the Ubuntu team
was to create an easy-to-use Linux desktop with new releases scheduled on a predictable six-
month basis, resulting in a more frequently updated system Ubuntu's first release was on 20
October 2004.
The data flow diagram (DFD) is one of the most important tools used by
system analysts. There are four components in DFD. Process, terminators, data flow,
and data source are the four components of DFD. Circles are used to represent the
process, data flows are represented using a thin line with arrow, the terminators are
represented using rectangle and the data source is represented as an open - ended
rectangle.
Unlike detailed Flowchart, Data Flow Diagram does not supply detailed
description of the modules but graphically describes a systems data and how the
data interact with the system.
A data flow diagram has the purpose of clarifying system requirements and
identifying major transformation that will become programs in system design. It is
the starting point of the system design phase that functionally decomposes the
requirements specifications down to the lowest level of details. A data flow diagram
consists of a series of bubbles joined by lines. The bubbles represent data process
and the line represents data flow in the system. Dataflow diagrams are also known
as bubble chart. It consists of a series of bubbles joined by lines. The bubbles
represent data transformation and the lines represent the dataflow in the system.
Data Flow diagram represents the flow of data rather than how they are process. So
it doesnt depend on hardware, software and data structure and file organization.
An arrow identifies the data flow in motion. It is a pipeline through which information is
flown like the rectangle in the flowchart. A circle stands for process that converts data into
information. An open, ended box represents a data store, data at rest or a temporary repository of
data. A square defines a source or destination of system data.
DATA FLOW
A data flow moves data between processes or between processes and data
stores. As such, it represents a data value at some point within a computation and
an intermediate value within a computation if the flow is internal to the diagram.
This value is not changed.
The names of input and output flows can indicate their roles in the
computation or the type of the value they move. Data names are preferably nouns.
The name of a typical piece of data, the data aspect, is written alongside the arrow.
CONTROL FLOW
Process should be named and numbered for easy references. Each name
should be representative of the process. The direction of flow is from top to bottom
and from left to right. That is data flow should be from source and destination. When
a process is exploded into lower level details, they are numbered. The name of the
data stores, sources and destinations are written in capital letters. Process and data
flow names have the first letter of each word capitalized. The DFD is particularly
designed to aid communication. If it contains dozens of process and data stores it
gets too unwieldy. The rule of the thumb is to explode the DFD into a functional
level
SAMPLE DFD
The components of the ERD are object type, the relationship, associative
object type, super type /subtype indicators.
Super type / Subtype Indicators, The super type / subtype indicators consists
of object type and one or more subcategories, connected by a relationship.
An entity is an object that exists and is distinguishable from other objects. For
instance, pair with S.I.N. 890-12-3456 is an entity, as he can be uniquely identified
as one particular person in the universe. An entity may be concrete (a person or a
book, for example) or abstract (like a holiday or a concept). An entity set is a set of
entities of the same type (e.g., all persons having an account at a bank). Entity sets
need not be disjoint.
OPTIONAL RELATIONSHIP
It means that there may be instances of the first entity, which are not
associated with any instance of the second entity. For example, employee-spouse
relationship has to be optional because there could be unmarried employees. It is
not correct to make the relationship mandatory.
NORMALIZATION
There are five normal forms, each with increasing levels of normalization
FIRST NORMAL FORM (1NF): Every cell in the table must have only one value
(i.e.,) it should not have multiple values.
SECOND NORMAL FORM (2NF): All non-key attributes must be fully functional
dependent on the primary key and not just the part of the key.
THIRD NORMAL FORM (3NF): The database must be in second normal form
and non-prime attribute should be transitively dependent on the primary key.
FOURTH NORMAL FORM (4NF): It deals with multiple values dependencies.
Sets of fundamental design concepts are evolved over the past here decades. Although the
degree of interest in each concept has varied over the years, each has stood the test of time.
Fundamental design concepts provide the necessary framework for getting it right, Design is
defining a model of the new system and continues by converting this model to a new system.
The method is used to convert the model of the proposed system into
computer specification. Data models are converted to a database and processes
and flow to user procedures and computer programs. This new system may be built
by a fresh or by changing the existing system. The detailed design starts with three
activities, database design, user design and program design.
The input requirement for the system involves the process of converting the
user oriented inputs to a computer format. Collecting the input data for a system is
an expensive one. The input design should be validated such that it is free from
erroneous data. The user interface requirements are important input design, which
helps users how to access or enter data in the input form. The data is validated by
the system if they are any errors the system will give error messages, which is easy
to understand by the users. USER-ID: The users can log on to the system with the
user-id, which helps the system to identify the users.
PASSWORD: This is a facility that along with the user-id allows a user to log on to
the system.
A source document differs from a turnaround document in that the former
contains data that change the status of a resource while the latter is a mobile
readable needed. Social network requirement satisfaction throughput is the number
of error-free transactions entered during a specified time period.
There are several reasons why an effective design should control the quantity
of data for input. The input phase of computing can be slow process that can take
many times longer than the time needed by computers to carry out their tasks. By
reducing the analyst can speed the entire process from data capture to processing
to providing results to users.
DATA VERIFICATION
Data Verification is intended to find errors. The data is verified after the users
had entered the input data.
DATA VALIDATION
Input data are validated to minimize error in data entry. Computer input
procedures are designed to detect errors in the data at a lower level of detail which
is beyond the capacity of the control procedures. These are combined with the
design of their input process itself.
BASIC PRINCIPLES
Text or Numbers
Selection box
Consistency check
Database check
4.3 OUTPUT DESIGN
Output is the most important and direct sources of information to the user.
Efficient and intelligent output design improves the systems relationship with the
user thus helping in the process of the decision making. Audio information
transactions are generally referred to the results and the information that are in the
activities of operational information shared in to the cloud.
The output design consists of the two stages namely the output definition
stage and the output specification stage. A quality output is one, which meets the
requirements of the end user and presents the information clearly. In any system
results of processing are communicated to the users and to other mo through
outputs. In the output design it is determined how the information is to be displayed
for immediate need and also the soft copy. Outputs Activities computers are
required primarily to communicate the results of processing to the users. They are
also used to provide a permanent copy of these results for later consultation.
It is the most important and direct source information to the user. Efficient
and intelligent output design improves the systems relationship the user and helps
in decision-making. It is necessary that the output reports be compatible format
with the automatically. The output has been designed in mind. Output design is the
basis by which many users evaluate the usefulness of the system. The output
forms used in this mobile application are required for query response and reports.
The emphasis is required for producing the hard copy of the information requested
or displaying the output on a mobile screen.
5. SYSTEM TESTING AND IMPLEMENTATION
Testing is vital to the success of the system. System testing makes a logical
assumption, if all the parts of the system are correct; the goal will be successfully
achieved. System testing is the stage of implementation that we aimed at assuring
that the system works accurately and efficiently before live operation commences.
PURPOSE OF TESTING
The objectives of testing are the process of executing the program with the
intention of finding an error.
Therefore the most useful approach and practical approach is aid the
understanding that testing is the process of executing a program explicit indention
of finding errors that is making the program fall.
5.1.1Testing Methodologies
The following are the Testing Methodologies
Unit Testing
Integration Testing
Validation Testing
System Testing
Activity Testing
Content Provider Testing
UNIT TESTING
Unit testing focuses verification effort on the smallest unit of software design
the module. The relative complexity of the tests and the errors detected as a result
is limited by the constrained scope established for unit testing. The unit test is
always white box oriented and the step can be conducted in parallel for multiple
modules. According to unit testing the router system is error free. Unit testing has
been performed for all the form modules. The syntax and logical errors has been
corrected then and there. The output has been tested with the manual.
INTEGRATION TESTING
VALIDATION TESTING
SYSTEM TESTING
System testing is the testing of the integrated black box application, against
the applications requirements during the construction phase. The purpose of
system testing is it identifies band correct errors in candidate system. System
testing is the stage of implementation which aims at ensuring that the system
accurately and efficiently before the actual operation comments. In the project the
system testing is implemented for checking the security requirements like
prohibiting from unauthorized access, failures during invalid conditions and the
operational availability requirements.
ACTIVITY TESTING
Android includes powerful tools for testing applications. The tools extend JUnit with
additional features, provide convenience classes for mock Android system objects, and use
instrumentation to give you control over your main application while you are testing it. The
entire Android testing environment is discussed in the document Testing Android Applications.
This tutorial demonstrates the Android testing tools by presenting a simple Android
application and then leading you step-by-step through the creation of a test application for it. The
test application demonstrates these key points:
An Android test is itself an Android application that is linked to the application under test
by entries in its AndroidManifest.xml file.
Instead of Android components, an Android test application contains one or more test
cases. Each of these is a separate class definition.
Android test case classes for activities extend JUnit and also connect you to the
application under test with instrumentation. You can send keystroke or touch events
directly to the UI.
You choose an Android test case class based on the type of component (application,
activity, content provider, or service) you are testing.
Additional test tools in Eclipse/ADT provide integrated support for creating test
applications, running them, and viewing the results.
The test application contains methods that perform the following tests:
Initial conditions test. Tests that the application under test initializes correctly. This is also
a unit test of the application's onCreate() method. Testing initial conditions also provides
a confidence measure for subsequent tests.
UI test. Tests that the main UI operation works correctly. This test demonstrates the
instrumentation features available in activity testing. It shows that you can automate UI
tests by sending key events from the test application to the main application.
State management tests. Test the application's code for saving state. This test
demonstrates the instrumentation features of the test runner, which are available for
testing any component.
Content providers, which store and retrieve data and make it accessible across
applications, are a key part of the Android API. As an application developer you're allowed to
provide your own public providers for use by other applications. If you do, then you should test
them using the API you publish.
This document describes how to test public content providers, although the information is
also applicable to providers that you keep private to your own application. If you aren't familiar
with content providers or the Android testing framework, please read Content Providers, the
guide to developing content providers, and Testing Fundamentals, the introduction to the
Android testing and instrumentation framework.
ACCORDING TO PROJECT
During testing I tried to make sure that the product does exactly what is
supposed to do. Testing is the final verification and validation activity within the
organization itself. In the testing stage, I try to achieve the following goals; to affirm
the quality of the product, to find and eliminate any residual errors from previous
stages, to validate the software as a solution to the original problem, to
demonstrate the presence of all specified functionality in the product, to estimate
the operational reliability of the system. During testing the major activities are
concentrated on the examination and modification of the source code.
The applications validations are taken into account of the entry levels
available in various modules. Possible restrictions like number formatting, date
formatting and confirmations for both save and update options ensure the correct
data to be fed into the database.
A viewer is provided on the cellular phone that enables the user to see and
manipulate the desktop of various remote systems such as MS Windows, Macintosh,
and UNIX. The system to be accessed must be running the client program and it
must be attached to a network.
This project is designed with the future in mind. Due care has been taken to
assimilate the needs for future development. The software is constructed along the
lines suggested by the users.
A new tool creation is under process which will have the drag and drop
options which help the users generate reports by themselves and it is considered
to be a major enhancement for the application.
7.CONCLUSION
A Testing and validity check has also been carried out in different formats
that specifically define each transaction. Once the testing of whole system has been
with a data and the various outputs obtained are according the requirements; the
efficiency of the new system Attendance Management Systemwas found out to
better than existing manual system in all respects.
The software user guidelines which are provided make the user
to access through the correct path. Handling seems to be very easy and efficient.
Finally it acts as a user friendly, advantageous and is of easy to exchange the data
of mobile. The system is designed based on the objectives prepared in the analysis
phase of the existing system. The software user guidelines which are provided make
the user to access through the correct path. Handling seems to be very easy and
efficient. Finally it acts as a user friendly, advantageous and is of easy maintenance.
The system is designed based on the objectives prepared in the analysis phase of
the existing system.
The system is designed to be user interactive and user friendly. It reduces all
the work with accuracy and reliability. System computerization makes the works
with accuracy and reliability. System Computerization the work quicker and also
maintains the transactions accurately. The computerization helps the organization
to change according to the modern trend. Since the requirements may increase in
future, the system can be easily modified accordingly, as the system has been
modularized. The future expansion can be done in a concise manner in order to
improve the efficiency of the system. It provides quality assurance for every request
of the customers
8.BIBLOGRAPHY
BOOKS REFERRED
1. WEI-MENG LEE Edition, Beginning Android Application Development Wiley
Publishing Inc.
2. Rick Rogrts,Jhon Lombardo,Zigurd & BLAKE MEIKE Android Application
Development O,REILLY
3. Matthew Baxter-Reynolds Multimobile Development Building Applications
for iPhone and Android Discover developing an application end-to-end
natively professional android 2 application development
4. Reto Meier .Professional Android 2 application Development
5. Roger S Pressman, Software Engineering, Fifth Edition, BPB Publications.
6. Ron Petrusha and Paul Lomax, Visual Basic 2005, 3rd Edition, Shroff
publications.
7. Silberschatz, Korth, Sudharsan Database System Concepts, McGraw
Fourth Edition Hill Publications
WEBSITES REFERRED
www.stackoverflow.com
www.datamodel.com
www.dotnetcurry.com
www.sqltutorials.com
www.msdn.com
http://developer.android.com
www.helloandroid.com
www.udemy.com
www.script-tutorials.com
www.json.org
9.APPENDIX
Level 0:
Level 1:
Opening Screen
Figure No 9.4.2
Sample Codes:
Codes for Main page:
<LinearLayout
android:layout_width="fill_parent"
android:layout_height="fill_parent"
android:orientation="vertical" >
<LinearLayout
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:orientation="vertical" >
<TextView
android:id="@+id/tv_header"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:gravity="center"
android:text="Student Register"
android:textAppearance="?android:attr/textAppearanceLarge"
android:textColor="#ff0000"
android:textSize="6pt"
android:textStyle="italic" />
</LinearLayout>
<LinearLayout
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:layout_marginTop="30dp"
android:visibility="gone"
android:orientation="horizontal" >
<TextView
android:id="@+id/textView1"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_marginLeft="10dp"
android:text="Id"
android:textAppearance="?android:attr/textAppearanceMedium" />
<EditText
android:id="@+id/ed_id"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_marginLeft="88dp"
android:layout_marginRight="10dp"
android:enabled="false"
android:layout_weight="1"
android:ems="10" />
</LinearLayout>
<LinearLayout
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:layout_marginTop="10dp" >
<TextView
android:id="@+id/newform_View2"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_marginLeft="10dp"
android:text="Name"
android:textAppearance="?android:attr/textAppearanceMedium" />
<EditText
android:id="@+id/ed_name"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_marginLeft="60dp"
android:layout_marginRight="10dp"
android:layout_weight="1"
android:ems="10" >
<requestFocus />
</EditText>
</LinearLayout>
<LinearLayout
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:layout_marginTop="10dp"
android:orientation="horizontal" >
<TextView
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_marginLeft="10dp"
android:text="Class"
android:textAppearance="?android:attr/textAppearanceMedium" />
<Spinner
android:id="@+id/ed_class"
android:layout_width="match_parent"
android:layout_height="wrap_content" />
</LinearLayout>
<LinearLayout
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:layout_marginTop="10dp" >
<TextView
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_marginLeft="10dp"
android:text="Roll No"
android:textAppearance="?android:attr/textAppearanceMedium" />
<EditText
android:id="@+id/ed_roll"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_marginLeft="40dp"
android:layout_marginRight="10dp"
android:layout_weight="1"
android:ems="10"
android:inputType="textPostalAddress" />
</LinearLayout>
<LinearLayout
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:layout_marginTop="20dp" >
<TextView
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_marginLeft="10dp"
android:text="Phone"
android:textAppearance="?android:attr/textAppearanceMedium" />
<EditText
android:id="@+id/ed_phone"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_marginLeft="55dp"
android:layout_marginRight="10dp"
android:layout_weight="1"
android:maxLength="10"
android:ems="10"
android:inputType="phone" />
</LinearLayout>
<LinearLayout
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:layout_marginTop="20dp" >
<TextView
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_marginLeft="10dp"
android:text="Password"
android:textAppearance="?android:attr/textAppearanceMedium" />
<EditText
android:id="@+id/ed_password"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_marginLeft="55dp"
android:layout_marginRight="10dp"
android:layout_weight="1"
android:ems="10"
android:inputType="textEmailAddress" />
</LinearLayout>
<LinearLayout
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:layout_marginTop="20dp" >
<TextView
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_marginLeft="10dp"
android:text="Department"
android:textAppearance="?android:attr/textAppearanceMedium" />
<Spinner
android:id="@+id/ed_depart"
android:layout_width="match_parent"
android:layout_height="wrap_content" />
</LinearLayout>
<LinearLayout
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:visibility="gone"
android:layout_marginTop="20dp" >
<EditText
android:id="@+id/ed_status"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_marginLeft="55dp"
android:layout_marginRight="10dp"
android:layout_weight="1"
android:visibility="gone"
android:hint="Status"
android:ems="10"
android:inputType="text" />
</LinearLayout>
<Button
android:id="@+id/btn_save"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:gravity="center"
android:text="Save" />
</LinearLayout>
</ScrollView>
</LinearLayout>
package com.example.classmanagement;
import java.util.ArrayList;
import android.os.Bundle;
import android.support.v7.app.ActionBarActivity;
import android.view.View;
import android.widget.ArrayAdapter;
import android.widget.Button;
import android.widget.EditText;
import android.widget.Spinner;
import android.widget.Toast;
Button btn_save;
EditText
Ed_Name,Ed_Age,Ed_Phone,ed_id,ed_user,ed_pass,ed_email,ed_roll;
Spinner spn_gender,ed_depart,ed_class;
String[] accessarea;
String[] departnam={"Bsc IT","Bsc Cs","Bsc CT","BCA"};
ArrayList<Integer> accessareaid = new ArrayList<Integer>();
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_student);
ed_id=(EditText)findViewById(R.id.ed_id);
Ed_Name=(EditText)findViewById(R.id.ed_name);
ed_class=(Spinner)findViewById(R.id.ed_class);
Ed_Phone=(EditText)findViewById(R.id.ed_phone);
ed_roll=(EditText)findViewById(R.id.ed_roll);
ed_depart=(Spinner)findViewById(R.id.ed_depart);
btn_save=(Button)findViewById(R.id.btn_save);
ed_pass=(EditText)findViewById(R.id.ed_password);
String[] classname={"I","II","III"};
ArrayAdapter<String> arrayA = new ArrayAdapter<String>(
Register.this,
android.R.layout.simple_list_item_1,classname);
ed_class.setAdapter(arrayA);
ArrayAdapter<String> arrayAdapter1 = new ArrayAdapter<String>(
Register.this,
android.R.layout.simple_list_item_1,departnam);
ed_depart.setAdapter(arrayAdapter1);
btn_save.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {
// TODO Auto-generated method stub
Savedetails();
}
});
}
public void Savedetails()
{
QueryAdapter mDbHelper = new QueryAdapter(this);
mDbHelper.createDatabase();
mDbHelper.open();
String name = Ed_Name.getText().toString();
String roll = ed_roll.getText().toString();
String classes = ed_class.getSelectedItem().toString();
String depart = ed_depart.getSelectedItem().toString();
String contact = Ed_Phone.getText().toString();
String pass=ed_pass.getText().toString();
if(name.length()==0)
{
Toast.makeText(getApplicationContext(), "please enter the
valid input ", Toast.LENGTH_SHORT).show();
return;
}
if(contact.length()<10)
{
if(pass.length()==0)
{