a. Establishing the Need for a System:
- Objective: Understand why a system is needed.
- Requirement: A specific goal the system must achieve.
b. Product Description Development:
- Process: Creating and refining a description based on user or marketing input.
c. Techniques for Requirement Determination:
- Direct Methods: Interacting directly with users.
- Face-to-Face Interview: One-on-one discussion with a user.
- Telephone Interview or Survey: Structured phone conversation.
- Traditional Focus Group: Small group discussion with a moderator.
- Facilitated Team Workshop: Structured workshop with users.
- Observational Field Study: Observing users over time.
- Requirements Prototyping: Early demo for user feedback.
- User Interface Prototyping: Early design demo for UI feedback.
- Usability Laboratory Testing: Observing users in a controlled lab.
- Card Sorting for Websites: Organizing web content collaboratively.
- Indirect Methods: Using intermediaries between users and developers.
- MIS Intermediary: Company representative defines user goals.
- Paper Survey or Questionnaire: Traditional mail for user input.
- Electronic Survey or Questionnaire: Email or web-based surveys.
- Electronic Focus Group: Online group discussion with a moderator.
- Marketing and Sales: Representatives gather suggestions from customers.
- Support Line: Analyzing customer support data for insights.
- E-Mail or Bulletin Board: Analyzing user feedback through email or forums.
- User Group: Customer groups provide suggestions periodically.
- Competitor Analyses: Studying competitors for ideas and requirements.
- Trade Show: Gathering feedback from customers at trade shows.
- Other Media Analysis: Studying how other media present information.
- System Testing: Obtaining new requirements and feedback during product testing.