Course code: WEB-7
Years with company:
Primary programming language:
C for embedded.
Other programming languages:
VHDL, systemVerilog, C++, Python, PERL
Unit test harnesses:
Test practice now:
Static and Dynamic Tests are run after development: for the first one we use MISRA PcLint tool; for the second we use TESSY tool.
Minim system, with sensors and actuators, and some other peripheral modules.
IBM Rhapsody for Architecture and Design, AUTOSAR tool for compliance. Windriver with Eclipse environment for code development.
Naming conventions, manual about handle variables (init, global vs locals), etc...
Function too long:
We have a measure of quantity of (conditions and loop) instructions that we can use in the development of a function. This measure is not mandatory to follow, but a good practice.
We have three types of code Reviews: Inpection, Walkthrough and Screenning. The first one is the deepest Review (three or more partners), the last one is only for very low changes.
1- 2 hrs
1- 2 hrs
Favorite thing about dev:
You always learn how to develop SW in better ways, there is always a way to make it safer. The code Reviews are a very good way to keep learning with the team.
Least favorite thing about dev:
We sometimes have lacks in the requirements from the client, and sometimes the requirements that are very well specified do change several times. This is normal and we live with this.
What I know about the subject is to develop the TESTS starting from well specified requirements. At the beginning the tests are not going to pass because the code developed is not compliant, after this the CODE is developed to fulfill those tests.
Why are you attending:
I'm attending this course to change the paradigm of our development, because we first develop the code and then the test to check the code development correctness. Is obvious that the test can be developed first or at least simultaneously.