1 / 18

Proposed Research TU Eindhoven

Proposed Research TU Eindhoven. Space 4 You Kick-off Mondragon 4 july 2003. People. Michel Chaudron (Health Management) Johan Muskens (Health Management) Johan Lukkien + Postdoc(Terminal Management) Alex Telea + Postdoc (SW visualization) Peter de With + Postdoc (Real Time).

nituna
Download Presentation

Proposed Research TU Eindhoven

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Proposed Research TU Eindhoven Space 4 You Kick-off Mondragon 4 july 2003 Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

  2. People • Michel Chaudron (Health Management) • Johan Muskens (Health Management) • Johan Lukkien + Postdoc(Terminal Management) • Alex Telea + Postdoc (SW visualization) • Peter de With + Postdoc (Real Time) Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

  3. Fault & Terminal Management • Fault & Terminal Management have in common that they aim to maintain system integrity: Health Management • Fault Management handles unforeseen events • Terminal Management handle foreseen changes Both tasks may benefit from the same mechanisms. Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

  4. Health Management Goal: Maintain a system integrity Who Tasks Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

  5. Health Management: Self Goal: Maintain a healthy system • Self model of whole system • Must be machine processable; e.g. represented using UML profiles; • Express system-wide non-functional properties: e.g. end-to-end deadlines • Define place of reflection in Robocop Architecture • update self-model? • Self-model of services • Integrity-tests • Certificate … could be Robocop models Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

  6. Health Management: External Goal: Maintain a healthy system • Protocols & API’s for remote monitoring, diagnosis & curing • communicate about self-model with external parties • Visualization techniques • … Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

  7. Self Monitoring Application or service will recognize when its ill. • Coding styles • Asserts • Exceptions • … • Dedicated task of a service • Continuously check of simple conditions (Checklist) • Self model of an application Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

  8. External Monitoring Third party will investigate health of an application. • Checking vital signs • Heart beat interface for services • … • Checking responses • Test scenario with correct responses • … Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

  9. Self Diagnostics Application or service will diagnose itself when its ill. • Checklist - simple check list a service can use to do simple diagnosis. Example: Condition : Cause Attr X == NULL : Init Failed Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

  10. causes External Diagnostics Third party will diagnose an application. • Checking vital signs • Vitals interface for services • Enables more extensive testing • Checking responses • Test scenario with wrong responses and possible causes. • Fault propagation model • Check possible reponses with possible causes • Relate faults in input to faults in output: Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

  11. Self Curing Application or service will cure itself. • Actions depending on diagnose Diagnose : Action Init Failed : init(); • Restore default situation (and start over) • Use default values for attributes • Corrupted service can replace itself with fresh instance. • Data can be saved • Switch to safe mode • Offer less functionality / low quality of service Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

  12. External Curing Third party will interfere an application. Application Level: • New Image • Fresh but probably basic system • Reboot • Data loss • … Service Level: External replacement of services • Trusted party needed • Instance of same service vs. instance of compatible service. Visualization techniques for cases human intervention is needed Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

  13. Approach Self-Model • A representation of allowed systems follows a multiple views model: • Structure: which topologies & dependencies? • Behaviour: which interactions, when? • Deployment: which services on which hw? • Development: which files where? • Describe using UML profiles? • Underlying analysis engine: based on graph-grammars? Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

  14. Initial Phase Approach • Develop scenario’s of several typical system operations... • component replacement • including interaction with a remote system as source of new component • interaction with similar, neighboring systems • consistency, integrity • remote interaction • retrieving data • using local functionality • vizualization • more....... • ....preferably using existing demonstrators • e.g. the Robocop demonstrators Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

  15. Power management • Could be based on self-model as well • Proposal M.Sc. Projects: • Predictable Assembly of Component Power Consumption models • Anytime algorithms Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

  16. Summary of Research Contributions • Investigate and develop health maintance framework • Through development of self-model • reflection mechanisms • include functional & non-functional behaviour • Experiment with different paradigms for a self model • prototypes • Develop techniques for putting real-time aspects in the component design trajectory & self-model • Investigate the techniques for external health management • support remote diagnosis, monitoring & curing Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

  17. Wish list • Access to cases (to be treated under NDA) that illustrate alternative system configurations; e.g. high-end and low-end • MP3 player • DVD player • Joint Masters projects • A spirit of cooperation Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

  18. May the force be with Space4U Michel Chaudron,Johan Muskens, and Johan J. Lukkien TU/e Computer Science, System Architecture and Networking

More Related