Beruflich Dokumente
Kultur Dokumente
CSCI 4800/6800
Feb. 25, 2003
Goals
Interviewing/questionnaires
Observation
Document analysis
Prototyping
Checklists
Types of Requirements
Entity-Relationship diagrams
Usability requirements
Learnability
Throughput
Flexibility
Attitude
Functional Requirements
What the system does
What the user does
Result of analysis & collecting requirements is
functional specification
Dataflow diagrams
Document or other representation
Separate modules
Organized hierarchically
Functional Requirements
Databases - more persistent than dataflows
An abstraction of the existing system, not a copy of the
current physical process
Basis for structured walkthrough - verbal
description of the system based on the
diagrammatic representation
Other approaches:
Flow charts
Scenarios - good for HCI
Data Requirements
User analysis –
– determine scope of population who will use
the system
– user modeling techiques may be applied
here
– typically use checklists
Environment Analysis
physical environment
– temperature, humidity, lighting, available space
social environment
– quiet/loud, busy/isolated, etc.
user support environment
– helpful/hostile