1

INTRODUCTION

Complain t management System

INTRODUCTION TO PROJECT

1.1

Project Profile

Complaint management system(CMS)which can be used in business to business and business to consumer . CMS is an android application that provides the complaints for different products and getting reply from the products handling teams. Customers may have complaints about its products. They will be given an email id for each product, where they can send an email when they have a complaint to register. The emails will get converted to complaints and get assigned to the persons handling that product. The complaints can be assigned to different persons and will get tracked to closure. The person handling the complaint will have the facility to communicate with the customer via emails through the system.

1.2

Objectives
Application will be written using Android SDK in Java and should run on all Android OS handsets User lodges a complaint and gets confirmation of the lodged complaint in form of some unique complaint ticket, complaint id User can check status of his complaints using the complaint ticket id and can provide feedback on the service they received against a complaint. Administrator reviews a customers inquiry or complaint about the goods they purchased, the terms of the business should be interpreted in a fair and impartial manner.

1.3 Requirements

Complain t management System

User Authentication Managing Employees Managing Complaints Managing Vendors Managing Customers Information Session Management

1.4

Purpose

The purpose of this project is to provide the complaints for different products and getting reply from the products handling teams. Customers may have complaints about its products. They will be given an email id for each product, where they can send an email when they have a complaint to register. The emails will get converted to complaints and get assigned to the persons handling that product. The complaints can be assigned to different persons and will get tracked to closure. The person handling the complaint will have the facility to communicate with the customer via emails through the system.

1.5

Scope:

With usage mobile phones and tablets are rapidly replacing laptops and PCs . Android OS provides a platform where One of the fastest growing industries now a days is mobile industry. There are many competitors in this area who are doing research and development on new platforms & user experience. One such technology is Android from Google which is supported for Google phones. Developing applications for such mobile phones using the open source android SDK with a well known concept getting things done is quite interesting.

1.6

Project Description

The android SDK includes a comprehensive set of development tools. Requirements includes java development kit, the officially supported integrated development environment(IDE) is Eclipse(3.2 or later) using the android development tools(ADT) plugComplain t management System

in, though developers may use any text editor to edit java and XML files then use command line tools to create, built and debug android applications.

1.7

Project Overview

The application is a tool developed on android platform, whichisused to provide the complaints for different products and getting reply from the products handling teams.The complaints can be assigned to different persons and will get tracked to closure. The person handling the complaint will have the facility to communicate with the customer via emails through the system.

Complain t management System

System Analysis

Complain t management System

System Analysis
2.1Problem Definition
Their always a communication gap between vendor and consumer. When Consumer face problems while using a particular product . They will be a gap in communication.

2.2

Proposed System

The Proposed System is an android Application that is used to perform the existing system functionality through Mobile Phone itself. To use this application we dont need a computer and all the related stuff. We just need a mobile phone that runs on Android Operating System and internet.

2.3

System Environment

Android is a software stack for mobile devices that includes an operating system, middleware and key applications. The android SDK provides the tools and APIs necessary to being developing applications on the android platform using the java programming language.

2.4

Features of Android
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.

Complain t management System

Optimized graphics powered by a custom 2d graphics library; 3d graphics based on the open GL ES 1.0 specification(hardware acceleration optional)

2.5

Android Application:

Developers have full access to the same framework APIs used by the core application. 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.

2.6

Android Architecture

Complain t management System

The main components of the Android architecture:

2.6.1 Applications:
These are applications written in Java. Some of basic applications include an calendar, email client, SMS program, maps, making phone calls, accessing the Web browser, accessing your contacts list and others.If you are an average user, this is the layer you will us most, rest all layers are used by Google programmers, developers and hardware manufacturers.

2.6.2 Application Framework:

This is the skeleton or framework which all android developers have to follow. The developers can access all framework APIs an manage phones basic functions like resource Complain t management System

allocation, switching between processes or programs, telephone applications, and keeping track of the phones physical location. The architecture is well designed to simplify the reuse of components. Think of the application framework as a set of basic tools with which a developer can build much more complex tools.

2.6.3 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 libraries 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 packet videos 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 sub-system and seamlessly composites 2D and 3D graphic layers from multiple applications. LibWebCore A model 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 open GL ES 1.0 APIs; the libraries use either hardware 3D acceleration or the included, highly optimized 3D rasterizer. Free Type bit map and vector font rendering.

