Advanced 3D Maps for Personal Digital Assistant

In this project it is proposed an efficient method to create three dimensional [3D] Maps for personal digital assistant. In this project its developed a 3D Map. Using this map the user will get a quick understanding about the campus structure and buildings. Similar manner 3D maps can be drawn to larger area that covers a city or state.

The objective of this project is to render a 3D map with some enhanced properties like Book marking, Illustrative and non photorealistic visualization alternatives, etc. In rendering static scenes we define a potentially visible set – a list of atomic objects or regions as seen from a viewpoint or a view cell. In dynamic entity management the real world’s dynamic entities are moving objects, such as GPS-tracked users, public transportation, bicycles or other vehicles.

In modern cities buildings effectively limit any movement to urban canyons – namely, streets and sidewalks. In location based information we consider the fixed entities like buildings, ground etc… to create location based information. Visibilities have been predetermined. If the target is visible, so is the information associated with it. We use audio to assist the user to follow the map.

3D Maps

Computer generated perspective views, such a Lake shown in Figure 2.1, are often simply referred to as “3D maps”. Although this term is not found in the cartographic literature, there are specific reasons why it should be used. “3D”, because we perceive the presented landscape with our human perception system in a three-dimensional perspective way, even when the landscape is depicted on two dimensional media. And, “maps”, because these products integrate and display spatially -arranged phenomena on the surface of a DTM [Digital Terrain Model] in accordance with cartographic symbolization and generalization conventions. Nevertheless, although they possess cartographic characteristics, 3D maps should be considered a map-related representation, not a map in the classic sense.

Design Process

Before analysing the many graphic cues and resources that influence the look of 3D maps, we should first examine the design process. By doing so, we will have a better understanding of how to apply these cues and resources in the design of 3D maps. We will also understand how they affect overall representation, and how they interact effectively with other graphic cues and resources.

The first step of the design process is data modeling. The original data are analyzed, and, depending on the circumstances, converted to another format and file structure, upon which subsequent 3D map design processes depend. The geometric and semantic aspects of the objects in the data are reshaped, aggregated, and/or classified in the format required with the specific software used for designing and producing 3D maps.

Symbolization is the next step. This step involves determining the graphic appearance of the DTM section as well as topographic and thematic objects. In other words, we define the legend for the 3D map. It must be noted that a physical image has not yet been created at this stage of the design process. The last step is visualization. Parameters are chosen for creating the image and completing the scenery that will become the final 3D map.

General Considerations about Graphic Aspects

For generating 3D maps, there are a great number of input cues that influence the map creation process (Kraak 1988). Taken together these cues are known as "graphic aspects" (or "design aspects"). The different kinds of maps and map creation steps require many graphic aspects to be distinguished by cartographers.

Graphic aspects are groups of parameters that exert different effects on the arrangement or appearance of the objects within the map. With them, it is possible to design and control all map features, including how features should appear in the perspective view. Every graphic aspect includes one or more graphic variables. A starting point for understanding graphic variables is Bertin's "visual variables" for graphics and maps (Bertin 1998).

For this discussion, however, it is necessary to enlarge Bertin's list to include sub variables within variables. A graphic variable is a design factor, which directly affects a focused map object in a one-dimensional way. Similar to the design process of 3D maps, all graphic aspects need to be divided into similar groups. But before doing this we will first examine the different object types, followed by an examination of their graphic aspects.

Highlights of the Project

This project provides 3D Map for a campus. This is installed in the server and can be instantly downloaded to the client using FTP. Also the user can walk through the 3D Map and can get clear idea about the place. Thus its believed that this project will provide a 3D Map with high degree of user friendliness, realistic representation, multiple views of an area, more degrees of freedom in movement.

System Specification

The hardware and software requirements for the development phase of our project are:

Software Requirements :

• Visual C++

• Google sketch up pro

• Windows NT family

• 64-bit operating systems

Hardware Requirements :

• 1 GB RAM

• 40 GB Hard Disk

• 2.8 GHz

• 56X CD ROM Drive

