1. Reminder of the principles of document management#

The Validation Manual contains code validation documentation. The validation sheets it contains make it possible to specify the guaranteed field of use and to give confidence in the use of the code. They are an illustration of the use of the various modeling options and are an essential complement to learning how to calculate structures.

1.1. Identification of the fascicles of the validation and codification manual#

Each issue is identified by a key written on all pages. This key allows the progressive management of documentation as it is written.

The manual is subdivided into ten parts. The parts of the manual are materialized by cardboard dividers, delivered with the binder. They are numbered from 0 to 9.

The parts of the manual consist of fascicles, software notes under A.Q. that respect the rules for presenting D.E.R. technical notes (HI notes, HP,…); a note can contain one or more fascicles. Each part of the manual can apparently contain one hundred fascicles. Each fascicle is identified by a fascicle number between 00 and 99.

A fascicle can be divided, as required, into documents numbered starting with 0.

Key: Manual_partie.fascicle_number [.document_number]

V1.01

Validation Manual/Validation Organization/

V3.04.004

Validation Manual/Linear Mechanics/ Linear statics of solid structures/SSLV004

Each validation test is associated with a coded reference that is specific to it (see attached table).

This codification, taken from guide VPCS, is composed of eight alphanumeric characters:

  • takes into account the type of problem treated by the test (4 alphabetic characters),

  • the order number of the test in the list of tests of the same type (2 or 3 numerical characters).

The four alphabetic characters indicate in order:

1st

character

:

the field of application,

2nd

character

:

the type of analysis,

3rd

character

:

the type of behavior,

4th

character

:

the type of model.

Example: SDLA04 will be the 4th SDLA type test

Document numbers between 01 and 99 correspond to tests from guide VPCS.

The numbers between 100 and 299 correspond to the tests offered by the developers.

The numbers between 300 and 399 are reserved for tests resulting from the independent validation of version 3, between 400 and 499 for that of version 4,… For tests resulting from independent validation, only those included in the Code_Aster non-regression list are documented in the Validation Manual.

Several models can be associated with a test. Each model is also subject to its own codification, which is composed of eight characters. The first six or seven consist of the coded reference of the test, the last character indicates the order number of the modeling in the list of models associated with the test.

By convention, the numbers will be taken in the following order:

A, B, C,…, Y, Z

Example:

SDLA04C will be the codification relating to the 3rd modeling studied in test SDLA04.

If only one model is studied in a test, it will be indexed A.

Exam: SDLA04A, SSLV101A.

By convention, tests YYYY are performance tests and tests ZZZZ are tests to validate computer functionalities. Other names that do not correspond to the nomenclature exist. These tests are generally linked to business tools.

Coding of validation forms: 7 characters

1

2

3

4

5 6 7

Domain of application

Analysis type

Type of behavior

Model type

Order Number

S Structural mechanics

S Static

L Linear

D Discreet

01 to 999

T Thermal

D Dynamic

N Nonlinear

L Linear (beam)

H Thermo-mechanics

P Stationary

C Nonlinear boundary condition

S Surface (shell plate)

F Fluids

T Transitional

P Blueprint (2D)

A Acoustics

H Harmonic

A Axi-symmetric

W Porous Medium

Z Fatigue

V Volumic (3D)

W Metallurgy

X Mixed model

1.2. Responsibilities associated with documentation#

Each fascicle or document is identified, on each page, by several pieces of information, in addition to the classification key:

  • a title, truncated if it is too long,

  • the date of publication,

  • the name of the responsible author,

  • the page number, followed by the total number of pages,

  • the revision number of the document, which reflects changes in the documentation,

  • the version and, possibly, sub-version number of the code for which the fascicle or document applies:

  • default, documentation valid for the development version,

  • 9.5 documentation valid for version 9.5.