[./depot_contenupag.html]
[./depot_contenu_uspag.html]
On-the-spot deposit content validation Suggestions on improvement of the form and actual content. See: What should be deposited? If time permits, the ideal approach is to perform, at the Depositor's offices and with its competent engineering staff, on a reformatted machine, optionally previously installed with its operating system, the following verifications: a Inventory of the deposit and description of its content and structure (tree of the repositories and files) a Reinstallation of the specified development and packaging environment according to the deposited procedure and from the original CD-ROM or back-up of the downloaded external components, a Installation of the previously prepared "deposit" pursuant to the deposited installation, build and deployment procedures, in order to produce a deliverable version from nothing but the deposited elements. It is the only way to validate that the deposit will function as a Crash Recovery back up and that it will constitute solid evidence of the technical state of the IT asset and its ownership. This evidence is necessary in case of any litigation, regulating authority investigation, or other liabilities. a Deployment (flashing or embedding) of the deliverable version in a test or deployed environment, using deposited deployment scripts and/or procedures, a If applicable, creation of a new database via execution of the relevant creation, parameterization and data population scripts, a Basic verification of this deployed application. The most efficient verification would be done by the End User as he/she best knows the expected functionalities and behaviour of the software. a Verification of the content, version and organization of the deposited internal and End User documentation. Remark: LOGITAS will also ask the Depositor to make a security copy of the entire development and packaging environment he is using under licence. Such back up should be stored in a different geographic location. These security copies could be used to reinstall the development environment and consequently their readability should be checked. LOGITAS can of course perform these verifications however it is the Depositor's decision, based on his or his customer's priorities, as to whether LOGITAS performs all, some or none of the verification. However the ultimate goal remains the creation of a well defined and complete software asset that can exist independently of the original designers and developers. The LOGITAS Escrow System allows the End User, under explicit and formal Depositor authorization, to receive from LOGITAS a copy of the deliverable version built from the deposited material for deployment in his test or deployment environment. The End User may attend the verification, again under the formal and explicit Depositor authorization.
[mailto:contact@logitas.com]
[./equipe_uspag.html]
Contact : +33 (0)1 45 607 678 contact@logitas.com Our cell phones
[./telechargement_uspag.html]
Download PDF documentation
[./telechargement_uspag.html]
[./accueil_uspag.html]
[./accueilpag.html]
[./accueil_uspag.html]
[./equipe_uspag.html]
[./references_utilisateurs_uspag.html]
[./references_editeurs_uspag.html]
[./societe_uspag.html]
[./sys_def_uspag.html]
[./tarifs_uspag.html]
[./sys_cont_abo_uspag.html]
[./sys_contrats_uspag.html]
[./systeme_contractuel_uspag.html]
[./assistance_contractuelle_uspag.html]
[./sys_remise_dep_uspag.html]
[./dep_intermediaire_uspag.html]
[./dep_conserv_uspag.html]
[./dep_controle_uspag.html]
[./depot_contenu_uspag.html]
[./dep_conseil_uspag.html]
[./synthesedemarche_uspag.html]
[./qualite_uspag.html]
[./respon_civile_uspag.html]
[./valo_patrimoine_uspag.html]
[./protection_patrimoine_uspag.html]
[./protection_client_uspag.html]
[./enjeux_uspag.html]
[https://www.logitas.com/php/upload.php5]
[https://www.logitas.com/php/files.php5]
[https://www.logitas.com/php/files.php5]
[./accueil_uspag.html]
[Web Creator] [LMSOFT]