lobster-codebeamer improvements#571
Conversation
…n extraction and baseline_id support - Requirement data model: new optional fields asil, ver_ValSetup, ver_ValRationalargumentation with JSON serialisation/deserialisation - codebeamer tool: extract ASIL from native aSIL field and customFields; extract ver_ValSetup and ver_ValRationalargumentation with fallbacks for varied field names and WikiText value/values structures; fetch detailed item only when needed (fetch_missing_details flag); merge report-wrapper fields preserving non-null values - codebeamer config: new baseline_id parameter (validated positive int); verify_ssl extended to accept bool or PEM path string - html_report: render ASIL, Ver_Val setup, Ver_Val rational/argumentation for Requirement items - trlc converter: propagate asil field value into Requirement objects - Unit tests: extended coverage for all new extraction paths, ASIL propagation, merge behaviour, detail-fetch count, baseline_id config - PyInstaller spec files and certifi hook added for packaging
…n extraction and baseline_id support - Requirement data model: new optional fields asil, ver_ValSetup, ver_ValRationalargumentation with JSON serialisation/deserialisation - codebeamer tool: extract ASIL from native aSIL field and customFields; extract ver_ValSetup and ver_ValRationalargumentation with fallbacks for varied field names and WikiText value/values structures; fetch detailed item only when needed (fetch_missing_details flag); merge report-wrapper fields preserving non-null values - codebeamer config: new baseline_id parameter (validated positive int); verify_ssl extended to accept bool or PEM path string - html_report: render ASIL, Ver_Val setup, Ver_Val rational/argumentation for Requirement items - trlc converter: propagate asil field value into Requirement objects - Unit tests: extended coverage for all new extraction paths, ASIL propagation, merge behaviour, detail-fetch count, baseline_id config - certifi hook added for packaging
…m/bmw-software-engineering/lobster into feature/lobster_codebeamer_update
| asil: Optional[str] = None, | ||
| ver_ValSetup: Optional[str] = None, | ||
| ver_ValRationalargumentation: Optional[str] = None, |
There was a problem hiding this comment.
Unfortunately this feature is against the LOBSTER philosophy. LOBSTER shall remain an agnostic tool that can trace arbitrary artifacts. They don't need to be requirements, they could be architecture elements, Jira tickets or customer bug reports. If attributes like asil are hard-coded into Item, then we enforce attributes on artifacts which just don't make sense. What is the ver_ValSetup of a bug report?
By the way, I assume ver_ValSetup means something like "verification and validation setup", but it is not very clear.
If you want to include further information in your LOBSTER item, then please use the text attribute. Since #545 the tool lobster-html-report prints this JSON property into the HTML report also for Activity objects (not only Requirement). You can do so by opening the *.lobster file generated by lobster-report, enriching the text property, and feeding it to lobster-html-report.
We are working on a more generic solution regarding the handling of items, see #524.
Note that you can use markdown inside the text property to structure your text, see --render-md command line argument:
2 participants
add ASIL, ver_ValSetup, ver_ValRationalargumentation extraction and baseline_id support