advanced structural and pipework analysis

Program Verification  

The program has been validated against analytical solutions, analysis solutions in the public domain and other software packages. 


Included in Section 11 of the Help are a range of validation examples. The inclusion of these examples demonstrates some of the analysis features of FS2000 and also provides evidence of program verification.  These examples may be recreated by a new user to verify their understanding of the operation of the program.   Sample solution extracts for each of the models are given so that the user may check their solution.  Also given for validation purposes are solutions from either analytical solutions or computer based solutions from other software.


A verification document(pdf) can be found in the Examples/Verification folder. The installation includes the MOD files of these verification models. The verification pdf can be accessed using the following links.

View Verification PDF

Download Verification PDF

It is important that the end user verifies their understanding of the operation of the program as well as the analytical correctness of the solutions.  AES consider that some verification documentation should be created by the user to suit their particular analysis requirements and over their range of application.  This is a task that should be done by any user during the initial familiarisation process. The above mentioned examples or the verification document may assist in this.


If any user has specific requirements for verification documentation/examples then AES will consider the provision of such.

 

Program Development

During the development of the program modules of FS2000 every effort has been made to ensure the correctness of any analysis results.  The quality system adopted during program development is that all program developments are thoroughly verified through worked examples. This verification is generally based on small models for which analytical solutions are available or computer based solution using other software packages.


Ongoing program verification following program modification and maintenance is accomplished using a number of benchmark models. These models are re-analysed and their results are compared with results from previous versions of the programs.