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.0INTRODUCTION
1.1STATEMENT OF PROBLEM
1.2AIMS AND OBJECTIVES
1.3PURPOSE OF STUDY
1.4SIGNIFICANT OF STUDY
1.5SCOPE/DELIMITATIONS
1.6LIMITATIONS/CONSTRAINTS
1.7ASSUMPTION OF STUDY
1.8DEFINITION OF TERMS
CHAPTER TWO
2.0LITERATURE REVIEW
CHAPTER THREE
3.0DESCRIPTION AND ANALYSIS OF THE EXISTING SYSTEM
3.1FACT-FINDING METHOD/ METHODOLOGY
3.2ORGANIZATIONAL STRUCTURE/ORGANOGRAM
3.3OBJECTIVES OF THE EXISTING SYSTEM
3.4INPUT, PROCESS, AND OUTPUT ANALYSIS
3.4.1INPUT ANALYSIS
3.4.2PROCESS ANALYSIS
3.4.3OUTPUT ANALYSIS
3.5INFORMATION FLOW DIAGRAM
3.6PROBLEMS OF THE EXISTING SYSTEM
3.7JUSTIFICATION OF THE NEW SYSTEM
CHAPTER FOUR
4.0DESIGN OF THE NEW SYSTEM
4.1DESIGN STANDARD
4.2OUTPUT SPECIFICATION AND DESIGN
4.3INPUT SPECIFICATION AND DESIGN
4.3.1FILE DESIGN
4.4PROCEDURE CHART
4.5SYSTEMS FLOWCHART
4.6SYSTEM REQUIREMENTS
4.6.1HARDWARE REQUIREMENTS
4.6.2SOFTWARE REQUIREMENTS
4.6.3OPERATIONAL REQUIREMENTS
4.6.4PERSONNEL REQUIREMENTS
CHAPTER FIVE
5.0IMPLEMENTATION
5.1DESIGN STANDARD
5.2PROGRAM DESIGN
5.2.1PROGRAM FLOWCHART
5.2.2PSEUDO CODE
5.3CODING
5.4TEST DATA/TEST RUN
5.5USER TRAINING – AN OVERVIEW
5.6CUTOVER PROCESS
CHAPTER SIX
6.0DOCUMENTATION
6.1THE USER DOCUMENTATION
6.2THE PROGRAMMER DOCUMENTATION
CHAPTER SEVEN
7.0RECOMMENDATIONS, SUMMARY AND CONCLUSION
7.1RECOMMENDATION
7.2SUMMARY
7.3CONCLUSION
REFERENCES
BIBLIOGRAPHY
APPENDIX
SOURCE LISTING
LIST OF FIGURES
