Sample Annotation

Sample Student Annotation

The following is a sample annotation derived from one created by a student in a Computer Science course.

Exploring Ambiguity in Requirements and Clarifying Expectations
Description:	The following two artifacts concern the book "Exploring Requirements" [Gause 1989]. The artifacts address the first half and the second half of the book. This parallels the two areas that the book covers: ambiguity in requirements and requirements expectations. I provide a paragraph in each artifact that establishes context for each of the two points in the chapters that I believe are most important.
Reflection:	I found "Exploring Requirements" to be a very useful tool. The book obviously has an emphasis on ambiguity in requirements. But it does more than that because there are several areas of ambiguity that can be studied. Recognizing ambiguity, measuring ambiguity, and removing ambiguity in requirements are all part of finding out the reality of what a customer needs. Once ambiguity is under control, the requirements of the product can be clarified and discussed with the client. From this class alone I can see how hard it is to obtain clear requirements. In the workplace, I have seen how the realization of poor analysis of user needs has jeopardized a project's success. Requirements gathering, to me, is the most important part of a successful development project, something that many developers don't seem to realize.