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

Secondary Loss Event Frequency PERT input values should be between 0 and 1 #29

Open
vidhisshah opened this issue Sep 30, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@vidhisshah
Copy link

Similar to the validation checks in place for 'Probability of Action', 'Vulnerability', 'Control Strength', 'Threat Capability', there probably should be a check in place for Secondary Loss Event Frequency as well. The value will eventually be multiplied with Loss Event Frequency, so it should be less than or equal to one, more specifically between zero and one.

I looked through some other issues, to see if others are using it as I am, and they are. (Example issue 17)

@theonaunheim theonaunheim added the bug Something isn't working label Oct 1, 2020
@theonaunheim
Copy link
Contributor

Thanks for the issue, @vidhisshah . You are correct: this is how it is intended to be used and should be validated.

Will tweak the master_fix branch and send an update this weekend.

@cneskey cneskey added enhancement New feature or request bug Something isn't working and removed bug Something isn't working enhancement New feature or request labels Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants