Différences entre les versions de « DataFlowGenerator »
toross>WikiAdmin m (1 révision importée) |
m (1 version importée : dfg) |
(Aucune différence)
| |
Version actuelle datée du 24 juillet 2026 à 19:08
|
1 Data Flow Generator V1
- Version de développement : Les versions de DataFlowGenerator
|
2 Data Flow Generator V0
3 Les versions de DataFlowGenerator
4 Versionnement
4.1 Application versioning
- R-V1.V2.V3.V4
- The identification consists of:
- R (release) xn pre-alpha alpha beta gamma/rcn prod/gold/live_release
- The release is the qualification of software distribution or delivery often as a file or set of files, called a package. Here are the qualifications in the logical order of software development project (http://en.wikipedia.org/wiki/Software_testing):
- xn or x1,x2, ...
- delivery made during the development after unit tests. Distribution can be used between development teams who do not share the same basic sources;
- pre-alpha or rpa
- delivery made before the end of development and after integration tests. Distribution can be used between development integration testing teams;
- alpha or ra
- delivery made to the test team for System tests;
- beta or rb
- delivery made to a small number of users for User Acceptance Tests(UAT);
- gamma_n or rcn
- delivery also called "Release Candidate" number n, after nth UAT;
- prod, gold, ou lr (live release)
- delivery called "live release" which is considered to be very stable and relatively bug-free with a quality suitable for wide distribution and use by end users (http://en.wikipedia.org/wiki/Software_release_life_cycle).
- V1
- a number that indicates the evolution of the system architecture and/or a large number of functional changes;
- V2
- a number that indicates the evolution of the functions provided by the application;
- V3
- a number that indicates the evolution of implementations of functions;
- V4
- a number, optional, which indicates the integration of bugfixes.
- R (release) xn pre-alpha alpha beta gamma/rcn prod/gold/live_release
4.2 Grammar/File Format versioning
- grV1.grV2.grV3 / flV1.flV2.flV3
- xxV1 changes that can not keep backward compatibility when reading
- xxV2 developments that maintain backward compatibility when reading
- xxV3 changes such as additions, comments or additional support in the grammar that have no impact on reading
Le format du fichier et le modèle définit par le fichier même, cette version est celle du modèle.
4.3 Driver versioning (python or c++)
- For each grammar main version number, which is grV1, a new driver versioning starts.
- drV1.drV2.drV3
- drV1 major modifications
- drV2 minor modifications
- drV3 bug corrections
5 Scripts d'utilisation
#!/bin/bash
cafile=~/scratch/change/doc/certificat/cacert.cer
if [ -f $cafile ] ; then
echo ""
else
cafile=~/cacert.cer
fi ;
rm -Rf ./generated/*
python ~/scratch/svnDvlp/dfg1/dfg_V1PythonGenDriver.py \
--pathGrammarfile doc/dvlp/spec/fileModel/graphGenFileModel.xml \
--dataName graphGenhFile \
--cartridgeFile tool/data/cartridge.txt \
--licenceFile tool/data/licence.txt \
--driverVersion "0.0.0" \
--fileformatVersion "0.0.0" \
--pathGen modFileDrv/api/impl
#!/bin/bash
cafile=~/scratch/change/doc/certificat/cacert.cer
if [ -f $cafile ] ; then
echo ""
else
cafile=~/cacert.cer
fi ;
rm -Rf ./generated/*
python ~/scratch/svnDvlp/dfg1/dfg_V1PythonGenDriver.py \
--pathGrammarfile doc/dvlp/spec/fileModel/calibrationModel.xml \
--dataName calibrationConfig \
--cartridgeFile tool/data/cartridge.txt \
--licenceFile tool/data/licence.txt \
--driverVersion 0.0.0 \
--fileformatVersion 0.0.0 \
--pathGen modFileDrv/api/impl
