The document discusses various methods for gathering requirements for information systems development projects, including interviews, questionnaires, observation, and joint application design (JAD) sessions. It provides details on each method, such as advantages and disadvantages of interviews, structured vs unstructured interviews, open vs closed questions, and roles in JAD sessions. The document also discusses characteristics of good requirements and different scales that can be used in questionnaires.

1. Categorization of Sample Types No Random Selection Random Selection No Specific Selection Criteria Applied Convenience Sample Simple Random Sample Specific Selection Criteria Applied Purposive Sample Complex Random Sample

2. Sample Business Form

3. IBID Electronic Whiteboard Source: http://www.microtouch.com/ibid/ibid100.htm

4. Requirements Determination Information Gathering Approach Examples Interview - current system operations - data needs - proposed system requirements - process sequences Questionnaire - confirmation of facts - end-user demographics - general user attitudes Focus Group - conflicting system requirements - synergies across functional areas Observation - implementation of current processes - confirmation of interview data Archival Document Analysis - Org. policies & procedures - current system documentation - examples of data capture & usage External Research - industry best-practices - technological developments Joint Application Design - synergistic gathering of system requirements - identification of conflicting perspectives Iterative Prototyping - refined understanding of system configuration - operationalization of system look and feel

5. Well-Stated System Requirements Requirements Characteristic Description Testable and Verifiable Requirement must be stated to allow for independent verification that the system meets or exceeds the stated requirement. Justifiable Requirement should be necessary rather than simply desirable. Unambiguous Requirement should be stated such that multiple interpretations are excluded. Consistent Requirement should not be in conflict with any other stated requirement. Modifiable Requirement should allow for changes in the business environment. Hierarchically Traceable Requirement should contain a single system attribute and should be traceable back to a higher level requirement.

6. Testable vs. Nontestable Testable Requirement Nontestable Requirement Compute Price Extension by multiplying Quantity by Unit Price . Price Extension is the total cost for each item ordered. Reorder Quantity is computed by multiplying Average Daily Sales by 30. Reorder Quantity should be equal to a 30 day supply. Daily inventory levels must be accurate. Daily inventory levels must be accurate to within 2% for at least 99% of all raw material stores. The system must increase sales and market share. The system will increase annual sales by 14% and current market share by 6.5% within the first 12 months of operation.

7. Traditional Information Gathering Information Gathering Activity Explanation Direct Interview Consists of meeting with individuals or small groups to ask questions about their roles, responsibilities, and needs for the current and proposed systems. Questionnaires and Surveys Consists of submitting written, structured questions to selected individuals to gather information regarding attitudes, perceptions, or population characteristics. Direct Observation Consists of observing individuals or groups, processes, and events to determine the facts surrounding a particular process or the culture within a business environment. Archival Document Analysis Consists of reviewing recorded organizational documents such as current system documentation, mission statements, policies and procedures, and recorded memos and reports. Forms Analysis Consists of analyzing and cataloging the existing data capture forms within the organization to assist in determining the current sources and uses of data.

9. Structured vs. Unstructured Variable Structured Interview Unstructured Interview Required preparation time High Low Required contact time with respondent Moderate High Analyst experience and training required High Low Evaluation of results and responses Easy Difficult Degree of spontaneity of responses Low High Depth and breadth of topic coverage Moderate High Reliability and precision of responses Moderate to High Low to Moderate Insight into respondent Low High Overall analyst control of dialogue High Low to Moderate Degree of flexibility of interaction Low High

10. Open vs. Closed Questions

11. Open vs. Closed Questions

13. Scaling Methods

14. Scaling Methods (continued)

15. Choosing the Appropriate Scale Scale Type General Application Nominal Classification without need for ranking Ordinal Classification with ranking but without need for equal intervals between ranks Interval Degree of presence of phenomena using equal intervals without need for absolute zero Ratio Degree of presence or absence of a phenomena

16. Confidence Coefficients Level of Confidence (%) Confidence Coefficient (z) 99 2.58 98 2.33 97 2.17 96 2.05 95 1.96 90 1.65 80 1.25 50 0.67