8000 The methods of ISO 26262 shall be explained · Issue #497 · eclipse-score/score · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

The methods of ISO 26262 shall be explained #497

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
Tracked by #320
pahmann opened this issue Feb 25, 2025 · 1 comment · Fixed by #721
Closed
Tracked by #320

The methods of ISO 26262 shall be explained #497

pahmann opened this issue Feb 25, 2025 · 1 comment · Fixed by #721
Assignees
@pahmann
Labels
community:process community:testing
Milestone
2025-05-30 Proces...

Comments

@pahmann
Copy link
Contributor
pahmann commented Feb 25, 2025 •
edited
Loading

The verification methods of ISO 26262 shall be explained: E.g. what is meant with “static code analysis”?
This was a finding from the 2nd interim audit.
@pahmann pahmann modified the milestone: SCORE Process Audit 3 Feb 25, 2025
@pahmann pahmann changed the title Finding: The methods of ISO 26262 shall be explained: E.g. what is meant with “static code analysis”? The methods of ISO 26262 shall be explained Feb 25, 2025
@pahmann pahmann mentioned this issue Feb 25, 2025
Closed
17 tasks
@pahmann pahmann mentioned this issue Mar 10, 2025
Closed
5 tasks
@aschemmel-tech aschemmel-tech mentioned this issue Mar 14, 2025
Closed
52 tasks
pahmann added a commit that referenced this issue Mar 18, 2025
@pahmann
process: verification guide for types and methods
77be985 
see #497

Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
@pahmann
Copy link
Contributor Author
pahmann commented Mar 18, 2025

Description from audit document:

Finding: The methods of ISO 26262 shall be explained:

  • E.g. what is meant with “static code analysis”? Polyspace Analysis or Cyclomatic Complexity with limit values, or what else (Hint: MISRA or similar analysis are static analysis, but are already used to make the programming language a suitable language for
  • What is meant by Fault Injection Testing on unit test level?
  • What is meant by Interface testing (permutation of all possible input pattern?)

@pahmann pahmann mentioned this issue Mar 18, 2025
Merged
pahmann added a commit that referenced this issue Mar 18, 2025
@pahmann < 8000 /a>
process: correct minor typos
ad727c3 
see #497

Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
pahmann added a commit that referenced this issue Mar 25, 2025
@pahmann
process: verification guide for types and methods
4e841d1 
see #497

Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
pahmann added a commit that referenced this issue Mar 25, 2025
@pahmann
process: correct minor typos
465c4a8 
see #497

Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
pahmann added a commit that referenced this issue Mar 25, 2025
@pahmann
process: verification guide for types and methods
655f13a 
Additionally, addressing Typos.

see #497

Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
pahmann added a commit that referenced this issue Mar 25, 2025
@pahmann
process: add condition coverage as testing method
d39bfcc 
see #497

Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
@pahmann pahmann linked a pull request Mar 25, 2025 that will close this issue
process: verification guide for types and methods #721
Merged
@pahmann pahmann moved this to In Progress in Process Community Mar 27, 2025
@pahmann pahmann moved this to In Progress in Milestone Planning Mar 27, 2025
@pahmann pahmann moved this to In progress in S-CORE Roadmap Mar 27, 2025
pahmann added a commit that referenced this issue Apr 8, 2025
@pahmann
process: improve condition coverage guide
365b047 
see #497

Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
pahmann added a commit that referenced this issue Apr 8, 2025
@pahmann
process: condition vs branch coverage example
b2b02c0 
see #497

Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
pahmann added a commit that referenced this issue Apr 9, 2025
@pahmann
process: fix test method review findings
9293b68 
see #497

Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
aschemmel-tech added a commit that referenced this issue Apr 9, 2025
@aschemmel-tech
process: correct branch coverage description
46cf8b4 
Ref: solves #497
pahmann added a commit that referenced this issue Apr 9, 2025
@pahmann
process: verification guide for types and methods
027687a 
Additionally, addressing Typos.

see #497

Co-authored-by: Alexander Schemmel <alexander.schemmel@bmw.de>

Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
pahmann added a commit that referenced this issue Apr 9, 2025
@pahmann
process: add condition coverage as testing method
3c71a9f 
see #497

Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
pahmann added a commit that referenced this issue Apr 9, 2025
@pahmann
process: improve condition coverage guide
47fc25d 
see #497

Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
pahmann added a commit that referenced this issue Apr 9, 2025
@pahmann
process: condition vs branch coverage example
7f789d9 
see #497

Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
pahmann added a commit that referenced this issue Apr 9, 2025
@pahmann
process: fix test method review findings
4bc5dbd 
see #497
pahmann pushed a commit that referenced this issue Apr 9, 2025
@aschemmel-tech @pahmann
process: correct branch coverage description
2f23a0e 
Ref: solves #497
pahmann added a commit that referenced this issue Apr 9, 2025
@pahmann
process: fix documentation build error
6371f3c 
see #497

Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
pahmann added a commit that referenced this issue Apr 9, 2025
@pahmann
process: split verification methods into own file
2c80024 
closes #497

Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
pahmann 8000 added a commit that referenced this issue Apr 9, 2025
@pahmann
process: correct wrong condition coverage mentioning
9460d9a 
closes #497

Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
pahmann added a commit that referenced this issue Apr 10, 2025
@pahmann
process: remove structural coverage test type
766e44a 
close #497

Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>
@github-project-automation github-project-automation bot moved this from In Progress to Done in Process Community Apr 10, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Done in Milestone Planning Apr 10, 2025
@github-project-automation github-project-automation bot moved this from In progress to Done in S-CORE Roadmap Apr 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pahmann pahmann

Labels
community:process community:testing
Projects
Milestone Planning
Status: Done
Process Community
Status: Done
S-CORE Roadmap
Status: Done
Milestone
2025-05-30 Process & Tools Enable Tes...
Development

Successfully merging a pull request may close this issue.

process: verification guide for types and methods eclipse-score/score
1 participant
@pahmann
0