Minor Project Report On

BILL BRAIN (Android Application)

Bhagwan Parshuram Institute of Technology, Delhi

Submitted by: Ritesh Chandna (14820802710) Nikhil Nanda (14920802710) Shashank Jain (15220802710) CSE - B

Submitted To: Mr. Madhur Jain

TABLE OF CONTENTS

Topic No. 1 2 2.1 2.2 3 3.1 3.2 4 5

Particulars Problem Statement Introduction What is Android? Features and Specifications Project Details User Interface Database Connectivity Future Scope References

Page No. 1

2 3

4 8 10 11

1. INTRODUCTION
This wonderful application, BILLBRAIN, makes the tiring task of filling in your billing information a thing of the past. All of us generally face a problem of remembering the unique consumer IDs and then comes the monotonous task of filling in your basic information every time you need to pay the bills online. This application helps to root out this problem. It will help you auto-fill all the required data of your online billing transactions. All you need to do is to do a onetime sign up and fill in all the details in our interface. The application will then store all this information in its database and the next time you need to pay a bill just sign in and click on the company name for which the bill is due and DONE! All your details are filled. The payment option will then simply redirect you to the online payment page and you can carry on as usual. Currently, due to our limited resources and time, we have only developed this application for the bill payment of MTNL, the national telephone company and BSES, but we have planned to develop a similar facility for payments of other utilities such as domestic fuel gas, electricity supply and other telecom companies as well which can be paid through a single application and a single username.

ANDROID:
Operating Systems have developed a lot in last 15 years. Starting from black and white phones to recent smart phones or mini computers, mobile OS has come far away. Especially for smart phones, Mobile OS has greatly evolved from Palm OS in 1996 to Windows pocket PC in 2000 then to Blackberry OS and Android. [4] One of the most widely used mobile OS these days is ANDROID. Android does a software bunch comprise not only operating system but also middleware and key applications. Android Inc was founded in Palo Alto of California, U.S. by Andy Rubin, Rich miner, Nick sears and Chris White in 2003. Later Android Inc. was acquired by
3

Google in 2005. After original release there have been number of updates in the original version of Android. [4]

Features and Specifications

Android is a powerful Operating System supporting a large number of applications in Smart Phones. These applications make life more comfortable and advanced for the users. Some of the current features and specifications of android are:

Table 1.1 Features of Android [4] Android comes with an Android market which is an online software store. It was developed by Google. It allows Android users to select, and download applications developed by third party developers and use them. There are around 2.0 lack+ games, application and widgets available on the market for users. Android applications are written in java programming language. Android is available as open source for developers to develop applications which can be further used for selling in android
4

market. Android relies on Linux version 2.6 for core system services such as security, memory management, process management, network stack, and driver model. For software development, Android provides Android SDK (Software development kit). [4]

CHAPTER 2 - SOFTWARE REQUIREMENT SPECIFICATION

CONTENTS 2.1 Introduction 2.1.1 Purpose 2.1.2 Definitions, Acronyms and Abbreviations 2.1.3 Intended Audience and Reading Suggestions 2.1.4 Project Scope 2.2 Overall Description 2.2.1 Product Perspective 2.2.2 Product Functions 2.2.3 User Classes and Characteristics 2.2.4 Operating Environment 2.2.5 Design and Implementation Constraints 2.2.6 Assumptions and Dependencies 2.3 External Interface Requirements 2.3.1 User Interface 2.3.2 Hardware Interfaces 2.3.3 Software Interfaces 2.3.4 Communications Interfaces 2.4 Other Nonfunctional Requirements 2.4.1 Performance Requirements 2.4.2 Safety Requirements 2.4.3 Security Requirements 2.4.4 Software Quality Attributes 2.4.5 Business Rules

2.1 Introduction
2.1.1 Purpose The purpose of this Software Requirement Specification (SRS) is to specify the requirements of the android application Bill Brain. This document will cover each of the systems intended features, as well as offer a preliminary glimpse of the software applications User Interface (UI). The document will also cover hardware, software, and various other technical dependencies.

2.1.2 Definitions, Acronyms and Abbreviations SRS: Software Requirement Specification IEEE: Institute of Electrical and Electronic Engineers. GUI: Graphical User Interface

