Design And Implementation Of Web Test Tool Application Design And Measure Performance

(case Study Of Kia Motors Enugu)

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.

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