2.6.3.1 Introduction SQLite database:

SQLite is an open source embeddable database engine written in C by D. Richard Hipp. It is entirely self-contained with no external dependencies. It was introduced Complain t management System

10

as an option in PHP V4.3 and is built into PHP V5. SQLite supports much of the SQL92 standard, runs on all major operating systems, and has support for the major computer languages. SQLite is also surprisingly robust. Its creator conservatively estimates that it can handle a Web site with a load of up to 100,00 hits a day, and there have been cases where SQLite has handled a load 10 times that. SQLite is an embedded relational database engine. Its developers call it a self-contained, server less, zero-configuration and transactional SQL database engine. It is very popular and there are hundreds of millions copies worldwide in use today. SQLite is used in Solaris 10 and Mac OS operating systems, iPhone or Skype. Qt4 library has a built-in support for the SQLite as well as the Python or the PHP language. Many popular applications use SQLite internally such as Firefox or Amarok. SQLite implements most of the SQL-92 standard for SQL. The SQLite engine is not a standalone process. Instead, it is statically or dynamically linked into the application. SQLite library has a small size. It could take less than 300 KiB. An SQLite database is a single ordinary disk file that can be located anywhere in the directory hierarchy. It is a cross platform file. Can be used on various operating systems, both 32 and 64 bit architectures. SQLite is created in C programming language and has bindings for many languages like C++, Java, C#, Python, Perl, Ruby, Visual Basic, Tcl and others. The source code of SQLite is in public domain. Definitions: A relational database is a collection of data organized in tables. There are relations among the tables. The tables are formally described. They consist of rows and columns. SQL (Structured Query Language) is a database computer language designed for managing data in relational database management systems. A table is a set of values that is organized using a model of vertical columns and horizontal rows. The columns are identified by

Complain t management System

11

their names. A schema of a database system is its structure described in a formal language. It defines the tables, the fields, relationships, views, indexes, procedures, functions, queues, triggers and other elements. A database row represents a single, implicitly structured data item in a table. It is also called a tuple or a record. A column is a set of data values of a particular simple type, one for each row of the table. The columns provide the structure according to which the rows are composed. A field is a single item that exists at the intersection between one row and one column. A primary key uniquely identifies each record in the table. A foreign key is a Referential constraint between two tables. The foreign key identifies a column or a set of columns in one (referencing) table that refers to a column or set of columns in another (referenced) table. A trigger is a procedural code that is automatically executed in response to certain events on a particular table in a database. A view is a specific look on data in from one or more tables. It can arrange data in some specific order, higlight or hide some data. A view consists of a stored query accessible as a virtual table composed of the result set of a query. Unlike ordinary tables a view does not form part of the physical schema. It is a dynamic, virtual table computed or collated from data in the database. A transaction is an atomic unit of database operations against the data in one or more databases. The effects of all the SQL statements in a transaction can be either all committed to the database or all rolled back. An SQL result set is a set of rows from a database, returned by the SELECT statement. It also contains meta-information about the query such as the column names, and the types and sizes of each column as well. An index is a data structure that improves the speed of data retrieval operations on a database table. Functionality SQLite's support of the SQL92 standard includes indices, limitations, triggers, and views. SQLite does not support foreign key constraints, but supports Atomic, Consistent, Isolated, and Durable (ACID) transactions.

Under the hood:

Internally, SQLite consists of several components: an SQL compiler, a core, a back end, and accessories. SQLite's utilization of a virtual machine, the Virtual Database Engine

Complain t management System

12

(VDBE), makes it easy to debug, modify, and extend SQLite's core. All SQL statements are compiled into easy-to-read assembly executed in the SQLite virtual machine.

SQLite supports databases of up to 2 TB, with each database stored entirely in a single disk file. These disk files are portable across different byte-ordered machines. The data is stored on disk in a B+ tree data structure. SQLite depends on the file system for its database permissions. 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 it divides can run multiple VMs efficiently. The Dalvik VM executes files in the Dalvik executable format which is executable format which is optimized for minimal memory foot print. The VM is registered based and run classes compiled by 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. An android code editor that helps you write valid XML for your android manifest and resource files. It will even export your project into a signed APK, which can be distributed to users. To begin developing android applications in the eclipse IDE with ADT you first need to download the eclipse IDE and then download and install the ADT plug-in.

