This standard is intended to provide corporations that develop embedded software for the automotive industry direction on how to effectively publish and promote their organization’s development capabilities. The organization’s maturity may be measured through several capability assessment methods; this document addresses how the results of those assessments are shared within the SAE J2746 Software Assessment Repository. The repository is the online database system utilized by the SAE to facilitate accurate and secure sharing of corporations’ software development capabilities.
The SAE Software Assessment Repository is a web-based repository that allows organizations that develop embedded software to post and share their assessments in a uniform, disciplined manner. The repository does not mandate the use of one assessment method over another; rather, it reports the salient results from industry accepted assessment methods. It is important to recognize that both OEM’s and suppliers developing software which goes into vehicles should participate in the SAE J2746 Repository and follow improved practices of software engineering. Since car manufacturers OEMs (Original Equipment Manufacturer) also develop embedded software, they should participate in the Software Assessment Repository in addition to the supply base.
In order to better focus software improvements in the industry, the intent of Software Process Improvement (SPI) and related assessments must be focused upon industry specific technologies. When a customer is interested in the capabilities of a supplier, the relevance of those capabilities to the customer’s need is critical. SAE J2746 proposes to utilize the Functional Domains of the automotive electronics systems as defined by AutoSAR to partition suppliers’ capabilities. The six functional domains as defined by AutoSAR are Chassis, Powertrain, Safety, Multimedia/Telematics, Body/Comfort and Human Machine Interface.
These functional domains provide the repository the ability to better define the capabilities of OEMs and Suppliers for creating specific types of product software. Furthermore, by also understanding the geographic locations of OEM’s and Supplier’s engineering facilities, it is possible to understand the capability of a specific team, in a specific location to create a product of a specific Functional Domain. Instead of a blanket statement that Company Y is Level 3, a more precise statement of; “Company Y’s engineering team located in Facility X and engineering products of Functional Domain Z is Level 3” would be found within the SAE J2746 Software Assessment Repository (SAR), and offer a higher fidelity of insight into a company’s capabilities.
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
J2746_200904
Software Assessment Repository
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
Software Assessment Repository
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, Software Assessment Repository
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, Software Assessment Repository.
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.
