Back to Details

requirements-analysis

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Requirements Analysis

需求分析

Requirement Types

需求类型

Functional Requirements

功能性需求

What the system should DO.
  • "Users can log in with email and password"
  • "System sends order confirmation email"
系统应实现的功能。
  • "Users can log in with email and password"
  • "System sends order confirmation email"

Non-Functional Requirements

非功能性需求

How the system should BEHAVE.
  • Performance: "Page loads in < 2 seconds"
  • Security: "Passwords stored with bcrypt"
  • Scalability: "Supports 10,000 concurrent users"
系统应具备的特性。
  • Performance: "页面加载时间< 2秒"
  • Security: "密码使用bcrypt存储"
  • Scalability: "支持10,000并发用户"

Constraints

约束条件

Limitations on the solution.
  • "Must use existing authentication system"
  • "Must run on AWS"
解决方案的限制条件。
  • "必须使用现有认证系统"
  • "必须部署在AWS上"

Analysis Techniques

分析技巧

Ask "Why?" Five Times

五次“为什么”提问法

Uncover the real requirement.
Requirement: "Add export to Excel button"
Why? → "Users need to share reports"
Why? → "Finance reviews monthly sales"
Why? → "They compare against targets"
Why? → "To identify underperforming regions"
Real Need: Regional performance dashboard
挖掘真实需求。
Requirement: "Add export to Excel button"
Why? → "Users need to share reports"
Why? → "Finance reviews monthly sales"
Why? → "They compare against targets"
Why? → "To identify underperforming regions"
Real Need: Regional performance dashboard

SMART Criteria

SMART 准则

Requirements should be:
  • Specific: Clear and unambiguous
  • Measurable: Can verify completion
  • Achievable: Technically feasible
  • Relevant: Aligned with goals
  • Time-bound: Has deadline
需求应满足：
  • S具体：清晰明确，无歧义
  • M可衡量：可验证完成情况
  • A可实现：技术上可行
  • R相关性：与目标一致
  • T时限性：具备截止日期

Edge Case Analysis

边缘场景分析

  • What happens with no data?
  • What happens with too much data?
  • What if the user is offline?
  • What if permissions are denied?
  • 无数据时会发生什么？
  • 数据过多时会发生什么？
  • 用户离线时会怎样？
  • 权限被拒绝时会怎样？

Requirement Validation

需求验证

  • Is it testable?
  • Is it achievable?
  • Is it necessary?
  • Is it consistent with other requirements?
  • Is it complete?
  • Is the priority clear?
  • 是否可测试？
  • 是否可实现？
  • 是否必要？
  • 是否与其他需求一致？
  • 是否完整？
  • 优先级是否明确？

Documenting Requirements

需求文档撰写

markdown
**REQ-001**: User Authentication

**Description**: Users must authenticate to access the system.

**Acceptance Criteria**:
1. Given valid credentials, user gains access
2. Given invalid credentials, user sees error
3. After 5 failed attempts, account is locked

**Priority**: Must Have
**Dependencies**: REQ-002 (User Management)
markdown
**REQ-001**: 用户认证

**描述**: 用户必须通过认证才能访问系统。

**验收标准**:
1. 给定有效凭据，用户获得访问权限
2. 给定无效凭据，用户看到错误提示
3. 5次失败尝试后，账户被锁定

**优先级**: Must Have
**依赖项**: REQ-002 (User Management)