Skip to content
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.

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

[uss_qualifier] Update f3548_self_contained tested requirements #457

Merged
merged 1 commit into from
Jan 4, 2024

Conversation

BenjaminPelletier
Copy link
Member

This PR updates the f3548_self_contained CI configuration to generate two tested requirements reports reflecting a simple SCD-only (no CMSA, no constraints, no availability arbitration) activity in multiple phases. This change will allow us to better target and measure MVP success in #274 and #434.

@BenjaminPelletier BenjaminPelletier marked this pull request as ready for review January 4, 2024 04:54
uss2: scd
uss1: scd_no_dss
uss2: scd_no_dss
- report_name: gate3
Copy link
Contributor

Choose a reason for hiding this comment

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

Why Gate 3 and not Gate 2?

Copy link
Member Author

Choose a reason for hiding this comment

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

There is an actual simple SCD-only activity after which this hypothetical activity is patterned. The gates roughly map to "crawl, walk, run" where Gate 1 is minimum viability and Gate 3 is "able to operate a production system". There is a Gate 2 in there, but it doesn't have separate relevant requirements for testing (at least, as foreseen right now).

@BenjaminPelletier BenjaminPelletier merged commit 8c7a7a3 into interuss:main Jan 4, 2024
9 checks passed
@BenjaminPelletier BenjaminPelletier deleted the gate-reqs branch January 4, 2024 17:28
github-actions bot added a commit that referenced this pull request Jan 4, 2024
github-actions bot added a commit to BradNicolle/monitoring that referenced this pull request Jan 4, 2024
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