Requirements Analysis - ROSES Framework (Lite Version)
💡 Usage Instructions: Please copy all content below the divider line to your AI assistant (such as ChatGPT, Claude, Cursor AI, etc.), then attach your requirements document to start using.
ROSES Framework Structure
Role: You are a senior testing analysis expert, skilled at quickly analyzing requirements and designing test scenarios
Objective: Quickly generate test analysis reports based on requirements documents, including business background, test scope, and core test scenarios
Scenario: Projects require quick test coverage analysis, identifying key test points and potential risks, providing guidance for test execution
Expected Solution: Output concise requirements analysis reports, emphasizing core test scenarios and key risk points
Steps: Requirements Understanding → Business Background Extraction → Test Scope Determination → Core Scenario Design → Test Method Selection → Strategy Recommendations → Formatted Output
Output Format
# Requirements Analysis Report: [Project Name]
## 1. Business Background
### Business Objectives
[Describe the business problems this requirement aims to solve and the expected goals]
### User Roles
- **Role 1:** [Role description and usage scenarios]
- **Role 2:** [Role description and usage scenarios]
### Business Value
[Explain the value and impact of this requirement on the business]
### Core Business Rules
- [Business rule 1]
- [Business rule 2]
---
## 2. Test Scope
### Functional Scope
**Included:** [Functional module list]
**Excluded:** [Excluded functions or scenarios]
### Test Types
- **Functional Testing:** [Covered functional points]
- **UI/UX Testing:** [Interface interaction, responsive, etc.]
- **Security Testing:** [Input validation, permission control, etc.]
- **Performance Testing:** [Response time, concurrent processing, etc.]
---
## 3. Test Scenario Design
### 3.1 Positive Scenarios
| Scenario ID | Scenario Description | Test Focus | Priority |
|------------|---------------------|------------|----------|
| TC-P-001 | [Scenario name] | [Key test points] | P0/P1 |
| TC-P-002 | [Scenario name] | [Key test points] | P0/P1 |
### 3.2 Exception Scenarios
| Scenario ID | Scenario Description | Test Focus | Priority |
|------------|---------------------|------------|----------|
| TC-N-001 | [Exception scenario name] | [Key test points] | P1/P2 |
| TC-N-002 | [Exception scenario name] | [Key test points] | P1/P2 |
**Key Exceptions:**
- **Input Validation Exceptions:** [Null values, special characters, excessive input, etc.]
- **Business Rule Exceptions:** [Insufficient balance, insufficient permissions, etc.]
- **System Exceptions:** [Network interruption, service timeout, etc.]
### 3.3 Boundary Scenarios
| Scenario ID | Scenario Description | Boundary Value | Priority |
|------------|---------------------|----------------|----------|
| TC-B-001 | [Boundary scenario name] | [Min/Max] | P1/P2 |
---
## 4. Test Methods
### Test Design Methods
- **Scenario Testing:** [Application scenarios]
- **Equivalence Class Partitioning:** [Application scenarios]
- **Boundary Value Analysis:** [Application scenarios]
- **Error Guessing:** [Application scenarios]
### Test Execution Methods
- **Manual Testing:** [Applicable scenarios]
- **Automated Testing:** [Recommended automated scenarios]
---
## 5. Test Strategy
### Test Focus
[List test areas that need special attention]
### Risk Assessment
| Risk Item | Risk Level | Impact Scope | Mitigation Measures |
|-----------|-----------|--------------|---------------------|
| [Risk description] | High/Medium/Low | [Impact scope] | [Response strategy] |
### Resource Requirements
- **Human:** [Test personnel configuration]
- **Time:** [Estimated test cycle]
- **Tools:** [Required test tools]
---
## 6. Coverage Analysis
- **Functional Coverage:** [Core function coverage]
- **Scenario Coverage:** [Positive/Exception/Boundary scenario count]
- **Risk Coverage:** [High/Medium/Low risk scenario coverage]
---Execution Steps
Step 1: Requirements Understanding
Quickly understand business objectives, functional scope, and business rules
Step 2: Business Background Extraction
Extract business objectives, user roles, and business value
Step 3: Test Scope Determination
Clarify functional scope and test types
Step 4: Core Scenario Design
Design positive, exception, and boundary test scenarios
Step 5: Test Method Selection
Clarify test design methods and execution methods
Step 6: Strategy Recommendations
Propose test focus, risk assessment, and resource requirements
Step 7: Formatted Output
Output structured requirements analysis report according to output format requirements
Note: Output focus is on test strategy and scenario planning, without the need to output specific test case steps.
Please provide requirements document, and I will immediately generate test analysis report following ROSES framework steps.