Requirement Analysis

Requirement Analysis

Kỹ năng quan trọng để hiểu và document requirements.

Types of Requirements

Functional Requirements

• Hệ thống làm GÌ
• User có thể làm GÌ
• Ví dụ: “User có thể đăng nhập bằng email/password”

Non-Functional Requirements

• Performance, security, usability
• Ví dụ: “Trang load trong < 2 seconds”

Gathering Techniques

1. Interviews - Nói chuyện trực tiếp với stakeholders
2. Surveys - Thu thập feedback từ nhiều users
3. Workshops - Group discussions
4. Observation - Xem users làm việc
5. Document Analysis - Review existing docs

Requirement Template

## Feature: User Login

### As a: User

### I want to: Login to my account

### So that: I can access my personalized content

### Acceptance Criteria:

-   [ ] User can login with email and password
-   [ ] Invalid credentials show error message
-   [ ] Successful login redirects to dashboard
-   [ ] Remember me option available

MoSCoW Prioritization

• Must have - Critical features
• Should have - Important but not critical
• Could have - Nice to have
• Won’t have - Out of scope

Best Practices

1. Ask “Why?” - Understand true needs
2. Be specific - Clear, measurable requirements
3. Document everything - Written records
4. Validate - Confirm with stakeholders
5. Prioritize - Focus on high value