You are on page 1of 16

1

CONTENTS
Sr. No 1 2 3 4 5 6 7 Particular Problem Definition Introduction System Requirement Tools & Technology Feasibility Study Information Gathering System Analysis Page No 2 3 4 5 14 15 16

2

Problem Definition
In this modern competitive world marketing a product of a company is very difficult task. They have to tackle the competitors, dealers and customers. In every stage of marketing the market, the company should have to plan perfectly. Otherwise they cannot able to market their products successfully. N o w a d a ys , I n t e r n e t b e c o m e s o n e o f t h e m o s t p o p u l a r m e d i a t o r e a c h t h e c u s t o m e r directly and market our products to the customers directly. In this regard, for my project I am trying to market the products of E-Shopping through the Internet

3

INTRODUCTION
The central concept of the application is to allow the customer to shop virtually using the Internet and allow customers to buy the items and articles of their desire from the store. The information pertaining to the products are stores on an RDBMS at the server side (store). The Server process the customers and the items are shipped to the address submitted by them. The application was designed into two modules first Os for the customers who wish to buy the articles. Second is for the storekeepers who maintains and updates the information pertaining to the articles and those of the customers. The end user of this product is a departmental store where the application is hosted on the web and the administrator maintains the database. The application which is deployed at the customer database, the details of the items are brought forward from the database for the customer view based on the selection through the menu and the database of all the products are updated at the end of each transaction .Data entry into the application can be done through various screens designed for various levels of users. Once the authorized personnel feed the relevant data into the system, several reports could be generated as per the security.

4

SYSTEM REQUIREMENT
Hardware requirements: Processor used-Intel core 2 duo.  Ram-512MB or higher.  The hard disk memory requirement for installation of Net Beans 6.9 is 228MB.  100 MB HD memory required for Eclipse IDE. Software requirements: Operating system used  Any operating system that supports Eclipse IDE for development and testing of software.  Back End  My-SQL server 5.0  Front End  Android V2.2  Java jdk1.6

5

TOOLS AND TECHNOLOGY USED
Front End:Android Android is a software stack for mobile devices that includes an operating system, middleware and key applications. Android is a software platform and operating system for mobile devices based on the Linux operating system and developed by Google and the Open Handset Alliance. It allows developers to write managed code in a Java-like language that utilizes Googledeveloped Java libraries, but does not support programs developed in native code. The unveiling of the Android platform on 5 November 2007 was announced with the founding of the Open Handset Alliance, a consortium of 34 hardware, software and telecom companies devoted to advancing open standards for mobile devices. When released in 2008, most of the Android platform will be made available under the Apache free-software and open-source license

Features of Android OS

· · · · · · · · · ·

