Skip to content
This repository has been archived by the owner on Apr 20, 2024. It is now read-only.

4. Software Development and Validation Process

Chris DeBoer edited this page Dec 18, 2023 · 3 revisions

Software Development and Validation Process

Software creation consists of two phases, Development and Validation. Development is the creation of the code and Validation is testing to ensure that the code functions properly and does not break existing features of the software.

Software Development always starts with an assigned Issue. A software branch can then be created with the appropriate name. (See Software Branching Process) All work must be done on the software branch. The only work done on the branch should be directly related to the issue being resolved. Do NOT just "Fix" things in a branch. This will help minimize merge conflicts with other ongoing tasks.

Software Validation involves ensuring that the software change functions as desired. This can involve simulation or testing on the robot. If the change affects others, (Mechanical Team, Drive Team) ensure that the change meets their needs as well. The final step is the branch merge that involves review and approval of the changes.

Software Development is usually an iterative process going back and forth between Development and Validation.