01-XML Based Validators Development and Validation Process
Process
Flowchart
01-Requirements
Requirements Process
Objectives
- To identify new validator from standardization bodies
Pre-requisites
Inputs
- Needs of the new validator
- Requirements concerned by the validator
Actions
- Writing needs in specification document or an accessible documentation to be analysed by development team
Outputs
- Specification Documents
- Normative XSD
- Formal requirements
02-Specification
Specification Process
Objectives
- Identify and analyse impact from requirements process outputs
- Identify functionnality and release
- Identify tool impact
Pre-requisites
- Requirements are identified by bodies standardization
Inputs
- Specification Documents
- Normative XSD
Actions
- Analysis specifications documents
- Analysis normative XSD
- Extract requirements of documentation
Outputs
- XML Format Document with requirements to manage linking documentation with test
03-Design
Design Process
Objectives
- Design receive specifications
Pre-requisites
- Specfication Documents are delivered and analysed
Inputs
- XML Format analysed from Specification Process
- Formalized requirements
Actions
- Processing XSD -> UML
- Convert the normative XSD document in a UML model
- OCL Injection
- Include constraints in the model to assure the validation
Outputs
- UML Model
- UML Model + OCL
04-Realisation
Realisation Process
Objectives
- Develop new or existing validator module respecting normatives
Pre-requisites
- Specfication Documents are translated in UML Model with OCL from normatives
Inputs
- UML Model with OCL implemented from Design Process
Actions
- Generating JAVA code from UML Model
- Create unit test from each function/constraint
- Generate documentation of the module
Outputs
- JAVA code
- Unit test JAVA code
- JAVA code documentation of module
05-Test
Test Process
Objectives
- Verify if module respect all rules and specifications
Pre-requisites
Inputs
- JAVA Code
- Validator webservice
- Samples documents
Actions
- Unit Test
- Static analysis
- UT Generation and verification
- System Test
- System testing relative Specifications documents
- Acceptance Test
- Beta testing by vendors relative their needs
Outputs