Critical Control
Points During the Software Testing Process
|
Team |
Examples of Who |
Tasks |
Vendor, State, or Combination |
|
Project Management |
Project Manager Technical
Manager Functional
Manager |
Manage
project: - communications - planning - resources - budget - timeline - issue resolution - risk analysis & control - daily tasking |
Functional
Manager normally is State. Others may be either vendor or State. |
|
Configuration Management |
Technical
and Functional staff |
Manage
configuration items: - version control - environment control - change control - release management - test documentation - issue tracking - meeting minutes |
Combination |
|
Change Management or Change Control Board (Under
Configuration Management Umbrella |
Technical
and Functional staff |
Review
and control system change requests: - defect or new request? - impact on project if approved/not
approved - authorize/reject request |
Combination |
|
Release Management (Under
Configuration Management Umbrella) |
Technical
and functional staff |
Control
code releases as they move through system environments from test region to
test region and to production. - version control - verify code compatibility with existing
programming - prepare build/release - verify implementation plan and management approval of code moves |
Combination |
|
Technical Team |
Developers Database
Admin Network
Admin System
Analysts |
Develop
system: - general design - detailed design - program specifications - code - unit testing - tech support - operations support |
Combination |
|
Technical Test Team |
Technical
staff |
Integration
testing System
testing |
Combination |
|
Acceptance Test Team |
Functional
staff |
Acceptance
testing and possible assistance with System Testing. |
Usually State,
but could be combination |
|
System Administration |
Technical
staff |
Move code
executable builds from one system environment to another. |
Either or
combination |