Web Engineering Elicitation Meeting

Stakeholders collaborate to gather detailed requirements in a formulation meeting.

Agenda setting for a meeting should be formal to encourage the free flow of ideas.

A facilitator, such as a customer or an outsider, controls the formulation meeting.

In some cases, informational and applicative goals may not provide enough information to identify the scope of the problem.

Work sheets, flip charts, and wall stickers are examples of definition mechanisms used during a meeting.

The WebApp description is assembled before the formulation meeting to guide stakeholders in providing requirements.

Stakeholders and the WebE team establish goals and objectives for each WebApp increment during meeting preparation.

Meeting preparation helps identify the scope of the development effort for the WebApp.

The WebE team is solely responsible for determining a successful outcome of the WebApp development effort.

Different stakeholders may have varying views of the WebApp and different benefits upon successful deployment.

During formulation and elicitation, stakeholder information should not be categorized to set the stage for negotiation.

Meeting with stakeholders is not essential before beginning the communication activity in preparation for the WebApp development.

A framework activity is always the same for every Web engineering project.

Each framework activity consists of a set of actions, work tasks, and quality assurance points.

Umbrella activities are not part of a framework.

Communication in Web engineering involves interaction only with the developer.

Planning in Web engineering includes creating a detailed design of the WebApp.

Modeling in Web engineering assists only the developer in understanding requirements.