search

openETCS / toolchain

WP7: Top Level Project for the toolchain
27 stars 30 forks source link

Import part of the subset-26 as req-IF for reqcycle evaluation #465

Closed cecilebraun closed 9 years ago

cecilebraun commented 9 years ago

For the reqcycle evaluation #452 we want to try out with a part of the subset. We will need a req-IF version of part of the subset-26 corresponding to the section: §4.4 et 5.4, 5.5, 5.6, 5.7, 5.8, 5.9, 5.10, 5.11, 5.12, 5.13, 5.19

Thanks,

MariellePetitDoche commented 9 years ago

And ideally §4.6 too

morido commented 9 years ago

Chapter 4

I am currently working on it. I hope to be able to provide you with a first draft by the beginning of next week.

Chapter 5

My tool currently does not support tracing into table cells (i.e. one table cell will always become one requirement no matter how long it is). Since chapter 5 contains very long cells I want to implement that feature before I trying to parse this chapter. Time frame: With luck before the 15th of December. Otherwise no earlier than January 2015.

Any chance that you can evaluate reqcycle with the chapters which I already provided to you?

morido commented 9 years ago

As promised here comes a first version of chapter 4.

cecilebraun commented 9 years ago

thanks @morido we gonna start with this part.

morido commented 9 years ago

A first version of chapter 5 is now available, too.

MariellePetitDoche commented 9 years ago

Thanks, this will be useful for me. I succeed to import the files in ProR and ReqCycle.

MariellePetitDoche commented 9 years ago

However could you give me an explicit list of the attributes you defined for each requirement ?

I assume rID is the ID (which format), but I do not understand the difference between rich and palin text.

morido commented 9 years ago

However could you give me an explicit list of the attributes you defined for each requirement ?

See the readme of my repository.

I assume rID is the ID (which format),

The readme links to a (slightly outdated) technical specification of the tracestring geneneration (whose result is shown under rID). Is that sufficient for you? There is also a more birds-eye like explanation here.

but I do not understand the difference between rich and palin text.

Well, richText comes with formatting (bold, italics, sub-/superscript, ...), plainText is just plain text. Apparently, SCADE is unable to handle richText, so it has to fallback to the plain text version. For viewing requirements in ProR (esp. tables, figures, images) richText makes a lot more sense, though. With a very few exceptions (i.e. deleted text can only be conveyed in richText) the textual contents of both fields are otherwise identical.

jastram commented 9 years ago

@MariellePetitDoche , considering that @morido published the converted version, can we close this?

MariellePetitDoche commented 9 years ago

yes