Functional Use Case Introduction
Functional use casesare the "quality specifications" of software—they clearly describe how the system should work and how to verify it works correctly.
AngusTester transforms use case management from document piles into living guidelines, helping teams improve testing efficiency by 50% and reduce requirement misunderstandings by 70%!
What Are Functional Use Cases? The Blueprint for Quality
Functional use cases are specific operational guides describing how software features work, including:
Simplified Explanation:
- Like an appliance user manual
- Like a game walkthrough
- Like an experimental procedure
Core Elements:
Six Core Values: Assurance from Requirements to Delivery
1. Clear Functional Specifications – Eliminate Misunderstandings
User Story → Functional Use Case
2. Efficient Test Execution – Standardized Operations
Test Checklist:
markdown
✅ Enter correct username
✅ Enter correct password
✅ Click login button
✅ Verify homepage redirect
✅ Verify login info display3. Version Control – Track Change History
Use Case Change Tracking:
4. Precise Accountability – Define Quality Ownership
Role Assignment Matrix:
| Use Case Element | Owner | Collaborator |
|---|---|---|
| Requirement Definition | Product Manager | Dev + QA |
| Use Case Writing | QA Engineer | Dev + Product |
| Use Case Execution | QA Engineer | - |
| Bug Fixing | Developer | QA Verification |
5. Intelligent Risk Assessment – Optimize Test Coverage
Risk Use Case Identification System:
6. Knowledge Retention – Onboard New Members Quickly
Use Case Reuse Center:
markdown
[Payment Use Case Library]
├── WeChat Pay.ATC
├── Alipay.ATC
├── Bank Card Pay.ATC
└── Apple Pay.ATCAngusTester Use Case Management: Three Steps to Create Efficient Use Cases
Step 1: Smart Use Case Design
Design Tips:
- 📌 Use active voice: "The system shall display..."
- 📌 Executable steps: "Click instead of select"
- 📌 Verifiable results: "Show green checkmark icon"
Step 2: Multi-Dimensional Use Case Management
Four Views for Collaboration:
Step 3: Automated Execution & Validation
Execution Pipeline:
Functional Use Case Lifecycle Management
1. Requirement Conception Phase
2. Development & Validation Phase
Developer Reference Guide:
markdown
## User Registration Use Case
**Precondition**: Registration page is open
**Steps**:
1. Enter valid email
2. Enter compliant password
3. Check user agreement
4. Click register button
**Expected Results**:
- Display "verification email sent"
- User receives activation email3. Test Execution Phase
Execute Test Case:
4. Delivery & Maintenance Phase
Use Case Optimization Mechanism:
Team Use Case Collaboration Platform
Real-Time Collaboration Features
Permission Management System
| Role | Use Case Permissions | Typical Actions |
|---|---|---|
| QA Engineer | Create/Edit/Execute | Write use cases, execute tests |
| Developer | View/Comment | Clarify requirements, confirm defects |
| Product Manager | Approve/Baseline | Confirm business accuracy |
| External Collaborator | Restricted View | Provide feedback |
Smart Analytics Hub
Use Case Quality Radar Chart:
| Quality Dimension | Current Score | Industry Std | Visual | Gap Analysis |
|---|---|---|---|---|
| Executability | 0.8 | 0.7 | ████████████░░ (8/10) | +14% above industry |
| Verifiability | 0.9 | 0.7 | ████████████▓░ (9/10) | +29% above industry |
| Completeness | 0.7 | 0.7 | █████████░░░░ (7/10) | Meets industry standard |
| Maintainability | 0.6 | 0.7 | ██████░░░░░░ (6/10) | -14% below industry |
| Readability | 0.8 | 0.7 | ████████████░░ (8/10) | +14% above industry |
Evaluation Summary:
- ✅ Excellent executability & verifiability
- ⚠️ Maintainability needs improvement
- 🔄 Completeness & readability meet standards
Use Case Field Information
| Parameter | Field Name | Type | Required | Length Limit | Description |
|---|---|---|---|---|---|
| ID | id | bigint | Conditional | / | Unique identifier; required for modifications |
| Use Case Name | name | string | Yes | ≤400 | Functional description |
| Plan ID | planId | long | Yes | / | Linked test plan ID |
| Module ID | moduleId | long | No | / | Functional module ID |
| Software Version | softwareVersion | string | No | ≤40 | Target version |
| Priority | priority | enum | No | / | See Priority |
| Deadline | deadlineDate | datetime | Yes | / | Execution deadline |
| Estimated Effort | evalWorkload | bigdecimal | No | / | Estimated effort |
| Precondition | precondition | string | No | ≤2000 | Execution preconditions |
| Step View | stepView | enum | No | / | See Step View |
| Test Steps | steps | list | No | / | Step list (max 100 steps) |
| Description | description | string | No | ≤2000 | Detailed description |
| Developer ID | developerId | long | Yes | / | Linked developer ID |
| Tester ID | testerId | long | Yes | / | Linked tester ID |
| Tag Set | tagIds | set | No | / | Tag ID collection |
| Attachments | attachments | list | No | / | Related files |
| Linked Tasks | refTaskIds | set | No | / | Linked task IDs |
| Linked Use Cases | refCaseIds | set | No | / | Linked use case IDs |
| Use Case Code | code | string | Read-only | / | Auto-generated unique code |
| Version | version | int | Read-only | / | Version number |
| Project ID | projectId | long | Read-only | / | Project ID |
| Plan Name | planName | string | Read-only | / | Linked plan name |
| Plan Auth Status | planAuth | boolean | Read-only | / | Whether plan has permission control |
| Module Name | moduleName | string | Read-only | / | Module name |
| Overdue Status | overdue | boolean | Read-only | / | Whether execution is overdue |
| Effort Estimation Method | evalWorkloadMethod | enum | Read-only | / | See Effort Estimation Method |
| Actual Effort | actualWorkload | bigdecimal | Read-only | / | Actual effort consumed |
| Review Status | review | boolean | Read-only | / | Whether reviewed |
| Reviewer ID | reviewerId | long | Read-only | / | Reviewer ID |
| Reviewer Name | reviewerName | string | Read-only | / | Reviewer name |
| Review Time | reviewDate | datetime | Read-only | / | Review timestamp |
| Review Status | reviewStatus | enum | Read-only | / | See Review Status |
| Review Notes | reviewRemark | string | Read-only | / | Review comments |
| Review Count | reviewNum | int | Read-only | / | Total reviews |
| Failed Reviews | reviewFailNum | int | Read-only | / | Failed review count |
| Tester Name | testerName | string | Read-only | / | Tester name |
| Developer Name | developerName | string | Read-only | / | Developer name |
| Unplanned Flag | unplanned | boolean | Read-only | / | Whether unplanned |
| Test Count | testNum | int | Read-only | / | Total test executions |
| Failed Tests | testFailNum | int | Read-only | / | Failed test count |
| Test Result | testResult | enum | Read-only | / | See Test Result |
| Test Notes | testRemark | string | Read-only | / | Test result comments |
| Result Handling Time | testResultHandleDate | datetime | Read-only | / | Result processing time |
| Tag Details | tags | list | Read-only | / | Tag info list |
| Linked Task Info | refTaskInfos | list | Read-only | / | Linked task details |
| Linked Use Case Info | refCaseInfos | list | Read-only | / | Linked use case details |
| All Versions | allVersionCaseVos | map | Read-only | / | Historical version data |
| Progress Info | progress | object | Read-only | / | Execution progress |
| Favorite Status | favourite | boolean | Read-only | / | Whether favorited |
| Follow Status | follow | boolean | Read-only | / | Whether followed |
| Comment Count | commentNum | int | Read-only | / | Comment count |
| Activity Count | activityNum | int | Read-only | / | Activity log count |
| Tenant ID | tenantId | long | Read-only | / | Tenant ID |
| Creator ID | createdBy | long | Read-only | / | Creator ID |
| Creator Name | createdByName | string | Read-only | / | Creator name |
| Creator Avatar | avatar | string | Read-only | / | Creator avatar URL |
| Creation Time | createdDate | datetime | Read-only | / | Creation timestamp |
| Last Modifier ID | lastModifiedBy | long | Read-only | / | Last modifier ID |
| Last Modifier Name | lastModifiedByName | string | Read-only | / | Last modifier name |
| Last Modified Time | lastModifiedDate | datetime | Read-only | / | Last modification time |
Test Steps (steps)
Data Structure:
json
[
{
"step": "Enter username and password",
"expectedResult": "Login successful"
},
{
"step": "Click payment button",
"expectedResult": "Redirect to payment page"
}
]Step View (stepView)
| Mode | Display Format |
|---|---|
TABLE | Table View – Steps in tabular format |
TEXT | Text View – Steps in plain text |
Priority (priority)
| Value | Description |
|---|---|
HIGHEST | Highest – Extremely urgent, must be handled immediately |
HIGH | High – Important, prioritize to ensure project progress/quality |
MEDIUM | Medium – Moderate importance, handle as planned |
LOW | Low – Lower importance, handle later |
LOWEST | Lowest – Minimal importance, handle during spare time |
Effort Estimation Method (evalWorkloadMethod)
| Value | Description |
|---|---|
WORKING_HOURS | Hours Estimation – Effort in actual working hours |
STORY_POINT | Story Points – Agile complexity-based estimation |
Review Status (reviewStatus)
| Value | Description |
|---|---|
PENDING | Pending Review – Not yet reviewed |
PASSED | Approved – Review passed |
FAILED | Rejected – Review failed, requires modifications |
Test Result (testResult)
| Value | Description |
|---|---|
PENDING | Pending – Test not executed |
PASSED | Passed – Test succeeded |
NOT_PASSED | Failed – Test did not meet expectations |
BLOCKED | Blocked – Test cannot proceed |
CANCELED | Canceled – Test was canceled |