Vision Document Review

<System Being Reviewed>

Team <#, names of reviewers>

<Note: everything surrounded by <> is either a placeholder to be filled in or a comment to be deleted. All tables contain fictional example entries which should be removed.>

Answer Yes, No or Unknown to each of the following. If the answer is “No” or “Unknown” please comment on the problem.

(This checklist is derived from Table 29-4, pp. 364 of the requirements text.)

_____ Is the vision of the project clear?

If your answer is “No” or “Unknown”, please explain.

_____ Does the vision document include input from relevant sources (authors/inventors, stakeholders, subject matter experts, development team) about key aspects of the project (system requirements, constraints, other systems and applications, competitive products)?

If your answer is “No” or “Unknown”, please explain.

______ Does the vision document contain the requisite elements: user’s profile, types, environments, product overview/perspective, product position statement, product features, applicable system requirements, and so on?

If your answer is “No” or “Unknown”, please explain.

______ Has the exemplary use case(s) been named and described?

If your answer is “No” or “Unknown”, please explain.

______ Have the various features had effort estimated, prioritized, and risk assessed?

If your answer is “No” or “Unknown”, please explain.

______ Has a requirements baseline been established?

If your answer is “No” or “Unknown”, please explain.