Re: Interest in a "Known Issues for Release Notes" (Task-Focussed) Working Group
On Mon, Feb 21, 2022 at 4:01 PM Gabriele Paoloni <gpaoloni@...> wrote:
Sorry, I missed to answer this question in my previous email. The point above is the critical first task for a group to agree on. ISO 26262 mentions: "the reactions of the functions under anomalous operating conditions" and "a description of known anomalies"; and it defines anomaly as "condition that deviates from expectations based on requirements specifications, design documents, user documents, standards, etc., or from someone’s perceptions or experiences". Both could well be covered by the term "known issues". Other standards might have different formulations to refer to a similar concept. I am also fine to include 'failing tests'; that is probably pretty close to the definition of known issues above. I am also fine to include 'static checker violations' (or compiler warnings)---with which we are moving a bit away from the definition above---but if you live up to the professional standard of writing warning-free code, I guess a code with a compiler warnings deviates from your standard. I agree the source and database are different and probably the "corresponding work-around measures" (in terms of ISO 26262) may be different here to other classes of known issues. All of this can be pretty well explored with some examples that are just sitting there to be picked up in various open-source packages. Lukas
|
|