|
|
|
|
There are two types of quality assurance associated with ARCHIE. The first, and least important so far as users are concerned is our own attempts to ensure that the software does what it claims. The more important level is in the hands of the user. We have set up output at various stages in the calculations. That output can be copied into a spreadsheet and used to provide your own confirmation of the processes used. There are limitations on what we have been able to achieve but there is considerable help with achieving Self Assurance.
LimitationsThere are limits to what we can promise about ARCHIE-M. We have made our best endeavours to ensure that it does what we intended. That leaves two potential gaps between the user's expectations and experience: What we intended may not be what the user expects. This is almost an inevitable consequence of writing software. We believe that ARCHIE-M represents the best possible response to the problems posed by first level of assessment of arch bridges. Engineers used to "black box" programs may disagree, but our experience is that most users grow to love archie and multi. We may have failed to achieve what we set out to achieve. That is also an almost inevitable consequence of the endeavour to automate a complex process. The Archie-M program now contains about 30,000 lines of C++ code. The design process was carried through with care but in a program of such length and complexity it is most unlikely that there are no bugs. Despite our efforts at testing, users will quickly find points where the response is clearly wrong or just confusing. Please let us know quickly, preferably by email. If you can give us a set of data and clear instructions on how to get to the point of breakdown, it will help us considerably in our efforts to provide a timely response.
Best EndeavoursWhen we say we will make out best endeavours, we mean exactly that. We do not have unlimited resources of time or money, but we are conscious of the importance users place on the output from our software. We will try to respond quickly to issues which compromise confidence in the program. Where users find that our philosophy or implementation is not to their taste, we will listen to the arguments and consider making changes, but we cannot promise to do so. In the limit, Archie-M stems from deeply held beliefs about the proper nature of engineering software. Those beliefs are unlikely to change radically now, so if you don't agree with our views, you may be better to seek an alternative program.
Price and SizeARCHE-M is a specialist piece of software with a narrow market. The income from it is not such as will support continuous upgrades and modifications. We have a number of plans for developments which will push the predicted capacities, particularly of multi span bridges, further in a favourable direction, without compromising the conservatism of the approach. These developments will take ARCHIE further from immediate compliance with BD21 particularly and so will be available only as extras rather than being built in to the core code of the program.
Self AssuranceSelf assurance is vitally important in the use of engineering software. Users are encouraged to make checks on the validity of the results our program produces. To this end, we have provided a substantial amount of intermediate output data.
Intermediate ResultsIntermediate calculation results are tabulated output presented in a form to ease and encourage checking of the calculations within Archie-M. The data can be copied to the clip-board and pasted into a spreadsheet. From there, it is easy to extend the calculations backwards and forwards to ensure that the results properly correspond to the basic input data. Users are encouraged to make use of this facility AT LEAST ONCE before they come to rely on the output from Archie-M.
CalculationsCheck calculations can be made in a number of ways. The value of Archie-M is in producing a graphical image of thrust quickly. The calculations themselves are not difficult to understand or to carry out, but speed is of the essence. When you come to do checks on Archie-M, a quick hand check can be useful. For example:
Close checks can then be done using a spreadsheet. In this case, it will be possible to do detailed checks of the geometry of the zone of thrust without having to repeat the data preparation and hinge search tasks.
SpreadsheetA sample spreadsheet with some simple check calculations for Bargower bridge appears on the installation disk. The notes attached explain how these figures are derived. Bargower bridges features in the list of test bridges provided, so users can rework this example for themselves.
|
|
Send mail to
web@obvis.com with
questions or comments about this web site. |
