CHAPTER-1 INTRODUCTION
1. INTRODUCTION
Friend Finder is an Andriod based project to locate Friends in the contact lit based on locations and proximities. FriendFinder is project is basically divided into two sections, Contacts (Friends) management (With CRUD operation):
Contacts Management will allow the user to add “Friends” as contacts into a mobile database. This will have all the CRUD (Create Read Update Delete) operation on the contacts. A contact consists of a name and a geographic coordinate location. Friend Location map feeder: The second part, Friend location map feeder will allow the user to graphically position its contacts into on a Google map. The application needs save these contacts the mobile and their locations. Friend Finder should display a map when the user selects a contact. What make this different from the other Google map is that this map will include a Google maps overlay, which enables you too write names, give information, and draw items on top of a Google maps tile. This process includes creating and using the users own custom content provider to work with the user’s database. Then, you will take the data that is stored in the user’s database and write it out to a Google maps overlay. Overlays to draw shapes and write text on your resulting in very informative maps. What is ? Friend Finder is an Android based project to locate Friends in the contact list based on locations and proximities. The scope of this project is to develop Friend Finder application that runs on Android platform. This is the first version of it kind and is developed based on Android platform. The goal of this project is to find Friends in the Google map feeder based on locations and proximities. Purpose of the Project: The purpose of the project is to list down requirements for the Friend Finder application. The goal of this project is to find Friends in the Google map feeder based on locations and proximities to find the Friend in different places in that place we must specify the two values like latitude and longitude. These values are useful to the finding a Friend. 1.2 Existing system: The current system only has a phone book which will show only specific entries.
1.3 Proposed system:
This application will not only store what a general phone book stores but also metadata like photos, text and other related things. This is having a feature of storing Friend’s location on Google maps. 1.4 Feasibility study:
All projects are feasible if they have unlimited resources and infinite time. But the development of software is plagued by the scarcity of resources and difficult delivery dates. It is necessary and prudent to evaluate the feasibility of a project at the earliest possible time. The three considerations are involved in the feasibility analysis. 1.4.1 Economic Feasibility: The procedure is to determine the benefits and savings that are expected from a candidate system and compare with cost. If benefits outweigh cost then the decision is made to design and implement the system. Otherwise further justification or alterations in proposed systems that are to be made if it is having a change of being approved. This is an ongoing effort that improves in accuracy of each phase of the system life cycle. For my project I am not expecting any. 1.4.2 Technical Feasibility: Technical Feasibility centres al the existing mobile system (hardware, software etc.,) and to what extent it can support the proposed addition if the budget is the serious constraint, then the project is judged not feasible. The technical feasibilities are important role in my project because here I am using Android operating system. 1.4.3 Operational Feasibility: People are inherently resistant to change and mobile have been known to facilitate change. In my project a technical people require to configure the software and technical background is necessary to work on the sensors. 1.5 Intended Developers: Mobile operators
China mobile KDDI corporation NTT DOCOMO Sprint Nextel T-mobile Telecom Italia Telefonica
Software companies Ascender corporation Ebay Esmertec Google Livingimage NMS communications Nuance communications Packetvideo Skypop SONIVOX
Commercialization companies
Apix Noser engineering The astonishing tribe Wind river systems
Semiconductor companies Audience Broadcom corporation Intel corporation Marvell technology group Nvidia corporation Quaicomm SIRF technology holdings Synaptics Texas instruments
Handset manufacturers
HTC LG Motorola Samsung electronics
CHAPTER -2 SCOPE OF THE PROJECT
2. SCOPE OF THE PROJECT
The (Friend Finder) feature is a vital layer of the Android framework for combining many of the lower level Android components tasks for Friend Finder. The application needs save these contacts in the mobile and their locations have been obtained from the server. Each contacts location is used to calculate the distance between the user and the Friend and displayed in list. The scope of this project is to develop Friend Finder application that runs on Android platform. This is the first version of its kind and is developed based on Android platform. The goal of this project is to find Friends in the Google map feeder based on locations and proximities.
CHAPTER -3 PRODUCT PERSPECTIVE
3. PRODUCT PERSPECTIVE
Sensors are already available in other mobiles. This research is on the latest open source mobile development platform called, • Android and to implement sensor based technologies for different requirements. Sensors are available in most of the mobile devices we use but the software • availability to interact with this hardware and to get more from these sensors is very less. Product features: •
•
•
• •
•
Android is “openness.” The promise is that developer can produce applications without interference. “The fact that (Android) is an advanced, open operating system is important to the development community, but customers don’t buy operating systems.” The interface is flexible. The Android Platform provides a rich security model that allows developers to request the capabilities, or access, needed by their application and to define new capabilities that other applications can request. Developers have full access to the same framework APIs used by the core applications.
CHAPTER -4 ASSUMPTIONS AND DEPENDENCIES
4. ASSUMPTIONS AND DEPENDENCIES • •
•
• •
To use this application Friend Finder add-on must be available. Having only hardware is not sufficient, to access an application software is must. Assumption is made in such a way that the mobile is charged with enough battery The battery should be in a working mode The one who using the mobile must have a minimum knowledge of how to use the Friend Finder.
CHAPTER -5
SOFTWARE REQUIREMENTS SPECIFICATION
5. SOFTWARE REQUIREMENTS SPECIFICATION
5.1 System Environment: 5.2 Functional Requirements Specification: The system is required to perform the following functions: 1). Display all the information about the application that is being developed and some set of instructions the user might want to remember before he sets up the system for configuring Friend Finder. 2).The system should display all the screens to get the information about the user contacts information and the Google map feeder configuration. User information includes name, contact number and address where as the Google map feeder configuration include services usage and all other screens that are going to establish the connectivity between the Android application and the Google map feeder. 3).Given all the details the system should establish a connection between the Android application and the configured online Google map feeder. 4).After establishing the connection between the Android phone and the server the system should download all the contacts from contacts list and the contacts should be of any number. 5.3 Non-Functional Requirements:
Applications framework enabling reuse and replacement of components. Dalvik virtual machine optimized for mobile devices. • Integrated browser based on the open source Web Kit engine. • Optimized graphics powered by a custom 2D graphics library; 3D graphics • based on the open GL ES 1.0 specification(hardware acceleration optional). SQLite for structured data storage. • GSM Telephony (hardware Dependent)Bluetooth, EDGE, 3G, and Wify • (hardware dependent), Camera, GPS, compass and accelerometer(hardware dependent). Rich development environment including a device emulator, tools for • debugging, memory and performance profiling, and a plug-in for the eclipse IDE. The system is expected to run on low memory devices also. The system should not consume lot of bandwidth so that the other applications • will block for the internet. The system should provide secured access to the web server. • Requirements Specifications: 5.4 Software Requirements: J2SE, Android, SOA, Web services, Linux, Windows XP, Dalvik Emulator, Eclipse3.4, Mobile IDE Plug-in. 5.5 Hardware Requirements: Pentium IV with 2GHZ, 1GB RAM, 40 GB Hard Drive, Android Phone (optional). •
CHAPTER-6 PROJECT ANALYSIS
6. PROJECT ANALYSIS
6.1 Overview: Friend Finder is an Android based project to locate Friends in the contact list based on location and proximities. Friend Finder is project is basically divided into two sections. Contacts (Friends) management (With CRUD operation):
Contacts Management will allow the use to add “Friends” as contacts into a mobile database. This will have all the CRUD (Create Read Update Delete) operation on the contacts. A contact consists of a name and a geographic coordinate location. Friend Location map Feeder: The second part, Friend location map feeder will allow the use to graphically position its contacts into on a Google map. The application needs save these contacts the mobile and there locations have been periodically updated using GPRS connection. Each contacts location is broadcasted using GPRS with location information obtained from GPS. Friend Finder should display a map when the user selects a contact. What make this different from the other Google map is that this map will include a Google Maps Overlay, which enables you to write names, give information, and draw items on top of a Google Maps tile. This process includes creating and using the users own custom Content Provider to work with the user’s database. Then, you will take the data that is stored in the user’s database and write it out to a Google Maps overlay. Overlay to draw shapes and write text on your resulting in very informative maps.