2.7
2.7.1

Android Application Development

Android Runtime Complain

t management System

13

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 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.An Android code editor that helps you write valid XML for your Android manifest and resource files. It will even export your project into a signed APK, which can be distributed to users. To begin developing Android applications in the Eclipse IDE with ADT, you first need to download the Eclipse IDE and then download and install the ADT plugin. To do so, follow the steps given in Installing the ADT Plugin. 2.7.2 Developing in eclipse with ADT:

The Android Development Tools (ADT) plugin for Eclipse adds powerful extensions to the Eclipse integrated development environment. It allows you to create and debug Android applications easier and faster. If you use Eclipse, the ADT plugin gives you an incredible boost in developing Android applications: It gives you access to other Android development tools from inside the Eclipse IDE. For example, ADT lets you access the many capabilities of the DDMS tool: take screenshots, manage port-forwarding, set breakpoints, and view thread and process informationdirectly from Eclipse. It provides a New Project Wizard, which helps you quickly create and set up all of the basic files you'll need for a new Android application. It automates and simplifies the process of building your Android application. Complain t management System

14

2.7.3 Creating an Android project The ADT plugin provides a New Project Wizard that you can use to quickly create a new Android project (or a project from existing code). To create a new project:
1. Select File>New>Project. 2. Select Android>Android Project, and click Next.

3. Select the contents for the project: Enter a Project Name. This will be the name of the folder where your project is created. Under Contents, select Create new project in workspace. Select your project workspace location. Under Target, select an Android target to be used as the project's Build Target. The Build Target specifies which Android platform you'd like your application built against. Unless you know that you'll be using new APIs introduced in the latest SDK, you should select a target with the lowest platform version possible, such as Android 1.1. Note: You can change your the Build Target for your project at any time: Right-click the project in the Package Explorer, select Properties, select Android and then check the desired Project Target. Under Properties, fill in all necessary fields. Enter an Application name. This is the human-readable title for your application the name that will appear on the Android device. Enter a Package name. This is the package namespace (following the same rules as for packages in the Java programming language) where all your source code will reside. Select Create Activity (optional, of course, but common) and enter a name for your main Activity class. Enter a Min SDK Version. This is an integer that indicates the minimum API Level required to properly run your application. Entering this here automatically sets the minSdkVersion attribute in the <uses-sdk> of your Android Manifest file. If you're unsure of the appropriate API Level to use, copy the API Level listed for the Build Target you selected in the Target tab.

Complain t management System

15

4.ClickFinish. Once you complete the New Project Wizard, ADT creates the following folders and files in your new project: src/ Includes your stub Activity Java file. All other Java files for your application go here. <Android Version>/ (e.g., Android 1.1/) Includes the android.jar file that your application will build against. This is determined by the build target that you have chosen in the New Project Wizard. gen/ This contains the Java files generated by ADT, such as your R.java file and interfaces created from AIDL files. assets/ This is empty. You can use it to store raw asset files. res/ A folder for your application resources, such as drawable files, layout files, string values, etc. AndroidManifest.xml The Android Manifest for your project. default.properties This file contains project settings, such as the build target. This files is integral to the project, as such, it should be maintained in a Source Revision Control system. It should never be edited manually to edit project properties, right-click the project folder and select "Properties". 2.7.4 Running your application:

Complain t management System

16

Before you can run your application on the Android Emulator, you must create an Android Virtual Device (AVD). An AVD is a configuration that specifies the Android platform to be used on the emulator. 2.7.5 Creating an AVD: With ADT 0.9.3 and above, the Android SDK and AVD Manager provides a simple graphical interface for creating and managing AVDs. To create an AVD with the AVD Manager: Select Window >Android SDK and AVD Manager, or click the Android SDK and AVD Manager icon (a black device) in the Eclipse toolbar. In the Virtual Devices panel, you'll see a list of existing AVDs. Click New to create a new AVD. Fill in the details for the AVD. Give it a name, a platform target, an SD card image (optional), and a skin (HVGA is default). Click Create AVD. Your AVD is now ready and you can close the AVD Manager. In the next section, you'll see how the AVD is used when launching your application on an emulator.

