1 / 12

S oftware E ngineering for E mbedded S ystems using a C omponent- O riented A pproach

S oftware E ngineering for E mbedded S ystems using a C omponent- O riented A pproach. Vergadering Gebruikerscommissie. Agenda of today. Progress report Discussion Composition and working of user group. Overview. General status of project and planning in the short and medium term

kuame-rodriquez
Download Presentation

S oftware E ngineering for E mbedded S ystems using a C omponent- O riented A pproach

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. Software Engineering for Embedded Systems using a Component-Oriented Approach Vergadering Gebruikerscommissie

  2. Agenda of today • Progress report • Discussion • Composition and working of user group

  3. Overview • General status of project and planning in the short and medium term • Accents during previous months • Valorization: overview publications

  4. General purpose of project Innovative method for component-based software-development for ES, supported by • a notation for component modeling, with emphasis on RT aspects, memory and power consumption, and supported by a development environment • a componentarchitecture and method • a generic architecture for the realization of user interfaces for ES • improving the observability of the dynamic behavior of ES (debugging, profiling) General methodology: case driven SEESCOA is generic, conceptual basic research.All developed software is to be considered as proof-of-concept.

  5. Overview project WP 1 WP2: component modeling WP 7: final validation (second case study) WP3: component architecture WP4: user interfaces WP5: observability WP6: Coordination and project management 0 6 12 18 24 30 36 42 48

  6. Previous 6 months (7-12) • T 2.2: Reuse contracts for component-based embedded software • T 3.2: Development of component architecture for first case • T 4.2: Implementation of component-based UIs • T 5.2: Specification and implementation of a generic debug interface for components

  7. Short term: months 13-15 • T 2.2: Reuse contracts for component-based embedded software • D 2.2: A modeling formalism that can be used for structured documentation of embedded software components • T 3.2: Development of component architecture for first case • D 3.3 A component architecture, results after first case • T 4.2: Implementation of component-based UIs • D 4.2 Component-based UI development, results after first case • T 5.2: Specification and implementation of a generic debug interface for components • D 5.2 A generic debug-interface for components Jan 2001: User group meeting : presentation deliverables

  8. Medium term: months 16-24 • T 2.3: Component composer + static consistency checking • T 3.3: refinement of architecture • T 3.4: design of common test case using components • T 4.3: Generalization of component-based UIs • T 5.3: Implementation of external debugger component • April 2001: User group meeting with progress report

  9. Accents during previous months • components, contracts, component system • components: central theme • important for all work packages • many mails, several internal documents and meetings • platform that will be used for case • hardware choices were made • software has been ported • demo

  10. Basic concept of the case Camera 1 Camera 2 Camera 3 Controller Controller Archiving Unit (PC) Unit (PC) Unit

  11. Accents during previous months • case • deliverable D1.3: generic application • now: description of small concrete application • to extract requirements for component model • camera with certain level of intelligence • takes decisions about quality of images to be sent to server • compromise between quality and completeness

  12. Valorization • Ronsse, M.; De Bosschere, K.; Chassin de Kergommeaux, J.; "Execution replay and debugging". Proceedings of the Fourth International Workshop on Automated Debugging (AADEBUG2000). Aug., 2000, pp. 5-18. TUM/IRISA, Munchen, Eds. Ducasse, M.; Brugge, M • Ronsse, M.; De Bosschere, K.; "Non-intrusive on-the-fly data race detection using execution replay". Proceedings of the Fourth International Workshop on Automated Debugging (AADEBUG2000). Aug., 2000, pp. 148-163. TUM/IRISA, Munchen, Eds. Ducasse, M.; Brugge, M • Ronsse, M.; De Bosschere, K.; "JiTI: A Robust Just in Time Instrumentation Technique". Proceedings of WBT-2000 (Workshop on Binary Translation). Oct., 2000, pp. 1-12. Philadelphia • S. Van Baelen, D. Urting, W. Van Belle, V. Jonckers, T. Holvoet, Y. Berbers, K. De Vlaminck, “Toward a Unified Terminology for Component-based Development” ECOOP 2000 Workshop on Component-Oriented Programming (WCOP), June 2000 • Y. Barbaix, K. Hermans, T. Holvoet, Y. Berbers, “Tuning Parameters for Component Based Design with Memory Constraints” ECOOP 2000 Workshop on Pervasive Component Systems, June 2000 • K. Coninx, "Enhancing the development of UIs for Embedded Systems", The Open Technology Seminar "Future User Interface Technology in Europe", June 19th, 2000

More Related