 |
|
|
In this phase of the project, you will continue the software construction process. Your priorities during this phase will be adding configuration management to your automated build and preparing for continuous integration.
Your reference materials for this phase include
Continue your build, following the TDD procedures of the prior phases.
You will be graded based upon the final commit (to the main/origin branch) by the end of the day on the Phase 5 due date.
If you did not do so in phase 4, place the project under continuous integration, using the gitlab-ci function of the course forge.
Do this as early in phase 5 as possible. Part of your grade will depend on how complete a historical record you establish during this phase.
Add test coverage and at least one static analysis tool to the build.
Add graphs of data trends to your Reports page (e.g., like this one).
The report_accumulator plugin is designed collect such data.
Again, do this as early in phase 5 as possible, as your score for this will depend on having established a historical record.
Add integration and systems tests. A “systems test” in this project would be an execution from the Jar file you have constructed as a build artifact.
Each team member must individually take the peer evaluation survey.
Evaluations will be conducted as was done in Phase 4.
This phase concludes with a project review meeting, conducted according to the same guidelines as in phase 4.
|
|