Abstract: A method of establishing traceability for embedded software systems. A design code database is provided for an embedded software system. A test suite database including a plurality of test cases is structured for testing design code of the embedded software system. The structuring of the test cases provides a correspondence from a respective test case to a respective portion of the design code. A processor receives a design code modification to the embedded software. An associated test case is identified for testing the modified design code being based on traceability data. The associated test case is revised to accommodate the modified design code. The modified test cases are integrated into the test suite. A traceability database establishes a one-to-one correspondence between the modified design coder and the modified test case is updated.

Abstract: A system and method for accessing coherent data on a controller. The system and method include a first buffer and a second buffer that each may be read from or written to and an indicator that indicates which of the first or the second buffer is read from while the other of the first or second buffers is written to. The system and method also include a read synchronization protocol that allows the coherent data to be read from the buffer that the indicator indicates is the read buffer and a write synchronization protocol that allows the coherent data to be written to the buffer that the indicator indicates is the write buffer.

Abstract: A system and method for scheduling the execution of multiple mixed-criticality software applications on the same processor. The method separates higher critical, but lower operational rate, software applications into multiple segments so that the separated segments cause the lower rate applications to have a higher rate so that they operate before the lower critical software applications. Alternately, the method increases the length of a lower critical, but higher frequency, software application so that the software application has a lower frequency than the more critical application so that the more critical application has a higher priority.

Abstract: A system and method for scheduling the execution of multiple mixed-criticality software applications on the same processor. The method separates higher critical, but lower operational rate, software applications into multiple segments so that the separated segments cause the lower rate applications to have a higher rate so that they operate before the lower critical software applications. Alternately, the method increases the length of a lower critical, but higher frequency, software application so that the software application has a lower frequency than the more critical application so that the more critical application has a higher priority.

Abstract: A system includes a source module configured to generate a value related to control of a vehicle component. A destination module is configured to receive the value and implement the value in a control procedure to control the vehicle component. A diagnostic tool is configured to implement a diagnostic language that defines a compatibility relationship between the source module and the destination module. The diagnostic tool can determine whether the value generated by the source module is compatible with the control procedure based on the compatibility relationship. A method includes identifying a value generated by the source module, identifying a characteristic of the value generated by the source module, determining whether the destination module is configured to receive the value from the source module and implement the value in the control procedure, and determining whether the value is compatible with the control procedure given the compatibility relationship.