Skip to content

Conversation

@RolandJentschETAS
Copy link
Contributor

@RolandJentschETAS RolandJentschETAS commented Dec 17, 2025

add linking to iso26262 and add requirements according to ISO26262

See also findings in as base of these changes:
#82 (comment)

@github-actions
Copy link

The created documentation from the pull request is available at: docu-html

Copy link
Contributor

@masc2023 masc2023 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If manual check is required, it should be covered by the checklist for architectural design

* - ARC_04_03
- Are the the scheduling properties for the component defined and documented?

Note: see ISO 26262-6, 7.4.3
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use definitions in standards, as here std_req__iso26262__software_743

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changed

:tags: prio_3_automation, model, check
:complies: std_req__iso26262__software_743, std_req__aspice_40__SWE-3-BP3

A complexity analysis for the components shall be performed. It shall consider appropriate code metrics like lines of code, cyclomatic complexity, number of public interfaces, number of parameters and so on. The results of the analysis shall be documented in the component classification document. The project specific limits for the complexity measures shall be defined in the project guidelines.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still has the word component classification document. I would say, it should be the SW Verification Report, which should contain that.

masc2023
masc2023 previously approved these changes Dec 17, 2025
Copy link
Contributor

@masc2023 masc2023 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine now, but would be better to check the document for the measure again

@masc2023 masc2023 merged commit 3e9e3f0 into eclipse-score:main Dec 18, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants