Introduction to Software Engineering

CS 3302 Spring 1997

Agenda for Requirements Review


Project to be reviewed

YCT squared

Artifact to be reviewed

Requirements review (V. 1)
  1. Introductions (1 minute)

  2. Purpose (1 minute)

    The purpose of this review is to provide feedback on issues arising from the first version of requirements for this project. If all goes well, we expect agreement with the customer to proceed with the project as defined in the requirements, after resolving any issues that arise from this review.
  3. General reactions (10 minutes)

    From the customer, we are mainly interested in hearing reactions on scope, clarity, omissions, effectiveness of diagrams.

    From the internal developers, we are mainly interested in hearing any potential objections to feasibility of these requirements given scheduling and resource constraints.

  4. Specific details (15 minutes)

    Each section of the document will be reviewed in order. For each section, we are looking for issues arising from confusing over use of language in the document. Any spelling and/or grammatical mistakes should not be mentioned here, as those can be provided to the minute taker before or after the review on a marked up version of the document.


Back to Spring 97 CS 3302 Home Page