-
Notifications
You must be signed in to change notification settings - Fork 15
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
V&V Tasks Not Associated With Requirement #52
Comments
Fixed Validation-Hardware issue in commit 78dced1 Moving to release 1.3.0 for Validation-Software fix. |
- Fixes issue #52 for Validation:Hardware. - Add method to create/refresh matrix. - Update method names to conform with RTK coding standards. - Add Hardware:Requirement matrix. - Add Hardware:Validation matrix. - Add Validation:Requirement matrix. - Add Validation:Hardware matrix. Signed-off-by: Doyle Rowland <[email protected]>
This no longer makes sense (if it ever did). V&V tasks need to be associated with a Requirement. Updated title to reflect desired outcome. This will require a new many-to-many relationship (table or view?) in the database. Probably display this using a RAMSTKTreeView in list mode. Could have the treeview be a list of all requirements with a checkbox to indicate which are verified by a given V&V task. Or the treeview could list only those requirements the V&V task is associated with and each requirement is selected from a combo. |
Branch feat/issue-52 created! |
There is no way to associate a V&V task with a hardware or software item. Provide a method to associate a V&V task with at least one hardware and one software item. At minimum, the task should be associate-able with the assembly level for hardware and module level for software.
A V&V Task/Hardware and V&V Task/Software matrix would be even better to allow a task to be associated with multiple hardware/software items. The ability to select whether components/units are included in the matrix would be best.
The text was updated successfully, but these errors were encountered: