Scribd Logo
Upload

Welcome to Scribd!

  • 457 views

    Chapter 6 - Fact-Finding Techniques

    Uploaded by

    morohen
    This document discusses techniques for discovering requirements for new information systems. It covers key concepts like functional and non-functional requirements. Methods discussed include problem analysis using Ishikawa diagrams, observation, questionnaires, interviews, prototyping, and joint requirements planning sessions. Documentation of discovered requirements is also discussed. Managing changing requirements over the project lifecycle is important. Fact-finding should be done ethically without misusing sensitive information.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd

    Chapter 6 - Fact-Finding Techniques

    Uploaded by

    morohen
    457 views28 pages
    This document discusses techniques for discovering requirements for new information systems. It covers key concepts like functional and non-functional requirements. Methods discussed include problem analysis using Ishikawa diagrams, observation, questionnaires, interviews, prototyping, and joint requirements planning sessions. Documentation of discovered requirements is also discussed. Managing changing requirements over the project lifecycle is important. Fact-finding should be done ethically without misusing sensitive information.

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses techniques for discovering requirements for new information systems. It covers key concepts like functional and non-functional requirements. Methods discussed include problem analysis using Ishikawa diagrams, observation, questionnaires, interviews, prototyping, and joint requirements planning sessions. Documentation of discovered requirements is also discussed. Managing changing requirements over the project lifecycle is important. Fact-finding should be done ethically without misusing sensitive information.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    457 views28 pages

    Chapter 6 - Fact-Finding Techniques

    Uploaded by

    morohen
    This document discusses techniques for discovering requirements for new information systems. It covers key concepts like functional and non-functional requirements. Methods discussed include problem analysis using Ishikawa diagrams, observation, questionnaires, interviews, prototyping, and joint requirements planning sessions. Documentation of discovered requirements is also discussed. Managing changing requirements over the project lifecycle is important. Fact-finding should be done ethically without misusing sensitive information.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    of 28

    Chapter 6: Fact-Finding Techniques for Requirement Discovery

    Key Concepts
     System Requirements  Functional and Nonfunctional Requirements  Problem Analysis - Ishikawa (fishbone) Diagram.  Fact-Finding Techniques.  Understand six guidelines for effective listening.  Joint Requirements Planning (JRP)
    2

    Introduction to Requirements Discovery


    Requirements discovery the process and techniques used by systems analysts to identify or extract system problems and solution requirements from the user community. System requirement something that the information system must do or a property that it must have. Also called a business requirement.
    3

    Functional vs. Nonfunctional Requirements


    unctional requirement - something the information system must do Nonfunctional requirement - a property or quality the system must have
      

    Performance Security Costs

    Results of Incorrect Requirements


     The system may cost more than projected.  The system may be delivered later than promised.  The system may not meet the users expectations

    and they may not to use it.  Once in production, costs of maintaining and enhancing system may be excessively high.  The system may be unreliable and prone to errors and downtime.  Reputation of IT staff is tarnished as failure will be perceived as a mistake by the team.
    5

    Relative Cost to Fix an Error

    Process of Requirements Discovery


     Problem discovery and analysis  Requirements discovery  Documenting and analyzing

    requirements  Requirements management

    Ishikawa Diagram
     Graphical tool used to identify, explore, and

    depict problems and the causes and effects of those problems. It is often referred to as a cause-and-effect diagram or a fishbone diagram.

    Ishikawa Diagram (Cont.)


     Problem at right (fish head)  Possible causes drawn as "bones" off main backbone  Brainstorm for 3-6 main categories of possible causes

    Requirements Discovery
     Given an understand of problems, the

    systems analyst can start to define requirements. act-finding the formal process of using research, meetings, interviews, questionnaires, sampling, and other techniques to collect information about system problems, requirements, and preferences. It is also called information gathering or data collection.
    10

    Documenting and Analyzing Requirements


     Documenting the draft requirements  Use cases  Decision tables  Requirements tables  Analyzing requirements to resolve problems  Missing requirements  Conflicting requirements  Infeasible requirements  Overlapping requirements  Ambiguous requirements  Formalizing requirements  Requirements definition document  Communicated to stakeholders or steering body
    11

    Sample Requirements Definition Report Outline

    12

    Requirements Management
    Requirements management - the process of managing change to the requirements.
    

    Over the lifetime of the project it is very common for new requirements to emerge and existing requirements to change. Studies have shown that over the life of a project as much as 50 percent or more of the requirements will change before the system is put into production.
    13

    Fact-Finding Ethics
     Fact-Finding often brings systems analysts into

    contact with sensitive information.


      

    Company plans Employee salaries or medical history Customer credit card, social security, or other information

     Ethical behavior  Systems analysts must not misuse information.  Systems analysts must protect information from people who would misuse it.

    14

    Seven Fact-Finding Methods


     Sampling of existing documentation, forms,

    and databases.  Research and site visits.  Observation of the work environment.  Questionnaires.  Interviews.  Prototyping.  Joint requirements planning (JRP).
    15

    Sampling Existing Documentation, Forms, & Files


    Sampling process of collecting a representative sample of documents, forms, and records.  Organization chart  Memos and other documents that describe the problem  Standard operating procedures for current system  Completed forms  Manual and computerized screens and reports  Samples of databases  Flowcharts and other system documentation  And more
    16

    Determining Sample Size for Forms


     Sample Size = 0.25 x (Certainty factor/Acceptable

    error) 2  Sample Size = 0.25(1.645/0.10) 2 = 68  Sample Size =0.10(1 0.10)(1.645/0.10)2 = 25


    Or if analyst knows 1 in 10 varies from norm. Certainty factor from certainty table. 10% acceptable error.

    17

    Sampling Techniques
     Randomization a sampling technique

    characterized by having no predetermined pattern or plan for selecting sample data.


    

    Stratification a systematic sampling technique that attempts to reduce the variance of the estimates by spreading out the samplingfor example, choosing documents or records by formulaand by avoiding very high or low estimates.
    18

    Observation
    Observation a fact-finding technique wherein the systems analyst either participates in or watches a person perform activities to learn about the system.
    Advantages? Disadvantages?

    Work sampling - a fact-finding technique that involves a large number of observations taken at random intervals.
    19

    Questionnaires
     Questionnaire a special-purpose document that

    allows the analyst to collect information and opinions from respondents. designed to offer the respondent greater latitude in the answer. A question is asked, and the respondent records the answer in the space provided after the question.

     Free-format questionnaire a questionnaire

     Fixed-format questionnaire a questionnaire

    containing questions that require selecting an answer from predefined available responses.
    20

    Types of Fixed-Format Questions


     Multiple-choice questions  Rating questions  Ranking questions
    Rank the following transactions according to the amount of time you spend processing them. ___ % new customer orders The implementation of quality discounts would ___ % order cancellations cause an increase in customer orders. ___ % order modifications ___ Strongly agree ___ % payments ___ Agree ___ No opinion Is the current accounts receivable ___ Disagree report that you receive useful? ___ Strongly disagree ___ Yes ___ No
    21

    Interviews
    Interview - a fact-finding technique whereby the systems analysts collect information from individuals through face-to-face interaction.
          

    Find facts Verify facts Clarify facts Generate enthusiasm Get the end-user involved Identify requirements Solicit ideas and opinions
    22

    Types of Interviews and Questions


    Unstructured interview conducted with only a general goal or subject in mind and with few, if any, specific questions. The interviewer counts on the interviewee to provide a framework and direct the conversation. Structured interview interviewer has a specific set of questions to ask of the interviewee. Open-ended question question that allows the interviewee to respond in any way. Closed-ended question a question that restricts answers to either specific choices or short, direct responses.

    23

    Prepare for the Interview


     Types of Questions to Avoid
      

    Loaded questions Leading questions Biased questions Use clear and concise language. Dont include your opinion as part of the question. Avoid long or complex questions. Avoid threatening questions. Dont use you when you mean a group of people.
    24

     Interview Question Guidelines


        

    Discovery Prototyping
    Discovery prototyping the act of building a small-scale, representative or working model of the users requirements in order to discover or verify those requirements.

    25

    Joint Requirements Planning


    Joint requirements planning (JRP) a process whereby highly structured group meetings are conducted for the purpose of analyzing problems and defining requirements.
    

    JRP is a subset of a more comprehensive joint application development or JAD technique that encompasses the entire systems development process.

    26

    Steps to Plan a JRP Session


    1.

    Selecting a location
      

    Away from workplace when possible Requires several rooms Equipped with tables, chairs, whiteboard, overhead projectors Needed computer equipment Each needs release from regular duties Briefing documentation Agenda distributed before each session
    27

    2. 3.

    Selecting the participants


    

    Preparing the agenda


     

    Typical Room Layout for JRP session

    28

    You might also like