2.7.6 Running your application: Note: Before you can run your application, be sure that you have created an AVD with a target that satisfies your application's Build Target. If an AVD cannot be found that meets the requirements of your Build Target, you will see a console error telling you so and the launch will be aborted.

Complain t management System

17

To run (or debug) your application, select Run>Run (or Run>Debug) from the Eclipse main menu. The ADT plugin will automatically create a default launch configuration for the project. When you choose to run or debug your application, Eclipse will perform the following: Compile the project (if there have been changes since the last build). Create a default launch configuration (if one does not already exist for the project). Install and start the application on an emulator or device (based on the Deployment Target defined by the run configuration). By default, Android application run configurations use an "automatic target" mode for selecting a device target. If debugging, the application will start in the "Waiting For Debugger" mode. Once the debugger is attached, Eclipse will open the Debug perspective. To set or change the launch configuration used for your project, use the launch configuration manager. 2.7.7 Creating a run configuration: The run configuration specifies the project to run, the Activity to start, the emulator options to use, and so on. When you first run a project as an Android Application, ADT will automatically create a run configuration. The default run configuration will launch the default project Activity and use automatic target mode for device selection (with no preferred AVD). If the default settings don't suit your project, you can customize the launch configuration or even create a new. To create or modify a launch configuration, follow these steps as appropriate for your Eclipse version: Open the run configuration manager. Complain t management System

18

In Eclipse 3.4 (Ganymede), select Run >Run Configurations (or Debug Configurations) Expand the Android Application item and create a new configuration or open an existing one. To create a new configuration: Select Android Application and click the New launch configuration icon above the list (or, right-click Android Application and click New). Enter a Name for your configuration. In the Android tab, browse and select the project you'd like to run with the configuration. To open an existing configuration, select the configuration name from the list nested below Android Application. Adjust your desired launch configuration settings. In the Target tab, consider whether you'd like to use Manual or Automatic mode when selecting an AVD to run your application. You can specify any emulator options to the Additional Emulator Command Line Options field. For example, you could add -scale 96dpi to scale the AVD's screen to an accurate size, based on the dpi of your computer monitor.

2.8

Hard Ware & Soft Ware Requirements

Hard Ware Requirements

Hardware Requirements are Core2Duo above processor, 2GB+ of main memory (RAM) and 100MB hard disk.

Soft Ware Requirements

Complain t management System

19

Java Android SDK 1.5 or later

Eclipse Ganymede IDE Operating System can be Windows XP, LINUX and Mac etc.

Technologies to be used:
1. 2. 3. 4. 5. 6. User Interface: Android XML. Programming Language: Java Debug Tool: LogCat (Android) Backend Database :SQLite Operating System: Windows 7/ XP/2000/2003, LINUX. IDEs: Eclipse with Android plug-in.

2.9

Module Description

The system can be consist of two modules 1. System Admin Module 2. Customer Module

2.9.1 System Admin Module

The admin can view all the team details and the all the customer details.The Complain t management System

20

administrator is responsible for the oversight, management and administration of the complaints received from the customers. Administrators can now configure complaint box administrators for each category type of complaints. This will make it easier to assign owners for different aspects of managing the complex. Administrator has to respond to the customer inquiries and complaints. The administrator is expected to observe high standards of integrity and honesty, and to act in good faith and in the best interests of the customer. For example, when the administrator reviews a customers inquiry or complaint about the goods they purchased, the terms of the business should be interpreted in a fair and impartial manner.

2.9.2 Customer Module

The following are the benefits to the customers from the CMS android app: User lodges a complaint and gets confirmation of the lodged complaint in form of some unique complaint ticket, complaint id etc. User can check status of his complaints using the complaint ticket id i.e. he can track the status of his complaint at any point of time. User gets notified when the complaint is rectified. He can view his Profile when ever his/details change. They can provide feedback on the service they received against a complaint. They can give the suggestions also to the complaint management people to improve their service in resolving the complaint quoted by the customers.

Complain t management System

21

Feasibility Study

Feasibility Study :
Preliminary investigation examine project feasibility, the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging

