1. Case Assignment
Cases are assigned to the respective developer based on the requirement, priority, and availability. Once the case is assigned, the developer reviews the requirement and confirms the scope of work.
2. Requirement Analysis
The assigned developer reviews the case details and understands the required functionality or issue. The developer identifies the impacted components, required changes, and any dependencies before starting the development.
3. Development
After understanding the requirement, the developer starts the development work in the appropriate development environment.
All code changes should follow the project coding standards and existing implementation patterns. The developer should ensure that only the required changes are implemented as part of the assigned case.
4. Code Review
Once development is completed, the implemented changes must go through a code review process.
The reviewer verifies:
- Code quality and standards
- Functionality and implementation approach
- Impact on existing functionality
- Potential issues or dependencies
- Unnecessary or unrelated code changes
- Proper handling of errors and validations
Any review comments or required corrections should be addressed by the developer before proceeding to testing.
5. Testing
After the code review is completed and all review comments are addressed, the changes are moved to the testing stage.
Testing is performed to verify that:
- The requested functionality works as expected.
- The reported issue is resolved.
- Existing functionality is not impacted.
- Required validations and scenarios are working correctly.
- No unexpected errors are introduced.
The developer addresses any issues identified during testing and provides the updated changes for re-testing.
6. Testing Completion
Once testing is successfully completed, the changes are considered ready for version control and deployment preparation.
The final tested code should be verified to ensure that the code being committed matches the changes that were reviewed and tested.
7. Git Commit and Branch Push
After successful testing, the final code changes are committed and pushed to the appropriate Git branch.
The commit should contain clear and complete information, including:
- Case Number: The corresponding case/ticket number.
- Commit Comment: A meaningful summary of the implemented change.
- Description: A brief explanation of the functionality, issue, or requirement addressed.
- Changed Code: The final code changes associated with the case.
Example Commit Format
Case Number: CASE-XXXXX
Comment: Implemented [Feature/Issue Name]
Description:
Implemented the required changes to address the case requirement. Updated the relevant components and functionality as identified during development and testing.
8. Final Verification
After pushing the code to the designated Git branch, the developer verifies that:
- The correct branch was used.
- The correct case number is included in the commit.
- The commit comment and description are clear.
- All required code changes are included.
- No unrelated changes are included.
- The pushed code matches the tested version.
Process Flow
Case Assignment → Requirement Analysis → Development → Code Review → Testing → Testing Completion → Git Commit → Push to Specific Branch → Final Verification
Process Completion Criteria
A case is considered development-complete when the required changes have been successfully developed, reviewed, tested, and pushed to the appropriate Git branch with the correct case number, commit comment, description, and final code changes.