05

To show that there are different design choices, there are alternatives. Then it's a matter of weighting and looking at the pros and cons of each design choice and then to report it.

There are [disagreements] several times. There is something that I think 'ha, this is problematic.' My colleagues say 'no, that's okay.' And then we try to make an agreement on that. And then when we agree on that, if we think it's okay or problematic, then we also add it to the evaluation rubric.

Not adhering to MVC (by having an association from model to gui)

We try to see whether students have good modelling skills. [...] [For use case diagrams] they are supposed to not use technical terms, it should be kept kind of abstract, language independent. [In communication and class diagrams] we expect more technicality, association, division of responsibility. [In the code] for example, having small, well-focused classes.

Remove all pre-written text (lists of common mistakes, good to have)