Thanks Raphaël FAUDOU for your remarks.
I have still difficulties to work with csv inputs: columns are not "detected".
I should definitely miss something.
The csv file is as follow (id, text, criticity):
capa-01,system should, important
capa-02,system may, low
Please correct me:
- in Requirement and attributes recognition:
- Requirement identification:
- Column: 0 (no regexp)
- Attributes identification:
- Column: 1 (no regexp)
- Column: 2 (no regexp)
- Mapping:
- Requirement: Text: Column: 1
- Requirement: Text: Column: 2
The resulting requirement file is :
<upstreamModel ident="UpstreamModel">
<documents ident="requirement.csv">
<children xmi:type="ttm:Requirement" ident="simple-01,should be
done,low"/>
<children xmi:type="ttm:Requirement" ident="simple-02,may be done,high"/>
</documents>
I used an ods file as input. Columns are properly parsed. I get:
<upstreamModel ident="UpstreamModel">
<documents ident="simple.ods">
<children xmi:type="ttm:Requirement" ident="Capa-01">
<texts value="system should"/>
<texts value="important"/>
</children>
...
thanks
2009/8/28 nicolas romain lac <[email protected]>:
> Hello,
>
> Thanks for all the great job done by developers. Topcased is really
> getting more and more closed to a perfect tools chain.
>
> I am evaluating the requirements capabilities of Topcased (version 3.0.1). I
> read the TPC_3.0_Requirements_tutorial.pdf and wants to use a file with csv
> format as input.
>
> I can't populate (build) the upstream requirements. I am certainly missing
> something (or maybe the documentation is lacking something).
>
> Here are my steps:
>
> My input file is;
>
> simple.csv
> CAPA-01,system should,important
> CAPA-02,system should also,low
>
> 1. right click on the simple.csv file > Topcased > Import requirements
> 2. use defaults values,
> 3. in the requirement and attribute recognition dialog box :
> 1. requirement identification : Column: 0 Regex: .*
> 2. other columns:
> - Column: 1 Regex: .*
> - Column: 2 Regex: .*
> 4. creation of two attributes (text and criticity) and mapping,
> 5. Finish -> I can see my simple.requirement file...
> 6. Open a uml di file,
> 7. click on define requirements,
> 8. browse workspace,
> 9. select simple.requirement
> 10. open the two views
> 1. upstreams requirement,
> 2. current requirement
> -> then I don't know what I have to do...
>
> By the way, my simple.requirement model seems not to be correct. I don't have
> the properties that I created. Properties that can use are only the "basic
> ones"..
>
> simple.requirement
> ...
> <attributeConfiguration>
> <listAttributes name="#Allocate" type="Allocate"/>
> <listAttributes name="#Covered_by"/>
> <listAttributes name="#Justify"/>
> <listAttributes name="#Link_to" type="Link"/>
> <listAttributes name="#Maturity">
> <defaultValue
> value="//@attributeConfiguration/@listAttributes.4/@listValue.0"/>
> <listValue value="TBD"/>
> <listValue value="TBC"/>
> </listAttributes>
> </attributeConfiguration>
> ...
>
_______________________________________________
Topcased-users mailing list
[email protected]
http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
