General Automotive Embedded Software Design Requirements
- Ground Vehicle Standard
- J2640_200604
- Issued
Scope
-
Concentrate on the general best practices for vehicular embedded software design.
-
Establish programming language-independent best practices.
-
Establish hardware/software interface best practices.
-
Establish preemptive system best practices.
-
Provide verification criteria to evaluate product compliance with this best practice.
Rationale
Recommended Content
Technical Paper | Architecture Design and Implementation Issues for Model-Based Automotive Embedded Software Development |
Progress In Technology | Automotive Software |
Technical Paper | Software Testing Coverage for Automotive Embedded Controllers |
Data Sets - Support Documents
Issuing Committee
Embedded Software Standards Committee
SAE Embedded Software Created to address in-vehicle software technical and business issues and based on input from automotive software experts of automotive OEMs, the automotive electronic module supplier base, embedded software providers, software tool providers, and consultants to the industry, SAE Embedded Software's industry-level goal is "to reduce automotive electronic system cost and development time through efficiency in software". The SAE Embedded Software agenda also includes: Reducing automotive electronic complexity Raising industry awareness of embedded software development issues Increasing the knowledge level across the entire automotive software engineering community Developing information reports, recommended practices, and standards The SAE Embedded Software Standards Committee is composed of the following task force efforts: J2632 "C Coding Practices" - a recommended practice that targets a common set of C coding methods suitable for automotive embedded software development. This effort is currently in progress. Monthly meetings are conducted. J2640 "General Embedded Software Requirements" - a recommended practice that focuses on passing lessons learned into the automotive embedded software development community. This effort is currently in progress. Monthly meetings are conducted. J2516 "Embedded Software Development Lifecycle" - a recommended practice that discusses a wide range of available off-the-shelf software improvement processes including CMMI. This effort is currently in progress.. J2356 Software/Systems This activity is based on J2356-1 A Graphic Model for Distributed Functions that characterizes the basic input, output, control, transmission, and reception processes of a distributed function. This Software/Systems task force effort is just beginning. J2720 Software Development for Calibration & Manufacturing This low-level activity is expected to create an information report to address the use of CCP, assignment of CCP identifiers for module suppliers, discussion of OEM sanction of CCP usage, CCP security issues, and some comparison to alternate methods like ISO14229. This effort is in a beginning stage. J2734 Embedded Software Verification and Validation Task Force. J2746 Software Assessment Repository Task Force.
Reference
Number | Title |
---|