Professional Documents
Culture Documents
BANK RATING
APPLICATION
A report on Bank Rating Application
Using Android and MySQL
By
ANUJ AGRAWAL
(1509113020)
Submitted to
I do, hereby, declare that the summer training report entitled BANK
RATING APP Project is done by me at QZIP INDIA PRIVATE
LIMITED under the supervision of Mr. Ashish Banerjee and submitted
as VII semester practical training for the degree of B.Tech.(IT) at JSS
ACADEMY OF TECHNICAL EDUCATION, INDIA.
ANU
J AGRAWAL
Rol
l No: 1509113020
2
3
ACKNOWLEDGEMENT
Anuj Agrawal
4
ABSTRACT
Access to relevant and accurate information is at the heart of tourism, more so in this
era of the Internet information overload has become a prevalent phenomenon and as
such a serious issue for those seeking for appropriate information. Furthermore,
various researches have been carried out on how to make information on tourism
website more effective. Tourism management system tries to bridge the gap by noting
what a tourist perceives as relevant, in terms of content pertaining to tourism products
in tourism websites. This study focuses mainly on content because it is seen as the key
factor associated with an effective website. Hence, the aim of this research entails the
design and implementation of an intelligent platform that will assist tourists in gaining
access to information on tourist locations in India. In view of the forgoing, the system
was implemented using Rational Unified Process as the adopted software
development process, whereas MySQL, HTML and JSP were the implementation
tools used in the development of the system. Upon completion, the system was able to
provide information by fetching information from the web pertaining to the subject of
interest to assist tourists in decision making process
Mobile technology is the technology used for cellular communication. Since the start
of this millennium, a standard mobile device has gone from being no more than a
simple two-way pager to being a mobile phone, GPS navigation device, an embedded
web browser and instant messaging client, and a handheld game console. Many types
of mobile operating systems are available for smart phones, including Android,
BlackBerry OS, iOS, Symbian, Windows Mobile and Bada.
1.2. Android
Android is an operating system based on Linux with a Java programming interface.
Android is a mobile operating system (OS) developed by Google. Android is the first
completely open source mobile OS. Building on the contributions of the open-source
Linux community and more than 300 hardware, software, and carrier partners,
Android has rapidly become the fastest-growing mobile OS.
Android Versions
2. Introduction to Android
7
Android Libraries
This category encompasses those Java-based libraries that are specific to Android
development. Examples of libraries in this category include the application
framework libraries in addition to those that facilitate user interface building, graphics
drawing and database access. A summary of some key core Android libraries available
to the
Android developer is as follows –
android.app − Provides access to the application model and is the cornerstone of all
android applications.
android.content − Facilitates content access, publishing and messaging between
applications and application components.
android.database − Used to access data published by content providers and includes
SQLite database management classes.
android.opengl − A Java interface to the OpenGL ES 3D graphics rendering API.
android.os − Provides applications with access to standard operating system services
including messages, system services and inter-process communication.
android.text − Used to render and manipulate text on a device display.
android.view − The fundamental building block of application user interfaces.
android.widget − A rich collection of pre-built user interface components such as
buttons, labels, list views, layout managers, radio buttons etc.
android.webkit − A set of classes intended to allow web-browsing capabilities to be
built into applications.
Having covered the Java-based core libraries in the Android runtime, it is now time to
turn our attention to the C/C++ based libraries contained in this layer of the Android
software stack.
Android Runtime
This is the third section of the architecture and available on the second layer from the
bottom. This section provides a key component called Dalvik Virtual Machine which
is a kind of Java Virtual Machine specially designed and optimized for Android. The
Dalvik VM makes use of Linux core features like memory management and
multithreading, which is intrinsic in the Java language. The Dalvik VM enables every
8
Android application to run in its own process, with its own instance of the Dalvik
virtual machine. The Android runtime also provides a set of core libraries which
enable Android application developers to wite Android applications using standard
Java programming language
Application Framework
The Application Framework layer provides many higher-level services to applications
in the form of Java classes. Application developers are allowed to make use of these
services in their applications.
The Android framework includes the following key services −
Activity Manager - Controls all aspects of the application lifecycle and activity stack
Content Providers - Allows applications to publish and share data with other
applications.
Resource Manager - Provides access to non-code embedded resources such as
strings, color settings and user interface layouts.
Notifications Manager - Allows applications to display alerts and notifications to the
user.
View System - An extensible set of views used to create application user interfaces.
Applications
You will find all the Android application at the top layer. You will write your
application to be installed on this layer only. Examples of such applications are
Contacts Books, Browser, and Games etc.
Each building block is a different point through which the system can enter your
application. Not all components are actual entry points for the user and some depend
on each other, but each one exists as its own entity and plays a specific role—each
one is a unique building block that helps define your application's overall behavior.
3.1 Activities
An activity is an application component that provides a screen with which users can
interact in order to do something, such as dial the phone, take a photo, send an email,
or view a map. Each activity is given a window in which to draw its user interface.
9
The window typically fills the screen, but may be smaller than the screen and float on
top of other windows. An application usually consists of multiple activities that are
loosely bound to each other. Typically, one activity in an application is specified as the
"main" activity, which is presented to the user when launching the application for the
first time. Each activity can then start another activity in order to perform different
actions. Each time a new activity starts, the previous activity is stopped, but the
system preserves the activity in a stack (the "back stack"). When a new activity starts,
it is pushed onto the back stack and takes user focus. The back stack abides to the
basic "last in, first out" stack mechanism, so, when the user is done with the current
activity and presses the Back button, it is popped from the stack (and destroyed) and
the previous activity resumes. When an activity is stopped because a new activity
starts, it is notified of this change in state through the activity's lifecycle callback
methods. There are several callback methods that an activity might receive, due to a
change in its state— whether the system is creating it, stopping it, resuming it, or
destroying it—and each callback provides you the opportunity to perform specific
work that's appropriate to that state change. For instance, when stopped, your activity
should release any large objects, such as network or database connections. When the
activity resumes, you can reacquire the necessary resources and resume actions that
were interrupted. These state transitions are all part of the activity lifecycle.
10
Figure 4 : Activity Lifecycle
4.PROPOSED SYSTEM:
The system allows one to easily access the relevant information and make
necessary travel arrangements.
Users can decide about places they want to visit and make bookings online for
travel and accommodation.
11
5. FEASIBILITY STUDY:
12
Will there be any resistance from the user that will undermine the possible application
benefits?
This system is targeted to be in accordance with the above-mentioned issues.
Beforehand, the management issues and user requirements have been taken into
consideration. So there is no question of resistance from the users that can undermine
the possible application benefits.
The well-planned design would ensure the optimal utilization of the computer
resources and would help in the improvement of performance status.
6. FUNCTIONAL REQUIREMENTS:
Number of Modules
After careful analysis the system has been identified to have the following modules:
1. Administrator module
2. Travels module
3. Routes module
4. Reservations module
5. Testimonials module.
13
This module provides the details of various travel agencies. A user can select the
appropriate agency depending on convenience and accessibility.
6.3. ROUTES MODULE:
This module provides information related to various routes connecting sources
and destinations. For each route, information such as source, destination, fare,
reservation details, pick up points etc are provides. Only administrator can add ,
delete, edit and manage the data. Users can only view the information.
6.4. RESERVATIONS MODULE:
This module provides functionalities that allow a user to book tickets or cancel
previously booked tickets. The module maintains the details of all reservations made
so far and allows administrator to either confirm or reject the bookings.
6.5. TESTIMONIALS MODULE:
Users of this application can post their opinions, complaints and suggestions
regarding this portal and services to the administrator. Accordingly, the administrator
can take various steps to act on the complaints and suggestions.
7. NON-FUNCTIONAL REQUIREMENTS:
Hardware: Pentium
RAM: 1GB
14
8. E-R DIAGRAM(ENTITY-RELATIONSHIP):
15
9.DFD (Context level Diagram):
Stately
USER Sojourn ADMINISTRATOR
Booking
DB
10.USE-CASE DIAGRAM:
16
11.DATABASE SCHEMA:
17
12.Architecture flow(N-Tier):
Security
Manageability
Easy Maintenance
Data Abstraction
The above mentioned points are some of the key design goals of a successful
n-tier application that intends to provide a good Business Solution.
Definition:
Simply stated, an n-tier application helps us distribute the overall
functionality into various tiers or layers:
Presentation Layer
Database/Data Store
18
Each layer can be developed independently of the other provided that it
adheres to the standards and communicates with the other layers as per the
specifications. This is the one of the biggest advantages of the n-tier
application. Each layer can potentially treat the other layer as a ‘Block-Box’.
In other words, each layer does not care how other layer processes the data as
long as it sends the right data in a correct format.
Presentation
Layer
Reques Respons
Business t e
Logic Layer
Data Link
Layer
Data
Fig 12 : N-Tier Architecture
Base
19
This layer encapsulates the Business rules or the business logic of the
encapsulations. To have a separate layer for business logic is of a great
advantage. This is because any changes in Business Rules can be easily
handled in this layer. As long as the interface between the layers remains the
same, any changes to the functionality/processing logic in this layer can be
made without impacting the others. A lot of client-server apps failed to
implement successfully as changing the business logic was a painful process.
12.4Database Layer:
13.Advantages:
Estimates(i.e. budget, schedule etc .) become more relistic as work
progresses, because important issues discoved earlier.
20
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
14.Performance Requirements:
Performance is measured in terms of the output provided by the
application. Requirement specification plays an important part in the analysis
of a system. Only when the requirement specifications are properly given, it
is possible to design a system, which will fit into required environment. It
rests largely with the users of the existing system to give the requirement
specifications because they are the people who finally use the system. This
is because the requirements have to be known during the initial stages so that
the system can be designed according to those requirements. It is very
difficult to change the system once it has been designed and on the other
hand designing a system, which does not cater to the requirements of the
user, is of no use.
The requirement specification for any system can be broadly stated as
given below:
The system should be able to interface with the existing system
The system should be accurate
The system should be better than the existing system
The existing system is completely dependent on the user to perform all the
duties.
15. Limitations
The study was limited to fifty (50) tourist locations in India; spanning both
the Natural and artificial attractions. There were cost and time implications
21
during the course of the study as it required gathering information of tourist
locations over a large geographical area.
22
CONCLUSION
23
MANAGEMENT SYSTEM will make tourism round the country fun and
easy because of easy access to relevant information.
REFERENCES
24
[4] Zhou F, Zhao M, Sun Z, Zhao J & Gong Z. (2014). The application of
intelligence tourism mobile client based on ontology. Journal of Chemical
and Pharmaceutical Research, Vol. 6(Isssue 5), pp 258-265.
[5] Sommerville, I. (2006). Software Engineering (Vol. 8). Addison-Wesley.
[6] Oludele A., Onuiri E., Olaore O., Sowunmi O. & Ugo-Ezeaba A. (2015).
A Real-Time Crime Record Management System For National Security
Agencies. European Journal Of Computer Science And Information
Technology, Vol. 3(2), pp. 1-12.
25