Book contents
- Frontmatter
- Contents
- Foreword by Bob Bartlett
- Acknowledgments
- 1 Introduction
- PART 1 REVIEW OF OLD-SCHOOL AND AGILE APPROACHES
- PART 2 EVERYONE IS DIFFERENT: AGILE CASE STUDIES
- 4 From Waterfall to Evolutionary Development and Test
- 5 How to Test a System That Is Never Finished
- 6 Implementing an Agile Testing Approach
- 7 Agile Testing in a Remote or Virtual Desktop Environment
- 8 Testing a Derivatives Trading System in an Uncooperative Environment
- 9 A Mixed Approach to System Development and Testing: Parallel Agile and Waterfall Approach Streams within a Single Project
- 10 Agile Migration and Testing of a Large-Scale Financial System
- 11 Agile Testing with Mock Objects: A CAST-Based Approach
- 12 Agile Testing – Learning from Your Own Mistakes
- 13 Agile: The Emperor's New Test Plan?
- 14 The Power of Continuous Integration Builds and Agile Development
- 15 The Payoffs and Perils of Offshored Agile Projects
- 16 The Basic Rules of Quality and Management Still Apply to Agile
- 17 Test-Infecting a Development Team
- 18 Agile Success Through Test Automation: An eXtreme Approach
- 19 Talking, Saying, and Listening: Communication in Agile Teams
- 20 Very-Small-Scale Agile Development and Testing of a Wiki
- 21 Agile Special Tactics: SOA Projects
- 22 The Agile Test-Driven Methodology Experiment
- 23 When Is a Scrum Not a Scrum?
- PART 3 AGILE MY WAY: A PROPOSAL FOR YOUR OWN AGILE TEST PROCESS
- APPENDIX A The Principles of Rapid Application Development
- APPENDIX B The Rules and Practices of Extreme Programming
- Appendix C The Principles of the Dynamic Systems Development Method
- Appendix D The Practices of Scrum
- APPENDIX E Agile Test Script Template
- Appendix F Agile Test Result Record Form Template
- Appendix G Agile Test Summary Report Template
- Appendix H My Agile Process Checklist
- References
- Index
8 - Testing a Derivatives Trading System in an Uncooperative Environment
Published online by Cambridge University Press: 26 October 2009
- Frontmatter
- Contents
- Foreword by Bob Bartlett
- Acknowledgments
- 1 Introduction
- PART 1 REVIEW OF OLD-SCHOOL AND AGILE APPROACHES
- PART 2 EVERYONE IS DIFFERENT: AGILE CASE STUDIES
- 4 From Waterfall to Evolutionary Development and Test
- 5 How to Test a System That Is Never Finished
- 6 Implementing an Agile Testing Approach
- 7 Agile Testing in a Remote or Virtual Desktop Environment
- 8 Testing a Derivatives Trading System in an Uncooperative Environment
- 9 A Mixed Approach to System Development and Testing: Parallel Agile and Waterfall Approach Streams within a Single Project
- 10 Agile Migration and Testing of a Large-Scale Financial System
- 11 Agile Testing with Mock Objects: A CAST-Based Approach
- 12 Agile Testing – Learning from Your Own Mistakes
- 13 Agile: The Emperor's New Test Plan?
- 14 The Power of Continuous Integration Builds and Agile Development
- 15 The Payoffs and Perils of Offshored Agile Projects
- 16 The Basic Rules of Quality and Management Still Apply to Agile
- 17 Test-Infecting a Development Team
- 18 Agile Success Through Test Automation: An eXtreme Approach
- 19 Talking, Saying, and Listening: Communication in Agile Teams
- 20 Very-Small-Scale Agile Development and Testing of a Wiki
- 21 Agile Special Tactics: SOA Projects
- 22 The Agile Test-Driven Methodology Experiment
- 23 When Is a Scrum Not a Scrum?
- PART 3 AGILE MY WAY: A PROPOSAL FOR YOUR OWN AGILE TEST PROCESS
- APPENDIX A The Principles of Rapid Application Development
- APPENDIX B The Rules and Practices of Extreme Programming
- Appendix C The Principles of the Dynamic Systems Development Method
- Appendix D The Practices of Scrum
- APPENDIX E Agile Test Script Template
- Appendix F Agile Test Result Record Form Template
- Appendix G Agile Test Summary Report Template
- Appendix H My Agile Process Checklist
- References
- Index
Summary
SYNOPSIS
This case study describes a project where our team was contracted to assist the resolution of quality issues in a commercially critical derivatives trading system and the challenges imposed by the demanding development environment in a financial institution.
After reviewing the testing requirements, the timescales and budget, and the difficult nature of the development environment, an agile testing approach was selected. This case study covers the selection process for the use of and the results obtained from using an agile approach.
Introduction
My name is Nick Denning and at the time of this case study I was the managing director of Strategic Thought Limited, a company I founded in 1987, which we subsequently floated on AIM in 2005 and which now specializes in the development and sale of financial risk management products. At the time the events in this case study took place, we were an IT consultancy with a strong reputation for work in the Ingres Relational Database Management System arena. A particular strength of ours was to be able to analyze systems, identify performance issues, and make changes to the database configuration, the database structures, and the SQL code within the application.
Making changes to mission-critical applications, sometimes directly on the production environment, required a careful consideration of the implications for a change, and the ability to assess the risks and agree with a customer on the risk reward profile to justify implementing changes that bypassed the conventional release procedures.
- Type
- Chapter
- Information
- Agile TestingHow to Succeed in an Extreme Testing Environment, pp. 53 - 61Publisher: Cambridge University PressPrint publication year: 2009