2.1.3 Intended Audience and Reading Suggestions This document is intended for all individuals participating in and/or supervising the Bill Brain application. Readers interested in a brief overview of the product should focus on the rest of Part 1(Introduction), as well as Part 2 of the document (Overall Description), which provide a brief overview of each aspect of the project as a whole. Part 3 (External Interface Requirements) offers further technical details, including information on the user interface as well as the hardware and software platforms on which the application will run. Readers interested in the non-technical aspects of the project should read Part 4, which covers performance, safety, security, and various other attributes that will be important to users.

2.1.4 Project Scope The Bill Brain system is composed of two main components: a client-side application which will run on Android handsets, and a server-side application which will support and interact with various client-side features. The system is designed to help user auto-fill all the required data of their online billing transactions. User need to do a onetime sign up and fill in all the details in the interface. The application then store all this information in its database and the next time user need to pay a bill has to just sign in and click on the company name for which the bill is due and DONE! All the details are filled. The payment option then simply redirect to the online payment page and user can carry on as usual.

2.2 Overall Description

2.2.1 Product Perspective The Bill Brain project is a new, self-contained product intended for use on the Android platform. While the Bill Brain mobile application is the main focus of the project, there is also a server-side component which will be responsible for database and synchronization services. The scope of project encompasses both server- and client-side functionalities, so both aspects are covered in detail within this document.

2.2.2 Product Functions

This application makes the tiring task of filling in billing information a thing of the past. All of us generally face a problem of remembering the unique consumer ID s and then comes the monotonous task of filling in our basic information every time we need to pay the bills online.

Application helps to root out the above problem. It helps user auto-fill all the required data of their online billing transactions. User need to do a onetime sign up and fill in all the details in the interface. The application stores all this information in its database and the next time user need to pay a bill has to just sign in and click on the company name for which the bill is due and DONE! All the details are filled. The payment option then simply redirect to the online payment page and user can carry on as usual.

2.2.3 User Classes and Characteristics There are two types of users that interact with the system: users of the mobile application and administrators. Both of users have different use of the system so each of them has their own requirements. The mobile application helps the users to pay their respective bills of MTNL and BSES anywhere anytime from their android smartphone. In order to this, user doesnt require to have its bill details at its disposal as the information is automatically retrieved from the applications database. The administrator is managing the overall system so there is no incorrect information within it.

2.2.4 Operating Environment The main component of the Bill Brain project is the software application, which will be limited to the Android operating system (specifically Android 2.2 and above). The application is not resource or graphics-intensive, so there are no practical hardware constraints. Beyond that, the application is self-contained unit and will not rely on any other Android-related software components.

2.2.5 Design and Implementation Constraints

The primary design constraint is the mobile platform. The application is designated for mobile handsets, limited screen size and resolution will be design consideration. Creating a user interface which is effective and easily navigable will be difficult challenge. 2.2.6 Assumptions and Dependencies One assumption about the product is that it will always be used on mobile phones that have enough performance. If the phone does not have enough hardware resources available for the application, for example the users might have allocated them with other applications; there may be scenarios where the application does not work as intended or even at all. The implementation of the above mentioned features is entirely dependent upon the time spent designing and implementing the core features. The final decision on whether or not to implement these features will be made during the later stages of the design phase.

2.3 External Interface Requirements

2.3.1 User Interface

On the first page, there is an image button whose onclick property sets the next activity. In the next two screenshots, list view has been used and the onclick property of each of its items sets the next activity.

In the last screenshot, custom view has been used wherein two text views have been combined, one for the subject and the other for the book name.

10

2.3.2 Hardware Interfaces Bill Brain is intended as a mobile application for the Android platform and hence is solely supported on Android-powered devices. It is being developed specifically for Android 2.2 (Froyo) and all versions released after it. The Android platform provides abstractions for all network communication interfaces and thus the hardware as well.

2.3.3 Software Interfaces Any windows based operating system Eclipse for developing the software

2.3.4 Communications Interfaces The communication between the different parts of the system is important since they depend on each other. However, in what way the communication is achieved is not important for the system and is therefore handled by the underlying operating systems for the mobile application.

2.4 Other Nonfunctional Requirements:

