Project Phase 4: Configuration Management and Continuous Integration

CS350

Last modified: Dec 4, 2016

Contents:

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, enacting continuous integration, and incorporating analysis tools.

Your reference materials for this phase include

the requirements definition
these design notes

1 Continue Building

Continue your build, following the TDD procedures of the prior phase.

Update your Wiki to reflect your plans for this increment of the project.
All code for this project should reside in the package to be in edu.odu.cs.cs350.

Add configuration management to your build. Your build should use Maven or Ivy to retrieve any third-party libraries from a Maven repository.

All of these functions must be integrated into your build manager.

Place the project under continuous integration, using the Jenkins area of the course forge.

Your Jenkins site should automatically build your project after each checkin on GitLab.
It should present updated Javadocs and reports on tests passed and failed after each such build.

Add test coverage and static analysis tools to the build.

Coverage should be computed using both unit and integration tests.
These reports should appear on your project’s Jenkins page. (Do not leave this until the end. One of the evaluation criteria will be the ability to show a history of the changes in these reports over time.)

Add integration and systems tests. These should include tests on the trained learning machines.

“Submit” your project for this phase by tagging the version as “phase4”.

Each team member must individually take the peer evaluation survey.

2 Evaluation

Evaluations will be conducted as was done in Phase 3.

3 Project Review Meetings

This phase concludes with a project review meeting, conducted according to the same guidelines as in phase 3.

There will, however, be no individual assignments after the meeting unless the instructor is given serious reasons to doubt team members’ abilities during the meeting.