Daidalos Integration Framework TridentCom 2007
•Télécharger en tant que PPT, PDF•
1 j'aime•617 vues
Presentation of the paper by F. Cleary Grant, M. Ponce de Leon, Marta GARCÍA MORENO, Antonio ROMERO VICENTE, Mark Roddy, Czeslaw Jedrzejek, Daidalos Framework for Successful Testbed Integration, Tridentcom 2007, May 2007
![Daidalos WP5 ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
Similaire à Daidalos Integration Framework TridentCom 2007
Similaire à Daidalos Integration Framework TridentCom 2007 (20)
Plus de Miguel Ponce de Leon @ TSSG / Waterford Institute of Technology
Plus de Miguel Ponce de Leon @ TSSG / Waterford Institute of Technology (20)
Dernier
Dernier (20)
Daidalos Integration Framework TridentCom 2007
- 1. Daidalos Framework for successful Testbed Integration Frances Cleary Grant Miguel Ponce de Leon TSSG – Waterford Institute of Technology Ireland
- 3. Nidaros Scenario WP2 Innovations WP3 Innovations WP4 Innovations The Integration of WP innovations were completed through the selected ‘Nidaros’ Scenario.
Notes de l'éditeur
- With the Daidalos Architecture consisting of 3 technical work packages WP2 “ Network Integration” WP3 “Service and Network Management” WP4 “ Pervasive Systems” WP5 “Integrated System Evaluation” aim was to materialise the achievements of work packages into practical assessment to allow for concept validation.
- With the Daidalos Architecture consisting of 3 technical work packages WP2 “ Network Integration” WP3 “Service and Network Management” WP4 “ Pervasive Systems” WP5 “Integrated System Evaluation” aim was to materialise the achievements of work packages into practical assessment to allow for concept validation.
- Other task forces were also created as required , for example inventory control checkers task force.
- With the Daidalos Architecture consisting of 3 technical work packages WP2 “ Network Integration” WP3 “Service and Network Management” WP4 “ Pervasive Systems” WP5 “Integrated System Evaluation” aim was to materialise the achievements of work packages into practical assessment to allow for concept validation.
- Other task forces were also created as required , for example inventory control checkers task force.
- Other task forces were also created as required , for example inventory control checkers task force.
- Other task forces were also created as required , for example inventory control checkers task force.
- The problems identified in 1st validation could only produce very high-level results (i.e. pass/fail of test cases). After these issues were resolved we were able to validate the demonstrator at a much lower level of detail, which has produced significant input to the technical work-packages Phase2. In a conformance session in Aveiro up to 120 test cases were planned based on the Nidaros Test case specifications. These covered the execution of multiple tests varying from step -1 to step 6 of the Nidaros scenario. Within in the first testing iteration 89 test cases were executed with 59 being successful.
- Unstable Mobile IP hindered conformance testing initially in Sophia, this was rectified in the Aveiro test bed by switching from Mandrake to Debian-based Ubunto Linux. Specific machines crashing and rebooting proved to be very time consuming. Minor Errors encountered, led many times to major complications in the whole Daidalos system due to the large amount of Daidalos components and their interconnections. Undocumented initial steps and configurations unforeseen prior to the testing phase, eroded into valuable scheduled testing allocated time, as these required configurations and steps had to be figured out and setup correctly for the test case to be executed.
- Unstable Mobile IP hindered conformance testing initially in Sophia, this was rectified in the Aveiro test bed by switching from Mandrake to Debian-based Ubunto Linux. Specific machines crashing and rebooting proved to be very time consuming. Minor Errors encountered, led many times to major complications in the whole Daidalos system due to the large amount of Daidalos components and their interconnections. Undocumented initial steps and configurations unforeseen prior to the testing phase, eroded into valuable scheduled testing allocated time, as these required configurations and steps had to be figured out and setup correctly for the test case to be executed.
- Communication was one of the main issues encountered during Daidalos Phase I integration, In phase I the integration wiki was not as effective as it should have been. It can be a powerful tool if used effectively and would have great potential for Phase II. Following the change from Mandrake to Ubunto in Aveiro , MIPv6 became a lot more stable, and it was possible to complete further testing than was previously capable in Sophia Antipolis conformance iteration. A key point realised is the importance for developers to meet iteration delivery deadlines, leading to early fault detection. Scenario step planning contributed positively to the integration process. The First successful integrated testing utilising all Work packages took place at Aveiro, demonstrating overall successful interoperability and integration.