Automated Spreadsheet Development Originally titled: There will be a better way...

Of doing what ? Creating large stand-alone spreadsheets, designed to support decision making And then using them in the run-up to the decision And, as appropriate, thereafter

Bee in my bonnet for twelve years! Was doodling my first attempt to write a spreadsheet generator in 1998 Then met BRIXX, who appeared at first sight to have the answer, even though, initially anyway, BRIXX did not generate a spreadsheet, as well as being opaque Spreadsheets are hugely powerful, but untamed, they are also hugely dangerous The effort has been all about taming spreadsheets

Stop : Drafting straight into a Workbook Putting the parameters in first Drafting the spreadsheet in one big lump Maintaining version control just on the whole Documenting just the whole (better than many people manage, but even that can be bettered!) Just keeping a record of who has last checked that the whole spreadsheet is right

Instead, start : Drafting into a specification of the spreadsheet Leaving the parameters until the end Drafting the individual pieces separately Maintaining version control on each piece Documenting each piece Keeping records of who last checked each piece

Then, Generate the spreadsheet from its specification, whenever required Assess whether it fills the bill Assess the results it shows Then throw it away! (My way, you can get it back if you need to) If unhappy with what you saw, change the specifications (not the spreadsheet) Otherwise, just continue to develop

That way Instead of looking at 1 MB of Excel file, called version 65, stamped as most recently changed last week but as having been created five years ago, of which you know that bits will not have been looked at for five years (but not of course, which bits) You will be looking at c. 200 KB of text file, stamped as having been created yesterday and as having never been changed, also called Version 65, and you will be able see when each bit of it was last changed, and furthermore, which bits if any have been changed since they were last checked

My way, The pieces, and the whole, evolve, version by version Each piece, as well as the whole, is documented –With a general note –With text for a data book –With a status report – “OK”, “Warning” or “Failure” –And with an Audit Trail

The Audit Trail Enables you –To look up how Version x was reached from the previous Version as which it had been saved

Will there be a better way ? I could have called the paper: “There should be a better way” –I hope with EuSPRIG as an audience that would not have been much of a challenge “There could be a better way” –And I seriously hope I am beginning to persuade some of you that this is true and that this is it But will there be a better way” ??

Looking for My objective is to give life to the ideas behind this system Hence my wish to broadcast those ideas In order to give life to Ringtail itself, seeking a partner –Who is convinced in principle about the merits of the approach –And who wishes to try using it in house with a view: Initially, to acquiring at minimal cost and risk a tool which he will find hugely useful And ultimately, if all goes well, to publishing it, profitably, to a wider audience

How far has it got ? RingtailXL is effectively ready to go forward to “in house” use now It requires only a very few final tweaks, which need the input of the potential user Almost immediately, it will prove useful But at the same time, it will be undergoing Beta testing – the system is pretty complete and pretty robust, but it is a new computer programme, and furthermore, one written over an extended period by a single, self taught, individual, so inevitably there will be glitches Before going wider, user documentation needs writing

So, if anybody : Is interested –in a closer look –In discussing how they might become involved Or knows another organisation which might have such an interest, please grab me and lets talk

Angus Dunn (44) (0) (44) (0)