1 / 13

Computer System Analysis

University of Palestine. Computer System Analysis. Chapter 7 Determining System Requirements Dr. Sana’a Wafa Al-Sayegh 1 st quadmaster. IGGC 1101. Learning Objectives.

robbin
Download Presentation

Computer System 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. University of Palestine Computer System Analysis Chapter 7 Determining System Requirements Dr. Sana’a Wafa Al-Sayegh 1st quadmaster IGGC 1101

  2. Learning Objectives • Describe options for designing and conducting interviews and develop a plan for conducting an interview to determine system requirements • Design, distribute, and analyze questionnaires to determine system requirements • Explain advantages of observing workers and analyzing business documents to determine requirements 7.2

  3. Learning Objectives • Explain how computing can provide support for requirements determination • Learn about Joint Application Design (JAD) • Use prototyping during requirements determination 7.3

  4. Performing Requirements Determination • Gather information on what system should do from many sources • Users • Reports • Forms • Procedures 7.4

  5. Deliverables and Outcomes • Types of deliverables: • Information collected from users • Existing documents and files • Computer-based information • Understanding of organizational components • Business objective • Information needs • Rules of data processing • Key events 7.5

  6. Traditional Methods for Determining Requirements • Interviewing and Listening • Gather facts • Observe body language and emotions • Guidelines • Plan (Checklist or Appointment) • Be neutral • Listen • Seek a diverse view • Interview Questions • Additional Guidelines • Do not phrase questions in ways that imply a wrong or right answer • Listen very carefully to what is being said • Type up notes within 48 hours • Do not set expectations about the new system 7.6

  7. Traditional Methods for Determining Requirements • Administering Questionnaires • More cost-effective than interviews • Choosing respondents • Should be representative of all users • Types of samples (Convenient, Random sample, Purposeful sample, Stratified sample) • Questionnaires • Design • Mostly closed-ended questions • Can be administered over the phone or in person • Vs. Interviews • Interviews cost more but yield more information • Questionnaires are more cost-effective 7.7

  8. Traditional Methods for Determining Requirements • Interviewing Groups • Advantages • More effective use of time • Enables people to hear opinions of others and to agree or disagree • Disadvantages • Difficulty in scheduling • Directly Observing Users • Serves as a good method to supplement interviews • Often difficult to obtain unbiased data • People often work differently when being observed 7.8

  9. Analyzing Procedures and Other Documents • Four types of useful documents • Written work procedures • Describes how a job is performed • Includes data and information used and created in the process of performing the job or task • Business form • Explicitly indicate data flow in or out of a system • Report • Enables the analyst to work backwards from the report to the data that generated it • Description of current information system 7.9

  10. Modern Methods for Determining Requirements • Joint Application Design (JAD) • Brings together key users, managers and systems analysts • Purpose: collect system requirements simultaneously from key people • Conducted off-site • Prototyping • Repetitive process • Replaces or augments SDLC • Goal: to develop concrete specifications for ultimate system 4.10

  11. Business Process Reengineering (BPR) • Search for and implementation of radical change in business processes to achieve breakthrough improvements in products and services • Goals • Reorganize complete flow of data in major sections of an organization • Eliminate unnecessary steps • Combine steps • Become more responsive to future change 7.11

  12. Summary • Interviews • Open-ended and close-ended questions • Preparation is key • Questionnaires • Must be carefully designed • Can contain close-ended as well as open-ended questions 7.12

  13. Summary • Other means of gather requirements • Observing workers • Analyzing business documents • Joint Application Design (JAD) • Prototyping • Business Process Reengineering (BPR) 7.13

More Related