peer review: <Mitchell Weingust Team 22> Verification and Validation Team Breakdown is Too General

[mitcholll]

artifact under review.

VnV Plan Document

team number (for the team doing the review).

Team 22

description of issue.

Section 3.1 Verification and Validation Team is a bit too general, and leaves out crucial details when it comes to verifying and validating your system. For example, there is no mention of regular reviews by your supervisor or TA. As well, having the general statement of "Automated Testing" as a role could overlap with other team members roles, such as in "Software Validation" and "SRS Validation", as all 3 will touch the system's software.

It would be beneficial for the team to identify their core strengths and interests when it comes to testing. Perhaps you can organize your responsibilities by areas of testing/features instead of only by the documents. Multiple people can be assigned to a document too, as testing the entire SRS may be quite challenging and time consuming for one person!

@CSchank