1 / 9

Software Considerations for Automotive Pervasive Systems

Software Considerations for Automotive Pervasive Systems Software Engineering Challenges for Ubiquitous Computing, Lancaster, UK. Ross Shannon Dr. Aaron Quigley Prof. Paddy Nixon UCD Dublin, Ireland. Automotive Software Modern cars contain hundreds of microcontrollers multimedia systems

jana
Download Presentation

Software Considerations for Automotive Pervasive Systems

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 Considerations for Automotive Pervasive Systems Software Engineering Challenges for Ubiquitous Computing, Lancaster, UK. Ross Shannon Dr. Aaron Quigley Prof. Paddy Nixon UCD Dublin, Ireland.

  2. Automotive Software • Modern cars contain hundreds of microcontrollers • multimedia systems • navigation • communication • safety Ross Shannon: Software Considerations for Automotive Pervasive Systems

  3. In-car networking • complex sensor networks • communicate through a Controller Area Network (CAN) • AUTOSAR project for inter-car communication Ross Shannon: Software Considerations for Automotive Pervasive Systems

  4. Componentisation • different car models will have distinct capabilities • modules can be replaced or upgraded • may add new capabilities to the system • software system must adapt to changes • opportunity for autonomics • software project lines Ross Shannon: Software Considerations for Automotive Pervasive Systems

  5. Example • GPS module • should be unobtrusively integrated • make use of existing systems within the car • display console for mapping • driver feedback Ross Shannon: Software Considerations for Automotive Pervasive Systems

  6. Feature Discoverability • Opportunity for Service-Oriented Architecture (SOA) • services offer different Quality of Service parameters but may require use of same sensors/actuators/displays Ross Shannon: Software Considerations for Automotive Pervasive Systems

  7. Prioritisation of inputs • driver vs. automatic inputs • all inputs are filtered by the software system • which are more reliable? • software system may be taking more factors into account • particularly relevant as a safety concern Ross Shannon: Software Considerations for Automotive Pervasive Systems

  8. Summary • system stability is critical • component view of systems • discoverability • adaptation • prioritisation of signals Ross Shannon: Software Considerations for Automotive Pervasive Systems

  9. Thanks!Questions? ross.shannon@ucd.ieUniversity College Dublin, Ireland.

More Related