Complain t management System

22

old running system. All system is feasible if they are unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation:

3.1

Technical Feasibility Operational Feasibility Economical Feasibility

Technical Feasibility:

The technical issue usually raised during the feasibility stage of the investigation includes the following:

Does the necessary technology exist to do what is suggested? Do the proposed equipments have the technical capacity to hold the data required to use the new system? Will the proposed system provide adequate response to inquiries, regardless of the number or location of users? Can the system be upgraded if developed? Are there technical guarantees of accuracy, reliability, ease of access and data security? Earlier no system existed to cater to the needs of Secure CMS System.

Thus it provides an easy access to the users. The databases purpose is to create, establish and maintain a workflow among various entities in order to facilitate all concerned users in their various capacities or roles. Permission to the users would be granted based on the Complain t management System

23

roles specified. Therefore, it provides the technical guarantee of accuracy, reliability and security. The software and hard requirements for the development of this project are not many and are already available in-house at NIC or are available as free as open source. The work for the project is done with the current equipment and existing software technology. Necessary bandwidth exists for providing a fast feedback to the users irrespective of the number of users using the system.

3.2

Operational Feasibility:
Proposed projects are beneficial only if they can be turned out into

information system. That will meet the organizations operating requirements. Operational feasibility aspects of the project are to be taken as an important part of the project implementation. Some of the important issues raised are to test the operational feasibility of a project includes the following: -

Is there sufficient support for the management from the users? Will the system be used and work properly if it is being developed and implemented? 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.

3.3

Economical Feasibility:

Complain t management System

24

A system can be developed technically and that will be used if installed must still be a good investment for the organization. In the economical feasibility, the development cost in creating the system is evaluated against the ultimate benefit derived from the new systems. Financial benefits must equal or exceed the costs. The system is economically feasible. It does not require any additional hardware or software. Since the interface for this system is developed using the existing resources and technologies available at NIC, There is nominal expenditure and economical feasibility for certain.

Complain t management System

25

System Design

Complain t management System

26

System Design
System design is transition from a user oriented document to programmers or database personnel. The design is a solution, how to approach to the creation of the new system. This is composed of several steps. It provides the understanding and procedural details necessary for implementing the system recommended in the feasibility study. Designing goes through logical and physical stages of development, logical design reviews the present physical system, prepare input and output specification, details of implementation plan and prepare a logical design walkthrough The database tables are designed by analyzing functions involved in the system and format of the fields is also designed. The fields in the database tables should define their role in the system. The unnecessary fields should be avoided because it affects the storage areas of the system. Then in the input and output screen design, the design should be made user friendly. The menu should be precise and compact.

4.1Architecture Diagram

Fig 3.1

Complain t management System

27

User uses the gphone and stores the actions into the database .The gphone alerts the user to perform particular action with respect to the scheduled time. The Android SDK contains inbuilt SQLite Database, SQL Query statements are used to store and retrieve the actions.

Complain t management System

28

4.2 UML Diagrams

4.2.1 Class Diagram:

Complain t management System

29

Fig 3.2

4.2.2 Sequence Diagram

Fig 3.3

Complain t management System

30

4.2.3Collaborative Diagram

Complain t management System

31

Fig 3.4

4.2.4 Use case diagram

Complain t management System

32

Fig 3.5

4.2.5 Activity Diagram

Complain t management System

33

Fig 3.6

Complain t management System

34

4.2.6 State Chart Diagram

Complain t management System

35

Fig 3.6

Complain t management System

36

3.2.7 Component Diagram

Fig 3.7

Complain t management System

37

System Testing

Complain t management System

38

TESTING
Soft Ware Testing
Testing
Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design and code generation.

5.1 TESTING OBJECTIVES

To ensure that during operation the system will perform as per specification. TO make sure that system meets the user requirements during operation To make sure that during the operation, incorrect input, processing and output will be detected To see that when correct inputs are fed to the system the outputs are correct To verify that the controls incorporated in the same system as intended Testing is a process of executing a program with the intent of finding an error A good test case is one that has a high probability of finding an as yet undiscovered error

The software developed has been tested successfully using the following testing strategies and any errors that are encountered are corrected and again the part of the program or the Complain t management System

39

