`,

MOBILE BASED ATTENDANCE SYSTEM

A PROJECT REPORT

Submitted by

ISHAN DWIVEDI
(1400118047)
&
MANMEET KAUR
(1400118053)

in partial fulfillment for the award of the degree

of

Bachelor of Computer Application

INTEGRAL UNIVERSITY LUCKNOW

MAY 2017

1
 INTEGRAL UNIVERSITY: LUCKNOW

CERTIFICATE

Certified that this project report “MOBILE BASED ATTENDANCE

SYSTEM” isbonafide work of “ISHAN DWIVEDI & MANMEET KAUR

”who carried out the project work under my supervision.

Mr. Mohammed Kalamuddin Ahmad

Assistant Professor
Department of Computer Application
Integral University, Lucknow

2
 INTEGRAL UNIVERSITY: LUCKNOW

CERTIFICATE

Certified that this project report “MOBILE BASED ATTENDANCE

SYSTEM “isbonafideworkof“ISHAN DWIVEDI &MANMEET KAUR”

who have successfully carried out the project.

Mr. Mohd. Faisal Dr. Mohammed Faizan Farooqui

Project Coordinator Head of Department
Department of Computer Application Department of Computer Application
Integral University, Lucknow Integral University, Lucknow

3
 DECLARATION

“I hereby declare that this submission is my own work and that, to the best of
my knowledge and belief, it contains no material previously published or
written by another person nor material which has been accepted for the award of
any other degree or diploma of the university or other institute of higher
learning, except where due acknowledgment has been made in the text”.

Date:

…………................

ISHAN DWIVEDI

…………................

MANMEET KAUR

4
 ACKNOWLEDGEMENT

It give me great pleasure to present before you my final year project report
on “MOBILE BASED ATTENDANCE SYSTEM.” strictly under the
guidance of guide Mr. Mohammed Kalamuddin Ahmad.
He had made sincere efforts to make the final year project more meaningful,
complete, compact and comprehensive. It’s a great pleasure to let you know
that I have put my felling into practice.
At last we give our special thanks to our batch mates for all the valuable
suggestion without which this project could not be completed.

THANK YOU

5
 ABSTRACT

Managing the attendance using traditional approach is really a cumbersome

process. The person has to maintain the attendance record in registers and file
using pen and paper. The problem with this approach is that it requires lots of
paper which are the part of our non-renewable natural resources. We are in the
age, where we have to think about sustainable development. Managing the
attendance using mobile phones, providean alternative way in this direction.
Communication between teachers and the parent is also an important issue
that should also be considered, because parent can only get the information
about their ward after the interaction with teachers. So, we also tried to bring
the system which enables parent to receive the information of their ward of
regularity on daily basis.

6
 INTRODUCTION

Attendance is taken every day on each working day whether it is

college, school or anyother institution and in this process every institution
wasted lots of paper just for keeping the record. With such small
reasons, our natural resources are depleting at the enormous rate
and it can be possible that our descendants don’t able to get those
resources. It is also important to inform guardians of the students about the
absence or presence of their ward. Some reputed schools and colleges are
there, who do it by arranging meetings between them at a specific interval of
time. But that’s not enough, parent need the report of their ward on regular basis.
So, there is a need to solve this problem and automate this process so that for
the absentees’ student, the sms or by any other means we should able to inform
that their ward is absent. This could be very helpful for both the teachers and
their guardians to keep an eye on their ward about their activity, his interest,
their regularity etc. So, they can take appropriate action accordingly.

7
 HARDWARE &SOFTWARE REQUIREMENT

For Development Purpose:

Software:

 Android SDK tools.

 Android Studio IDE.
 Android Emulator.
 Java SE JDK.
 Adobe Photoshope.

Hardware:

 4 GB RAM or more.
 Intel Pentium 4 or AMD Athlon 2 GHz (or Faster).
 At least 160 GB of the free hard disk space.

For Application Purpose:

Hardware:
 Android Device.
 At least 1 GB RAM.
 4 GB ROM or external space.

SOFTWARE:
 Android OS ( At least Lolipop).
 Bluestack (For window).

8
 EVOLUTION OF TECHNOLOGY ON MOBILE
DEVICES
It is possible to categorize the handheld transceiver (personal radio
transceiver or “walkie-talkie”) as the first mobile device used for
communication . The possibility 2 persons to communicate over a large
area increased the possibility to coordinate and implement actions
without visual contact. Its development dates from the Second World
War using batteries and vacuum tubes which made the devices a
considerable size. After the war and with the introduction of the
transistor, the handheld transceiver reduced its size and was introduced
safely and as a consumer device for recreation or other activities.
During the 50’s new ways for communication were introduced with the
pager. The pager was introduced as a device to receive phone messages
from a limited range, and it was used first by physicians in New York .
The technology of the pager also evolved to acknowledge, and replay
received messages. Although by the mid 90’s the availability of cellular
networks displaced the popularity of the pager, this technology is still
used in locations were the simplicity, and cost of the device still offer an
advantage over more advanced technologies.
Recently, the technology of mobile phones has also evolved. The first
mobile calls were performed on a device placed on a car in St Luis, USA
during the first half of the 40’s decade . By the 70’s mobile phone
technology started to grain ground based on the advances made by
Motorola Research Laboratories , with the first commercially available
mobile phone sold in the first half of the decade. While the phone had
severe disadvantages (high price, size, weight battery duration and
charging times), it had a very good consumer reception for the time, with
orders numbering in the thousands .

9
During the 80’s the technology started to be commercialized in the rest of
the world. Countries like Japan and the Nordic countries increased their
investment in infrastructure to support the cell networks needed to
support mobile phones . During this time new features were introduced
by the phone manufacturers to increase consumer appeal. Technologies to
reduce the batteries’ size (reducing the overall phone size) and the
introduction of text messages by the short message service
(SMS) were counted among these advancements. By the middle of the
1990s, mobile phones were starting to gain ground in the common
population. The call and device prices, while still high, started to be
accessible by the majority of the people . With the introduction of higher
processing power and features like games and applications, mobile phone
stopped being a luxury item and started to become tools for efficient
communication and collaboration among their users.
By the 2003, hardware resources where advanced enough to start
increasing additional features on phones. The launch of devices like
Blackberry started the era of smartphones, which increased mobile phone
features, by adding E-mail messaging, internet browsing, and a greater
number of business and consumer applications. By the first half of the
decade, it was possible for consumers to acquire smart phone devices
with an extend array of sensors and communication technologies
(Bluetooth, Wi-Fi) and high quality touch screens. By this time, advances
in new Operating Systems (OS) like iOS and Android, made it possible
for the general population to start creating applications, taking advantages
of the phone’s capabilities, and to commercialize them through vendor-
supported marketplaces.

10
 DESCRIPTION OF SOFTWARE SPECFICATION

Android

Android is a mobile operating system (OS) based on the Linux Kernel and
currently developed by Google. With a user interface based ondirect, Android is
designed primarily for touchscreen mobile devices such as smartphones and
tablet computers, with specialized user interfaces for televisions (Android TV),
cars (Android Auto), and wrist watches (Android Wear). The OS uses touch
inputs that loosely correspond to real-world actions, like swiping, tapping,
pinching, and reverse pinching to manipulate on-screen objects, and a virtual
keyboard. Despite being primarily designed for touchscreen input, it has also
been used in game consoles, digital cameras, regular PCs, and other electronics.
As of 2015, Android has the largestinstalled base of all operating systems.

As of July 2013, the Google Play store has had over one million Android
applications ("apps") published, and over 50 billion applications
downloaded.An April–May 2013 survey of mobile application developers found
that 71% of them create applications for Android;another 2015 survey found
that 40% of full-time professional developers see Android as the "priority"
target platform, which is more than iOS (37%) or other platforms.At Google
I/O 2014, the company revealed that there were over one billion active monthly
Android users, up from 538 million in June 2013.

Android's source code is released by Google under open source licenses,

although most Android devices ultimately ship with a combination of open
source and proprietary software, including proprietary software developed and
licensed by Google.Initially developed by Android, Inc., which Google bought
in 2005, Android was unveiled in 2007, along with the founding of the Open
Handset Alliance(OHA) – a consortium of hardware, software, and

11
telecommunication companies devoted to advancingopen standards for mobile
devices.

Android is popular with technology companies which require a ready-made,

low-cost and customizable operating system for high-tech devices. Android's
open nature has encouraged a large community of developers and enthusiasts to
use the open-source code as a foundation for community-driven projects, which
add new features for advanced usersor bring Android to devices which were
officially released running other operating systems. The operating system's
success has made it a target for patent litigation as part of the so-called
"smartphone wars" between technology companies.

Applications ("apps"), which extend the functionality of devices, are written

using the Android software development kit (SDK) and, often,
the Java programming language that has complete access to the Android APIs.
Java may be combined with C/C++, together with a choice of non-default
runtimes that allow better C++ support;the Go programming language is also
supported since its version 1.4, which can also be used exclusively although
with a restricted set of Android APIs.

The SDK includes a comprehensive set of development tools, including

a debugger, software libraries, a handset emulator based on QEMU,
documentation, sample code, and tutorials. Initially, Google's
supportedintegrated development environment (IDE) was Eclipse using the
Android Development Tools (ADT) plugin; in December 2014, Google
released Android Studio, based on IntelliJ IDEA, as its primary IDE for
Android application development. Other development tools are available,
including a native development kit (NDK) for applications or extensions in C or
C++, Google App Inventor, a visual environment for novice programmers, and
various cross platform mobile web applications frameworks. In January 2014,
Google unveiled a framework based on Apache Cordova for

12
porting Chrome HTML 5 web applications to Android, wrapped in a native
application shell.

Java

Java Platform, Standard Edition or Java SE is a widely used platform for

development and deployment of portable applications for desktop and server
environments. Java SE uses the object-oriented Java programming language. It
is part of the Java software platform family. Java SE defines a wide range of
general purpose APIs – such as Java APIs for the Java Class Library – and also
includes the Java Language Specification and the Java Virtual Machine
Specification. One of the most well-known implementations of Java SE
is Oracle Corporation's Java Development Kit (JDK).

13
 SYSTEM ANALYSIS AND USER REQUIREMENTS

The software requirement specification is produced at the culmination of the

analysis task. The function and performance allocated to software as part of
system engineering are refined by establishing a complete description, a
detailed functional description, a representation of system behavior, an
indication of performance requirements and design constraints, appropriate
validation criteria and other information requirements.

The Introduction of software requirements specification states the goals and

objectives of the software, describe it in context of the computer based system.
Actually the information may be nothing more than the software scope planning
document.
Here in this project the introduction is described as follows:

 Information content, flow and structure are documented.

 Hardware, software and human interfaces are described for external system
elements and internal software functions.
 The use of sensor that improves the usability efficiency.
A description of each function required to solve the problem is present in
functional description. A processing narrative is also provided.
In many cases, the software requirement specification maybe accompanied by
an executable prototype, a paper prototype or a preliminary user’s manual. The
preliminary user’s manual presents the software manual as a black box, i.e.,
heavy emphasis is laid on user input and the resultant output. The manual can
serve as valuable tool for uncovering problems at the human/machine interface.

14
 FEASIBILITY STUDY

A feasibility study is done to acquire a sense of the scope of application. During

the study, problem definition was crystallized and aspects of the problem to
included in the system were determined.
The answers of many key question (satisfaction of user need, estimated develop
ment cost etc.) were investigated to justify the possibilities of the project imple
mentation.
Following feasibilities were examined:
 Technical feasibility.
 Operational feasibility.
 Economic feasibility.
 Legal feasibility

Technical Feasibility
As we know the technical feasibility it concerned with specifying equipment
and software that will successfully satisfy the user requirement the technical
need of the system may vary considerable, but might include:

 The facility to produce output of advertisements, shopping and mailin

g in a given time for ease of use.
 Response time under certain condition is minimal.
 Ability to process a certain volume of transaction at a particular speed.
 Facility to communicate data to distinct location.

In examining the technical feasibility, configuration of the system is given more

importance them the actual make of hardware. The configuration should give
thecomplete the picture about the system’s requirement how many workstation

15
are required, how these units are interconnected so that they could separate and
communicate smoothly.

The videos that were recorded for the app were heavy in size which somehow
compromised with the technical feasibility of the app. But those videos were the
n converted into small sized frames that made it technically feasible. It is a light
weight app that consume lees memory and hard drive space.

Being a simple app that supports all version of android, the app can be downloa
ded and run any android device.

Operational Feasibility
Proposed project are beneficial only if they can be turned into information syste
m that will meet the financial management requirement of the organization.
This test of feasibility asks if the system will work when it developed and install
ed. If there are any major barriers to implementation or not.

Some of the important question that are useful to the test the operation
feasibility of a project are given below:

 Is there sufficient support for the project from the implementation? From
user? If the present system is well liked and used to the extent that person
will not be able to see reasons for change, there may be resistance.

 Are the current business method acceptable to the user? If they are not,
user may welcome a change that will bring about a more operational and
useful system.

16
 Have the user been involved in the planning and development of the
project, Ifthey are involved at the earliest stage of the project
development, the chances of resistance can be possibly reduced.

 Will the proposed system cause harm? Will it produce result in any case
or area?
 Will the performance of staff member fall down after implementation?
 Appears to be quite minor at the early stage can grow into major problem
after implementation.
After analysing the above points it was found that the developed project r
esponds positively in context to the raised queries. Hence, operational fea
sible.

Economical Feasibility
Economic analysis is the most frequently used technique for evaluating
theeffectiveness of the proposed system. More commonly known as cost
analysis, the procedure is to determine the benefits and savings that are
expected from the purposed system and compared with costs.

If benefit outweight cost, a decision is taken to design and implement syst

ems Otherwise, further justification or alternative of the proposed system
will have to be made if it has a chance of being approved. This is an ongo
ingeffort that improves in accuracy at each phase of the system life cycle.
The analysis part also clears the doubt of economic problems which coul
d be possible in developing the system. As already mentioned that compa
ny has to just pay the developed software cost and not other investment is
needed at the time of implementation of the new system as the preliminar
y requirements already exist in the company.

17
The development of this application didn’t involve any unbalance in the c
ontanalysis. Hence, Economically feasible.

Legal Feasibility
In the legal Feasibility is necessary to check that the software we are goin
g to develop is legally correct which means that the ideas which we have t
aken for the proposed system will legally implemented or not so, it is also
an important step in feasibility study.

Development of this project doesn’t involve any compromise to legal issu

es or political factors. This proves that the development of this software is
also feasible in legal aspect. Being legally feasible also ensures the future
scope of the developed project.

18
 SYSTEM PLANNING

Work Breakdown Structure:

Work breakdown structure is used to decompose a given task set recursively

into small activities. WBS provides a notation for representing the major tasks
needed to be carried out in order to solve a problem. The root of the tree is
labeled by the problem name. Each node of the tree is broken down into smaller
activities that are made the children of the node. Each activity is recursively
decomposed into smaller sub-activities until at the leaf level; the activities
require approx. two weeks to develop. If a task is broken down into a large
number of very small activities, these can be distributed to a large number of
engineers. If the activity ordering permits, the solutions to these can be carried
out independently. Thus, it becomes possible to develop the product faster.

19
 DESIGN

After the analysis phase we have with us the details of the existing system and
the requirements of the user for the new system. This phase diverts focus from
the problem domain to the solution domain. It acts as a bridge between the
requirement phase and its solution. The design phase focuses on the detailed
implementation of the system recommended in the feasibility study.
Systems design is the process or art of defining the architecture, components,
modules, interfaces, and data for a system to satisfy specified requirements.
There is some overlap with the disciplines of systems analysis, systems
architecture and systems engineering.
Object-oriented analysis and design (OOAD) methods are becoming the most
widely used methods for computer system design. The UML has become the
standard language used in Object-oriented analysis and design. It is widely used
for modeling software systems and is increasingly used for high designing non-
software systems and organizations

External Design
External design consists of conceiving, planning out and specifying the
externally observable characteristics of the software product.
These characteristics include user displays or user interface forms and the report
formats, external data sources and the functional characteristics, performance
requirements etc. External design begins during the analysis phase and
continues into the design phase.

20
Logical design
The logical design of a system pertains to an abstract representation of the data
flows, inputs and outputs of the system. This is often conducted via modeling,
which involves a simplistic (and sometimes graphical) representation of an
actual system. In the context of systems design, modeling can undertake the
following forms, including:
 
 Data flow diagrams
 
 Entity Life Histories
 
Entity Relationship Diagrams

Physical design
The physical design relates to the actual input and output processes of the
system. This is laid down in terms of how data is input into a system, how it is
authenticated, how it is processed, and how it is displayed as output.
Physical design, in this context, does not refer to the tangible physical design of
an information system. To use an analogy, a personal computer's
physical design involves input via a keyboard, processing within the CPU, and
output via a monitor, printer, etc.
It would not concern the actual layout of the tangible hardware, which for a PC
would be a monitor, CPU, motherboard, hard drive, modems, video/graphics
cards, USB slots etc.

21
 TESTING METHODOLOGIES

System Testing
This is the phase of the software development life cycle where the system
testing or integration testing is carried out. The system test is done using the
STP, STS and system test data. Many companies do alpha and / or beta testing
also.
Alpha testing is done when the system or product has a lot of new previously
untested features. Since there is a lot of untested functionality, the development
team might be uncomfortable proceeding with the final testing and release of
the product until they get a feedback from a limited Number of users/customers.
So the developers use the alpha testing primarily to evaluate the success or
failure of the new features incorporated into the system.
Beta testing is required when the development team decides that some level of
customer evaluation is needed prior to the final release of the product. In the
case of the beta testing the developers are no longer looking for user inputs on
functionality or features. The product has all the functionality incorporated in it,
so the development team will be looking for the beta testers to uncover bugs and
faults in the system. Unlike alpha testing the beta testing is done at a much
higher than that for alpha testing. Usually companies distribute the beta releases
free of cost to the people who have enrolled for the beta testing program and in
many cases the beta versions will be available for download from the
company’s web site. New products will have the alpha testing followed by the
beta testing. But in the case of new versions of existing products either product
either alpha or beta testing is done. The tasks in this phase are:
 Carry out system test according to the STP and STS. For alpha and beta
testing there will be no test plans. In the case of alpha testing the testers will

22
 be evaluating the acceptability of the new features or functionality and in
thecase of beta testing the testers will be trying to find out bugs or problems
in the product.
 Record the test results.
 Log the test errors.
 Diagnose and fix errors
 Update defect logs.
 Initiate corrective action as applicable. This might involve revisiting earlier
phases of SDLC.
 Perform regression testing.
 Consolidate and report test results and findings.

Acceptance Testing
Acceptance testing is the formal testing that is conducted (usually by the user,
client or an authorized entity) to determine whether or not a system satisfies its
acceptance criteria and to enable the customer to determine whether or not to
accept the system. This phase is carried out only if the system is developed for a
particular client /customer. In this phase the project team prepares for the
acceptance test by ensuring the availability and completeness of all work items
needed for acceptance test and loading the acceptance test data. The project
team will assist the client/customer in acceptance testing, recording the errors
found and fixing them. The main tasks in the phase are:
 Provide support to the client in conducting acceptance test. Ensure that
documentation-related tests are also completed.
 Record acceptance test results.
 Log acceptance test errors.
 Diagnose and fix errors.
 Update the defect logs.
 Revisit earlier phases of SDLC, as required, in order to fix errors.

23
 REVIEW OF PREVIOUS WORK

Many systems and applications have been developed in this regard to solve
the automating the process of attendance, but almost none of them fullfil the
whole requirements. Many problems can be seen on those existing applications,
some lack GUI, some lack automating the process of informing the care taker
or guardians. There are software available for automating such problem of
attendance but being the fact that desktop it consumes more energy or power
consumption that the mobile.
Nowadays, attendance is generally taken on the piece of paper in register.
Using mobile for taking attendance, consumes not only less energy but also
helps in reducing the wastage of paper and can serve as green way for taking
the attendance. Use of paper, nowadays can be eliminated by the use of mobile
or automating the process of attendance. As now generally every person has a
mobile device and thus can read the sms easily on the spot to get the status of
their ward in their college or school.

Thus although there exists a system for implementing this feature as desktop
applicationfor particular college or school or any other place, But with the
mobile, we get solution that is green and eco -friendly i.e. consume less energy
and power and also provide a good interface and easy to use for taking the
attendance. Mobile being portable can help teachers or any other user to
take attendance on their mobile and view the various statistics to analyze the
attendance record of the student.

24
 PROPOSED WORK

We tried to implement a system which overcomes the limitations of the existing

approach. Taking the attendance on mobile phones instead of traditional
approach is one step forward to sustainable development. Doing the same
work on mobile phones not only saves our resources but also enables the user
to get easy and interactive access to the attendance records of student. We
tried to make an application that can help the teacher to take attendance of
the students through their own mobile device. What could me more interesting
for that!!
The problem that guardians or parents are not able to get the status of their
child time to time or we can say on daily basis. The application that we
are building can allows teacher or any departmental head to take the
attendance through their mobile devices, manage records, inform to their
parents or guardians to the status of his/her child of what actually they are
doing it. It provides a good interactive user interface to get the user of taking
the attendance and he become able to send the sms to the mobile number given
in the details of the students in the file. User should make sure that the mobile
number entered is of their mobile device. So sending emails and sms or
calling them individually is old process now. It reduces many things like
energy coefficients thus green method and helps user to get reduce the effect of
greenhouse gases.

25
 DATA FLOW DIAGRAM

A data flow diagram (DFD) is a graphical representation of the "flow" of data

through an information system, modelling its process aspects. A DFD is often
used as a preliminary step to create an overview of the system, which can later
be elaborated. DFDs can also be used for the visualization of data processing
(structured design).

A DFD shows what kind of information will be input to and output from the
system, where the data will come from and go to, and where the data will be
stored. It does not show information about the timing of process or information
about whether processes will operate in sequence or in parallel

0 Level DFD

A context diagram is a top level (also known as "Level 0") data flow diagram. It
only contains one process node ("Process 0") that generalizes the function of the
entire system in relationship to external entities. DFD Layers. Draw data flow
diagrams can be made in several nested layers.

26
27
 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 logical structure of databases.

28
SYSTEM ARCHITECTURE

29
STRUCTURE OF PROPOSED SYSTEM

30
FUNCTIONAL BLOCK DIAGRAM

31
STRUCTURES OF FUNCTIONAL MODELS

32
SCREENSHOTS OF PROJECT

Activity-1

Activity-1

User Login Page

33
 Activity-2

Field of Teacher Attendance

34
Activity-3

35
Activity-4

36
 Gantt chart

Gantt charts (developed by Henry L. Gantt) are project control techniques

that can be used for several purposes, including scheduling, budgeting and
resource planning. A Gantt chart is a bar chart, with each bar representing an
activity. The bars are drawn against a time line. The length of each bar is
proportional to the length of time planned for the activity. We estimated the
number of weeks required for each of the seven tasks as follows:
1. Analysis 3 Weeks
2. Design 4 Weeks
3. Coding 8 Weeks
4. Testing 4 Weeks
5. Write Manual 2 Weeks
6. Implementation 1 Week
7. Maintenance 2 Weeks

37
 Pert chart

A PERT (Program Evaluation and Review Technology) chart is a

network of boxes (or circles) and arrows. There are different variations of PERT
Charts, some use the boxes to represent the activities and some use arrows to do
so. We will use the first approach here. Each box thus represents an activity.
The arrows are used to show the dependencies of activities on one another. The
activity at the head of an arrow can not start until activity at the tail of the arrow
is finished.

38
 CONCLUSION

In this paper we have discussed about the problems caused due to the use of
traditional approach in taking the attendance and solutions for that through
the use of mobile and provide a new approach.
The goals achieved in following this approach: Automate the
attendance management using mobile devices to reduce the dependencies on
natural resources and also provides a way of communication between parents
and teachers. Integrating the student’s mobile phones with the application so
that the application detects automatically the students that are present is a great
thing to be added in the future.
Integrate it with the centralized server of the college/school so that the server
will send the sms to the guardians of the absentee’s students and informing
them about his or her ward. We will try to generate the daily report that will be
submitted to the centralized server for its record. This can also use
Bluetooth technology or Wi-Fi technology for communication between
device and central server within campus. These are some future works which
can be implemented further.

39
 References

Designing and implementation purpose: -

1. Software engineering: a practitioners approach by roger s pressman.
2. System analysis and design by Elias m. Ewad.

Coding phase: -
1. Android Programming by Bill Philips & Brian Hardy
2. Android Design Patterns by Greg Nudelman

3. Android : user Interface Design by Lan G. Clifton

Referenced Sites:
.http://www.iisjaipur.org/iiim-current-
08/MCA_IV_Sem_Pro_Eva/15.Project%20
Attendence%20managemnt%20system.pdf
12.http://www.engadget.com/2005/07/24/could-nokia-dump-symbian/

40
Bio Data of group member 1:
Ishan Dwivedi
Email:[email protected]
Mob.:7275797466
Jankipuram
Lucknow, Uttar Pradesh-226021

ACADMIC QUALIFICATION
Degree University/Institute Board of Subject Percentage Year of
Education / CGPA Passing
Bachelor Integral 60% 2017
of University,Lucknow
Computer
Application
XII Nirmala Convent ISC Science 68% 2014
Inter College (P.C.M)
X Nirmala Convent ICSE Science 59% 2012
Inter College

MINI PROJECT


The topic of my Mini Project was “Photo Editor” with Visual Basic as a Front
end and Access as a Back end.


PROGRAMMING LANGUAGES KNOWN

 C++
 JAVA
 HTML





41
SEMINAR AND WORKSHOP

 Participated in “ X’ZEQT” conducted on October 7th,2015 organized by

Competitive Examination Preparation Committee (C.E.P.C) under aegis
of Indian Society for Technical Education (ISTE) Student Chapter.


 Participated in National Seminar on “Emerging Trends &
Advancement in Cyber Security” held on 4th April, 2016 under the
aegis of Indian Society for Technical Education (ISTE) Chapter
organized by Department of Computer Application, Integral University,
Lucknow.

 As Student Volunteer in Seminar and Workshop held in School, College

and outside.

PERSONAL PROFILE

Father’s Name : Mr. Kamlesh Kumar Dwivedi

Date of Birth : 1st April, 1996

Date: ,2017
Place :Lucknow (ISHAN DWIVEDI)

42
 Bio Data of group member 2:
Manmeet Kaur
Email:@gmail.com
Mob.:8604007341
Chaman Park, Indra Vihar
New Delhi - 110094

ACADMIC QUALIFICATION

Degree University/Institute Board of Subject Percentage Year of

Education / CGPA Passing
Bachelor Integral University, 78.2% 2017
of Lucknow
Computer
Application
XII Sri Ram Champa UP Science 80.00% 2014
Devi VidyaMandir (P.C.M)
Inter College
X Biswan City UP Science 79.20% 2012
Montessori School

Mini Project

The topic of my Mini Project was “ATM SECURITY” with Visual Basic as a
Front end and Access as a Back end.

LANGUAGES :

Core Java
C++

43
SEMINAR AND WORKSHOP

 Participated in “APTI-TECH 2015” conducted on March 18-19 2015

organised by CAREER COUNSELING COMMITTEE (CCC) of
Department of Computer Application, Integral University, Lucknow.

 Participated in “ X’ZEQT” conducted on October 7th,2015 organized by

Competitive Examination Preparation Committee (C.E.P.C) under aegis of
Indian Society for Technical Education (ISTE) Student Chapter.

 Participated inNational Seminar on “Emerging Trends & Advancement

in Cyber Security” held on 4th April, 2016 under the aegis of Indian
Society for Technical Education (ISTE) Chapter organized by Department
of Computer Application, Integral University, Lucknow.

 As Student Volunteer in Seminar and Workshop held in School, College

and outside.

PERSONAL PROFILE

Father’s Name : Mr. Divendra Singh

Date of Birth : 4th July,1997

DATE: , 2017
PLACE:Lucknow(MANMEET KAUR)

44
45