Implementation model: Phase 4

Solution development and conformance and interoperability test

OBJECTIVE: To develop the solution and to check its compliance to eBIZ.
OUTPUT:
  • The solution implementation Specification (technical description of the implemented products/adapters/interfaces).
  • A set of Test Reports collecting the results of the test activities performed in simulated environment.
  • The software solution ready to be released (Release Candidate).
AVAILABLE RESOURCES:
  • a set of Test Plans: a set of Test plans stating the minimal set of actions to do in order to check solution compliance to eBIZ in a Laboratory environment.
  • Test Platform supporting the test activities.
  • Test Report Template TP513-005 : a template useful for reporting and collecting the test activities performed to check the eBIZ based solution.
 
 
Phase 4
Phase 4

 

STEP 1:

Solution development		 This step regards the effective realization of the new solution.
Describing this step is out of the scope of this document.

Expected Outputs:
  • the solution implementation Specification (i.e. the technical description of the implemented products/adapters/interfaces);
  • the software solution ready to be tested.
STEP 2:

Laboratory test		 This step aims to check the compliance of the implemented solution to eBIZ. This should be done performing test activities designed to verify the conformance of the solution and its capacity to interoperate. On this purpose eBIZ provides a Test Bed platform that the adopters can freely use and customise.
The expected actions for this step are:
  1. Test Platform set up, in order to enable the validation against the Use Profiles coming from Phase 3;
  2. execution of the conformance Test Cases provided by the Test Platform for each eBIZ document types coming from Phase 2;
  3. resolution of the detected errors (solution adjustment), if any;
  4. execution of the interoperability Test Cases provided by the Test Platform for each eBIZ document types;
  5. resolution of the detected errors (solution adjustment), if any.

Furthermore, if the Business Scenario requires RFId, during this step the RIFd infrastructure has to be tested (both reader than antennas) and the middleware between the RFId hardware and the eBIZ infrastructure has to be validated. The objective is the verification that information coming from readers are correctly delivered to every partner using eBIZ documents.

Expected Outputs:
  • laboratory Test Reports;
  • the software solution ready to be released (Release Candidate).