Description:
"Welcome back to our AUTOSAR Basics series, where we continue our exploration into automotive software architecture! 🚗💻 In Part 2, we delve deeper into the project objectives of AUTOSAR, uncovering its key principles and strategies for success. From interoperability to standardization, join us as we navigate through the core objectives driving AUTOSAR development.
Whether you're an automotive enthusiast or an aspiring engineer, this episode promises to deepen your understanding of AUTOSAR's mission. Tune in, learn, and embark on a journey towards AUTOSAR excellence with us! #AUTOSARBasics #ProjectObjectives #TechEducation"
Follow us on:
LinkedIn: https://www.linkedin.com/company/8255...
YouTube: https://www.youtube.com/channel/UC8E4...
#automotive #automotiveembeddedsystem #vehicle #car #protocol #automotiveengineering #autosar#AUTOSAR #AutomotiveSoftware #SoftwareArchitecture #TechExplained #AutomotiveInnovation #EngineeringBasics #AutomotiveEngineering #TechInsights #AutomotiveIndustry #EngineeringEducation #FutureMobility #TechTrends #LearnWithUs
In
the last video, We have covered all the main requirement
under Standarization under the Project objective AUTOSAR shall support the transferablity of
software, Next lets look into Abstraction requirements [RS_Main_00130] AUTOSAR shall provide an abstraction
from hardware The MicroController Abstraction Layer (MCAL)
of Autosar ,which we had discussed in previous video ,shall provide an abstraction from hardware
characteristics. This MCAL shall be limited to the software
modules directly inter
acting with the HW. Other parts of the Basic Software shall be
independent from hardware. Usecase here is to relocate the Application
Software from one hardware to other or to use of same Application Software in multiple
HW. [RS_Main_00310] AUTOSAR shall support hierarchical
Application Software design methods Which implies that AUTOSAR shall provide means
to structure Application Software in a hierarchical way, so that only links to outside Software
need to be treated / adapted / changed in the
next hierarchical
level. So the internal working of the Software is
abstracted from the next hierarchy and each hierarchy
can work on their development independently. Basic Objective is to allow each actor in
the development chain to focus on the required level and tasks. [RS_Main_00400] AUTOSAR shall provide a layered
software architecture Basically AUTOSAR shall provide a software
architecture, which distinguishes between Application Software, a Runtime Enironment
and Basic Software. Objectiv
e here is to have
layering inturn an Abstraction from the basics to concentrate more on the complex design
in Application Software. We have now covered all the main requirement
under Abstraction , Next lets look into Migration requirements [RS_Main_00270] AUTOSAR shall provide mitigation
strategies towards new releases Basically AUTOSAR shall provide migration
instructions and strategies on how Software Components and ECUs of different release have
to be adapted to interoperate. Usecase here is
to Integration of ECU’s
using BSW of the latest AUTOSAR release in a network built from ECU’s using a former
release. [RS_Main_00150] AUTOSAR shall support the
deployment and reallocation of AUTOSAR Application Software Here Autosar shall provides means by which
the application SW can be changed in the ECU during developement phase or even after production. Over the Air update along with Safety and
security are some aspects that should be considered in Autosar compliant Software [RS_Main_00507]
AUTOSAR shall reflect the
stages of a software system development in a formal model description AUTOSAR shall reflect the stages of a software
development process and define templates how information at these
stages can be exchanged between the different parties.To develop such blueprint AUTOSAR
considers existing standards like ISO26262 and Automotive SPICE During the development of a vehicle, software
system at different process steps have information exchange between
various partners. AUTOSAR
shall refine the formats and state
criteria for completeness of the exchanged information
to capture general requirements on the progress of development. We have now covered all the main requirement
under Migration for the objective , Next lets look into Test requirements [RS_Main_00480] AUTOSAR shall support the
test of implementations The Software implemented based on Autosar
standards shall be tested during software development for software maturity and software
safety standards. Next 3 requ
irements are on the definition
of Acceptance test. What is Acceptance test ? Acceptance test
are the tests that gives confidence to OEM and supplier on software meeting the expected
behaviour. [RS_Main_00122] Acceptance tests shall test
interoperability of BSW implementations of one AUTOSAR release in one vehicle network These acceptance tests shall ensure that the
different BSW implementation on same release of Autosar works well in the vehicle network. [RS_Main_00123] Acceptance tests shall te
st
interoperability of BSW implementations in vehicle networks These acceptance tests shall ensure that the
BSW implementation from different supplier works well in the vehicle network. [RS_Main_00124] Acceptance tests shall test
interoperability of BSW implementations to applications These acceptance tests shall ensure that the
BSW implementation from different supplier works well with the Application Softwares. With this we have covered all the categories
namely Standardization , Abstraction ,
Migration and Test Requirements for the objective :AUTOSAR
shall support the transferablity of software
Comments