• 1.44MB Floppy Disk

• VGA monitor

Crypto Acceleration Using Asynchronous FPGAs

The goal of this project, sponsored by General Dynamics C4 Systems, is to evaluate proprietary FPGA technology developed by Achronix Semiconductor Corporation and its effectiveness using a 128-bit, one clock cycle multiplier in a finite field, GF(2 128 ), as a test application. The testing will determine if there is a significant increase in speed that can be achieved by simple modifications of existing synchronous HDL designs using three metrics: number of LUTs, number of registers, and clock speed

Throughout the course of this project, multiple software tools were used in order to facilitate simulation, version comparison and simplification processes to increase productivity. The most important of these tools are explained in further detail in this section.

Mentor Graphics QuestaSim

Questa is Mentor Graphics' Advanced Functional Verification (AFV) tool and is an integrated platform that includes QuestaSim. QuestaSim is capable of high efficiency advanced verification of large electronic systems, and includes built-in management and debugging utilities. QuestaSim, based upon Mentor Graphics' ModelSim, seen in Figure 1 , is a standards-based digital simulator capable of receiving VHDL or a variety of other languages' code as input and simulating results based on test bench waveforms.

QuestaSim displaying simulation results for a period of 400ns

QuestaSim boasts a variety of features in addition to its primary functionality, such as low-power design verification and fast time-to-debug using assertions and a multi-abstraction debug environment [11].

Synplicity Synplify and Synplify Pro

Synplify is synthesis engine that is used to create FPGA designs. It takes in VHDL or Verilog code and outputs a netlist which can be optimized for a variety of FPGA vendors and packages. Synplify uses Behavior Extracting Synthesis Technology® (B.E.S.T. T) to produce designs which are fast and highly efficient. Additionally, it is designed with a simple interface so that it is easy to use

Synplify Pro is similar in operation and use to that of Synplify, but offers better algorithms for compilation and mapping. In addition, it also improves the user interface (the Synplify Pro interface can be seen in Figure 3) and adds a great deal more options that may be used in design. This project uses both Synplify and Synplify Pro, the latter being used in situations concerning benchmarking due to the need of the auto constraining feature found within Synplify Pro.

Achronix CAD Environment (ACE)

The Achronix CAD Environment runs as a complementary tool to Synplicity's Synplify Pro software, seen in Figure 3 , and allows for enhanced optimization techniques using Achronix's proprietary technology to decrease routing delays. This results in an overall throughput increase of the system and allows for FPGAs to run some applications at speeds greater than 1GHz.

ACE, which can be seen in Figure 4 , has been designed to be intentionally easy to use and while it functions on the premises of an asynchronous logic design, all input to the program is standard architecture, synchronous logic designs. This allows for current configurations to only require slight HDL modifications in order to benefit from the performance improvements ACE offers.

Altera's Quartus II software is a product of the Altera Corporation that provides a unified development design flow for FPGAs, structured ASICs, and CPLDs. Quartus II is capable of easily addressing problems relevant to designs such as post place-and-route design modifications.

Compared to the Xilinx ISE, Quartus II provides higher benchmarks in performance with relevance to FPGA and CPLD designs. Quartus II also provides tools such as TimeQuest and PowerPlay that assist in timing analysis and power analysis, respectively, as well as a pin planner feature to be used in I/O pin assignment

 

XML-enabled Wrapper Construction

The amount of useful semi-structured data on the web continues to grow at a stunning pace. Often interesting web data are not in database systems but in HTML pages, XML pages, or text les. Data in these formats is not directly usable by standard SQL-like query processing engines that support sophisticated querying and reporting beyond keyword-based retrieval.

Hence, the web users or applications need a smart way of extracting data from these web sources. One of the popular approaches is to write wrappers around the sources, either manually or with software assistance, to bring the web data within the reach of more sophisticated query tools and general mediator-based information integration systems.