2.4.1 Performance Requirements Performance should not be an issue because all of our server queries involve small pieces of data. Changing screens will require very little computation and thus will occur very quickly. Server updates should only take a few seconds as long as the phone can maintain a steady signal.

2.4.2 Safety Requirements

11

Bill Brain will not affect data stored outside of its servers nor will it affect any other applications installed on the users phone. It cannot cause any damage to the phone or its internal components. The only potential safety concern associated with this application applies to virtually all handset apps: Bill Brain should not be used while operating a vehicle or in any other situation where the users attention must be focused elsewhere.

2.4.3 Security Requirements This application assumes that only the user or whoever he/she allows will have access to his/her Android handset.

2.4.4 Software Quality Attributes The system is easy to load and light .It adds to the quality and usability of the system. Some others quality considerations such as adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability will also be very seriously taken to consideration.

2.4.5 Business Rules Nothing is above customer satisfaction. So the rules need to be kept flexible to meet user needs and preferences at different times. Other models can be applied but is beyond the scope of the team.

12

3. DIAGRAMS

13

3. PROJECT DETAILS
3.1 User Interface
Register New Account

The user will have to go through a onetime signup where he will have to set up an account against an email id and select the password for the same. To create a signup page following components have been used: EditText: It is used to get the basic information like email id, password from the user [5] TextView: It tells the user which field to enter Button: By clicking on Register New Account button user account is created. And, if email already exists in database then it will toast up a warning message to user. Once a user account is successfully created, intent function is used to navigate a user to login page.
14

Log in Page

The Login page will have the basic functions and would give a clean and finished look. The user will have to enter its user name which will be an email id along with the password. EditText: It is used to get the basic information like email id, password from the user [5] TextView: It tells the user which field to enter Button: By clicking on Login button user is navigated to user account page of Bill Brain; only if email and password matches with the database record Check Box: If it is checked, the application remembers the last user id and password entered by the user
15

User Account

. In this four Buttons are used in which each button is used to go to a respective page. By clicking on View Bill and Pay Bill button, user is navigated to the respective service provider website. Add bill details: Navigated to the page where user adds their bill details. View bill details: User can view their entered details which are stored in database
16

Register New Bill

User need to fill in all the billing information such as CA number for the first time so that it can be stored in a database. After clicking on Confirm Button, user would be navigated back to his account, where user can View, Pay and Add bill details.

Selection of vendor: ImageButton:

17

18

3.2 Database Connectivity

An external database is created in MySQL which is stored on our local host that contains all the data entered in the application by the user. It is connected to the application by a PHP (Hypertext Preprocessor). All the data entered can be verified and accessed by the administrator. All the details entered by the user during login are verified from the external database and the user is granted an access only if the details entered matches with the details in the database. Flow of Data will be: [6]

Android

PHP

PHP

MySQL

19

This page shows the users information entered in Register New Bill. User information is taken from the database which is created in MySQL.

20

CHAPTER 4 PROCESS SELECTION For the development of our android application, we have used following applications/technologies: Eclipse: In computer programming, Eclipse is an Integrated development
environment (IDE) comprising a base workspace and an extensible plug-in system for customizing the environment. It is written mostly in Java. Released under the terms of the Eclipse Public License, Eclipse SDK is free and open source software (although it is incompatible with the GNU General Public License). It was one of the first IDEs to run under GNU Classpath and it runs without problems under IcedTea.

Java 1.7: Java is a set of several computer software products and specifications
from Sun Microsystems (which has since merged with Oracle Corporation), that together provide a system for developing application software and deploying it in a crossplatform computing environment. Java is used in a wide variety of computing platforms from embedded devices and mobile phones on the low end, to enterprise servers and supercomputers on the high end.

Php 5: PHP is a server-side scripting language designed for web development but also
used as a general-purpose programming language. PHP is now installed on more than 244 million websites and 2.1 million web servers. Originally created by Rasmus Lerdorf in 1995, the reference implementationof PHP is now produced by The PHP Group.[3] While PHP originally stood for Personal Home Page, it now stands for PHP: Hypertext Preprocessor, a recursive acronym.

MySql: MySQL is a popular choice of database for use in web applications, and is a
central component of the widely used LAMP open source web application software stack (and other 'AMP' stacks). LAMP is an acronym for "Linux, Apache,

21

