The scope of this Recommended Practice encompasses the following objectives:
Concentrate on general best practices for vehicular embedded software design.
Establish programming language-independent best practices.
Establish hardware/software interface best practices.
Establish multi-threaded system best practices.
Provide verification criteria to evaluate product compliance with this best practice.
Rationale
Changes were made based on the feedback from the previously balloted document. Changes include consistent terminology usage and spelling mistakes in the following section;
3. Definitions
5.1.2 Use of Interrupts Caused by Module Input Signals (1-2)
5.1.3 Bounding Interrupt Overhead (1-3)
5.1.4 Use of Nested Interrupts (1-4)
5.2.1 Worst-Case CPU Load Measurement (2-1)
5.2.4 Use of Software Wait Loops (2-4)
5.3.1 Initialization of All Control Registers (3-1)
5.3.2 Refreshing Control Registers (3-2)
5.3.3 Clock Prescaler and Pll (3-3)
5.5.2 Unused Memory (5-2)
5.5.4.4 Data Integrity – Recovery (5-6)
5.5.4.6 Non-Volatile Memory Initialization (5-8)
Appendix A – Discussion on System Design Interactions
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.
* Redlines comparisons are available for those standards
listed in the Revision History that contain a radio button. A
redline comparison of the current version against a revision is
accomplished by selecting the radio button next to the standard and
then selecting 'compare'. At this time, Redline versions only exist
for some AMS standards. SAE will continue to add redline versioning
with ongoing updates to SAE MOBILUS.
View/Annotate
Content Loading, Please Wait
Document Preview
Content Loading, Please Wait
Document Comparison
Content Loading, Please Wait
Download
A list of downloadable items.
Product Code
Document Title
File Type
Download
J2640_200810
General Automotive Embedded Software Design Requirements
Export Metadata
This modal will allow the user to download citation information or export specific fields of data into one of three file formats: Excel, comma-separated values, or text.
You are currently not logged into your Dashboard account, which is required for annotating.
Please select Login to login or register for the Dashboard. Select Continue to view the content without the ability to annotate.
Redline Warning
You are currently not logged into your Dashboard account, which is required for annotating.
Please select Login to login or register for the Dashboard. Select Continue to view the content without the ability to annotate.
Data Set Warning
General Automotive Embedded Software Design Requirements
SAE Journal Subscriptions are available in a variety of options, which include electronic, electronic with back file, and archive. For detailed information and options, please complete the following:
Content Request
Check My Access!
You may already have access to the Ground Vehicle Standard, General Automotive Embedded Software Design Requirements
Subscription Access
If you have Subscription Access with a username and password, please login below.
Institutional Login
If you have Institutional Access to SAE MOBILUS, using a predetermined organizational login utilizing single-sign-on (Shibboleth), please login below. To request institutional access to SAE MOBILUS, please complete the institutional subscription information form.
Purchase
If you do not have access to SAE MOBILUS via username/password or institutional access, you can still purchase the Ground Vehicle Standard, General Automotive Embedded Software Design Requirements.
Search Tips: Search Operators:AND, OR, NOT; Wild Cards; Using Quotes
SAE MOBILUS® Search Tips
Please note: All terms not contained within quotes, will be evaluated using the OR operator. This means that your search results will contain all results that contain ANY of the entered terms.
AND, OR, NOT
SAE MOBILUS supports the use of the AND, OR and NOT BOOLEAN operators ONLY function with the Advanced Search.
Wild Cards
Using the asterisk, ( * ) allows you to search for a partial word. For example, entering a keyword search of aero* will search for any word beginning with aero.
Using the question mark, ( ? ) allows you to search for a word with a single character wildcard. For example, searching for t?re would match both tire and tyre
Using Quotes
Words in double quotes " " are treated as a phrase. Conducting a search for "heat model" will return all results in which the exact phrase "heat model" is found, while "heat modeling" would NOT be included.
A term combined with a phrase will be joined with an OR operator.
Searching for Standards
When searching for a standard please use the entire Document Number assigned, which includes the abbreviation. A space can be used, or omitted between the abbreviation and number.