This commit was manufactured by cvs2svn to create branch 'init'.

[helm.git] / helm / mowgli / home / xml / work-packages / requirement-analysis.xml

diff --git a/helm/mowgli/home/xml/work-packages/requirement-analysis.xml b/helm/mowgli/home/xml/work-packages/requirement-analysis.xml
deleted file mode 100644 (file)
index 996fce7..0000000
--- a/helm/mowgli/home/xml/work-packages/requirement-analysis.xml
+++ /dev/null
@@ -1,94 +0,0 @@
-<?xml version="1.0"?>
-
-<!DOCTYPE work-package SYSTEM "work-package.dtd">
-
-<work-package number="1">
- <name>Requirement Analysis</name>
- <begin>Month 0</begin>
- <end>Month 6</end>
- <leader file="nijmegen/geuvers"/>
- <person-month participant="bologna" number="3"/>
- <person-month participant="inria" number="4"/>
- <person-month participant="dfki" number="3"/>
- <person-month participant="nijmegen" number="6"/>
- <person-month participant="aei" number="3"/>
- <person-month participant="trusted-logic" number="1"/>
- <objectives>
-  <ul>
-   <li>Definition of the application scenarios.</li>
-   <li>Precise articulation of all the functionalities required
-       by the system, and all possible expected interactions
-       with documents.</li>
-   <li>Overall requirements of the distribution model of the
-       library.</li>
-  </ul>
- </objectives>
- <description>
-  <p>The work plan is naturally organised in subtasks according
-     to the different basic kind of interactions and manipulation
-     to be considered, namely:</p>
-  <tasks>
-   <task id="T1.1">
-    <name>Mathematics and the Web.</name>
-    <p>State of the art, standards and
-       tools.</p>
-   </task>
-   <task id="T1.2">
-    <name>Structured and Formal Mathematics.</name>
-    <p>Delineation and
-       layering of Semantic Components. Requirements for
-       the interaction with tools for the automation of formal
-       reasoning.</p>
-   </task>
-   <task id="T1.3">
-    <name>Metadata.</name>
-    <p>Classification and data mining for content-based
-       mathematical documents, and key architectural guidelines
-       for the metadata model.</p>
-   </task>
-   <task id="T1.4">
-    <name>Searching and Retrieving.</name> 
-    <p>State of the art, use cases and
-       application scenarios.</p>
-   </task>
-   <task id="T1.5">
-    <name>Distribution.</name>
-    <p>Distributed document repositories and
-       peer-to-peer interoperability.</p>
-   </task>
-   <task id="T1.6">
-    <name>Document Authoring.</name> 
-    <p>State of the art, use cases and
-       application scenarios.</p>
-   </task>
-  </tasks>
-  <p>Part of the activity, covering Tasks T1.1-2-6 should be
-     concluded within the first three months, with the
-     preliminary report D1.a. The main aim of this phase is
-     to rapidly reach a good level of inter-operability among the
-     different sites, by implementing a suitable politic of
-     knowledge and skills transfer between the members of the
-     consortium (short visits and/or small thematic workshops,
-     according to the case).</p>
-  <p>However, some delicate issues, such as Metadata, Searching
-     and Retrieving and Distribution (Task T1.3-4-5) will
-     eventually require a deeper analysis (deliverables D1.b and
-     D1.c).</p>
-  <p>WP1 will be eventually closed during the first meeting of
-     the Project (month six), when all the reports will be
-     discussed and approved.</p>
- </description>
- <deliverable file="requirement-analysis/d1a"/>
- <deliverable file="requirement-analysis/d1b"/>
- <deliverable file="requirement-analysis/d1c"/>
- <milestones>
-  <p>The preliminary report D1.a is not a realmilestone:
-     it should be considered as a first internal draft summarising
-     the main functionalities required by the system and the basic
-     intelligence to add to documents, as markup and/or metadata,
-     to meet these requirements. All these issues will be
-     eventually detailed in D1.b and D1.c, which are real
-     Milestones, since the rest of the work will be largely
-     driven by them.</p>
- </milestones>
-</work-package>