COMPSCI 132 Lecture Notes - Lecture 1: Structured Interview, Unstructured Interview
Document Summary
Select representative sample of people and provide motivation for responding. Make sure questions and answers are unbiased and unambiguous. Ask the same things in different ways- check if answers are consistent. Goal: acquire/validate info from concrete examples through narratives. Illustrate typical sequences of interaction among system components to meet an implicit objective. Widely used for: explanation of system-as-is, exploration of system-to-be and elicitation of further info. Storyboards: tells a story by a sequence of snapshots (sentence, sketch, slide, pic etc. ) A running/ seemingly running version of a system/ concrete system used for experimentation/feedback: focus on unclear, hard to formulate requirements. Pros: discover what they need, establishes feasibility at a low cost, detailed study of the reuqirements. Cons: increased development time and cost, misleading (setting expectations too high), incompleteness. Goal: speed up elicitation by reuse of knowledge from experience with related systems. Requirements meta-models: typical things to look for in requirements in a general way.