Project Title MINI-PROJECT REPORT SUBMITTED TO MANIPAL UNIVERSITY, MANIPAL (A Deemed University)

FOR THE PARTIAL FULLFILLMENT OF THE DEGREE OF MASTER OF COMPUTER APPLICATION

By Your Name (Reg. No: 1222333) Your Name (Reg. No: 1222333) Your Name (Reg. No: 1222333) Under the guidance of Mr. Karunakar A K Sr. Lecturer Department of MCA Manipal 576 104

Mr. Tojo Thomas Sr. Lecturer Department of MCA Manipal 576 104

DEPARTMENT OF MASTER OF COMPUTER APPLICATION MANIPAL INSTITUTE OF TECHNOLOGY, MANIPAL-576104 KARNATAKA, INDIA May 2009

DECLARATION I hereby declare that this mini project work entitled xxxxx yyyyy zzzzz is original and has been carried out by me in the Department of Information and Communication Technology of Manipal Institute of Technology, Manipal, a constituent Institute of Manipal University, a Deemed University, under the guidance of Mr. Karunakar A K and Mr. Tojo Thomas, Dept. of Information and Communication Technology, M. I. T., Manipal. No part of this work has been submitted for the award of a degree or diploma either to this University or to any other Universities.

Place: Manipal Date: 30-03-2009

aaaaa

bbbbb

cccccc

(1234)

(1234)

(1234)

i

CERTIFICATE This is to certify that this mini project entitled xxxxx yyyyy zzzzz is a bonafide work done by xxxx (Reg. No. 1234), yyyyy (Reg. No. 1234), zzzzz (Reg. No. 1234) at Manipal Institute of Technology, Manipal independently under my guidance and supervision for the partial fullfillment of Degree of Master of Computer Application.

Mr. Karunakar A K

Mr. Tojo Thomas

Sr. Lecturer

Sr. Lecturer

Department of Information and

Department of Information and

Communication Technology

Communication Technology

Manipal 576 104

Manipal 576 104

Place: Manipal Date: 30-03-2009

ii

This work is dedicated to zzzzzz xxxxx and yyyyy

iii

Abstract kaf;lka;lfkakf;la kf;alk;fka; kf;alkf;lak;fka lfa;kfa;l kf;alkf;a ;akf;lakf;las kljalfjlajflkajfljflkajflk jflkjalfkjlkfjla lljaflja flajf aflkajlkajlkfja;l ajflj aljalfjla jlfajlkjflakj flka jlajfla jlajflkjalkfa lkfjalkjflkajf lkajfalkfjlakfjalk jflkajflkasjlfsajf;lkjalfkjlkfjlsafj ;lalka kljalfjlajflkajfljflkajflk jflkjalfkjlkfjla lljaflja flajf aflkajlkajlkfja;l ajflj aljalfjla jlfajlkjflakj flka jlajfla jlajflkjalkfa lkfjalkjflkajf lkajfalkfjlakfjalk jflkajflkasjlfsajf;lkjalfkjlkfjlsafj ;lalka

iv

Acknowledgments kljalfjlajflkajfljflkajflk jflkjalfkjlkfjla lljaflja flajf aflkajlkajlkfja;l ajflj aljalfjla jlfajlkjflakj flka jlajfla jlajflkjalkfa lkfjalkjflkajf lkajfalkfjlakfjalk jflkajflkasjlfsajf;lkjalfkjlkfjlsafj ;lalka kljalfjlajflkajfljflkajflk jflkjalfkjlkfjla lljaflja flajf aflkajlkajlkfja;l ajflj aljalfjla jlfajlkjflakj flka jlajfla jlajflkjalkfa lkfjalkjflkajf lkajfalkfjlakfjalk jflkajflkasjlfsajf;lkjalfkjlkfjlsafj ;lalka kljalfjlajflkajfljflkajflk jflkjalfkjlkfjla lljaflja flajf aflkajlkajlkfja;l ajflj aljalfjla jlfajlkjflakj flka jlajfla jlajflkjalkfa lkfjalkjflkajf lkajfalkfjlakfjalk jflkajflkasjlfsajf;lkjalfkjlkfjlsafj ;lalka kljalfjlajflkajfljflkajflk jflkjalfkjlkfjla lljaflja flajf aflkajlkajlkfja;l ajflj aljalfjla jlfajlkjflakj flka jlajfla jlajflkjalkfa lkfjalkjflkajf lkajfalkfjlakfjalk jflkajflkasjlfsajf;lkjalfkjlkfjlsafj ;lalka

v

