Database develop. life cycle - Gathering User Requirements

To understand what end-users need from the database.
Ensures the system is designed around real-world tasks, not just technical assumptions.
Prevents costly redesigns later by clarifying needs upfront.

Primary Users: People who directly interact with the database (clerks, students, sales staff).
Secondary Users: Managers and analysts who use reports.
Technical Staff: DBAs, IT support who maintain the system.
Decision Makers: Executives who need high-level insights.

Interviews
- One-on-one or group discussions.
- Ask open-ended questions:
  - “What reports do you need regularly?”
  - “What’s most frustrating about the current system?”
Questionnaires/Surveys
- Useful when there are many users.
- Can collect both qualitative and quantitative data.
Observation (Job Shadowing)
- Watch users perform tasks.
- Helps uncover needs they may not articulate.
Document Analysis
- Review existing records, spreadsheets, forms, and reports.
- Shows what data is already collected and what’s missing.
Workshops / Focus Groups
- Bring multiple stakeholders together.
- Helps resolve conflicting requirements.
Prototyping
- Show a mockup or simple interface.
- Gather feedback and refine requirements.

Prepare: Identify user groups, choose techniques, design interview/survey questions.
Collect Requirements: Use multiple techniques to avoid blind spots.
Analyze: Look for patterns, contradictions, and priorities.
Document: Write clear, structured requirements (business, user, data, functional, non-functional).
Validate: Review with users to confirm accuracy and completeness.

For a Hospital Patient Database:

From doctors: “We need quick access to patient history during emergencies.”
From nurses: “We need a simple way to record daily observations.”
From administrators: “We need billing and insurance records linked with patient visits.”
From patients: “We want online access to lab results.”