ABSTRACT

In software engineering, performance testing is testing that is performed, to determine how fast some aspect of a system performs under a particular workload. It can also serve to validate and verify other quality attributes of the system, such as scalability, reliability and resource usage. Performance testing is a subset of Performance engineering, an emerging computer science practice which strives to build performance into the design and architecture of a system, prior to the onset of actual coding effort

In recent years, Web applications have grown so quickly that they have already become crucial to the success of businesses. However, since they are built on Internet and open standard technologies, Web applications bring new challenges to researchers, such as dynamic behaviors, heterogeneous representations, novel control flow and data flow mechanisms, etc. In this paper, we propose an agent-based approach for Web application testing. While the agent-based framework greatly reduces the complexity of Web applications, a four-level dataflow test approach can be employed to perform structure testing on them. In this approach, data flow analysis is performed as function level testing, function cluster level testing, object level testing, and Web application level testing, from low abstract level to high abstract level. Each test agent in the framework takes charge of the testing in an abstract level for a particular type of Web document or object.

ORGANIZATION OF WORK

This project work is primarily designed to give an insight to Web test tool application design and measure performance.

Chapter one talks about introduction to Web test tool application design and measure performance, study of problem and objectives as well as definition of the scope.

Chapter two comprises the literature review. Chapter three gives the detailed information about the existing (old) system, while chapter four and five deals with the design and implantation of new system.

Chapter six documents the project work, while chapter seven summaries, conclusion and suggestions were made.

                    

                     TABLE OF CONTENT

TITLE PAGE                                                              

CERTIFICATION                                                 

APPROVAL                                                        

DEDICATION                                                             

ACKNOWLEDGEMENT                                         

ABSTRACT                                                        

ORGANIZATION OF WORK                                          

TABLE OF CONTENT                                                   

CHAPTER ONE

1.0    INTRODUCTION                                        

1.1    STATEMENT OF PROBLEM                                  

1.2    AIMS AND OBJECTIVES                                      

1.3    PURPOSE OF STUDY                                          

1.4    SIGNIFICANT OF STUDY                                     

1.5    SCOPE/DELIMITATIONS                                     

1.6    LIMITATIONS/CONSTRAINTS                              

1.7    ASSUMPTION OF STUDY                                    

1.8    DEFINITION OF TERMS                                      

CHAPTER TWO

2.0    LITERATURE REVIEW                                         

CHAPTER THREE

3.0    DESCRIPTION AND ANALYSIS OF THE EXISTING SYSTEM      

3.1    FACT-FINDING METHOD/ METHODOLOGY            

3.2    ORGANIZATIONAL STRUCTURE/ORGANOGRAM     

3.3    OBJECTIVES OF THE EXISTING SYSTEM              

3.4    INPUT, PROCESS, AND OUTPUT ANALYSIS   

3.4.1 INPUT ANALYSIS                                               

3.4.2 PROCESS ANALYSIS                                   

3.4.3 OUTPUT ANALYSIS                                            

3.5    INFORMATION FLOW DIAGRAM                          

3.6    PROBLEMS OF THE EXISTING SYSTEM                

3.7    JUSTIFICATION OF THE NEW SYSTEM         

CHAPTER FOUR

4.0    DESIGN OF THE NEW SYSTEM                            

4.1    DESIGN STANDARD                                           

4.2    OUTPUT SPECIFICATION AND DESIGN                 

4.3    INPUT SPECIFICATION AND DESIGN                   

4.3.1 FILE DESIGN                                                     

4.4    PROCEDURE CHART                                           

4.5    SYSTEMS FLOWCHART                                               

4.6    SYSTEM REQUIREMENTS                                   

4.6.1 HARDWARE REQUIREMENTS                                      

4.6.2 SOFTWARE REQUIREMENTS                                       

4.6.3 OPERATIONAL REQUIREMENTS                           

4.6.4 PERSONNEL REQUIREMENTS                              

CHAPTER FIVE

5.0    IMPLEMENTATION                                             

5.1    DESIGN STANDARD                                           

5.2    PROGRAM DESIGN                                            

5.2.1 PROGRAM FLOWCHART                                      

5.2.2 PSEUDO CODE                                                  

5.3    CODING                                                           

5.4    TEST DATA/TEST RUN                                       

5.5    USER TRAINING – AN OVERVIEW                        

5.6    CUTOVER PROCESS                                           

CHAPTER SIX

6.0    DOCUMENTATION                             

6.1    THE USER DOCUMENTATION                              

6.2    THE PROGRAMMER DOCUMENTATION                 

CHAPTER SEVEN 7.0    RECOMMENDATIONS, SUMMARY AND CONCLUSION

7.1    RECOMMENDATION                                           

7.2    SUMMARY                                                         

7.3    CONCLUSION                                                    

REFERENCES                                                            

BIBLIOGRAPHY

APPENDIX                                                                

SOURCE LISTING                                                       

LIST OF FIGURES                                                      

CHAPTER ONE

1.0    INTRODUCTION

