Discussion Threads

Documentation

Component documentation should be kept up-to-date as agile changes happen.

Engineer Process

As design/security description changes the development team should evaluate whether a change specific (mini) design/security review "DSR" would be beneficial.

To trigger a DSR:

  1. Dev-Ops team posts a revised design/security description to the component design thread listing which specific sections and changes need review
  2. Dev-Ops team notifies RACD management to request a mini-DSR and suggests reviewers
  3. RACD management will prepare and manage the mini-DSR
  4. Reviewers will provide feedback and the dev-ops team will reply thru the component design thread
  5. At the end of the DSR the dev-ops team will post a brief DSR summary to the component design thread

As functionality changes the development team should evaluate whether a change specific integration test would be beneficial.

To trigger the testing:

  1. Dev-Opts team posts the revised testing plan to component testing thread and lists which tests need to be run
  2. Dev-Ops tea notifies RACD management to start integration testing
  3. Testers will post issues and results and developers will reply thru the component testing thread
  4. Testing lead will summarize the testing results with the pass/fail to the testing thread

As functionality goes production:

  1. Operator will post changes to the production change log

Summary