Finance Focus Lev Lesokhin Ian Felice
Executive Vice President Strategy and Market Development, CAST
Partner- Hassans & CEO- Line Management Services Limited 57/63 Line Wall Road, Gibraltar
Tel - +(350) 200 79000 Fax - +(350) 200 71966 Email -
ian.felice@hassans.gi Website -
www.gibraltarlaw.com
Financial Services and Glitches- more to come
The glitch at RBS earlier this year left customers unable to pay their bills or move money around, causing considerable damage to the bank’s reputation, not to mention the £125m for compensation and £80m on an IT overhaul – resulting in a £205m bill for the bank. So what has been done by other financial institutions to ensure this does not happen again? Nothing. In fact in the period since then we have seen high profile outages at the NASDAQ – forcing the cancellation of trades, BATS – halting Apple’s share trading, and Knight Capital’s algorithmic glitch – costing the firm $440m. So why is so little being done to address the underlying technology issues which cause these problems?
S
oftware has long been integral to running core business functions, and is getting more complex every day, meaning we are going to continue to see more of these high profile outages.
This is an industry where microseconds can be the difference between winner and watchers, so to remain competitive requires constant upgrading of software capabilities. There is an arms race for speed among the major financial centres and exchanges worldwide which makes new software rollout decisions risker, as quality becomes a secondary issue.
The result is software development is often stretched to its limits to satisfy these demands and the pressure to cut corners and meet the ever increasing ‘need for speed’ is one cause of the damaging, costly, and nowadays, high profile failures in financial systems.
The tragedy is most, if not all, of these issues can be avoided by introducing code quality management processes. Software is complex, and getting more so, inevitably the factors which lead to these problems lie chiefly in a lack of insight into the application as a whole. For developers dealing with systems which have been added to, cropped, and changed over the years, it is often a struggle simply to understand the ‘ins’ and ‘outs’ of the whole system.
For example the glitch at Knight Capital occurred when the company updated its
112
www.finance-monthly.com
software. Most IT applications have dead code which is lying dormant in systems because none of the live modules are using it. The update brought some dead code back to life, causing the system to spit out wrong trades. If a company has no structural oversight of their systems then they cannot know when new updates might suddenly start calling on dead code.
An upgrade like the one which caused the RBS glitch, should not have been run without proper analysis of what was being added, especially on a system as interlinked as those which deal with bank payments. The real problem is many organisations have no kind of measurement procedures in place to guide management on the risks in an application. Without hard software risk measures it is often difficult for an IT executive to stand in the way of a determined CEO who wants to roll out similar applications to the competition. This is particularly difficult in consumer finance services where there is so much pressure to move towards mobile applications and to create new offers constantly.
However with so much information spread across systems it becomes increasingly difficult to create stable applications and problems begin to pile up on top of each other. Even more worrying is IT departments are often largely unaware of these problems, only becoming aware of them when a user complains about the performance. With so many companies in a
rush to out-innovate the competition and add new features, the quality of the code underneath it all gets quickly forgotten.
Of course, no organisation can remove all the defects in its software before it is rolled out. The problem now is many do not do enough analysis to make strategic decisions about which defects present the most serious risks to operations.
If financial institutions are going to stem the flood of costly failures, they must sacrifice some speed for quality software engineering and adopt at least the minimum quality practices to reduce business risk. Put another way, IT executives cannot leave structural quality to chance, or delegate responsibility to their minions of programmers – they must manage structural software risk top-down.
In the meantime no doubt there will be more outages, many of which will make the headlines, cause consumers more disruption and damage brand reputations. We should take the failures to date as a wake-up call to look at our own development and testing practices, and ask ourselves if our teams are doing all they can to ensure the utmost quality, performance and reliability.
Lev Lesokhin is Executive Vice President for Strategy and Marketing at CAST, providers of Software Analysis and Measurement solutions
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120 |
Page 121 |
Page 122 |
Page 123 |
Page 124 |
Page 125 |
Page 126 |
Page 127 |
Page 128 |
Page 129 |
Page 130 |
Page 131 |
Page 132 |
Page 133 |
Page 134