<name>Testing and Validation</name>
<begin>Month 12</begin>
<end>Month 30</end>
+ <leader file="nijmegen/geuvers"/>
<person-month participant="bologna" number="5"/>
<person-month participant="inria" number="6"/>
<person-month participant="dfki" number="3"/>
release of the first MOWGLI prototype, at month 18. We
shall consider three main validation tests:</p>
<tasks>
- <task name="T6.1">
- <p>Education. Full development of a fragment of the library
+ <task id="T6.1">
+ <name>Education.</name>
+ <p>Full development of a fragment of the library
covering a typical undergraduate course in algebra of
analysis.</p>
</task>
- <task name="T6.2">
- <p>Certified code. The aim is to be able to present the
+ <task id="T6.2">
+ <name>Certified code.</name>
+ <p>The aim is to be able to present the
formalization and the demonstration of some security
properties related to the code embedded into a smart card.
The presentation must be in a format understandable by
the company in charge of the evaluation of the code and
in accordance with the Common Criteria standard.</p>
</task>
- <task name="T6.3">
- <p>Electronic Publishing. The aim is to test the LaTeX-based
+ <task id="T6.3">
+ <name>Electronic Publishing.</name>
+ <p>The aim is to test the LaTeX-based
authoring tool and to demonstrate how an electronic
physics journal benefits from the exploitation of
content markup in journal articles.</p>
</task>
</tasks>
</description>
- <deliverable file="D6.a"/>
- <deliverable file="D6.b"/>
- <deliverable file="D6.c"/>
- <deliverable file="D6.d"/>
+ <deliverable file="testing-and-validation/d6a"/>
+ <deliverable file="testing-and-validation/d6b"/>
+ <deliverable file="testing-and-validation/d6c"/>
+ <deliverable file="testing-and-validation/d6d"/>
<milestones>
<p>We expect a lot of feed-back during this phase, that will
be taken into account for the definition of the advanced and