jastram
commented
11 years ago Hello Marielle,
There are two considerations here: (1) how to name things and (2) how to work.
(1) I would not change any document IDs at this point: Considering that these identifiers are used in many planning documents, I think it is next to impossible to change things without confusing people and/or to introduce errors. I am not sure whether you are proposing renaming or not.
(2) However, that does not mean that we cannot restructure the way you propose and keep the original identifiers at the same time. To give an example:
merge of O7.1.3 and O7.1.7 : in toolchain repository
You could create an output called "evaluations". On the front page of that document, it would state that it contains both O7.1.3 and O7.1.7
So my response is, regarding (1): Please don't change IDs if possible, but regarding (2): Feel free to restructure as much or as little, as you see fit.
- Michael
MariellePetitDoche
DoW of WP7 proposes the following outputs :
T7.1 Primary Tool Chain Analyses and Recommendations Duration Complete? T7.1.1 Identify and define the potential means of description ← O7.1.1 Formal Model representing the sample spec, one for each candidate ← O7.1.2 Documentation of the changes to each means of description used (if any) ← O71.3 Evaluation of the models against the WP2 requirements ← O7.1.4 Decision on the final means of description choice(s) T7.1.2 Identify and compare existing modelling tools ← O7.1.5 Evaluation of tool and model for each proto-type ← O7.1.6 Documentation of the changes to each tool (if any) ← O7.1.7 Evaluation of the tools against the WP2 re-quirements ← O7.1.8 Decision on the final tool choice(s) D D7.1 Report on the final choice(s) for the primary tool chain (means of description, tool and platform) T7.1.3 Identify the tool platform ← O7.1.9 Evaluation of each tool platform against WP2 requirements, independent of target tool ← O7.1.10 Evaluation of tool platform in the context of specific target tools ← O7.1.11 Selection of Tool Platform (and reasoning)
T7.2 Secondary Tools Analyses and Recommendations Complete? T7.2.1 Identify and define the supporting tools and methods ← O7.2.1 Evaluation of supporting tools and methods against the WP2 requirements and task 1 choices ← O7.2.2 Decision on the supporting tools choice(s) D D7.2 Report on all aspects of secondary tooling (results of T7.2) T7.2.2 Model Transformation and Code Generation ← O7.2.3 Model Transformation Strategy ← O7.2.4 Code Generation Strategy T7.2.3 Requirement traceability ← O7.2.5 Captured and organized designer require-ments T7.2.4 Validation and Verification Tools ← O7.2.6 V&V tool choice ← O7.2.7 Test automation tool choice with experience report T7.2.5 Safety analyses Tools ← O7.2.8 Safety analyses tools choices
Do you think it is better to keep each output in separate documents or to merge somme of them ?
A proposition (to respect a planning) :