Evaluation (Assessment Criteria)

1. Assessment of the responsiveness of the application in the context of the task / environment.

2. Overall latency permitted between physcial event and output (control out- put or display of data).

3. What is the sampling rate?

4. What bus protocol should be used (I2C, SPI, ...) and why?

5. How many channels?

6. Low level implementation: kernel or userspace and why?

7. Data flow from hardware to GUI to output with data formats, latencies, processing and conversions.

8. Buffering of data: how many samples?

9. How does the buffering impact on the realtime performance and how much latency is introduced?

10. Postprocessing of data and how that introduces latencies / processor load?

11. How many threads are needed and/or how can the load be distributed to allow a responsive application?

12. How to implement the GUI? Permitted refresh rate and latency resulted from it.

13. Structure of the software in classes, associated unit tests to turn it into reliable software

14. Team structure: which roles in a team of 3 and how equal contributions are guaranteed?

15. How much time is allocated to hard, software and debugging and how is this interleaved?

16. Which version control software is used? How are releases / milestones done and numbered?

17. What is the release strategy / publication / publicity? How is that mea- sured and deemed to be successful?

18. Measurement of success of the application in the context of the problem given and evaluation of it.