procedure or function is put to testing until all the errors are removed. A successful test is one that uncovers an as yet undiscovered error. Note that the result of the system testing will prove that the system is working correctly. It will give confidence to system designer, users of the system, prevent frustration during implementation process etc.

5.2 TEST CASE DESIGN:

White box testing White box testing is a testing case design method that uses the control structure of the procedure design to derive test cases. All independents path in a module are exercised at least once, all logical decisions are exercised at once, execute all loops at boundaries and within their operational bounds exercise internal data structure to ensure their validity. Here the customer is given three chances to enter a valid choice out of the given menu. After which the control exits the current menu. Black Box Testing Black Box Testing attempts to find errors in following areas or categories, incorrect or missing functions, interface error, errors in data structures, performance error and initialization and termination error. Here all the input data must match the data type to become a valid entry. The following are the different tests at various levels: Unit Testing: Unit testing is essentially for the verification of the code produced during the coding phase and the goal is test the internal logic of the module/program. In the Generic code project, the unit testing is done during coding phase of data entry forms whether

Complain t management System

40

the functions are working properly or not. In this phase all the drivers are tested they are rightly connected or not. Integration Testing: All the tested modules are combined into sub systems, which are then tested. The goal is to see if the modules are properly integrated, and the emphasis being on the testing interfaces between the modules. In the generic code integration testing is done mainly on table creation module and insertion module.

Validation Testing This testing concentrates on confirming that the software is error-free in all respects. All the specified validations are verified and the software is subjected to hard-core testing. It also aims at determining the degree of deviation that exists in the software designed from the specification; they are listed out and are corrected. System Testing This testing is a series of different tests whose primary is to fully exercise the computerbased system. This involves: Implementing the system in a simulated production environment and testing it. Introducing errors and testing for error handling.

Complain t management System

41

Test case1
Login :

Test id

Test name

Testing methodology

description

Expected output

Actual output

Pass/fail

LTC1

Functional testing

Black testing

box

LTC2

Functional testing Functional testing

Black testing Black testing

box

LTC3

box

LTC4

Functional testing

Black testing

box

t management System

Username Username should not and allow the It allows the password special special Fail allow the characters characters special but the characters password allow Username Does not Does not should not allow the allow the allow the Pass special special special characters characters characters Its allow the Allow the Allow the special special special Pass characters characters characters If the username should not allow the Username Username special should not should not characters allow, allow, ,but the password password Pass Complain password should allow should allow allows the special characters

42

LTC5

GUI

Black testing

If click the login button box It will login It will login it will login Pass to the system to the system to the system

LTC6

URL

Black testing

If u will enter the CMS airline industry in Return it will box It will open address bar open that Pass that website for login it website will open that login website

Complain t management System

43

Test Case 2
Customer Registration Form:

Test Id CRTC1

Test Name

Testing methodology box

Description Should not allow the blank Spaces password and Confirm passwords both should be match If the phone number allows numeric values only The email address should be valid If the customer will enter the address, the address component will be increase the address size If the registration is completed then click the submit

Expected output

Actual output

Pass/Fail

Functional Black testing testing

Should not Should not allow the allow the Pass blank spaces blank spaces Should match be Should match be

CRTC2

Functional Black testing testing

box

Pass

CRTC3

Functional Black testing testing

box

It returns the Returns valid Pass Phone number phone number Return the Return the valid Email valid Email Pass address valid address

Functional Black CRTC4 testing testing

box

Crtc5

GUI

Black testing

box

Automatically Automatically it will it will pass increase increase

CRTC6 GUI

Black testing

box

Registration is Registration is Pass completed completed

Complain t management System

44

button

Test case 3
Vendors Details:
Test id Test Name Testing methodology Description If u will click the add provider or vendor it will show the add vendors screen If u will click the edit provider or vendor it will show the edit vendors screen If u will click the search provider or vendor it will show the search vendors screen Expected output It will show the add vendors screen Actual output Pass/fail

FDTC1 GUI

Black box testing

It will show the add Pass vendors screen

FDTC2 GUI

Black box testing

It will show the edit vendors screen

It will show the show the Pass edit vendors screen

Functional FDTC3 Black box testing testing

It will show the search vendors screen

It will show the search Pass vendors screen