In this paper, we describe the methodology and the software development of an XML-enabled wrapper construction system - XWRAP for semi-automatic generation of wrapper programs. By XML-enabled we mean that the metadata about information content that are implicit in the original web pages will be extracted and encoded explicitly as XML tags in the wrapped documents. In addition, the query-based content ltering process is performed against the XML documents.

The XWRAP wrapper generation framework has three distinct features. First, it explicitly separates tasks of building wrappers that are speci c to a Web source from the tasks that are repetitive for any source, and uses a component library to provide basic building blocks for wrapper programs.

Second, it provides inductive learning algorithms that derive or discover wrapper patterns by reasoning about sample pages or sample speci cations. Third and most importantly, we introduce and develop a two- phase code generation framework.

The first phase utilizes an interactive interface facility to encode the source-speci c metadata knowledge identi ed by individual wrapper developers as declarative information extraction rules.

The second phase combines the information extraction rules generated at the rst phase with the XWRAP component library to contruct an executable wrapper program for the given web source. The two-phase code generation approach exhibits a number of advantages over existing approaches.

First, it provides a user-friendly interface program to allow users to generate their information extraction rules with a few mouse clicks. Second, it provides a clean separation of the information extraction semantics from the generation of procedural wrapper programs (e.g., Java code).

Such separation allows new extraction rules to be incorporated into a wrapper program incrementally. Third, it facilitates the use of the micro-feedback approach to revisit and tune the wrapper programs at run time. We report the performance of XWRAP and our experiments by demonstrating the bene t of building wrappers for a number of Web sources in di erent domains using the XWRAP generation system.

Architecture

The architecture of XWRAP for data wrapping consists of four components - Syntactical Structure Normalization, Information Extraction, Code Generation, Program Testing and Packaging. Figure 1 illustrates how the wrapper generation process would work in the context of data wrapping scenario.

Syntactical Structure Normalization is the rst component and also called Syntactical Normalizer, which prepares and sets up the environment for information extraction process by performing the following three tasks. First, the syntactical normalizer accepts an URL selected and entered by the XWRAP user, issues an HTTP request to the remote server identi ed by the given URL, and fetches the corresponding web document (or so called page object). This page object is used as a sample for XWRAP to interact with the user to learn and derive the important information extraction rules. Second, it cleans up bad HTML tags and syntactical erros.

Third, it transforms the retrieved page object into a parse tree or so-called syntactic token tree. Information Extraction is the second component, which is responsible for deriving extraction rules that use declarative speci cation to describe how to extract information content of interest from its HTML formatting.

XWRAP performs the information extraction task in three steps -

1. identifying interesting regions in the retrieved document,

2. identifying the important semantic tokens and their logical paths and node positions in the parse tree, and

3. identifying the useful hierarchical structures of the retrieved document. Each step results in a set of extraction rules speci ed in declarative languages.

Code Generation is the third component, which generates the wrapper program code through applying the three sets of information extraction ruls produced in the second step.

 

Battery Optimizer for Android Mobile Devices

In the growing world of technology, cellular devices have quickly emerged as one of the fastest evolving fields. They have increased greatly in both popularity and complexity, requiring more advanced operating systems and applications to meet the demands of the consumer. Android is a software stack designed to meet these demands in an open source environment. The project is currently being developed and funded by the Open Handset Alliance, which includes companies such as Google and T-Mobile.

Android includes an operating system, middleware, and key applications, as well as a Software Development Kit (SDK) for developers to create their own applications for the Android environment. Due to its open source license and tools provided, Android is an ideal platform for bringing the mobile market to the educational realm. This paper describes in detail what Android is, its architecture, and why developers should choose

Android to develop in a mobile de-vice platform environment. The paper also discusses the basic hardware requirements for porting the current version of Android to real hardware.

Android supports its own Power Management (on top of the standard Linux Power Management) designed with the premise that the CPU shouldn't consume power if no applications or services require power. Android requires that applications and services request CPU resources with "wake locks" through the Android application framework and native Linux libraries. If there are no active wake locks, Android will shut down the CPU.

