liveBook · Manning

Interview

As explained in Grokking Relational Database Design

An interview is a structured conversation for eliciting information from people about their work, requirements, or practices.

An interview is a planned conversation for discovering what a database must support. It is the most important task in requirement gathering because people reveal their goals, workflows, data, and reporting needs. section 3.15 section 3.16

Use this practical sequence when preparing and conducting interviews:

  • Group interviewees as stakeholders, subject-matter experts (SMEs), and IT or technical staff. section 3.15
  • Prepare questions for each group: goals and features for stakeholders; current data practices and workflows for SMEs; storage, retrieval, reports, and calculations for technical staff. section 3.15
  • During and after the conversations, record subjects, characteristics, and relationships. Subjects are people, places, things, or events; characteristics are their features. section 3.15 section 3.16
  • When interviews alone are not enough, ask an SME to demonstrate the process step by step and provide data samples for checking attributes and data types. section 3.14

Replacing an inventory spreadsheet

For The Sci-Fi Collective, interview more than the purchasing manager. Ask the purchasing team to walk through ordering a product, entering a new product, and updating or removing inventory records. The walkthrough exposes the real process, while sample records help verify the future database's attributes and data types. section 3.14

How Grokking Relational Database Design covers it

How deep it goes
Explains preparation, interviewee grouping, question design, findings to capture, and when demonstrations or data samples are needed.
Examples
Uses an inventory spreadsheet, purchasing workflow, product records, stakeholder questions, and SME process demonstrations.
What it assumes
Assumes a database-design project but defines subjects and characteristics from the beginning for inexperienced readers.
What you can do after
Apply interviews to identify database subjects, characteristics, relationships, workflows, goals, reports, and data-quality checks.
How it connects
Connects interviews to requirement gathering, database design, subject-matter expertise, subjects, characteristics, and relationships.

Also explained in

Compare how 7 books explain interview →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Relational Database Design. The section links point to the parts of the book it draws on.