sysd-critical-flows-a985cc0d3a-done-criteria.yaml
このページは
docs/ja/projects/prj-0001/execution/grade/criteria/sysd-critical-flows-a985cc0d3a-done-criteria.yamlから生成された表示用ページです。正本は YAML ファイルであり、このページは再生成できます。
yaml
# yaml-language-server: $schema=../../../../../../specdojo/schemas/v1/grade-done-criteria.schema.yaml
id: sysd-critical-flows-grade-criteria
document: sysd-critical-flows
path: docs/ja/product/040-system-design/sysd-critical-flows.md
graded_at: "2026-10-20T16:30:10.182Z"
graded_by: flash-high-executor
content_hash: 4b6b566dcca2287d98b1d520831f6263c2f92873c1a9bfaf4becaf7b72ff10ae
summary:
satisfied: 0
unsatisfied: 5
total: 5
criteria:
- id: DC-001
text: 重要フローの選定理由と業務影響が確認できること
roles:
- BA
viewpoint: vp-ba-business-value
status: unsatisfied
reason: Selection rationale comparing other candidates and concrete business impacts when issues occur are not identified.
- id: DC-002
text: 重要フローの内容を承認できること
roles:
- PO
viewpoint: vp-po-decision-readiness
status: unsatisfied
reason: >-
Decision criteria, open items, business impacts, approvers, and conditions for finalizing reference values are
missing.
- id: DC-003
text: フローの境界・永続化点・再実行性・失敗時挙動が定義されていること
roles:
- ARC
viewpoint: vp-arc-technical-constraints
status: unsatisfied
reason: >-
System and service boundaries, synchronization boundaries, and exact failure recovery constraints are not
sufficiently defined.
- id: DC-004
text: 重要フローのテストシナリオ設計に活用できること
roles:
- QE
viewpoint: vp-qe-verifiability
status: unsatisfied
reason: >-
Concrete test IDs, file paths, test commands, inputs, and expected outcomes are not provided for designing test
scenarios.
- id: DC-005
text: フロー実装の共通理解として参照できること
roles:
- DEV
viewpoint: vp-dev-implementation-readiness
status: unsatisfied
reason: >-
Implementation target files, schema, configuration keys, concrete limits, and input/output constraints are not
uniquely traceable.