To support design and other review, there should be a method for the user to work through a checklist to verify the completeness of an analysis. A list of basic questions should be provided by RTK "out of the box", but this list should be editable and addable by the end-user. At a minimum, the following checklists should be provided:
In addition, there should be design review checklists provided for PDR, CDR, and TRR. A checklist should be associated with the following:
1. Revision module to assess the overall RAM program.
2. Requirements module to assess the quality of the requirement/specification (analysis page already provides base questions, will need to re-format this to a RTKTreeView() to allow editing and addition of questions by the end-user).
3. Hardware module to assess the individual Hardware item.
4. Software module to assess the individual Software item (risk analysis page already provides base questions, will need to re-format this to a RTKTreeView to allow editing and addition of questions by the end-user).
The purpose of making these checklists addable by the end-user is to allow institutional knowledge to be captured for posterity.
To support design and other review, there should be a method for the user to work through a checklist to verify the completeness of an analysis. A list of basic questions should be provided by RTK "out of the box", but this list should be editable and addable by the end-user. At a minimum, the following checklists should be provided:
In addition, there should be design review checklists provided for PDR, CDR, and TRR. A checklist should be associated with the following:
The purpose of making these checklists addable by the end-user is to allow institutional knowledge to be captured for posterity.