# Adimec R&D Software Quality Working Group

* Iemand zal de kar moeten gaan trekken en verantwoordelijk zijn voor de qualiteitsverbetering(en)

- Long term goals 2022 and beyond
- Defined styles
- Defined procedures
- Defined tooling

## Firmware quality

* Codestyle enforce with automatic code formatting tool (like clang-format or uncrustify)
* Static analysis of C/C++ code (e.g clang scan-build, coverity, pvs studio, or sonar cube)

## Firmware verification framework

The current problem with verification is the amount of manual labor necessary to qualify cameras firmware. The only proof of quality is the simple verification matrix. Logging is sometimes done with hacked python scripts and taking screenshots and pasting it in excel sheets.

* Python scripts?, labview has its pros and cons to share with test-software team
* Well defined -> documented and everybody does it the same way (consistency and reproduability)
* Logging server for verification
* Verification matrix is different between projects, when automated/defined in python scripts the procedure and result documents can be automaticly generated in a uniform way

## Subversion to git migration

* Better tooling to gate software changes -> enforced review system (e.g bitbucket/gitea?)
* Artifacts should (not be) stored in svn? -> do some research

## 

Words:
- Intrensieke motivatie
- Niet stagneren
- Proactief
- Niet te beroerd om kennis op te doen of cursussen te volgen
- Pas op met burnout