1 / 15

Requirements Analysis

Explore the goals and methods of requirements analysis, including interviewing, questionnaires, and observation techniques. Learn key tips and tools for conducting successful analysis to determine system requirements and constraints. Recommended for IT professionals and students studying systems development.

effiel
Download Presentation

Requirements Analysis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirements Analysis Dr. Merle P. Martin CSU Sacramento

  2. Agenda • Goals • Methods • Interviewing • Questionnaires • Observation • Requirements Analysis Document

  3. Requirements Analysis Goals • Fully describe current system • Determine ideal information system • Identify resource constraints • Inspire user confidence / ownership • Figure 7-6, page 246

  4. Requirements Analysis Methods • Checklists pp. 228-233 • Interviews • Questionnaires • Observation • Procedure Analysis • Document Survey

  5. Methods (continued) • How method used • Target for method (DFD) • Advantages • Disadvantages • When method best used

  6. Interviewing Questions • Who should interview? • Should we take notes? • How many interviewers? • Structured or unstructured questions? • How long should interview last?

  7. Interviewing Tips • Watch the time • Don’t look at watch • No leading questions • Listen • No body language

  8. Interviewing Tips (continued) • Make user feel important • Be courteous / professional • Don’t take exhaustive notes • Use structured questions • Don’t ask users to remember details • use observation instead • Avoid gang interviews

  9. Questionnaires • Response Rate • % returned • questionnaire length • make first part interesting • place demographics at end • closed questions • Figure 7-5, page 240

  10. Observation • Not for long periods of time • will change what you’re measuring • Vary observation periods • Take only minimal, pre-planned notes • Coordinate visit beforehand • Beware of Selective Perception!

  11. Requirements Analysis Document • Parts • How analysis conducted • credibility • restarts • User Requirements • System Constraints • Realistic System Objectives • Documentation (appendix)

  12. User Requirements • User system objectives (unedited) • Reports (type / frequency) • User training needs • Effect of new system on various users • Organization Chart

  13. System Constraints • Time • Skills • Funds • Technology • External factors

  14. Documentation • Data collection instruments • DFDs • Other

  15. Concepts to Remember • Requirements Analysis goals • Methods (checklists) • Interviews • Questionnaires • Observation • Requirements Analysis Document

More Related