Determine the purpose of the interview

Identify users to include in interviews

Prepare questions for interviews

Make arrangements for final interviews

Limit interview time

Look for exceptions and error situations

Dive into the details

Keep records carefully

The first task is to absorb, understand, and record the information obtained from the interview

Record the questions that the user cannot answer and arrange them for the next interview for confirmation.

Send an interview memo to the user to confirm the interviewee's contribution and confirm incorrect answers to questions

Good flexibility and wide range of applications

Difficulty coordinating user time

Interviews contain a large amount of information and are difficult to record

Adequate communication skills

Sufficient domain knowledge

Encountering confidential issues and sensitive topics

Structured (prepare a series of questions in advance and conduct them in a targeted manner)

Unstructured (only lists rough ideas, all based on on-the-spot performance)

In fact, the most effective is a combination of the two

Identify the problem and type

Writing questions

Design the format of the questionnaire

Collect data from large numbers of responses in a short time and at low cost

Anonymous filling is conducive to true answers

Easy to organize and count

Explain the purpose and use of the questionnaire

Explain the answer requirements

Please ask the relevant person in charge to urge you to fill in and return

Participate in customer meetings and answer questionnaires for information processing direction

Reduce questionnaire response time

Set prizes

Calculation formula: heuristic factor (α) * (confidence coefficient/acceptable error) * (confidence coefficient/acceptable error)

Speed ​​up data collection

Depends on subjective factors of the system analyst, relying on experience and ability

Use tools to explain to users how the system fits the business

passive

Active

interactive

Static tools, such as pen and paper, PPT, pictures, etc.

Dynamic tools, such as flash and other animation tools, etc.

The most vivid demand acquisition technology, user-friendly and highly interactive

High time cost and slow acquisition of demand

It is very effective for ambiguous problems and areas where the needs are least clear.

Meetings are difficult to organize and require high capabilities of relevant personnel

Higher cost, obvious effect

Particularly suitable for collecting and organizing information at the business activity level

Detailed descriptions of work scenarios and processes by users

Describe features that are valuable to users

content

User story cards in the form of handwritten

Basic properties

Requirements recording tool similar to task cards

User stories and Volere white cards are positioned as minimum requirements and are suitable for use in agile methods.

Selection principles

Refine, analyze, and carefully review the obtained requirements to ensure that all stakeholders understand and identify them Errors, omissions, deficiencies

Draw system context scope diagram

Create user prototype interface

Analyze feasibility of requirements

Prioritize needs

Model the requirements

Create data dictionary

Use QFD

ER diagram represents the data model

DFD represents functional model

STD stands for behavioral model

The core is the data dictionary

Unified Modeling Language UML

use case model

Analytical model

Emphasize more description and less modeling

Description composition

Analysis process

Basic assumptions

Suitable for the situation

An iterative, cyclical development approach

Issues that need attention

Write text-based documents with good structure and natural language

Build graphical models

Write formal specifications

scope

reference materials

need

Eligibility regulations

Requirements traceability

unresolved issues

annotation

appendix

Review

examine

Walkthrough

plan

Prepare

conduct review

Take action on review results

Hierarchical review

A combination of formal and informal reviews

Staged review

Carefully selected reviewers

Train reviewers

Establish a standard review process

Carry out follow-up work after the review

Be fully prepared for the review

Not enough users participating

User classification ignored

Increasing user demands

Ambiguous needs

unnecessary features

Overly streamlined SSR

inaccurate estimate