NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 2

changes.mady.by.user Unknown User (hebell)

Saved on

compared with

New Version 3

changes.mady.by.user Unknown User (wileyal)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

NCI maintains several groups of servers, also referred to as "tiers," , to facilitate development, QA, User Acceptance Testing (UAT), UML Model loading, etc. Following are explanations for each tier.

...

Once the development team has completed a set of enhancements, the source is extracted for the Source Control Management (SCM) system, built and deployed onto QA for the purpose of qualifying the product changes. Development team unit testing is completed prior to QA deployments to guarantee the QA team is using stable software. Bugs found during QA testing are opened as formal trackers in GForge. In some cases a Subject Matter Expert (SME) may be asked to ceritfy certify a requested feature on the QA tier. However, this tier is only accessible behind the NIH firewall and SME verification of the product may wait until Stage or the SME will be given an NIH account.

...

Immediately after Production deployment, new releases are deployed to Sandbox. The primary use for this tier is to upload, review and ceritfy certify UML Models. This tier is also used by Training as a work area for students.