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

Your reference materials for this phase include

• the requirements definition
• these design notes

1. Continue your build, following the TDD procedures of the prior phase. Ideally, this phase will focus on your second planned increment.

   • Update your Wiki to reflect your plans for this increment of the project.

2. Add configuration management to your build. Your build should use Gradle to retrieve all required 3rd party libraries from a Maven/Ivy repository.

3. Choose a location from which to serve web pages containing project status reports You will need a mechanism by which you can permit any team member to update these pages. The file drop areas you created using ssh keys would be ideal for this purpose.

   Create a “Reports” web page there with the names of and links to the reports that you are posting (see below).

   Add a link to your reports web page in the Reports section of your Wiki opening page.

4. Modify your build so that an appropriate target (e.g., “reports”) guarantees that both updated Javadocs and JUnit test reports are generated.

5. Either

   • Add another target to your build (e.g., “deployReports”) that uploads the Javadoc and JUnit reports to your website, or

     • You may assume that each team member has a copy of the required ssh key handy, but do not check that key in to your repository.

   • Place the project under continuous integration, using the gitlab-ci function of the course forge.

     • Your GitLab project should automatically build your project after each commit to the master branch.
     • It should upload updated Javadocs and JUnit reports to the website after each build. If you do not have a target in the build to accomplish this, you may do so via the CI script.
       • The required ssh key should be supplied as a GitLab secret variable.

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

7. 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.

© 2015-2016, Old Dominion Univ.