MySQL, Perl/PHP/Python." Free-software-open source projects that require a fullfeatured database management system often use MySQL.

Xml 1.0: Extensible Markup Language (XML) is a markup language that defines a set
of rules for encoding documents in a format that is both human-readable and machinereadable. It is defined in the XML 1.0 Specification produced by the W3C, and several other related specifications, all free open standards. The design goals of XML emphasize simplicity, generality, and usability over the Internet. CODE

CHAPTER 5 - RESULTS

From a proper analysis of positive points and constraints on the component, the result is that the project is an efficient GUI based component. This application is properly running and meeting to all the user requirements. This project can be easily plugged in many other systems. This application is an android application which will run on android 2.2 and other higher versions of android. The application is a simple and user friendly GUI. BILLBRAIN makes the tiring task of filling in your billing information a thing of the past. All of us generally face a problem of remembering the unique consumer IDs and

22

then comes the monotonous task of filling in your basic information every time you need to pay the bills online. This application helps to root out this problem. And it is expected that this project will go a long way in satisfying users requirements.

23

CHAPTER 6 - COMPARISONS AND ANALYSIS

Comparison
BILLBRAIN makes the tiring task of filling in your billing information a thing of the past. All of us generally face a problem of remembering the unique consumer IDs and then comes the monotonous task of filling in your basic information every time you need to pay the bills online. This application helps to root out this problem by auto-filling all the required data of user online billing transactions.

Analysis
Strength -This is the first kind of application in the market and this gives us the first movers advantage. It solves the problem of remembering the unique consumer IDs and the monotonous task of filling in users basic information every time they need to pay the bills online.

Weakness Due to our limited resources and time, we have only developed this application for the bill payment of MTNL and BSES Opportunity - In future we have planned to develop a similar facility for payments of other utilities such as domestic fuel gas, electricity supply and other telecom companies as well which can be paid through a single application and a single username.

24

Threat - The interactive billing sector has been seeing a rapid growth and its only a matter of time until big developers see an opportunity in this domain. I have the first mover advantage but I need to expand fast so as to cover as much target group as possible

7. CONCLUSION & FUTURE SCOPE

This project increased my knowledge of mobile application development and understanding of various challenges in this field. Also, it gave me good exposure to learn development in various software development life cycle phases. The overall experience of developing GUI for a small screen with clean and elegant interface in contrast with my previous desktop application development was very nice. This application development improved my mobile development skills and analytical abilities. This project made me go through various ups and downs in the making of a project. I got an idea about the problems encountered in the analysis, coding, debugging and testing. I have tried to restrict these problems to a certain limit and have tried to make the project more users - friendly and easily accessible. Bill Brain is an application that helps to auto-fill all the required data of users online billing transactions. All user need to do is to do a onetime sign up and fill in all the details in our interface. The application will then store all this information in its database and the next time you need to pay a bill just sign in and click on the company name for which the bill is due and DONE! All your details are filled. The payment option will then simply redirect you to the online payment page and you can carry on as usual. Currently, due to our limited resources and time, we have only developed this application for the bill payment of MTNL and BSES, but we have planned to develop a similar facility for payments of other utilities such as domestic fuel gas, electricity supply and
25

other telecom companies as well which can be paid through a single application and a single username. We also aim to provide our users with better and secure access by providing data encryption. All the data entered and stored would be encrypted and hence provide heightened security.

8. REFERENCES

[1] http://developer.android.com/guide/index.html [2] http://www.vogella.de/articles/Android/article.html

26

[3] J. Simon; Head First Android Development; 1st ed., O. Reilly [4] http://www.engineersgarage.com/articles/what-is-android-introduction [5]http://stackoverflow.com/questions/4531396/get-value-of-a-edit-textfield/4531500#4531500 [6] http://www.androidhive.info/2012/05/how-to-connect-android-with-php-mysql [7]http://www.codeoncloud.blogspot.com/2013/07/android-mysql-php-jsontutorial.html?m=1

P. Hudson, "PM, Costello liars: former bank chief," (The Age), [online] 1998, http://www.theage.com.au/ daily/980916/news/news2.html (Accessed: 9 February 2000).

First name or initials, Surname. (eds) [if appropriate] "Title of page", (Title of site), [online] date, url (Accessed: Access date).

27