Meetings - both software Eng.'s and customers.

rules for preparation and participation are established and an agenda is suggested.

"Facilitator" - controls the meeting.

Goals:

• to identify the objective
• propose elements of the soln
• specify a preliminary set of solution requirements

Problems:

• Problem of Scope:
  requirements contain unnecessary detail, ill-defined, or not possible to implement.
• Problem of Understanding:
  Not having a clear cut understanding b/w the devs and the customer....
  misunderstanding requirements.
• Problem of Volatility:
  requirements changing over time can cause difficulties...wastage of time and resources.

Work Products:

• a statement of need and feasibility.
• a bounded statement of scope for the system or product.
• a list of customers, users, and other stakeholders who participated in requirements elicitation.
• a description of the system’s technical environment.
• a list of requirements (preferably organized by function) and the domain constraints that apply to each.
• a set of usage scenarios that provide insight into the use of the system or product under different operating conditions.
• any prototypes developed to better define requirements.