Abstract
An automotive middleware layer masks the heterogeneity of platforms. and provides high level communication services to applicative tasks. In addition. this layer is a software architecture, shared between car makers and third-part suppliers, ensuring the portability and interoperability of the applicative tasks. In this study, a method aiming at developing the middleware's software architecture, and obtaining a set of tasks well characterized representing the middleware's implementation, is presented. This architecture is built with a set of design patterns, and identifies a set of middleware tasks whose characteristics allow the execution of an algorithm trying to determine a feasible priority allocation for the set of applicative and middleware tasks.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
