Doyle Rowland

Results 36 issues of Doyle Rowland

There are no availability calculations for the Hardware class. Availability cannot be calculated until the maintainability analysis is added to the Hardware class.

priority: normal
status: backlog
bump: minor
type: feature

**Describe the test that is missing or needs to be fixed.** Add a logger to conftest.py with session scope to log all the exceptions and error messages generate during a...

priority: low
status: backlog
good first issue
type: test
dobranch

The Hardware class currently has no maintainability analysis. Add maintainability analysis per MIL-STD-471, MIL-HDBK-470, and MIL-HDBK-472.

priority: low
status: backlog
bump: minor
type: feature

in the Testing module, replace all instances of 'self._app.debug_log.' with rtk_error, rtk_warning, or rtk_question dialogs as appropriate. Existing 'self._app.debug_log.' calls may remain if the information being logged could be helpful...

priority: low
status: backlog
bump: patch
type: feature

The goodness of fit test using the Cramer-vonMises statistic needs to be implemented for the Power Law model. Currently the CvM function to calculate the test statistic, but this is...

priority: low
status: backlog
bump: minor
type: feature

When using the Power Law model, there is no way to use/select Crow or Fisher methods for estimating confidence bounds on the MTBF or failure rate.

priority: low
status: backlog
bump: minor
type: feature

When updating the RG planning and feasibility treeviews, the values that are edited are only set if the Tab key is used to leave the cell. The values should update...

type: fix
priority: low
status: backlog
bump: patch

In the reliability growth test planning treeview, the start date and end date must be manually entered in the correct format for each test phase. A calendar widget and associated...

priority: low
status: backlog
bump: patch
type: feature

When checking the feasibility of a reliability growth test plan, the management strategy isn't checked. Add this check and use the following to set the risk levels: - < 0.9...

priority: high
status: backlog
bump: minor
type: feature

Currently RTK defaults to Crow bounds for the Crow-AMSAA assessment model. There should be a method for the user to select from Crow, Fisher, or Bootstrap bounds. Add a rtk.Combo()...

priority: low
status: backlog
bump: minor
type: feature