IN4MATX 113 Lecture Notes - Lecture 1: Structured Interview, Unstructured Interview
- Guidelines for questionnaire design
· 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
· Have someone else check your questionnaire
- Storyboards and scenarios
· 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
· Cooperative and incremental
· Storyboards:
Tells a story by a sequence of snapshots (sentence, sketch, slide, pic etc. )
· Scenarios
Like a use case
Story that illustrates an interaction
Types: as-is, visionary (what could be our opportunities), evaluation (true or not,
validate), training
Pros: concrete examples/counter-examples, narrative style, useful for
validation, generating acceptance test cases
Cons: inherently partial, etc
- Prototyping
· 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
find more resources at oneclass.com
find more resources at oneclass.com
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. Exploration of system-to-be and elicitation of further info. Tells a story by a sequence of snapshots (sentence, sketch, slide, pic etc. ) Types: as-is, visionary (what could be our opportunities), evaluation (true or not, validate), training. Pros: concrete examples/counter-examples, narrative style, useful for validation, generating acceptance test cases. A running/ seemingly running version of a system/ concrete system used for experimentation/feedback. 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.