In recent years, Web applications (WAs) have grown so quickly that they have already become crucial to the success of businesses. However, since they are built on Internet and open standard technologies, WAs possess their own unique features, such as dynamic behaviors, heterogeneous representations, and novel data handling mechanisms. These features provide concrete support to the success of WAs, but they bring new challenges to researchers and developers, especially in regard to testing WAs and ensuring their quality. Testing approaches for non-WAs have to be extended to handle these features before they are used in WA testing. This paper presents an agent-based approach to perform data-flow testing of WAs. More precisely, the data-flow testing will be performed by autonomous test agents at the method level, object level, and object cluster level, from low abstraction level to high abstraction level. In the process of the recommended data-flow testing, an agent-based WA testing system (WAT) will automatically generate and coordinate test agents to decompose the task of testing an entire WA into a set of subtasks that can be accomplished by test agents. The test agents, rooted in the Belief-Desire-Intention (BDI) model, cooperate with each other to complete the testing of a WA. An example is used to show the feasibility of the proposed approach.

1.1    BACKGROUND OF STUDY

Kia Motors is South Korea's second largest automobile manufacturer, having sold over 1.6 million cars in 2009.[2]

The word Kia derives from Korean words meaning “to arise to the world from Asia.”

South Korea's oldest car company, Kia was founded on June 9, 1944 as a manufacturer of steel tubing and bicycle parts by hand — and has operated as one of the country's Chaebols since. In 1952, Kia changed its name from Kyungsung Precision Industry,[9] and later built motorcycles (starting in 1957), trucks (1962) and cars (1974). The company opened its first integrated automotive assembly plant in 1973, the Sohari Plant. Starting in 1986, in partnership with Ford, Kia produced several Mazda derived vehicles for both domestic sales in South Korea into other countries. These models include the Pride (based on the Mazda 121) and Avella, which were sold in North Americand Australasia as the Ford Festiva and Ford Aspire.

In 1992, Kia Motors America was incorporated in the United States. The first Kia-branded vehicles in the United States were sold from four dealerships in Portland, Oregon in February 1994. Since then, Kia expanded methodically one region at a time. Dealers in 1994 sold the Sephia, and a few years later the United States line expanded with the addition of the Sportage.

However, Kia's bankruptcy in 1997, part of the Asian financial crisis, resulted in 51% of the company being acquired in 1998 by South Korean rival Hyundai Motor Company, outbidding Ford Motor Company which had owned an interest in Kia Motors since 1986.[10] Subsequently, however, Hyundai has divested some of its ownership of Kia Motors,[11] and currently Hyundai Motor Company owns less than 40% of the company.

In October 2006, Kia Motors America broke ground for Kia Motors Manufacturing Georgia in West Point, Georgia, representing a $1 billion USD investment for the company.[12] Kia Motors Manufacturing Georgia opened in February, 2010. For 2009, KMA recorded its 15th consecutive year of increased U.S. market share.

1.2    STATEMENT OF PROBLEM

Owing to:

(i)          The difficulties people face in locating a web application workshop.

(ii)         Urgent need to contact a web application workshop at emergency time.

(iii)        Improper management of information/data in a web application workshop.

(iv)       Difficulties people encountered when ordering for web application workshop tools/equipment.

(v)        Time wasted in contacting a web application workshop.

The need arise for the development of Web test tool application design and measure performance.

1.3    AIMS AND OBJECTIVES

The aims and objectives of this project are listed below:

·        To develop software called Web test tool application design and measure performance that will replace the manual method of processing information.

·        To develop, promote, and provide adequate and efficiently coordinated web application workshop services at reasonable rates.

·        To maintain an efficient system of collection, sorting and delivery of web application workshop fault and solution.

·        To demonstrate increased motivation to the KIAMOTORS workers.

·        To provide a means of contacting web application workshops at any given time.

·        To eliminate the error involved with the manual method of processing data/information in a web application workshop.

·        To save the time wasted with manual method of processing data/information and items.

·        To establish and maintain web application workshop services.

1.4    PURPOSE OF STUDY

The main purpose of this study is to put to an end the difficulties people encountered in a web application workshop. This is actualized by Web test tool application design and measure performance which is user friendly and interactive. By the time this software is designed and implemented, the difficulties encountered with manual method of contacting and receiving information will be eliminated.

1.5    SIGNIFICANCE OF STUDY

With the growth in information technology, the study offers numerous benefits to the KIAMOTORS and to any organization that deals on data/information.

Manual method of process will no longer be there again because information will be stored on the computer with the help of the AGENT BASED TESTING FOR WEB APPLICATION.

Because of the easy to use nature of Web test tool application design and measure performance, any organization can easily develop it to make use of it.

1.6    SCOPE/DELIMITATION

This project work is narrowed to KIAMOTORS Enugu. It deals with the development of Web test tool application design and measure performance to help in the transferring of data/information and web application workshop tools.

1.7    LIMITATION/CONSTRAINTS

Owing to the scope of this project work as stated above, this project work is limited to Web test tool application design and measure performance, KIAMOTORS Enugu.

It is important to mention here that time was a major constraint in the course of fact finding. It is also wise to mention here that some information we need to work with was not collected because of the unwillingness of the staff to review such information.

1.8    ASSUMPTION OF STUDY

One of the major assumptions made in this project work is that manual methods of contacting and receiving data/information and tools from web application workshop are ineffective, time wasting, prone to error and high level of energy dissipation.

---

---