Description

The impact of software development on pre-production engineering costs has escalated in the last five years to unprecedented levels. Much of this cost is impacted by the quality and reliability of the software deliveries to vehicle builds. Rapid growth of feature content in electronics products has opened the field for new suppliers whose qualifications for software development are often not clear. Organizational level assessments from CMMI, SPICE or other methods do not offer enough granularity or relevance to the OEM's to ensure quality, on-time delivery. The question should not be, “Is this supplier capable?” But rather, “Is the team this supplier intends to use on this product capable of engineering software for products of this Functional Domain?” The significant difference between the answers to these two questions acts as the motivation for the SAE J2746 Software Assessment Repository. The intent of the repository is to promote finer resolution of software capability in an effort to dramatically improve the quality and reliability of automotive embedded software. This support will promote better software development in the industry reducing preproduction engineering re-work, as well as costly warranty issues which result from poor software quality.

Product Details

Published:

04/23/2009

File Size:

1 file , 200 KB

Description

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.

Product Details

Published:

04/01/2009

File Size:

1 file , 200 KB