Requirements Determination Fact finding process A critical initial stage in systems analysis Highly unstructured 72% of all errors in systems can be traced back to improper requirements determination How much time to spend?

Requirements Determination Involves four iterative processes –Discovery Find all relevant fact from people, old systems and environment –Representation Record facts for interaction with designers and users and for validation –Evaluation Completeness, consistency, correctness –Verification Compare to base line requirements

Discovery What facts to collect? –Get the big picture, start at the top –Problems, opportunities, constraints –Detailed information about the current way of doing things –Espoused versus actual theories of action –Rules and exceptions to rules –Organizational climate, politics –Get wish lists

Interview Process Fact finding Fact verification Clarification Generate enthusiasm Get end user involved Solicit ideas and opinions Get soft information

Uncertainties in Requirement Determination Existence and stability of requirements Ability of users to specify requirements –Cognitive biases Anchoring Recency effect Estimation errors –Chunking Ability of analysts to elicit and evaluate requirements –Preconceived solutions –Limited understanding of the problem domain –Lack of preparation

Fact Finding Techniques Interview –Individual –Group Document Examination –Policy manuals, SOPs –Memos, minutes, reports –Filled out forms –System manuals, consultant reports Direct observation –Measurement –Sampling –Questionnaire JAD