Project 2 - Development of TFT Cluster Speedometer Software Component
Development of TFT Cluster Speedometer Software Component
Cluster Instrument receives the signals from other ECU via CAN bus interface. It also receives commands from the driver via steering wheel buttons. The signals are then processed by the Cluster ECU, after which the Cluster ECU may send the vehicle information to the LCD or light the LEDs and so forth, according to the results. Therefore, the Cluster ECU can be viewed as a carrier of the information flow.
Model-
Requirement 1-
Requirement 2-
Requirement 3-
Requirement 4-
Requirement Tagging-
- Requirement document is created for the given requirement.
- From the requirement document requirement group and requirement are created in the requirement editor.
- All the requirements are tagged to the related subsystem.
Find the requirement document and requirement tagging report in the attachements.
Fixed Point Tool-
SLDV Tool-
Design Error Detection-
Design error detection was performed on the model and two integer overflow conditoins were obtained.
Corective action was taken and design error detection test was performed again.
This time their were no falsified conditions.
Design errors were removed
Find the Design error detection report in the attachements
Test Generation-
Test Generation was performed on the model.
All the objectives were satisfied.
Find the test generation report in the attachements.
Functional Testing-
Test cases were created.
Find the test case document in the attachements.
MIL testing-
MIL testing harness was created and MIL test was performed on the model.
As observed from the data inspector the calculated vehicle speed and actual vehicle speed is same.
SIL Testing-
SIL testing harness was created and SIL test was performed on the model.
As observed from the data inspector the calculated vehicle speed and actual vehicle speed is same.
As observed from the Above calcultion sheet, the calculated vehcle speed and actual vehicle speed is same at different time intervals, with exception of minor difference in the values at some points.
Find this calculation sheet and MIL & SIL test harness in the attachments.
Coverage-
Coverage was performed and a 100% coverage was obtained for the prepared test cases.
Find this coverage reports in the attachments.
Autocode generation-
Autocode geneartion was performed.
Find the Auto-code generation report, .c & .h codes in the attachments.
Polyspace Tool-
Bug finder test was performed.
Code prover test was performed.
Find both the bug finder and code prover reports in the attchments.
Test Manager-
Baseline test-
Baseline test was performed on this model.
There was only one condition evaluated it was successful
Find baseline test report in the attchments.
Back 2 Back test-
B2B test was performed on this model.
There were two conditions evaluated both were successful
Report for th B2B test was not generated due to some internal error.
But as seen from the image all the conditions were successfully evaluated.