Software Development Process Using TkGnats


Development Process
 

Development State

Class

State

Action

Start Development Orig: Open
Next: Review
Project Lead creates new TKgnats entry at start of development. Assign to tech lead for requirements review and task breakdown. Tech lead move to state Review when ready for requirements review.
Requirements Review Development Orig: Review
Next: Implementation
Requirements review complete. Move to State Implementation and assign to developer. 
 Software Development Development Orig: Implementation
Next: Test or UIWG
On completion of development, developer moves to state Test or UIWG. If this is display components that need to be presented to the UIWG, assign to UIWG, Kucera responsible.
UIWG Development Orig: UIWG
Next: Implementation or Test
*This step is only for display software. If there was a UIWG presentation, the UIWG chairperson will move the state to Test if acceptable, or Implmentation if more work needs to be completed per the meeting.
Staging and Testing Orig: Development
Next: SW-BUG or Integration
Test Test team stages and executes test plan. If no bugs are found, move to Class integration and assign to integrator. If bug found, move to Class SW-BUG and assign to developer. See next section.
Integration and distribution Integration Orig: Test
Next: Closed
Set up install instructions and integration information and distribute to customer. Fill in 
field for release.

 

Testing Process

Bugs from LM
 

Review Results

Class 

State

Action

Received bug from LM Orig: SW-BUG
Next: SW-BUG or TRAINING
Orig:Open
Next: Implementation,reviewed
Received email or communication from LM of a bug found at their site.Test team enter tkgnats bug. Restage and test. 
Reproducible SW-BUG IMPLEMENTATION PR can be reprocduced,assigned to a developer Developer fixes bug, and software builds. Move state to TEST. After software is staged and tested, state moves toREJECTED or CLOSED. Software release identified.
Non-Reproducible SW-BUG REVIEWED PR is unable to be reproduced. Darien will discuss with LM.  State moves to REVIEWED. State moves to CLOSED or an appropriate state depending on discussions with LM.
Training TRAINING IMPLEMENTATION PR is a training issue. Patrice corrects User's Manual or follows-up on the issue. State moves to CLOSED.
Test of bug fix failed SW-BUG REJECTED Bug fix failed. Reassign to developer and move state from TEST to REJECTED.

Bugs discovered at FSL
 
Bug discovered while testing at FSL SW-BUG TEST Test team discovered bug while testing or re-testing fixed software. Change class to SW-BUG and state to REJECTED and reassign to developer(s).
Bug fix SW-BUG Orig: REJECTED
Next: TEST
Developer has fix and needs functionality retested. Change state to TEST and assign to test team.