Elicitation. Requirements elicitation comprises activities that enable the understanding of the goals, objectives, and motives for building a proposed software system.
Elicitation also involves identifying the requirements that the resulting system must satisfy in order to achieve these goals.The requirements to be elicited may range from modifications to well-understood problems and systems (e.g., software
upgrades), to hazy understandings of new problems being automated, to relatively unconstrained requirements that are open to innovation2 (e.g., mass-market software).
As such, most of the research in elicitation focuses on technologies for improving the precision, accuracy, and variety of the requirements details:
• Techniques for identifying stakeholders help to ensure that everyone who may be affected by the software is consulted during elicitation.
• Analogical techniques, like metaphors and personas, help stakeholders to consider more deeply and be more precise about their requirements.
• Contextual and personal RE techniques analyze stakeholders’ requirements with respect to a particular context, environment, and perhaps individual
user, to help ensure that the eventual system is fit for use in that environment.
• Techniques for inventing requirements, like brainstorming and creativity workshops , help to identify nonessential requirements that make the final product
more appealing.
• Feedback techniques use models, model animations , simulation, and storyboards
to elicit positive and negative feedback on early representations of the proposed system.
Models can be used during elicitation to help catalyze discussion and to explore and learn about the stakeholders’needs. Such exploratory models, like cases, scenarios,enterprise models, and some policy and goal models, tend to be informal and intuitive, to facilitate early feedback from stakeholders. They tend also to be inexpensive to create and maintain, so that specifiers can keep them up-to-date as the requirements evolve.
No comments:
Post a Comment