eChallenges e2006 Large scale interoperability, integrating the Daidalos project

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    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.

    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.

    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.

    Favorites, Groups & Events

    eChallenges e2006 Large scale interoperability, integrating the Daidalos project - Presentation Transcript

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

    + Waterford Institute of Technology / TSSGWaterford Institute of Technology / TSSG, 3 months ago

    custom

    86 views, 0 favs, 0 embeds more stats

    This is the presentation of a paper which discusses more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 86
      • 86 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 0
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories