As explained before, a thesis in Holland is accompanied by a set of propositions. These propositions are considered to be a part of the thesis, which means that the members of the doctoral committee are allowed challenge them if they desire.
This is why the regulations state that the propositions:
'...shall be academically sound, shall lend themselves to opposition and be defendable by the PhD candidate, and shall be approved by the promotor.'
Furthermore, at least six of the propositions should not concern the topic(s) of the thesis, and at most two propositions can be playful in nature.
So let's see whether we succeeded, there is the list of my propositions (each one linking to this blog-post which contains an explanation for the proposition):
- To enable the effective application of software metrics, a pattern catalog based on real-world usage scenarios must be developed.
- The software architect should take the responsibility for the implementation of the system
- If software engineering PhD students spend 20% of their time `in the field', their research will be based on more realistic assumptions.
- Making the names of reviewers public will make reviewers more inclined to write better reviews, which increases the quality of the overall review process.
- Hiring a skilled typist is an often overlooked option during the design of an automated process.
- Understanding your goal makes it easier to deal with unpleasant chores.
- The replication of experiments becomes easier when all PhD students must replicate an existing study during their research.
- Using only metrics as acceptation criteria leads to undesired optimization.
- The most important objective in [Boy Scout] training is to educate, not instruct. (cf. Lord Baden-Powell)
- The fact that the McChicken tastes the same everywhere, proves that it is possible to have distinct teams produce the same results.