peer review: <Mitchell Weingust Team 22> All Critical Assumptions Not Covered

[mitcholll]

artifact under review.

Hazard Analysis Document

team number (for the team doing the review).

Team 22

description of issue.

Section 5. Critical Assumptions section states "No critical assumptions are being made for tinymorph that would limit the scope of mitigating or eliminating potential hazards." The following section 6.1 mentions Hazards Out of Scope, which some may fall into Critical assumptions.

You mention in the sentence below the list of 'hazards out of scope' that the first three are managed by users, which the team doesn't have control over. It would be a good idea to state that a critical assumption is "the team has no control over the user's hardware". That would justify why your chosen hazards are out of scope. This is a critical assumption as it relates to how the project's success does not depend on the user's physical devices.

@CSchank