On 20.01.23 23:55, Gedare Bloom wrote:
I understand this change. I wonder if there are some terms that you
definitely want to avoid though?
Do you have tooling to warn on the use of these terms in requirements?
If not, that could be something easy for a student to put together as
a beginner/janitor task.
This change is related to:
https://github.com/RTEMS/rtems-central/commit/28cee60d99535c27e4bad0c87b13aa67de931c7a
The string assertion statement simply checked if the given phrases were
contained in the text. This resulted in too many false positives. It
would be a nice project to check that requirement texts are in EARS
format. This probably requires the use of trained software and some
natural language processing tools.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.hu...@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
