 |
|
|
The project is divided into 5 phases
Software Requirements Specification
User stories
Version control, ADT documentation, build manager, unit tests, website/wiki
configuration management, continuous integration
Final implementation, code analysis, integration & system test
All five phases are team activities. The teams for this first phase will be randomly assigned. For the remaining phases, you will select your own teams.
One purpose of allowing teams is to distribute the workload. One purpose of requiring teams is to be sure that students can employ the relevant tools and techniques taught in this course in a collaborative environment.
Individual team members should not feel they can safely sit back and let everyone else do the work. Nor should one gung-ho team member, however talented, grab all the work and do it all. As a team, you must take responsibility for making sure that all team members understand and practice the relevant tools and techniques.
Prepare a Software Requirements Specification (SRS) document for this requirements definition.
Your SRS should follow the format of the IEEE 830 standard, available on the course Library page. For section 3, you may use any of the alternative organizations from the appendices of that standard.
After your work has been submitted, each team member must individually take the peer evaluation survey. The purpose of this survey is to assess the relative contributions made by individual team members.
This is a team assignment. Teams have been assigned randomly. You can view your team (group) assignment as one of the SRS… groups in the Groups area on your recitation Blackboard site.
Blackboard will allow you to email your team members for coordination purposes. Your team has also been provided with a Discussion Area, which you may use to facilitate your work. Both will be visible only to your team members and to me.
Keep in mind that you have access to Google drive via your ODU email account. You might chose to work collaboratively via a shared Google Docs document on that cloud drive.
Prepare your SRS as a PDF document, following these guidelines.
When you are ready to electronically submit your assignment, use the button below:
Only one team member should submit on behalf of each team. If you submit more than once, (e.g., you discover a mistake after submitting), only your LAST submission before the due date will be considered.
Evaluations will be a combination of what the group has accomplished and how much each individual contributed to that group’s effort.
This phase will be graded as:
score = doc. quality * indiv
where:
doc. quality is an assessment of the completeness, correctness, and quality of the document submitted by the team.
indiv is a scaling factor for an individual’s effort. A normal effort level is 1.0. This factor will be raised or lowered by a combination of
|
|