In our proposed system those handy applications like Bluetooth, WI-Fi will get turn-off automatically when the battery percentage reach to a certain point. So users don’t have to bother about to turn-off these applications when they are not in use. The Android Framework exposes power management to services and applications through the Power Manager class.

Applications

Android will ship with a set of core applications including an email client, SMS program, calendar, maps, browser, contacts, and others. All applications are written using the Java programming language.

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.

Underlying all applications is a set of services and systems, including:

• A rich and extensible set of Views that can be used to build an application, including lists, grids, text boxes, buttons, and even an embeddable web browser

• Content Providers that enable applications to access data from other applications (such as Contacts), or to share their own data

• A Resource Manager, providing access to non-code resources such as localized strings, graphics, and layout files

• 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

Objectives

The objective is to save the battery power to make our mobile alive for a long period. Let us look at the power consumption by the applications like Bluetooth, WI-FI and Brightness.

Flight mode 20% - the basic power consumption when almost all functionality is turned off.

Brightness – it takes 20% when it used at maximum and on average 10-12% .

Wi-Fi - 8% when turned on but not actively used and 13% when turned being actively used.

Bluetooth - 4% when it is not actively used.10% when it is actively used. If the total is 100% it represents that the battery is drained at the maximum possible speed. Hence we can save the power from 30% up to 50% approx.

Highlights of the Project

The technology used here in Android 2.1 platform. We already had Android’s earlier versions. But Android 2.1 is a minor platform release deployable to Android-powered handsets starting in January 2010. This release includes new API changes and bug fixes. For information on changes. For developers, the Android 2.1 platform is available as a downloadable component for the Android SDK. The downloadable platform includes a fully compliant Android library and system image, as well as a set of emulator skins, sample applications, and more. The downloadable platform includes no external libraries.

System Specification

The hardware and software requirements for the development phase of our project are:

Software Requirements :

• Windows XP (32-bit) or Vista (32- or 64-bit)

• Mac OS X 10.4.8 or later (x86 only)

• Linux (tested on Linux Ubuntu Hardy Heron)

• 64-bit distributions must be capable of running 32-bit applications.

Hardware Requirements :

• Although the source code for Android has not been officially released, it is still possible to port Android to real hardware.

• By using a compiled Linux kernel and applying the necessary Android patches, one can port Android to a real device and run a version of Android on the device. .

• Android is currently very hardware specific and when choosing a device to port to, one must abide by the minimum hardware requirements. Since Google has not released the source code to Android, only code available in the SDK can be used.

• The SDK itself uses an open source processor emulator, known as QEMU.

DEMOS Online Quiz

DEMOS ONLINE QUIZ is Windows based web application for facilitating quizzes on any subject based on the data provided to the application. This will be a data driven application whose behavior is mostly controlled by the data provided to this application which makes the application very flexible and powerful.

The features are:

• The application will list, the available subjects of quizzes to the end user where the user can select and execute the Quiz.

• The selected Quiz will have its own characteristics such as total number of questions, marks for each correct answer.

• A new quiz can be added to the system by proving the Quiz data.

Types Of Users

• Administrator: Person who is granted access to database.

The functions of administrator are:

• Add or edit Subjects

• Add or edit Questions

• Check the status of the on-going quiz

• Adds new participants and keep their details

• Controls registration of participants

• Add new News about the site

• Keeps the Login History

• Participants : These are the users who participate in the quiz competition .Each user has a unique user name and password with which they can log on to the system. User selects the category of quiz to participate in.

Modules

DEMOS is mainly divided into four modules, namely

• User Management Module

• Question management module

• Quiz Execution Module

• Mark calculation module

User Management Module

The functions of this module are:

• Add new users to the user table.

• Authenticating users in the system.

We use user table for user authentication purpose and for storing user data.

Question Management Module

The functions of this module are:

• To add new subjects

• To delete the subject

• Add questions to each category of subject.

• Update questions

Here we use a single table for each subject .

Each subject has 10 questions and each question has 4 choices.

Quiz Execution Module

The functions of this module are:

• Quiz Selection

• Listing a single question and its choices at a time