Application 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 OpenGL ES 1.0 specification (hardware acceleration optional) SQLite for structured data storage Media support for common audio, video, and still image formats (MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, GIF) GSM Telephony (hardware dependent) Bluetooth, EDGE, 3G, and WiFi (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 plugin for the Eclipse IDE

6

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 lat files · bar A Notification Manager that enables all applications to display custom alerts in the status

· An Activity Manager that manages the life cycle of applications and provides a common navigation backstack

7

Libraries :
Android includes a set of C/C++ libraries used by various components of the Android system. These capabilities are exposed to developers through the Android application framework. Some of the core libraries are listed below: · System C library - a BSD-derived implementation of the standard C system library (libc), tuned for embedded Linux-based devices · Media Libraries - based on PacketVideo's Open CORE; the libraries support playback and recording of many popular audio and video formats, as well as static image files, including MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG · Surface Manager - manages access to the display subsystem and seamlessly composites 2D and 3D graphic layers from multiple applications · LibWebCore - a modern web browser engine which powers both the Android browser and an embeddable web view · SGL - the underlying 2D graphics engine

· 3D libraries - an implementation based on OpenGL ES 1.0 APIs; the libraries use either hardware 3D acceleration (where available) or the included, highly optimized 3D software rasterizer · . Free Type - bitmap and vector font rendering SQLite - a powerful and lightweight relational database engine available to all applications.

8

Android Runtime:
Android includes a set of core libraries that provides most of the functionality available in the core libraries of the Java programming language. Every Android application runs in its own process, with its own instance of the Dalvik virtual machine. Dalvik has been written so that a device can run multiple VMs efficiently. The Dalvik VM executes files in the Dalvik Executable (.dex) format which is optimized for minimal memory footprint. The VM is register-based, and runs classes compiled by a Java language compiler that have been transformed into the .dex format by the included "dx" tool. The Dalvik VM relies on the Linux kernel for underlying functionality such as threading and low-level memory management. At the same level there is Android Runtime, where the main component Dalvik Virtual Machine is located. It was designed specifically for Android running in limited environment, where the limited battery, CPU, memory and data storage are the main issues. Android gives an integrated tool ―dx‖, which converts generated byte code from .jar to .dex file, after this byte code becomes much more efficient to run on the small processors. As the result, it is possible to have multiple instances of Dalvik virtual machine running on the single device at the same time. The Core libraries are written in Java language and contains of the collection classes, the utilities, IO and other tools.

9

Linux Kernal :
Android Architecture is based on Linux 2.6 kernel. It helps to manage security, memory management, process management, network stack and other important issues. Therefore, the user should bring Linux in his mobile device as the main operating system and install all the drivers required in order to run it. Android provides the support for the Qualcomm MSM7K chipset family. For instance, the current kernel tree supports Qualcomm MSM 7200A chipsets, but in the second half of 2008 we should see mobile devices with stable version Qualcomm MSM 7200, which includes major features: 1. WCDMA/HSUPA and EGPRS network support 2. Bluetooth 1.2 and Wi-Fi support 3. Digital audio support for mp3 and other formats 4. Support for Linux and other third-party operating systems 5. Java hardware acceleration and support for Java applications 6. Qcamera up to 6.0 megapixels 7. gpsOne – solution for GPS

10

The Dalvik Virtual Machine :
The Dalvik virtual machine is an interpreter only machine optimized for use on low powered, low memory devices like phones. Notably, Dalvik does not make use of just in time (JIT) Compilation to improve the performance of an application at runtime. Furthermore, Dalvik is not a Java virtual machine. This is because Dalvik is unable to read Java bytecode34, instead it uses its own bytecode format called ―dex‖. Google claims this format allows battery power to be better-conserved at all different stages of execution of an application. This means that standard Java SE applications and libraries cannot be used directly on the Android Dalvik virtual machine. Dalvik however stands at the center of the Android value proposition. Its low electrical power consumption, rich libraries, and unified, non-fragmented application programming interfaces make it stand out, or so Google hopes, over the fragmented ecosystem that is Java ME35 today. Furthermore, since Dalvik uses the Java programming language but not the Java execution environment (JVM), Google is free to develop Android without the need to license or obtain certification from Sun Microsystems Inc, the legal owner of the Java trademark and brands.

11

Development Tools:
The Android SDK includes a variety of custom tools that help develop mobile applications on the Android platform. The most important of these are the Android Emulator and the Android Development Tools plugin for Eclipse, but the SDK also includes a variety of other tools for debugging, packaging, and installing r applications on the emulator. Android Emulator A virtual mobile device that runs on computer use the emulator to design, debug, and test r applications in an actual Android run-time environment. Android Development Tools Plugin for the Eclipse IDE The ADT plugin adds powerful extensions to the Eclipse integrated environment, making creating and debugging r Android applications easier and faster. If use Eclipse, the ADT plugin gives an incredible boost in developing Android applications: It gives access to other Android development tools from inside the Eclipse IDE. For example, ADT lets access the many capabilities of the DDMS tool — taking screenshots, managing port-forwarding, setting breakpoints, and viewing thread and process information — directly from Eclipse. It provides a New Project Wizard, which helps quickly create and set up all of the basic files’ll need for a new Android application. It automates and simplifies the process of building r Android application. It provides an Android code editor that helps write valid XML for r Android manifest and resource files. Dalvik Debug Monitor Service (ddms) Integrated with Dalvik, the Android platform's custom VM, this tool lets manage processes on an emulator or device and assists in debugging. can use it to kill processes, select a specific process to debug, generate trace data, view heap and thread information, take screenshots of the emulator or device, and more. Android Debug Bridge (adb) The adb tool lets install application's .apk files on an emulator or device and access the emulator or device from a command line. can also use it to link a standard debugger to application code running on an Android emulator or device. Android Asset Packaging Tool (aapt) The aapt tool lets create .apk files containing the binaries and resources of Android applications. Android Interface Description Language (aidl)

12

Aidl Lets generate code for an interprocess interface, such as what a service might use. sqlite3 Included as a convenience, this tool lets access the SQLite data files created and used by Android applications. Trace view This tool produces graphical analysis views of trace log data that can generate from r Android application. mksdcard Helps create a disk image that can use with the emulator, to simulate the presence of an external storage card (such as an SD card). dx The dx tool rewrites .class bytecode into Android bytecode (stored in .dex files.)

activityCreator A script that generates Ant build files that can use to compile r Android applications. If are developing on Eclipse with the ADT plugin, won't need to use this script.

13

Back End
Mysql SQL (codename Yukon), released in October 2005, is the successor to SQL. It included native support for managing XML data, in addition to relational data. For this purpose, it defined an xml data type that could be used either as a data type in database columns or as literals in queries. XML columns can be associated with XSD schemas; XML data being stored is verified against the schema. XML is converted to an internal binary data type before being stored in the database. Specialized indexing methods were made available for XML data. XML data is queried using XQuery; Common Language Runtime (CLR) integration was a main feature with this edition, enabling one to write SQL code as Managed Code by the CLR. SQL Server 2005 added some extensions to the T-SQL language to allow embedding XQuery queries in T-SQL. In addition, it also defines a new extension to XQuery, called XML DML, that allows query-based modifications to XML data. SQL Server 2005 also allows a database server to be exposed over web services using TDS packets encapsulated within SOAP (protocol) requests. When the data is accessed over web services, results are returned as XML For relational data, T-SQL has been augmented with error handling features (try/catch) and support for recursive queries with CTEs (Common Table Expressions). SQL Server 2005 has also been enhanced with new indexing algorithms, syntax and better error recovery systems. Data pages are check summed for better error resiliency, and optimistic concurrency support has been added for better performance. Permissions and access control have been made more granular and the query processor handles concurrent execution of queries in a more efficient way. Partitions on tables and indexes are supported natively, so scaling out a database onto a cluster is easier. SQL CLR was introduced with SQL database mirroring in the RTM version, you had to apply trace flag 1400 at startup. Database mirroring is a high availability option that provides redundancy and failover capabilities at the database level. Failover can be performed manually or can be configured for automatic failover. Automatic failover requires a witness partner and an operating mode of synchronous (also known as high-safety or full safety). Server 2005 to let it integrate with the .NET Framework . SQL Server 2005 introduced "MARS" (Multiple Active Results Sets), a method of allowing usage of database connections for multiple purposes. SQL Server 2005 introduced DMVs (Dynamic Management Views), which are specialized views and functions that return server state information that can be used to monitor the health of a server instance, diagnose problems, and tune performance. SQL Server 2005 introduced Database Mirroring, but it was not fully supported until the first Service Pack release (SP1). In the initial release (RTM) of SQL Server 2005, database mirroring was available, but unsupported. In order to implement

14

Feasibility study
Feasibility studies aim to objectively and rationally uncover the strengths and weaknesses of an existing business or proposed venture, opportunities and threats as presented by the environment, the resources required to carry through, and ultimately the prospects for success. In its simplest terms, the two criteria to judge feasibility are cost required and value to be attained. As such, a well-designed feasibility study should provide a historical background of the business or project, description of the product or service, accounting statements, details of the operations and management, markets research and policies, financial data, legal requirements and tax obligations. Generally, feasibility studies precede technical development and project implementation.

(A)Economic feasibility:
The project is economically feasible as the only cost involved is having a computer with the minimum requirements mentioned earlier. For the users to access the application, the only cost involved will be in getting access to the Internet.

(B) Technical Feasibility
To deploy the application, the only technical aspects needed are mentioned below :        Operating EnvironmentWin2000/XP6/Win7 Android v 2.2 Java jdk l.6 Eclipse IDE Database SQL Server 2005 Internet Browser Internet Connection

(C) Behavioral feasibility :
The application requires no special technical guidance and all the views available in the application are self explanatory. The users are well guided with warning and failure messages for all the actions taken .

15

Information Gathering
As the goal of the application is ease of use and to provide an interactive interface, extensive research has been done to gain an insight into the needs and behaviors of various users. The working of the application is made convenient and easy to use for the end user.Users can be classified into two types based on their knowledge of the products that suit their needs. They can be classified as users who know about the product that would satisfy their needs and users who have to figure out the product that would satisfy their needs. Users who know about the product should be able to find the product easy with the click of a button. Such users can search for the product by using the product name as the search term. Users who have to figure out the product that would satisfy their needs could use a search term to find a list of products and then should be able to filter the results based on various parameters like product type, manufacturer, price range, platform supported etc. The users should be able to view the complete specification of the product and various images at different Zoom levels. The user should be able to read the customer reviews for the product and the ratings provided. They should be able to write their own reviews. They should be able to print out the specifications for a product or email the product page to a friends etc. To increase the ease of use the user should be able to add a product to the shopping cart by dragging a product and dropping it in the shopping cart. A user should able to edit the contents of a shopping cart. They should be able to update the quantities of the products added to the cart and remove the products from the cart. The user should be able to remove the product from the shopping cart by dragging the product and dropping it outside the cart. The application can be made interactive by pop up messages when a product has been dropped in to the shopping cart or out of the shopping cart. The user can be notified if the cursor enters a drop area and the object that could be dropped. Also users are impatient making it important to load pages soon .Other than this, I did a lot of research on various other methods of building this application which and was able to incorporate a few stronger features into the application.

16

System Analysis
After carefully analyzing the requirements and functionality of the web application, I had two important diagrams by the end of the analysis phase. They are the ER diagram and data flow diagram which were the basis for finding out entities and relationships between them, the flow of information.