Seaport-e - Quality Assurance

This Quality Assurance (QA) plan describes the general procedures used by GameSim to support the professional delivery of software under the Seaport-e contract. This plan was created to describe GameSim’s approach to QA and to define the responsibilities of QA personnel and the QA responsibilities of other team members.

Approach

GameSim’s QA plan focuses on frequent inspection of our software to capture issues during development, rather than afterward. The QA and Technical Leads work together in short “sprints” that result in fully functional modules. The QA Lead works from the design documents to create test cases in parallel with the Technical Lead, who develops software based on the same documents. The Technical Lead delivers functional modules to the QA Lead who executes the test cases. This process continues until the QA Lead signs off on the software as ready for delivery. The Program Manager executes a final pass on the software, and signs off on each deliverable before it is made available to the customer.

In the case of quality issues reported by the customer, GameSim utilizes a Rapid Response Team that is headed up by the Technical Lead. Depending on the severity of the issue, this team may develop a software patch, provide a work-around until the next deliverable, or may deliver an emergency corrected version of the software. Additionally, the QA Lead develops a test case to cover the use case that revealed the issue.

 

QA Responsibilities of Team Members

  1. Program Manager – The PM is responsible for the quality of all deliverables. The PM serves as the main interface with the customer. All customer quality issues should be reported through the PM unless a separate issue reporting system has been established for the specific project. The PM is responsible for signing off on every deliverable before it is presented to the customer
  2. QA Lead – The QA Lead is responsible for creating and executing test cases that cover as much of the project as practicable. The QA Lead is also responsible for signing off on every deliverable before it is presented to the customer.
  3. Technical Lead – The Technical Lead is responsible for ensuring that all code is peer reviewed before it is committed to the main software branch. The Technical Lead heads up the Rapid Response Team and is also responsible for the configuration management of the software repository.

Specific QA Measures

This QA Plan outlines the general procedures used by GameSim. GameSim will provide specific QA measures and metrics for evaluating performance on a Task Order on an individual basis for each Task Order.

 

Points of Contact

Stephen Eckman

Technical Point of Contact

Chief Scientist

(t) 407-688-0587 Ext. 122
(f) 888-551-8281
seckman@gamesim.com

Andrew Tosh

Contractual Point of Contact

President

(t) 407-688-0587 Ext. 100
(f) 888-551-8281
atosh@gamesim.com

Andrew Tosh

Customer Satisfaction Point of Contact

President

(t) 407-688-0587 Ext. 100
(f) 888-551-8281
atosh@gamesim.com

Share This