Contents

Abstract

iv

List of figures

1

1 Synopsis

2

1.1

1.2

1.3

1.4

1.5

Environment Details . . . . . . . . . . . . . . . . . . . . . . .

3

1.1.1

Hardware Requirements . . . . . . . . . . . . . . . . .

3

Introduction To Tools and Languages . . . . . . . . . . . . . .

3

1.2.1

Visual Basic.Net . . . . . . . . . . . . . . . . . . . . .

3

1.2.2

Oracle 9i . . . . . . . . . . . . . . . . . . . . . . . . . .

4

1.2.3

Windows XP . . . . . . . . . . . . . . . . . . . . . . .

5

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5

1.3.1

Overview of Existing System . . . . . . . . . . . . . . .

6

Proposed System . . . . . . . . . . . . . . . . . . . . . . . . .

7

1.4.1

Advantages of Proposed System . . . . . . . . . . . . .

7

1.4.2

Module Specification . . . . . . . . . . . . . . . . . . .

8

Process Model

. . . . . . . . . . . . . . . . . . . . . . . . . .

9

1.5.1

Waterfall Model . . . . . . . . . . . . . . . . . . . . . .

9

1.5.2

Waterfall Model . . . . . . . . . . . . . . . . . . . . . .

10

2 Software Requriement Specification

vi

13

2.1

xxxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13

2.2

yyyyy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14

2.3

xzzzzzz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14

3 Design

15

3.1

ER Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15

3.2

Schema Diagram . . . . . . . . . . . . . . . . . . . . . . . . .

15

3.3

Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16

4 Implementation Details

17

4.1

xxxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17

4.2

yyyyy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17

4.3

xzzzzzz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18

5 Sample Screen Shots

19

5.1

xxxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19

5.2

yyyyy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19

5.3

xzzzzzz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

20

6 Conclusions and Future Work

21

6.1

xxxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21

6.2

yyyyy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21

6.3

xzzzzzz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22

vii

List of Tables 2.1

Sample Table . . . . . . . . . . . . . . . . . . . . . . . . . . .

13

3.1

Sample Table . . . . . . . . . . . . . . . . . . . . . . . . . . .

16

viii

List of Figures 1.1

ER Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9

1.2

ER Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12

2.1

Sample Figure . . . . . . . . . . . . . . . . . . . . . . . . . . .

14

3.1

ER diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16

1

Chapter 1 Synopsis New Tech Infosol is the provider of the quality software with at least 4 years of experience and 2000 customers. The main goal of the company is to create quality software’s, which allows using the modern computer technologies with the maximum facility. The main field of the company is developing software’s for various kinds of organizations and making their management work more sophisticated and easier. New Tech Infosol has more than 170 different kinds of software’s running successfully in local market and major industries like: • Textile • Trading • Financial Accounting System (FAS) • Diamond • Finance • Share Trading • Design Tools 2

• Hotel and Restaurants • Hospital

1.1

Environment Details

1.1.1

Hardware Requirements

• ” Processor : Intel Pentium Pro 400 MHz or Higher • Hard Disk : 5 GB Or Above • RAM : 512 MB Or Above Software Requirements • OS : Windows 98, 2000,NT OR XP • Front End : Visual Basic.Net 2003 • Back End : Oracle 9i Development Environment • Operating System : Windows XP • Development Language : VB.Net • Backend Database : Oracle 9i

1.2 1.2.1

Introduction To Tools and Languages Visual Basic.Net

Visual Basic .NET is an object-oriented computer language that can be viewed as an evolution of Microsoft’s Visual Basic (VB) implemented on the Microsoft .NET framework. VB.Net is now a full-fledged object oriented programming language. It contains classes, objects, inheritance, polymorphism, abstract 3

classes, interfaces, structures, enumerations, delegates and other common object oriented concepts. This rich language enables you to develop many different types of applications. It is a programming language used to create window base application. Hundreds of functions and latest technological advances have been added to the language to make it an industrial - strength development environment suitable for almost my type of windows application. This is especially true with the advent of internet programming and object oriented programming.

1.2.2

Oracle 9i

An Oracle database is a collection of data treated as a unit. The purpose of a database is to store and retrieve related information. A database server is the key to solving the problems of information management. In general, a server reliably manages a large amount of data in a multiuser environment so that many users can concurrently access the same data. All this is accomplished while delivering high performance. A database server also prevents unauthorized access and provides efficient solutions for failure recovery. Oracle Database is the first database designed for enterprise grid computing, the most flexible and cost effective way to manage information and applications. Enterprise grid computing creates large pools of industry-standard, modular storage and servers. With this architecture, each new system can be rapidly provisioned from the pool of components. There is no need for peak workloads, because capacity can be easily added or reallocated from the resource pools as needed.

