Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

eChallenges e2006 Large scale interoperability, integrating the Daidalos project

607 views

Published on

This is the presentation of a paper which discusses the challenges of large scale integration within the context of the massive collaborative mobile & wireless systems beyond 3G research project IST Daidalos.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

eChallenges e2006 Large scale interoperability, integrating the Daidalos project

  1. 1. Large scale interoperability, integrating the Daidalos project Frances Cleary Grant Miguel Ponce de Leon TSSG – Waterford Institute of Technology Ireland
  2. 2. Daidalos WP5 <ul><li>Daidalos (49 partners), integration was an immense task </li></ul><ul><li>co-ordinated and implemented by WP5. </li></ul><ul><li>Tasks Included </li></ul><ul><li>Defining Integration Processes and Models </li></ul><ul><li>Defining conformance test Specifications </li></ul><ul><li>Test Site Planning,Deployment and Integration </li></ul><ul><li>Test planning/scheduling/status report documentation </li></ul><ul><li>Test case execution, fault detection, result reporting. </li></ul>
  3. 3. Daidalos WP5 Task Forces <ul><li>The Integration of WP innovations were completed </li></ul><ul><li>through the selected ‘Nidaros’ Scenario. </li></ul><ul><li>To evolve and implement this scenario, task forces were created </li></ul><ul><li>Scene analysis Task Force (Input from all WP’s) </li></ul><ul><li>Scene Step analysis Task Force (Input from WP5 step responsible) </li></ul><ul><li>Mapping and Deployment Task Force </li></ul>
  4. 4. Daidalos Integration Model <ul><li>Due to the complexity of the Daidalos Architecture, the integration model addressed the following main areas </li></ul><ul><li>Integrated Testbed (2 integrated test sites) </li></ul><ul><ul><li>Sophia Antopolis,France </li></ul></ul><ul><ul><li>Aveiro, Portugal </li></ul></ul><ul><li>Integration-oriented developments </li></ul><ul><ul><li>Intra work package integration activities </li></ul></ul><ul><ul><li>Formalisation of Integration roles and processes </li></ul></ul><ul><ul><li>Identification of best Integration and Testing strategy (i.e. sandwich testing) </li></ul></ul><ul><li>Conformance Test Specification </li></ul><ul><ul><li>Identification of Nidaros specific WP interfaces </li></ul></ul><ul><ul><li>Definition of Scenario specific Conformance tests </li></ul></ul>
  5. 5. Daidalos Integration Model <ul><li>Due to the complexity of the Daidalos Architecture, the integration model addressed the following main areas </li></ul><ul><li>Integrated Testbed (2 integrated test sites) </li></ul><ul><ul><li>Sophia Antopolis,France </li></ul></ul><ul><ul><li>Aveiro, Portugal </li></ul></ul><ul><li>Integration-oriented developments </li></ul><ul><ul><li>Intra work package integration activities </li></ul></ul><ul><ul><li>Formalisation of Integration roles and processes </li></ul></ul><ul><ul><li>Identification of best Integration and Testing strategy (i.e. sandwich testing) </li></ul></ul><ul><li>Conformance Test Specification </li></ul><ul><ul><li>Identification of Nidaros specific WP interfaces </li></ul></ul><ul><ul><li>Definition of Scenario specific Conformance tests </li></ul></ul>
  6. 6. Daidalos Integration Management <ul><li>Roles created for successful Integration management </li></ul><ul><li>Test Manager (one from each technical WP) </li></ul><ul><ul><li>Responsible for defining Nidaros conformance Test cases (including interface tests) </li></ul></ul><ul><li>Build Manager (one from each technical WP) </li></ul><ul><ul><li>Responsible for WP code builds, and corresponding documentation. </li></ul></ul><ul><ul><li>Responsible for WP deliveries, following delivery process outlined by WP5. </li></ul></ul><ul><li>Test Site Manager </li></ul><ul><ul><li>Organise Test schedule (Daidalos ~organisation approx 100 people at test site) </li></ul></ul><ul><ul><li>Responsible for the provision of required and specialised hardware and installing software components </li></ul></ul>
  7. 7. Daidalos Test Methodology <ul><li>Test Case Definition </li></ul><ul><ul><li>Test Case Naming (e.g. N3:01) </li></ul></ul><ul><ul><li>,Systems under test, test summary, </li></ul></ul><ul><ul><li>API’s & interfaces involved, </li></ul></ul><ul><ul><li>initial conditions </li></ul></ul><ul><li>Test Report </li></ul><ul><ul><li>Verdicts, person executed test, </li></ul></ul><ul><ul><li>any closure actions and impacts, </li></ul></ul><ul><ul><li>comments and possible actions </li></ul></ul><ul><li>to be performed if test fails. </li></ul>Test Case No N3:01 SubSystems/Systems UnderTest (SUT) WP3 MMSPP Subystem/WP4 Subsystems/ NEWSCAST Application Components involved MMSP UA MMSP P/B Streaming Server NEWSCAST & VoIP Application Rules & Event Management, Context, Personalisation Protocols/APIs/IFs involved Intra WP3 Intra WP4 Intra Subsystem EIF0: MMSP UA-MMSP P/B (SIP) CM/P/REM Inter WPs WP3-WP4 MCCS Test Summary: Newscast that was on hold in Car PC unholds when VoIP call terminates but resumes voice only because Bart is driving.
  8. 8. Daidalos Integration Testing <ul><li>Validation of the Nidaros Integrated Demonstrator conformance tests </li></ul><ul><li>Sophia Antopolis in November 2005 , Aveiro in March 2006. </li></ul><ul><li>The 1st validation could only produce very high-level results (i.e. pass/fail of TC). </li></ul><ul><li>As issues were resolved we were able to validate the demonstrator at a much lower level of detail. </li></ul><ul><li>Conformance session in Aveiro up to 120 test cases were planned, based on the Nidaros Test case specifications. </li></ul>
  9. 9. Integration Issues Encountered <ul><li>Unstable MIPv6, switch from Mandrake to Ubunto </li></ul><ul><li>Machines crashing and rebooting became time consuming. </li></ul><ul><li>Minor Errors encountered, led many times to major complications. </li></ul><ul><li>Initial steps and configurations unforeseen eroded into valuable scheduled testing allocated time. </li></ul>
  10. 10. Conclusion and Results <ul><li>Communication was a main issue encountered during integration </li></ul><ul><li>Using Ubunto, MIPv6 became a lot more stable. </li></ul><ul><li>Key point - developers to meet iteration delivery deadlines </li></ul><ul><li>Scenario step planning contributed positively to the integration process. </li></ul><ul><li>The 1st successful integrated testing utilising all Work packages took place at Aveiro. </li></ul>
  11. 11. <ul><li>End Of Presentation </li></ul><ul><li> Thank You For Your Time </li></ul><ul><li> Any Questions? </li></ul>

×