• Verifying selected answer

• Displaying the mark

• Navigating to the next question

Mark calculation module

The functions of this module are:

• Calculation of marks for each of the participants.

• Toppers of each Subject are found

The marks are stored in Marks detail table.

The Toppers are stored in Subject Table

Android Application for Call Taxi

A

This project addresses the study of the recently launched Google Android platform, and its online application marketplace, called the “Android Market.” The project examines the paths to success for third-party developers building applications for Android by comparing them with application development for the Apple iPhone. In addition, the project also includes a study of the Android business ecosystem. Research on related topics shows that mobile ecosystem benefits third-party developers and those application vendors play a critical role in contributing to the success of Android.

The main goal of this project is to develop an accessible and comprehensive Eclipse structure application, can potentially assist individuals to book a taxi from a phone and for the company to maintain a database for booking and sending driver details.

Existing system as Call Taxi Wiki, which is a system exists in the market for one year, the existing system helps user to find the nearest taxi around in a particular city. The system all allows full internet access. However, the number of cities in the whole world is huge; database can’t store all the cities names.

Methodologies are the process of analyzing the principles or procedure of a progressive Call taxi system.

Main Module’s

Sign up

Driver And Customer login

New booking and cancel booking.

Confirm booking xi

Transaction Status

Sign up:

This is the first step what user to do. In this module, user wants to create an account in database, to call taxi from system. The registration processes are done by any person non-violating the database privacy rules. The registration will be permitted by call taxi system administrator. After the registration process completed user can get the authentication code and machine generated user id, by using this only user can login to the call system.

Driver and Customer Login:

In this module user want to register the personal details in the call taxi company database and get the authentication processes to go forward.

User booking and cancel booking:

In this module authorized drivers can book a taxi from the call taxi system. Here also shows all the details about the driver who also registered in the system. And the system admin give the personal details to the particular driver only after the matching process is done. Now the matching process is done by the admin. After getting the user details, driver can wait the user confirms the booking.

Confirm booking:

In this process, user will get the information about the distance, time and required fees from the system, then booking can be confirmed or cancelled in the above module.

Transaction status:

This is a module in which only admin can access, all registrations got permitted by this module. Booking request by users and drivers’ information also can be viewed in this module, such as the admin will arrange available driver to serve the particular request.

Application

Call Taxi System is used to maintain the user database in the format. It also very easy to retrieve the accurate data from a database, here all the information about the user are maintained securely and also here we achieve the confidentiality for the data’s stored in the database.

Concerning the actual execution of the database update, once the system has verified that the Booking be safely inserted to the database the data can be easily accessed and be used for further purposes and also the transactions can be done both the ways. Its applied by retrieving information from the database and storing through the android application.

Future Enhancements

Devising private update techniques to database systems that support notions of anonymity different than k-anonymity.

Dealing with the case of malicious parties by the introduction of an un-trusted, no colluding third party.

Implementing a real-world database system.

Improving the efficiency of an application, in terms of number of transactions exchanged and in terms of their sizes, as well.

Highlights of the Project

A system which can be used for user to login to connect a database is proposed. The user can just login to the system over internet, and book the taxi from location to location. With the help of the proposed system, user can book taxi without making phone call, which takes time to wait to call in. In the proposed system, checking the data that are entered in the databases does not violate privacy, and performs such verification without seeing any sensitive data of an individual.

Under this approach, the entire tuple has to be revealed to the party managing the database server, thus violating the privacy of the user. Another possibility would be to make available the entire database to the user so that the user can verify himself if the insertion of his/her data violates his/her own privacy. This approach however, requires making available the entire database to the user thus violating data confidentiality. Once this anonymized record is stored in the research database, the non anonymized version of the record is removed from the system of the facility. Thus, the research database used by the researchers is anonymous.

System Specification

The hardware and software requirements for the development phase of our project are:

Software Requirements :

• FRONT END : Eclipse with Android plug

• BACK END : MYSQL

Hardware Requirements :