4

1.2.3

Windows XP

Windows XP is a line of operating system developed by Microsoft for use on general purpose computer systems, including home and business desktops and laptops. Windows XP is the successor to WINDOWS 2000 and is the first consumer oriented operating system product by Microsoft to be built on the Windows NT kernel and architecture. Windows XP is known for its improving stability and efficiency over various versions of Windows. It represents a significantly redesigned graphical user interface. New software management capabilities were introduced to avoid the ”DLL hell” that plagued the older version of Windows. It’s the first version of windows to use product activation to combat software privacy, a restriction that did not it well with some users and privacy advocates.

1.3

Introduction

Competitive and regulatory pressures are forcing organizations to change the way they handle, manage, respond to, and report customer complaints. Customer Care System is a comprehensive solution for managing complaints from customers. The real-time visibility provided by the software enables organizations to track each complaint through its lifecycle, following the appropriate process to ensure that nothing slips through the cracks. The Customer Care System enables customer service representatives and complaint managers to initiate a complaint for a product or service coming from multiple sources like phone, fax, email, or the web. All crucial details and parameters about the product as well as the incident are captured. The system guides the user by dynamically enabling, disabling, mandating, or defaulting fields based on data being entered. Drop-down menus, logical validations, 5

and auto-fill capabilities boost efficiency and ensure accuracy of information. Objective The main objective behind building this system is to computerize the complaint handling system which is being carried out manually till now. The system is designed in such a way that it stores the details of clients and complaints made by them.

1.3.1

Overview of Existing System

New Tech Infosol is a leading provider of software’s in various sectors of the industries. The company provides variety of software’s to a large number of customers with an experience of 4 years. It has around 2000 customers under it. The complaints of the customers’ were registered manually up till now. Whenever a customer makes a complaint, the complaint was first registered into a file or a complaint book. Then after the registration of the complaint it is forwarded to the engineer for further action. The feedback is then provided on the phone. Limitations of Existing System 1. Complaints are to be registered manually. 2. No facility for maintaining the Client details and information. 3. No facility to know which complaints are solved and which are pending. 4. No proper complaint number can be given. 5. Searching for a particular client or a complaint is very difficult. 6. Time consuming process.

6

1.4

Proposed System

The proposed system is to computerize the existing manual system. The system is named as Customer Care System. The Customer Care System is built to maintain the details of the client information and their complaints in a systematic format. When a customer complaint, his data is automatically fetched from the database and a complaint number is given to him. If the customer has more then one complaint in a day then only one complaint number is given to him for all the complaints, so that it will be easy for the client to remember only one complain number instead of remembering multiple complaint numbers. Also it will help the user to easily maintain the data without much ambiguity. If the complaint is not solved within specified time limit and client re-complaints then he is given a new complaint number. The system provides a flexible search feature which helps the user to search the client or complaint information easily.

1.4.1

Advantages of Proposed System

The Customer Care System has the following advantages: 1. Complaint registration is computerized. 2. Detailed information of each client is maintained. 3. Efficient searching facility. 4. Auto Filling Capabilities. 5. Enhanced effectiveness and saves the time. 6. User and Admin level security. 7. User friendly.

7

1.4.2

Module Specification

The system is mainly divided into 5 modules:

1. Client 2. Complaint 3. Categories 4. Search 5. Login

Client This module maintains the client information and its related operation.(This module is handled by Kanika and Sandeep .)

Categories Categories module deals with the types of the software developed by the company. (This module is handled by Rohit.)

Complaint Complaint module deals with the information related to complaints made by the clients. (This module is handled Manish and Kanika. )

Search This module aims to provide an efficient search facility to the user.(This module is handled by Manish and Rohit.)

8

Figure 1.1: ER Diagram Login Login module deals with the security level for the software. (This is handled by Sandeep.)

1.5

Process Model

1.5.1

Waterfall Model

The Waterfall Model is the classic software life cycle model. This model represents the software life cycle using processes and products. Each process transforms a product to produce a new product as output. Then the new product becomes the input of the next process. The advantage of waterfall development is that it allows for departmentalization and managerial control. A schedule can be set with deadlines for each stage of development and a product can proceed through the development process and be delivered on time.

9

1.5.2

Waterfall Model

Feasibility The feasibility study is used to determine if the project should get the goahead. If the project is to proceed, the feasibility study will produce a project plan and budget estimates for the future stages of development.

