Criteria

}Prioritized:

}Tradeoffs between requirements are clear.

} Multiple dimensions have been considered, such as cost, customer value, and development risk.

}All product stakeholders have provided input to the prioritization process.

}The requirements are realistically distributed among the priority levels.

}Unambiguous:

}Each requirement is clear to the intended audience, possessing a single interpretation.

}Terms are defined where necessary and used consistently.

}The requirements are devoid of weak words (easy, fast, etc.) and unbounded lists (such as, including, ...).

}Diagrams, algorithms, use cases, tables, or other devices are used to reduce ambiguity where appropriate.

}Verifiable:

}Each requirement is unambiguous.

}The implementation of each requirement can be clearly and effectively established via demonstration, inspection, or testing.

}Non-functional requirements (performance, reliability, etc.) are quantified using an appropriate scale of measure.

}Consistent:

}Each requirement is represented only once in a specification and referenced where needed.

}Each requirement is internally consistent with other product requirements at its level.

}Each requirement is externally consistent with requirements at other levels (product, business, market, etc.).

}Traceable:

}Each requirement is uniquely and persistently identified.

}Each requirement is written as concisely and simply as possible.

}Each requirement expresses only one function or idea.

Fill out the checklist

For each criteria, e.g. "tradeoffs between requirements are clear":

Specify the result of the criteria, e.g. yes, no, NA

Note the requirement number and describe any requirements that are exceptions/defects that require further review or analysis, e.g. Requirement 1.1 is not clear

Use the "Notes" column to describe anything else that the Requirements authors should know from the review.

Requirements to be reviewed:

Request Input:

The program will request 3 numbers, which we call A, B, and C, which are the sides of a possible triangle

Verify the Input:

The 3 inputs must be real numbers, greater than 0 and not too big.

Otherwise, output error message and stop

Verify that the sides form a legal triangle

If A + B >= C or B + C >= A or C + A >= B then a legal triangle

Otherwise, output error message and stop

Determine if the triangle is a right triangle

If A^2 + B^2 = C^2 or B^2 + C^2 = A^2 or C^2 + A^2 = B^2, then a right triangle.

Due to the issues of numerical precision, = in this case means within 1%

Determine if the triangle is equilateral, isosceles, or scalene

If the sides are all equal, then the triangle is Equilateral

Else if two side are equal, but not three, then the triangle is Isosceles

6. Display type of triangle

If it is a right and Isosceles Print Right Isosceles Triangle

If it is a right and Scalene Print Right Scalene Triangle

If is a right and Equilateral Print Equilateral Triangle

If it is not a right and Isosceles Print Isosceles Triangle.

These requirements should be reviewed and present in the form of upper table