PROCESSOR : PENTIUM IV 2.0 GHz, Intel Core 2 Duo.

RAM : 512 MB DD RAM

Phone : Android Phone

CDDRIVE : LG 52X

KEYBOARD : STANDARD 102 KEYS

MOUSE : 3 BUTTONS

Access My PC

Access My PC, as we call it, is a software that allows users to access devices connected to their systems from remote locations. The process starts when the different users, who need the facility, get registered through our website and download the application program for the said facility. Once the software is installed on the home pc then the user can access the devices connected to the system from any location using our website through the Internet.

A simple registration form is provided to the user wherein he can enter his name, address, contact number, email id, login id and password. After filling up the proper information, the user gets successfully registered for the application software. The user is authenticated for his login name and password, which was provided to him during the registration process. If the user fails to give his proper login id or password, an error message is displayed to him indicating that the login id does not exist.

The user has the option for downloading the software to the particular system that he is using. Once the system is installed in that system, say the Home PC, then the devices connected to that system can be accessed easily using our website.

Accessing the various devices connected to the Home PC is the feature that is being implemented in the project. Every user will have a particular Access code to be entered for getting access to this feature. If the Access code entered is wrong then the user get automatically logged out. Once the correct Access Code is entered the user can access the device he wants. The user can sign out of the login area any time using this function.

User Registration

A simple registration form is provided to the user wherein he can enter his name, address, contact number, email id, login id and password. After filling up the proper information, the user gets successfully registered for the application software.

Login and Authentication

The user is authenticated for his login name and password, which was provided to him during the registration process. If the user fails to give his proper login id or password, an error message is displayed to him indicating that the login id does not exist. If the login is successful then the user is able to perform the following functions:

• Software Download: The user has this option for downloading the software to the particular system that he is using. Once the system is installed in that system, say the Home PC, then the devices connected to that system can be accessed easily using our website.

• Access Devices: This is perhaps the purpose of Access My PC. Accessing the various devices connected to the Home PC is the feature that is being implemented here. Every user will have a particular Access code to be entered for getting access to this feature. If the Access code entered is wrong then the user get automatically logged out. Once the correct Access Code is entered the user can access the device he wants.

• Logout: The user can sign out of the login area any time using this function.

System Architecture

The System architecture has to be designed keeping all the above functions in mind. We can see that the system consists of mainly the following three parts:

Home PC

Home PC is the personal computer, which is owned by the user. The software that is Application part resides on this computer. It gets the data from the device and transmits it to the remote PC location and it also gives the status of the remote PC location. It has no level of user authentication. But it is the application part of this system that checks for the user device accessing. Home PC consists of mainly five modules namely:

• Network Interface: This is the part of the application, which is connected to the network.

• Data Manipulation Unit: This prepares the data from the devices to suitable for the network transmission.

• Device Access Module: This gets the data from the user from the interface corresponding to each of the users.

• Control Unit: Controls and coordinates each of the units in the Home PC.

• Device Interface: Interface of the operating system of the PC with the device so as to facilitate the communication between the two.

The Home PC consists of Data Manipulation and Device Access units. These two units are controlled by a Control unit. The Home PC is connected to a Network Interface. It is also connected with the devices via Device Interface.

System Requirement

After analyzing the requirements for our project we had come to the conclusion that our project users require the following requirements.

Client’s Requirements:

Needs a network connection

The account bound with a separate username and password for every user.

Needs the Internet facility

Server’s Requirements:

Should be connected to the Internet

Needs a Java Runtime Environment

Needs a database

System Specification

The hardware and software requirements for the development phase of our project are:

Software Requirements :

Development Tools : Java, JSP, HTML

Back end : SQL Server 2000

Browser : Mozilla 2.0 or IE

Web Server : Apache Tomcat Server

Hardware Requirements :

Processor : Pentium IV

RAM Capacity : 256 MB

Hard Disk Space : 40 GB

Mouse : MS Compatible

Keyboard : Standard 104 Keys

Monitor : Standard 15”

Floppy Disk Drive : 1.44 MB