Requirement Analysis and Design Analysis gathers the requirements for the system. This stage includes a detailed study of the business needs of the organization. Options for changing the business process may be considered. Design focuses on high level design like, what programs are needed and how are they going to interact, low-level design (how the individual programs are going to work), interface design (what are the interfaces going to look like) and data design (what data will be required). During these phases, the software’s overall structure is defined. Analysis and Design are very crucial in the whole development cycle. Any glitch in the design phase could be very expensive to solve in the later stage of the software development. Much care is taken during this phase. The logical system of the product is developed in this phase.

Implementation In this phase the designs are translated into code. Computer programs are written using a conventional programming language or an application generator. Programming tools like Compilers, Interpreters, and Debuggers are used to generate the code. Different high level programming languages are used for coding.

10

Testing In this phase the system is tested. Normally programs are written as a series of individual modules, this subject to separate and detailed test. The system is then tested as a whole. The separate modules are brought together and tested as a complete system. The system is tested to ensure that interfaces between modules work (integration testing), the system works on the intended platform and with the expected volume of data (volume testing) and that the system does what the user requires (acceptance/beta testing).

Maintenance Inevitably the system will need maintenance. Software will definitely undergo change once it is delivered to the customer. There are many reasons for the change. Change could happen because of some unexpected input values into the system. In addition, the changes in the system could directly affect the software operations. The software should be developed to accommodate changes that could happen during the post implementation period.

11

Figure 1.2: ER Diagram

12

Chapter 2 Software Requriement Specification fkjas;lf af a lkajfaf a klj lafjlakjfa lfjalkfjaljalfjla ja;fja lfjaljf ;laajflkajf;lajf akjlafja lafja;lkfja;lfkj;lajflajf a lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

2.1

xxxx

lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

Table 2.1: Sample Table 111

zzzz

bbbbb

222

aaaa

ccccc

333

wwww

ddddd 13

2.2

yyyyy

lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

2.3

xzzzzzz

lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

Figure 2.1: Sample Figure

14

Chapter 3 Design fkjas;lf af a lkajfaf a klj lafjlakjfa lfjalkfjaljalfjla ja;fja lfjaljf ;laajflkajf;lajf akjlafja lafja;lkfja;lfkj;lajflajf a lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

3.1

ER Diagram

lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

3.2

Schema Diagram

lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

15

Figure 3.1: ER diagram Table 3.1: Sample Table Attribute

Type

Constraints

emp-no

varchar2(10)

Primary Key

333

wwww

ddddd

3.3

Database

lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

16

Chapter 4 Implementation Details fkjas;lf af a lkajfaf a klj lafjlakjfa lfjalkfjaljalfjla ja;fja lfjaljf ;laajflkajf;lajf akjlafja lafja;lkfja;lfkj;lajflajf a lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

4.1

xxxx

lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

4.2

yyyyy

lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

17

4.3

xzzzzzz

lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

18

Chapter 5 Sample Screen Shots fkjas;lf af a lkajfaf a klj lafjlakjfa lfjalkfjaljalfjla ja;fja lfjaljf ;laajflkajf;lajf akjlafja lafja;lkfja;lfkj;lajflajf a lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

5.1

xxxx

lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

5.2

yyyyy

lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

19

5.3

xzzzzzz

lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

20

Chapter 6 Conclusions and Future Work fkjas;lf af a lkajfaf a klj lafjlakjfa lfjalkfjaljalfjla ja;fja lfjaljf ;laajflkajf;lajf akjlafja lafja;lkfja;lfkj;lajflajf a lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

6.1

xxxx

lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

6.2

yyyyy

lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

21

6.3

xzzzzzz

lkjaflja;lf ajfljalkfja ajflkajlkjalkfj ;lalfkjafja ajflkjalfkja llajfla fljalfjalfja;lkjfla flkjalkfj ;alkasjflkajlkfja lfjalkfj;lka jlkajf;lkajflksajflkajflkj;lkjaf;la

22

Bibliography [1] Lee and Bae Keun, Video/Image coding method and system enabling region of interest, International Publication Number WO/2005/069634 A1, Samsung Electronics Co. Ltd., 28th July 2005. [2] Miled and Mohamed Khames Ben Hadj, Region of Interest tracking method and device for wavelet based video coding, International Publication Number WO 2004/044830 A1, Nokia Inc US, 27th May 2004. [3] Bae, et al, Multiple region of interest support in scalable video coding, ETRI Journal Volume 28, Number 2, April 2006.

23