FDTC4 GUI

Black box testing

When the customer click the Returns logout. It logout can logout to the system

Returns logout

Pass

Complain t management System

45

Test case 4
Complaint Details:

Test id

Test name

Testing methodology

Description If u will click the add complaints it will show the add complaint screen If u will click the edit complaints it will show the edit complaint screen If u will click the search complaints it will show the search complaint screen

Expected output

Actual output

Pass/Fail

ODTC1

Functional Black box testing testing

It will It will add show the complaints add Pass screen complaints screen It will show the edit complaints screen It will show the edit Pass complaints screen

ODTC2 GUI

Black box testing

ODTC3 GUI

Black box testing

It will show the search complaints screen

It will show the search pass complaints screen

Complain t management System

46

Test case 5
Admin:

Test id

Test name

Testing methodology Black testing box

Description The admin should enter the username and password the admin clicks the login button The admin provides the all vendors. In this the admin provides the vendors details. If the admin login to the system and he should have delete and modify the old vendors, employees If the admin clicks the logout then he logout to the system

Expected output Should enter the username and password login

Actual output

Pass/Fail

ATC1

Functional testing

Enter the username pass and password Login Pass

ATC2 ATC3

GUI GUI

Black testing Black testing Black testing

box box

He can He can provide the provide the Pass vendors vendors It will Return all return all pass the details the details

ATC4

GUI

box

ATC5

GUI

Black testing

box

He will modify and provides the new details

Modify and pass provide the new details

ATC6

GUI

Black testing

box

He will He will logout to logout to Pass the system the system

Complain t management System

47

Test case 6
Database:

Test id DBTC1

Test name Functional testing

Testing methodology Black testing

Description

Expected output

Actual output

Pass/Fail

DBTC2

GUI

Black testing

DBTC3

Functional testing

Black testing

DBTC4

GUI

Black testing

The database box maintains the all the details about customer If the customer login to the system then the database should box check the details about customer. If it is valid he login to the system The admin can change the any box details, the details are stored into a database If the admin did any changes in box complaints it can stores into database

It maintain It maintain pass the details the details

If it is It is valid valid he can customer pass login to login to the system the system

Stored into Stored into Pass a database a database

Stored the Stored the pass database database

Complain t management System

48

OUTPUT SCREENS

Complain t management System

49

Complain t management System

50

Complain t management System

51

Complain t management System

52

Complain t management System

53

Complain t management System

54

Complain t management System

55

Complain t management System

56

Complain t management System

57

Complain t management System

58

Complain t management System

59

Complain t management System

60

Complain t management System

61

Complain t management System

62

Complain t management System

63

Complain t management System

64

Complain t management System

65

CONCLUSION
It is a tool developed for Android platform ,which is used to provide the complaints for different products and getting reply from the products handling teams. Customers may have complaints about its products. The complaints can be assigned to different persons and will get tracked to closure. The person handling the complaint will have the facility to communicate with the customer via emails through the system Applications can be developed on Android platform of Open Handset Alliance led by Google. Google provides simulated environment and standard development kit for developing Android applications. Although this platform is very new and SDK provided is still in its nascent stage, a great number of mobile companies are queuing up to install it on their devices. We chose Android as it is parallel to iOS (supported by Apple) in terms of facilities it provide and is also open source.

Complain t management System

66

FUTURE ENHANCEMENTS
Future Enhancements has been coined to denote the fact that Everything can always be done better than it being done. The denouncement engendered is satisfactory and implements many of the validations suggested. The future enhancement that can be done to the present project is : The processing power required for the application can be reduced. Which can in turn increase processing power of the application and the battery of the hardware. Applications can be developed on Android platform of Open Handset Alliance led by Google. Google provides simulated environment and standard development kit for developing Android applications. Although this platform is very new and SDK provided is still in its nascent stage, a great number of mobile companies are queuing up to install it on their devices. We chose Android as it is parallel to iOS (supported by Apple) in terms of facilities it provide and is also open source.

Complain t management System

67

BIBLIOGRAPHY
1. SOFTWARE ENGINEERIN By Roger.S.Pressman 2. JAVA HOW TO PROGRAM ByDietel 3. Android http://developer.android.com/index.html

Complain t management System