Coding Process
From CLAWSWiki
Contents |
Requirements
Requirements MUST be decided and agreed on by both the customer and the developers before being implemented. Any changes should be documented in the Requirements Documentation before any code begins on a given ticket. At this point, acceptance cases should be written. All the requirements to be implemented in a given release should be agreed on before moving forward with development.
Design
Think before you write
Code/Test
See the Coding Standards for more details on how to format code. Before a ticket can be closed, make sure you check the acceptance cases and make sure it works according to everything there. Also test anything else that may have been effected by the changes. TEST BEFORE YOU COMMIT CHANGES TO SUBVERSION
Test
Test ALL of the acceptance cases and make sure they all pass. In many cases, this involves simply running the Automated Test Cases.
Release
Make the release branch ONLY once all of the acceptance cases have passed.
