IT7001_Week4_02-Information Gathering-V2 (2).pdf

Introduction to Information Gathering Information Gathering • Techniques used to identify problems and requirements • Also called: – Requirements discovery – Fact-finding – Data collecting System Requirement • What the information system must do • A property that the information system must have. T...

Introduction to Information Gathering Information Gathering • Techniques used to identify problems and requirements • Also called: – Requirements discovery – Fact-finding – Data collecting System Requirement • What the information system must do • A property that the information system must have. Types of Requirements • Functional Requirements • Non-Functional Requirements Functional Vs Non-Functional requirements What is the difference between functional and non functional requirements? • Functional requirements explain how the system must work, while non functional requirements explain how the system should perform Functional Non-Functional Functional requirements help to understand the They help to understand the system's performance. functions of the system. Functional requirements are mandatory. While non-functional requirements mandatory, but desirable. are not They are easy to define. They are hard to define. They describe what the product does. They describe the working of product. It concentrates on the user's requirement. It concentrates on the expectation and experience of the user. It helps us to verify the software's functionality. It helps us to verify the software's performance. These requirements are specified by the user. These requirements are specified by the software developers, architects, and technical persons. What Happens When the Requirements are Incorrect?       The system may cost more than projected. The system may be delivered later than promised. The system may not meet the users’ expectations The costs of maintaining the system may be higher than projected. The system may be unreliable Etc. Relative Cost to Fix an Error Requirements Discovery Process Identify and analyse problems (we talked about that last week in problem analysis)  Discover requirements  Document and analyse requirements  Manage requirements  Problem Identification and Analysis Tools / Templates: ▪ Ishikawa diagram (see Figure 1) ▪ Problems, Opportunities, Objectives and Constraints Matrix (see the next slide) Figure 1 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 includes: ▪ Systems analysts must not misuse that information. ▪ Systems analysts must protect that information from people who would misuse it. Seven Fact-Finding Methods ▪ Sampling of existing documentation, forms, and databases ▪ Research and site visits ▪ Observation of the work environment ▪ Questionnaires ▪ Interviews ▪ Prototyping ▪ Joint Application Development (JAD) Sampling Sampling – the process of collecting a representative sample of documents, forms, and records.  Organisational chart  Memos and other documents that describe the problem  Standard operating procedures for current system  Completed forms  Manuals and computerised screens and reports  Samples of databases  Flowcharts and other system documentation Sampling of Completed Forms ▪ Helps to determine the type of data going into each blank ▪ Helps to determine the size of data going into each blank ▪ Helps to determine which blanks are not used or rarely used ▪ Helps to see data relationships Sampling of Existing Documentation, Forms and Files ▪ Determining the sample size: ▪ Desired certainty 90% → Certainty factor 1.645 ▪ Acceptable error: 100%-90% = 10% or 0.10 ▪ Sample Size = 0.25 (Certainty factor / Acceptable error)2 ▪ Sample Size = 0.25 (1.645 / 0.10) 2 = 68 Observation A fact-finding technique of watching people performing their activities to learn about the system. ▪ Advantages? ▪ Disadvantages? Observation Guidelines ▪ Determine the who, what, where, when, why, and ▪ ▪ ▪ ▪ ▪ ▪ ▪ how of the observation. Obtain permission from appropriate supervisors or managers. Inform those who will be observed of the purpose of the observation. Take notes during or immediately following the observation. Review observation notes with appropriate individuals. Don't interrupt the individuals at work. Don't focus heavily on trivial activities. Don't make assumptions. Questionnaires Questionnaire – a special-purpose document that allows the analyst to collect information and opinions from respondents.  Advantages?  Disadvantages? Free-format questionnaire – gives a freedom to the respondent to elaborate the answer. Fixed-format questionnaire – containing questions that require selecting an answer from predefined answers. Types of Fixed-Format Questions ▪ Multiple-choice questions ▪ Rating questions ▪ Ranking questions Developing a Questionnaire Determine what facts to collect and from whom 2. Determine the format ▪ Free- format, or ▪ Fixed-format 3. Write questions 4. Test questions on a small group of people 5. Distribute the questionnaire 1. Interviews A technique of collecting facts from individuals based on faceto-face meetings. ▪ Can be used to: ▪ Find facts ▪ Verify facts ▪ Clarify facts ▪ Generate enthusiasm ▪ Get the end-user involved ▪ Identify requirements ▪ Solicit ideas and opinions ▪ Advantages? ▪ Disadvantages? The personal interview is the most important and most often used fact-finding technique. Types of Interviews Unstructured interview Not planned in detail: conducted to get a general picture on subject. Structured interview Everything is planed in details: a specific set of questions, their order and timing. Types of Interview Questions Open-ended question – a question that allows the interviewee to respond in any way that seems appropriate. Example 1. What do you like the most about iPhone? What do you like the least? How does it compare to your existing mobile phone? Closed-ended question – a question that restricts answers to either specific choices or short, direct responses. Example 2. Did you ever use Microsoft Word? Did you find it hard to use? Have you checked your IT7001 Timetable? Interview Procedure 1. Select Interviewees ▪ For example, end users ▪ Learn about the interviewee prior to the interview 2. Prepare for the Interview ▪ Have an interview guide (see next slide) 3. Conduct the Interview ▪ Summarise the problem ▪ Offer an incentive for participation ▪ Ask the interviewee for assistance 4. Follow Up on the Interview ▪ Send a letter that summarises the interview Interview Questions ▪ Types of Questions to Avoid ▪ ▪ Loaded questions (e.g. “Should a smack as part of good parental correction be a criminal offence in New Zealand?”) ▪ Leading questions (e.g. “You are not going to use that program, are you?”) ▪ Biased questions (e.g. “Don’t you agree that the new policy is a problem?”) Interview Question Guidelines ▪ Use clear and concise language. ▪ Don’t include your opinion as part of the question. ▪ Avoid long or complex questions. ▪ Avoid threatening questions. ▪ Don’t use “you” when you mean a group of people. Interviewing Do’s and Don’ts Do • • • • • • • • • • Dress appropriately Be courteous Listen carefully Maintain control of the interview Probe Observe mannerisms and nonverbal communication Be patient Keep interviewee at ease Maintain self-control Finish on time Don’t • • • • • • • Assume an answer is finished or leading nowhere Reveal verbal and nonverbal clues Use jargon Reveal personal biases Talk more than listen Assume anything about the topic or the interviewee Tape record (take notes instead) Communicating with the User Guidelines for Communicating ▪ Approach the session with a positive attitude ▪ Make the other person feels comfortable ▪ Show that you are listening ▪ Ask questions ▪ Don’t assume anything ▪ Take notes “To hear is to recognise that someone is speaking, to listen is to understand what the speaker wants to communicate.” (Gildersleeve – 1978) Body Language and Proxemics Body language – the nonverbal information we communicate.  Facial disclosure  Eye contact  Posture Proxemics – the relationship between people and the space around them.  Intimate zone—closer than 1.5 feet  Personal zone—from 1.5 feet to 4 feet  Social zone—from 4 feet to 12 feet  Public zone—beyond 12 feet Discovery Prototyping The act of building a small-scale, representative or working model of the system requirements in order to discover or verify those requirements. ▪ Advantages? ▪ Disadvantages? Joint Application Development ▪ A technique used to expedite the discovery of system requirements. ▪ Group meetings are conducted for the purpose of analysing problems and defining requirements. JAD Participants ▪ Sponsor ▪ Facilitator (JAD Session Leader) ▪ Users and Managers ▪ Scribes ▪ IT Staff Steps to Plan a JAD Session Selecting a location  Away from workplace when possible  Equipped with tables, chairs, whiteboard, overhead projectors and computers Selecting the participants  Each needs release from regular duties Preparing the agenda  Briefing documentation  Agenda distributed before each session Guidelines for Conducting a JAD Session ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ Do not unreasonably deviate from the agenda Stay on schedule Ensure that the scribe is able to take notes Avoid the use of technical jargon Apply conflict resolution skills Allow for ample breaks Encourage group consensus Encourage user and management participation without allowing individuals to dominate the session Make sure that attendees abide by the established ground rules for the session Brainstorming JAD sessions generate possible ideas to solve a problem. ▪ Brainstorming is a common approach used to encourage participants to offer as many ideas as possible in a short period of time without any analysis until all the ideas have been exhausted. Benefits of JAD ▪ JAD actively involves users and management in the development project ▪ JAD reduces the amount of time required to develop systems. A Fact-Finding Strategy 1. 2. 3. 4. 5. 6. Learn from existing documents, forms, reports, and files Observe the system in action, if appropriate. Design and distribute questionnaires to clear up what is not understood Conduct interviews Build discovery prototypes for any functional requirements, when needed. Follow up to verify facts