Skip to content

Comments

add requirement coverage in checklist#585

Open
RolandJentschETAS wants to merge 2 commits intoeclipse-score:mainfrom
etas-contrib:improvement_arc_chklist
Open

add requirement coverage in checklist#585
RolandJentschETAS wants to merge 2 commits intoeclipse-score:mainfrom
etas-contrib:improvement_arc_chklist

Conversation

@RolandJentschETAS
Copy link
Contributor

Add requirement coverage in review checklist ...

See #584

@github-actions
Copy link

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

* - ARC_01_02
- Does the software architecture design consider all the requirements allocated to the architectural element, including functional, non-functional, safety, and security requirements and all related design decisions?
- manual
- Check if all requirements allocated to the architectural element are considered in the design. This includes functional requirements (e.g., use cases, functional safety requirements), non-functional requirements (e.g., performance, reliability), safety requirements (e.g., ASIL-related requirements), and security requirements (e.g., confidentiality, integrity). Additionally, ensure that all related design decisions are taken into account and documented in the architectural design.
Copy link
Contributor

Choose a reason for hiding this comment

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

How should the decision taken into account? What would be evidence for that?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The reviewer have to check in the review if all previous design decisions are fulfilled. Therefore he have to check the all the design decision. He provides evidence that he have done it. That's the same way as he states that the requirements are valid allocated or completely matches the requirements. Because there is no automatic way that a design decision is fulfilled in reality that have to be done by review. Which is exactly that review here. Best way would be, that any any design decision which influences the feature, the component, the requirements, ... would be linked to them. In such a case it would be easy for the reviewer to check that within the review.

Copy link
Contributor

Choose a reason for hiding this comment

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

Agree for linkage, can you discuss/Propose how we can do that?

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