Calculate Use Case Points (UCP) for software development work using Onshore's v4.0 complete coverage methodology...
Calculate Use Case Points for software development projects using Onshore's v4.0 complete work coverage methodology.
Minimal invocation:
"Calculate UCP for the Agent Studio Pro project. Input: git repository. Output: comprehensive UCP report."
With Azure DevOps:
"Calculate UCP from Azure DevOps User Stories for the Lighthouse project. Use references/azure-devops-hierarchy.md for work item guidance."
Using scripts:
python scripts/count_transactions.py "1. User enters credentials
2. System validates
3. System generates JWT
4. System returns token"
# Output: 3.6 transactions � Simple � 5 UUCW
python scripts/calculate_ucp.py --uaw 24 --uucw 562.4 --tcf 1.40 --ecf 0.86 --verbose
# Output: Realistic UCP: 494.22
Option A: Azure DevOps Work Items
references/azure-devops-hierarchy.md for guidanceOption B: Git Repository
references/git-repository-analysis.md for methodologyCount external entities that interact with the system:
Calculate UAW (Unadjusted Actor Weight):
UAW = (Simple � 1) + (Average � 2) + (Complex � 3)
v4.0 Complete Coverage - Count ALL work across 4 categories:
scripts/count_transactions.py for automationTransaction Counting Rules:
Classification:
Calculate UUCW per category:
Final UUCW = Base UUCW � Category Multiplier � (0.7 + 0.3 � SAF)
SAF (Specificity Adjustment Factor): Assess work item quality (0-1 scale)
references/saf-methodology.md for detailed rubricUUCP = UAW + Total UUCW (sum of all 4 categories)
Evaluate 13-20 technical factors (ratings 0-5):
Read references/tcf-factors.md for complete factor definitions and rating criteria.
TFactor = �(Rating � Weight)
TCF = 0.6 + (0.01 � TFactor)
TCF (capped) = min(TCF, 1.4)
Use scripts/calculate_ucp.py to automate:
python scripts/calculate_ucp.py --uaw 24 --uucw 562.4 --tcf 1.40 --ecf 0.86
Evaluate 8 environmental factors (ratings 0-5):
EFactor = �(Rating � Weight)
ECF = 1.4 + (-0.03 � EFactor)
Adjusted UCP = UUCP � TCF � ECF
Realistic UCP = Adjusted UCP � Framework Leverage Factor
(Framework Leverage: 0.6-1.0, typically 0.7 for framework-heavy projects)
Use assets/templates/ucp-report-template.md as structure.
Include:
v4.0 Complete Work Coverage: Unlike traditional UCP (50-60% coverage), v4.0 captures ALL development work across 4 categories with differentiated multipliers.
Specificity Adjustment Factor (SAF): Rewards high-quality specifications, reduces credit for vague requirements. Ranges 0.70x (no spec) to 1.00x (excellent spec).
Framework Leverage: Accounts for framework-provided functionality (FastAPI routing, SQLAlchemy ORM, etc.). Typically 0.7 for modern frameworks.
Azure DevOps Hierarchy:
Transaction Weighting:
scripts/count_transactions.py Parse acceptance criteria, count weighted transactions, classify complexity
python scripts/count_transactions.py --file user_story.txt --verbose
scripts/calculate_ucp.py Calculate UCP from UAW, UUCW, TCF, ECF
python scripts/calculate_ucp.py --uaw 24 --uucw 562.4 --tcf 1.40 --ecf 0.86 --framework-leverage 0.70
Generate comprehensive UCP Analysis Report with:
Section 1: Executive Summary (key metrics table) Section 2: Actor Summary (classification table, UAW calculation) Section 3: Work Item Analysis (4 categories, transaction counts, SAF scores, UUCW calculations) Section 4: SAF Distribution (quality assessment) Section 5: UUCP Calculation (UAW + UUCW) Section 6: TCF Assessment (factor ratings, TFactor, TCF formula) Section 7: ECF Assessment (factor ratings, EFactor, ECF formula) Section 8: UCP Calculation (Adjusted UCP, Framework Leverage, Realistic UCP) Section 9: Effort Estimation (productivity factor, estimated hours)
Include interpretations: What TCF/ECF values mean, accuracy notes, comparison to traditional UCP (v3.0 vs v4.0).
| Input Source | Accuracy | Speed | Use When |
|---|---|---|---|
| User Stories (Azure DevOps) | 95-98% | Fast | Work items available with acceptance criteria |
| Features (Azure DevOps) | 80-90% | Fast | No User Stories, apply 1.8x calibration |
| Git Repository | 95-98% | Slow | Retrospective analysis, 100% coverage needed |
| Mixed Sources | 85-95% | Medium | Some User Stories, some Features |
Pattern 1: Azure DevOps with User Stories
scripts/count_transactions.pyPattern 2: Azure DevOps with Features Only
references/azure-devops-hierarchy.mdPattern 3: Git Repository Analysis
references/git-repository-analysis.mdThis progressive disclosure keeps core instructions concise while making detailed reference material available when needed.