specdojo 0.1.0 → 0.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +22 -0
- package/README.md +82 -38
- package/dist/agent-response.js +27 -0
- package/dist/agent.js +124 -0
- package/dist/build-command.js +149 -0
- package/dist/build-if-stale.js +35 -0
- package/dist/catalog-build.js +1079 -0
- package/dist/catalog-generate.js +226 -0
- package/dist/catalog-paths.js +31 -0
- package/dist/catalog-plan-generate.js +301 -0
- package/dist/catalog-plan-prompt.js +73 -0
- package/dist/catalog-plan.js +471 -0
- package/dist/catalog-scaffold.js +255 -0
- package/dist/catalog-types.js +4 -0
- package/dist/catalog.js +606 -0
- package/dist/dashboard.js +980 -0
- package/dist/deliverable-trash.js +148 -0
- package/dist/deliverable.js +97 -0
- package/dist/dist-freshness.js +150 -0
- package/dist/doc-index.js +424 -0
- package/dist/exec-agent-config.js +172 -0
- package/dist/exec-agent-git-state.js +136 -0
- package/dist/exec-agent-protected-config.js +276 -0
- package/dist/exec-events.js +250 -112
- package/dist/exec-evidence.js +317 -0
- package/dist/exec-format.js +45 -0
- package/dist/exec-limit.js +202 -0
- package/dist/exec-parent-validation.js +169 -0
- package/dist/exec-pipeline-state.js +160 -0
- package/dist/exec-plans.js +1016 -0
- package/dist/exec-project.js +25 -11
- package/dist/exec-protection-handoff.js +169 -0
- package/dist/exec-provider-scaffold.js +99 -0
- package/dist/exec-register-resume.js +196 -0
- package/dist/exec-register.js +281 -0
- package/dist/exec-reporter.js +329 -0
- package/dist/exec-results.js +510 -0
- package/dist/exec-run-lock.js +149 -0
- package/dist/exec-run.js +4953 -0
- package/dist/exec-schedule-calendar.js +86 -9
- package/dist/exec-schedule-cpm.js +30 -12
- package/dist/exec-schedule-gantt-chart-render.js +428 -0
- package/dist/exec-schedule-gantt-chart-scope.js +111 -0
- package/dist/exec-schedule-gantt-chart.js +2 -0
- package/dist/exec-schedule-hash.js +34 -25
- package/dist/exec-schedule-index.js +200 -67
- package/dist/exec-schedule-initial.js +100 -0
- package/dist/exec-schedule-progress.js +51 -26
- package/dist/exec-schedule-ready.js +71 -27
- package/dist/exec-schedule.js +171 -93
- package/dist/exec-shared.js +146 -25
- package/dist/exec-strategy.js +547 -0
- package/dist/exec-task-view.js +64 -0
- package/dist/exec-trial.js +895 -0
- package/dist/exec-worktree-command.js +426 -0
- package/dist/exec-worktree-ops.js +847 -0
- package/dist/exec-worktree.js +359 -0
- package/dist/exec.js +744 -192
- package/dist/frontmatter-namespace.js +48 -0
- package/dist/git-environment.js +23 -0
- package/dist/grade-result.js +137 -0
- package/dist/grade.js +2456 -0
- package/dist/index-command.js +103 -0
- package/dist/job.js +1081 -0
- package/dist/kata-command.js +303 -0
- package/dist/kata.js +187 -0
- package/dist/package-paths.js +15 -0
- package/dist/practice-id.js +24 -0
- package/dist/register-date.js +122 -0
- package/dist/register-events.js +363 -0
- package/dist/register-history.js +323 -0
- package/dist/register-item.js +455 -0
- package/dist/register-migrate-timestamps.js +176 -0
- package/dist/register.js +2199 -0
- package/dist/review-plan.js +199 -0
- package/dist/review-types.js +1 -0
- package/dist/role-types.js +1 -0
- package/dist/routine.js +814 -0
- package/dist/schedule-approach.js +252 -0
- package/dist/schedule-build.js +552 -0
- package/dist/schedule-phase-sets.js +73 -0
- package/dist/schedule-strategy-generate.js +812 -0
- package/dist/schedule-strategy-profiles.js +276 -0
- package/dist/schedule.js +420 -0
- package/dist/spawn-self.js +28 -0
- package/dist/specdojo-config.js +133 -39
- package/dist/specdojo.js +55 -7
- package/dist/template-frontmatter.js +89 -0
- package/dist/template-resolution.js +92 -0
- package/dist/timeline-build.js +334 -0
- package/dist/timeline.js +107 -0
- package/dist/watch.js +313 -0
- package/dist/yaml-pages-command.js +28 -0
- package/dist/yaml-pages.js +180 -0
- package/dist/yaml-schema-modeline.js +49 -0
- package/docs/ja/specdojo/defaults/pm-review-viewpoints.yaml +600 -0
- package/docs/ja/specdojo/exec-templates/xep-bootstrap-template.md +120 -0
- package/docs/ja/specdojo/exec-templates/xep-common-conventions-template.md +37 -0
- package/docs/ja/specdojo/exec-templates/xep-cross-deliverable-dedup-template.md +51 -0
- package/docs/ja/specdojo/exec-templates/xep-freeform-template.md +74 -0
- package/docs/ja/specdojo/exec-templates/xep-fully-guided-template.md +109 -0
- package/docs/ja/specdojo/exec-templates/xep-job-template.md +43 -0
- package/docs/ja/specdojo/exec-templates/xep-recipe-guided-template.md +82 -0
- package/docs/ja/specdojo/exec-templates/xep-recipe-maintenance-template.md +86 -0
- package/docs/ja/specdojo/exec-templates/xep-register-investigate-template.md +42 -0
- package/docs/ja/specdojo/exec-templates/xep-register-template.md +49 -0
- package/docs/ja/specdojo/exec-templates/xep-retrofit-template.md +98 -0
- package/docs/ja/specdojo/exec-templates/xep-rulebook-maintenance-template.md +86 -0
- package/docs/ja/specdojo/exec-templates/xep-sample-maintenance-template.md +86 -0
- package/docs/ja/specdojo/exec-templates/xep-template-maintenance-template.md +86 -0
- package/docs/ja/specdojo/exec-templates/xep-template.md +66 -0
- package/docs/ja/specdojo/exec-templates/xer-cross-deliverable-dedup-template.md +31 -0
- package/docs/ja/specdojo/exec-templates/xer-human-bootstrap-finalize-template.md +40 -0
- package/docs/ja/specdojo/exec-templates/xer-human-finalize-template.md +30 -0
- package/docs/ja/specdojo/exec-templates/xer-template.md +19 -0
- package/docs/ja/specdojo/exec-templates/xrp-freeform-template.md +70 -0
- package/docs/ja/specdojo/exec-templates/xrp-fully-guided-template.md +97 -0
- package/docs/ja/specdojo/exec-templates/xrp-recipe-guided-template.md +76 -0
- package/docs/ja/specdojo/exec-templates/xrp-recipe-maintenance-template.md +73 -0
- package/docs/ja/specdojo/exec-templates/xrp-retrofit-template.md +74 -0
- package/docs/ja/specdojo/exec-templates/xrp-rulebook-maintenance-template.md +74 -0
- package/docs/ja/specdojo/exec-templates/xrp-sample-maintenance-template.md +73 -0
- package/docs/ja/specdojo/exec-templates/xrp-template-maintenance-template.md +73 -0
- package/docs/ja/specdojo/exec-templates/xrp-template.md +67 -0
- package/docs/ja/specdojo/exec-templates/xrp-viewpoint-detail-template.md +7 -0
- package/docs/ja/specdojo/exec-templates/xrr-template.md +21 -0
- package/docs/ja/specdojo/exec-templates/xrr-viewpoint-detail-template.md +7 -0
- package/docs/ja/specdojo/guides/branch-workflow-guide.md +354 -0
- package/docs/ja/specdojo/guides/docs-editing-guide.md +327 -0
- package/docs/ja/specdojo/guides/docs-structure-guide.md +519 -0
- package/docs/ja/specdojo/guides/exec-config-guide.md +589 -0
- package/docs/ja/specdojo/guides/exec-operation-guide.md +440 -0
- package/docs/ja/specdojo/guides/exec-worktree-guide.md +318 -0
- package/docs/ja/specdojo/guides/kata-guide.md +89 -0
- package/docs/ja/specdojo/guides/orchestrator-operation-guide.md +127 -0
- package/docs/ja/specdojo/guides/plan-result-lifecycle-guide.md +228 -0
- package/docs/ja/specdojo/guides/practice-system-composition-guide.md +111 -0
- package/docs/ja/specdojo/guides/quick-start-guide.md +473 -0
- package/docs/ja/specdojo/guides/register-operation-guide.md +418 -0
- package/docs/ja/specdojo/guides/review-guide.md +428 -0
- package/docs/ja/specdojo/guides/routine-operation-guide.md +282 -0
- package/docs/ja/specdojo/guides/ryu-guide.md +230 -0
- package/docs/ja/specdojo/guides/schedule-design-guide.md +429 -0
- package/docs/ja/specdojo/guides/schedule-operation-guide.md +151 -0
- package/docs/ja/specdojo/guides/specdojo-overview-guide.md +257 -0
- package/docs/ja/specdojo/guides/timeline-design-guide.md +160 -0
- package/docs/ja/specdojo/guides/track-design-guide.md +215 -0
- package/docs/ja/specdojo/guides/use-case-guide.md +133 -0
- package/docs/ja/specdojo/guides/waza-guide.md +224 -0
- package/docs/ja/specdojo/index.md +33 -0
- package/docs/ja/specdojo/philosophy/needs-to-implementation-philosophy.md +212 -0
- package/docs/ja/specdojo/philosophy/specdojo-philosophy.md +242 -0
- package/docs/ja/specdojo/recipes/cdfd-overview-recipe.md +198 -0
- package/docs/ja/specdojo/recipes/cdfd-recipe.md +218 -0
- package/docs/ja/specdojo/recipes/cdfd-uc-recipe.md +198 -0
- package/docs/ja/specdojo/recipes/exec-human-finalize-recipe.md +100 -0
- package/docs/ja/specdojo/recipes/ifx-cmd-recipe.md +148 -0
- package/docs/ja/specdojo/recipes/pm-communication-plan-recipe.md +97 -0
- package/docs/ja/specdojo/recipes/pm-members-recipe.md +149 -0
- package/docs/ja/specdojo/recipes/pm-organization-recipe.md +96 -0
- package/docs/ja/specdojo/recipes/pm-plan-recipe.md +98 -0
- package/docs/ja/specdojo/recipes/pm-quality-management-plan-recipe.md +97 -0
- package/docs/ja/specdojo/recipes/pm-raci-recipe.md +96 -0
- package/docs/ja/specdojo/recipes/pm-roles-recipe.md +136 -0
- package/docs/ja/specdojo/recipes/prj-assumptions-constraints-dependencies-recipe.md +162 -0
- package/docs/ja/specdojo/recipes/prj-charter-recipe.md +187 -0
- package/docs/ja/specdojo/recipes/prj-comparison-of-alternatives-recipe.md +235 -0
- package/docs/ja/specdojo/recipes/prj-issues-and-approach-recipe.md +205 -0
- package/docs/ja/specdojo/recipes/prj-overview-recipe.md +289 -0
- package/docs/ja/specdojo/recipes/prj-scope-recipe.md +201 -0
- package/docs/ja/specdojo/recipes/prj-stakeholder-register-recipe.md +168 -0
- package/docs/ja/specdojo/recipes/prj-success-criteria-and-acceptance-criteria-recipe.md +179 -0
- package/docs/ja/specdojo/recipes/stsd-recipe.md +138 -0
- package/docs/ja/specdojo/references/command-reference.md +718 -0
- package/docs/ja/specdojo/references/deliverables-reference.md +407 -0
- package/docs/ja/specdojo/references/directory-layout-reference.md +280 -0
- package/docs/ja/specdojo/references/specdojo-config-reference.md +133 -0
- package/docs/ja/specdojo/rulebooks/atc-index-rulebook.md +372 -0
- package/docs/ja/specdojo/rulebooks/atc-rulebook.md +302 -0
- package/docs/ja/specdojo/rulebooks/bac-rulebook.md +331 -0
- package/docs/ja/specdojo/rulebooks/bdd-rulebook.md +134 -0
- package/docs/ja/specdojo/rulebooks/bds-rulebook.md +207 -0
- package/docs/ja/specdojo/rulebooks/bes-index-rulebook.md +102 -0
- package/docs/ja/specdojo/rulebooks/bes-rulebook.md +131 -0
- package/docs/ja/specdojo/rulebooks/bps-rulebook.md +269 -0
- package/docs/ja/specdojo/rulebooks/br-rulebook.md +187 -0
- package/docs/ja/specdojo/rulebooks/ccd-mermaid-rulebook.md +279 -0
- package/docs/ja/specdojo/rulebooks/cdfd-mermaid-rulebook.md +219 -0
- package/docs/ja/specdojo/rulebooks/cdfd-overview-rulebook.md +233 -0
- package/docs/ja/specdojo/rulebooks/cdfd-rulebook.md +182 -0
- package/docs/ja/specdojo/rulebooks/cdfd-uc-rulebook.md +171 -0
- package/docs/ja/specdojo/rulebooks/cdsd-rulebook.md +105 -0
- package/docs/ja/specdojo/rulebooks/cld-rulebook.md +195 -0
- package/docs/ja/specdojo/rulebooks/cnd-mermaid-rulebook.md +285 -0
- package/docs/ja/specdojo/rulebooks/cnd-rulebook.md +292 -0
- package/docs/ja/specdojo/rulebooks/cop-index-rulebook.md +171 -0
- package/docs/ja/specdojo/rulebooks/cop-rulebook.md +325 -0
- package/docs/ja/specdojo/rulebooks/cpd-mermaid-rulebook.md +266 -0
- package/docs/ja/specdojo/rulebooks/cpd-rulebook.md +294 -0
- package/docs/ja/specdojo/rulebooks/cstd-rulebook.md +21 -0
- package/docs/ja/specdojo/rulebooks/cxd-mermaid-rulebook.md +401 -0
- package/docs/ja/specdojo/rulebooks/cxd-rulebook.md +311 -0
- package/docs/ja/specdojo/rulebooks/dct-index-rulebook.md +158 -0
- package/docs/ja/specdojo/rulebooks/dct-rulebook.md +287 -0
- package/docs/ja/specdojo/rulebooks/dec-rulebook.md +62 -0
- package/docs/ja/specdojo/rulebooks/dmd-index-rulebook.md +100 -0
- package/docs/ja/specdojo/rulebooks/dmd-rulebook.md +298 -0
- package/docs/ja/specdojo/rulebooks/etc-index-rulebook.md +379 -0
- package/docs/ja/specdojo/rulebooks/etc-rulebook.md +310 -0
- package/docs/ja/specdojo/rulebooks/gl-rulebook.md +86 -0
- package/docs/ja/specdojo/rulebooks/ifd-mermaid-rulebook.md +297 -0
- package/docs/ja/specdojo/rulebooks/ifx-api-rulebook.md +79 -0
- package/docs/ja/specdojo/rulebooks/ifx-cmd-rulebook.md +213 -0
- package/docs/ja/specdojo/rulebooks/ifx-file-rulebook.md +311 -0
- package/docs/ja/specdojo/rulebooks/ifx-index-rulebook.md +94 -0
- package/docs/ja/specdojo/rulebooks/ifx-msg-rulebook.md +81 -0
- package/docs/ja/specdojo/rulebooks/imp-business-rulebook.md +117 -0
- package/docs/ja/specdojo/rulebooks/imp-data-rulebook.md +118 -0
- package/docs/ja/specdojo/rulebooks/imp-interface-rulebook.md +116 -0
- package/docs/ja/specdojo/rulebooks/imp-operations-rulebook.md +116 -0
- package/docs/ja/specdojo/rulebooks/imp-test-rulebook.md +116 -0
- package/docs/ja/specdojo/rulebooks/itc-index-rulebook.md +421 -0
- package/docs/ja/specdojo/rulebooks/itc-rulebook.md +307 -0
- package/docs/ja/specdojo/rulebooks/mip-index-rulebook.md +312 -0
- package/docs/ja/specdojo/rulebooks/mm-rulebook.md +63 -0
- package/docs/ja/specdojo/rulebooks/mtp-rulebook.md +353 -0
- package/docs/ja/specdojo/rulebooks/nfr-availability-rulebook.md +184 -0
- package/docs/ja/specdojo/rulebooks/nfr-index-rulebook.md +179 -0
- package/docs/ja/specdojo/rulebooks/nfr-integrity-rulebook.md +184 -0
- package/docs/ja/specdojo/rulebooks/nfr-maintainability-rulebook.md +183 -0
- package/docs/ja/specdojo/rulebooks/nfr-operations-rulebook.md +185 -0
- package/docs/ja/specdojo/rulebooks/nfr-performance-rulebook.md +185 -0
- package/docs/ja/specdojo/rulebooks/nfr-reliability-rulebook.md +186 -0
- package/docs/ja/specdojo/rulebooks/nfr-security-safety-rulebook.md +186 -0
- package/docs/ja/specdojo/rulebooks/nfr-usability-rulebook.md +184 -0
- package/docs/ja/specdojo/rulebooks/ntp-rulebook.md +61 -0
- package/docs/ja/specdojo/rulebooks/opd-index-rulebook.md +84 -0
- package/docs/ja/specdojo/rulebooks/opd-rulebook.md +357 -0
- package/docs/ja/specdojo/rulebooks/opr-index-rulebook.md +80 -0
- package/docs/ja/specdojo/rulebooks/opr-rulebook.md +484 -0
- package/docs/ja/specdojo/rulebooks/otp-index-rulebook.md +120 -0
- package/docs/ja/specdojo/rulebooks/otp-rulebook.md +293 -0
- package/docs/ja/specdojo/rulebooks/pjr-rulebook.md +211 -0
- package/docs/ja/specdojo/rulebooks/pm-change-request-log-rulebook.md +94 -0
- package/docs/ja/specdojo/rulebooks/pm-communication-plan-rulebook.md +116 -0
- package/docs/ja/specdojo/rulebooks/pm-issue-log-rulebook.md +93 -0
- package/docs/ja/specdojo/rulebooks/pm-members-rulebook.md +190 -0
- package/docs/ja/specdojo/rulebooks/pm-organization-rulebook.md +108 -0
- package/docs/ja/specdojo/rulebooks/pm-plan-rulebook.md +122 -0
- package/docs/ja/specdojo/rulebooks/pm-quality-management-plan-rulebook.md +117 -0
- package/docs/ja/specdojo/rulebooks/pm-raci-rulebook.md +116 -0
- package/docs/ja/specdojo/rulebooks/pm-risk-register-rulebook.md +93 -0
- package/docs/ja/specdojo/rulebooks/pm-roles-rulebook.md +146 -0
- package/docs/ja/specdojo/rulebooks/pr-rulebook.md +65 -0
- package/docs/ja/specdojo/rulebooks/prj-assumptions-constraints-dependencies-rulebook.md +178 -0
- package/docs/ja/specdojo/rulebooks/prj-charter-rulebook.md +232 -0
- package/docs/ja/specdojo/rulebooks/prj-comparison-of-alternatives-rulebook.md +235 -0
- package/docs/ja/specdojo/rulebooks/prj-issues-and-approach-rulebook.md +242 -0
- package/docs/ja/specdojo/rulebooks/prj-overview-rulebook.md +187 -0
- package/docs/ja/specdojo/rulebooks/prj-scope-rulebook.md +201 -0
- package/docs/ja/specdojo/rulebooks/prj-stakeholder-register-rulebook.md +165 -0
- package/docs/ja/specdojo/rulebooks/prj-success-criteria-and-acceptance-criteria-rulebook.md +165 -0
- package/docs/ja/specdojo/rulebooks/sac-rulebook.md +202 -0
- package/docs/ja/specdojo/rulebooks/sch-rulebook.md +139 -0
- package/docs/ja/specdojo/rulebooks/sf-index-rulebook.md +63 -0
- package/docs/ja/specdojo/rulebooks/sf-rulebook.md +93 -0
- package/docs/ja/specdojo/rulebooks/sld-rulebook.md +93 -0
- package/docs/ja/specdojo/rulebooks/stc-index-rulebook.md +329 -0
- package/docs/ja/specdojo/rulebooks/stc-rulebook.md +297 -0
- package/docs/ja/specdojo/rulebooks/stsd-mermaid-rulebook.md +132 -0
- package/docs/ja/specdojo/rulebooks/stsd-rulebook.md +215 -0
- package/docs/ja/specdojo/rulebooks/sysd-critical-flows-rulebook.md +376 -0
- package/docs/ja/specdojo/rulebooks/sysd-cross-cutting-policy-rulebook.md +313 -0
- package/docs/ja/specdojo/rulebooks/sysd-index-rulebook.md +246 -0
- package/docs/ja/specdojo/rulebooks/sysd-rulebook.md +119 -0
- package/docs/ja/specdojo/rulebooks/tml-rulebook.md +188 -0
- package/docs/ja/specdojo/rulebooks/trc-requirements-to-specs-rulebook.md +114 -0
- package/docs/ja/specdojo/rulebooks/trc-requirements-to-tests-rulebook.md +117 -0
- package/docs/ja/specdojo/rulebooks/tsd-index-rulebook.md +101 -0
- package/docs/ja/specdojo/rulebooks/tsd-rulebook.md +103 -0
- package/docs/ja/specdojo/rulebooks/tsp-index-rulebook.md +396 -0
- package/docs/ja/specdojo/rulebooks/uis-rulebook.md +207 -0
- package/docs/ja/specdojo/rulebooks/utc-index-rulebook.md +387 -0
- package/docs/ja/specdojo/rulebooks/utc-rulebook.md +303 -0
- package/docs/ja/specdojo/samples/atc-index-sample.md +38 -0
- package/docs/ja/specdojo/samples/atc-sample.md +41 -0
- package/docs/ja/specdojo/samples/bac-sample.md +38 -0
- package/docs/ja/specdojo/samples/bdd-sample.yaml +71 -0
- package/docs/ja/specdojo/samples/bds-sample.md +38 -0
- package/docs/ja/specdojo/samples/bes-index-sample.md +38 -0
- package/docs/ja/specdojo/samples/bes-sample.md +38 -0
- package/docs/ja/specdojo/samples/bps-sample.md +38 -0
- package/docs/ja/specdojo/samples/br-sample.md +40 -0
- package/docs/ja/specdojo/samples/ccd-sample.md +38 -0
- package/docs/ja/specdojo/samples/cdfd-overview-sample.md +284 -0
- package/docs/ja/specdojo/samples/cdfd-sample.md +229 -0
- package/docs/ja/specdojo/samples/cdfd-uc-sample.md +146 -0
- package/docs/ja/specdojo/samples/cdsd-sample.md +38 -0
- package/docs/ja/specdojo/samples/cld-sample.md +38 -0
- package/docs/ja/specdojo/samples/cnd-sample.md +38 -0
- package/docs/ja/specdojo/samples/cop-index-sample.md +38 -0
- package/docs/ja/specdojo/samples/cop-sample.md +38 -0
- package/docs/ja/specdojo/samples/cpd-sample.md +38 -0
- package/docs/ja/specdojo/samples/cstd-sample.md +11 -0
- package/docs/ja/specdojo/samples/cxd-sample.md +38 -0
- package/docs/ja/specdojo/samples/dct-index-sample.yaml +39 -0
- package/docs/ja/specdojo/samples/dct-sample.yaml +91 -0
- package/docs/ja/specdojo/samples/dec-sample.md +39 -0
- package/docs/ja/specdojo/samples/dmd-index-sample.md +50 -0
- package/docs/ja/specdojo/samples/dmd-sample.md +74 -0
- package/docs/ja/specdojo/samples/etc-index-sample.md +38 -0
- package/docs/ja/specdojo/samples/etc-sample.md +38 -0
- package/docs/ja/specdojo/samples/gl-sample.yaml +37 -0
- package/docs/ja/specdojo/samples/ifd-sample.md +38 -0
- package/docs/ja/specdojo/samples/ifx-api-sample.yaml +102 -0
- package/docs/ja/specdojo/samples/ifx-cmd-sample.yaml +107 -0
- package/docs/ja/specdojo/samples/ifx-file-sample.md +38 -0
- package/docs/ja/specdojo/samples/ifx-msg-sample.yaml +89 -0
- package/docs/ja/specdojo/samples/imp-business-sample.md +66 -0
- package/docs/ja/specdojo/samples/imp-data-sample.md +60 -0
- package/docs/ja/specdojo/samples/imp-interface-sample.md +60 -0
- package/docs/ja/specdojo/samples/imp-operations-sample.md +60 -0
- package/docs/ja/specdojo/samples/imp-test-sample.md +60 -0
- package/docs/ja/specdojo/samples/itc-index-sample.md +38 -0
- package/docs/ja/specdojo/samples/itc-sample.md +38 -0
- package/docs/ja/specdojo/samples/mip-index-sample.md +38 -0
- package/docs/ja/specdojo/samples/mm-sample.md +35 -0
- package/docs/ja/specdojo/samples/mtp-sample.md +38 -0
- package/docs/ja/specdojo/samples/nfr-availability-sample.md +38 -0
- package/docs/ja/specdojo/samples/nfr-index-sample.md +38 -0
- package/docs/ja/specdojo/samples/nfr-integrity-sample.md +38 -0
- package/docs/ja/specdojo/samples/nfr-maintainability-sample.md +38 -0
- package/docs/ja/specdojo/samples/nfr-operations-sample.md +38 -0
- package/docs/ja/specdojo/samples/nfr-performance-sample.md +38 -0
- package/docs/ja/specdojo/samples/nfr-reliability-sample.md +38 -0
- package/docs/ja/specdojo/samples/nfr-security-safety-sample.md +38 -0
- package/docs/ja/specdojo/samples/nfr-usability-sample.md +38 -0
- package/docs/ja/specdojo/samples/ntp-sample.md +38 -0
- package/docs/ja/specdojo/samples/opd-access-control-sample.md +29 -0
- package/docs/ja/specdojo/samples/opd-incident-management-sample.md +31 -0
- package/docs/ja/specdojo/samples/opd-index-sample.md +41 -0
- package/docs/ja/specdojo/samples/opd-monitoring-sample.md +32 -0
- package/docs/ja/specdojo/samples/opd-sample.md +38 -0
- package/docs/ja/specdojo/samples/opr-access-control-sample.md +24 -0
- package/docs/ja/specdojo/samples/opr-backup-restore-sample.md +27 -0
- package/docs/ja/specdojo/samples/opr-batch-sample.md +23 -0
- package/docs/ja/specdojo/samples/opr-change-sample.md +24 -0
- package/docs/ja/specdojo/samples/opr-incident-sample.md +38 -0
- package/docs/ja/specdojo/samples/opr-index-sample.md +43 -0
- package/docs/ja/specdojo/samples/opr-monitoring-sample.md +27 -0
- package/docs/ja/specdojo/samples/opr-sample.md +38 -0
- package/docs/ja/specdojo/samples/opr-support-sample.md +23 -0
- package/docs/ja/specdojo/samples/otp-index-sample.md +66 -0
- package/docs/ja/specdojo/samples/otp-sample.md +68 -0
- package/docs/ja/specdojo/samples/pm-change-request-log-sample.md +47 -0
- package/docs/ja/specdojo/samples/pm-communication-plan-sample.md +46 -0
- package/docs/ja/specdojo/samples/pm-issue-log-sample.md +45 -0
- package/docs/ja/specdojo/samples/pm-members-sample.yaml +103 -0
- package/docs/ja/specdojo/samples/pm-organization-sample.md +46 -0
- package/docs/ja/specdojo/samples/pm-plan-sample.md +57 -0
- package/docs/ja/specdojo/samples/pm-quality-management-plan-sample.md +52 -0
- package/docs/ja/specdojo/samples/pm-raci-sample.md +57 -0
- package/docs/ja/specdojo/samples/pm-risk-register-sample.md +43 -0
- package/docs/ja/specdojo/samples/pm-roles-sample.yaml +41 -0
- package/docs/ja/specdojo/samples/pr-sample.md +39 -0
- package/docs/ja/specdojo/samples/prj-assumptions-constraints-dependencies-sample.md +57 -0
- package/docs/ja/specdojo/samples/prj-charter-sample.md +121 -0
- package/docs/ja/specdojo/samples/prj-comparison-of-alternatives-sample.md +105 -0
- package/docs/ja/specdojo/samples/prj-issues-and-approach-sample.md +78 -0
- package/docs/ja/specdojo/samples/prj-overview-sample.md +95 -0
- package/docs/ja/specdojo/samples/prj-scope-sample.md +71 -0
- package/docs/ja/specdojo/samples/prj-stakeholder-register-sample.md +60 -0
- package/docs/ja/specdojo/samples/prj-success-criteria-and-acceptance-criteria-sample.md +62 -0
- package/docs/ja/specdojo/samples/sac-sample.md +38 -0
- package/docs/ja/specdojo/samples/sf-index-sample.md +38 -0
- package/docs/ja/specdojo/samples/sf-sample.md +38 -0
- package/docs/ja/specdojo/samples/sld-sample.md +38 -0
- package/docs/ja/specdojo/samples/stc-index-sample.md +38 -0
- package/docs/ja/specdojo/samples/stc-sample.md +38 -0
- package/docs/ja/specdojo/samples/stsd-sample.md +58 -0
- package/docs/ja/specdojo/samples/sysd-critical-flows-sample.md +38 -0
- package/docs/ja/specdojo/samples/sysd-cross-cutting-policy-sample.md +38 -0
- package/docs/ja/specdojo/samples/sysd-index-sample.md +38 -0
- package/docs/ja/specdojo/samples/trc-requirements-to-specs-sample.md +56 -0
- package/docs/ja/specdojo/samples/trc-requirements-to-tests-sample.md +56 -0
- package/docs/ja/specdojo/samples/tsd-index-sample.md +29 -0
- package/docs/ja/specdojo/samples/tsd-sample.md +38 -0
- package/docs/ja/specdojo/samples/tsp-index-sample.md +38 -0
- package/docs/ja/specdojo/samples/uis-sample.md +38 -0
- package/docs/ja/specdojo/samples/utc-index-sample.md +38 -0
- package/docs/ja/specdojo/samples/utc-sample.md +38 -0
- package/docs/ja/specdojo/schemas/v1/guide-content.schema.yaml +20 -0
- package/docs/ja/specdojo/schemas/v1/philosophy-content.schema.yaml +21 -0
- package/docs/ja/specdojo/schemas/v1/reference-content.schema.yaml +21 -0
- package/docs/ja/specdojo/standards/document-metadata-standard.md +323 -0
- package/docs/ja/specdojo/standards/exec-human-finalize-standard.md +75 -0
- package/docs/ja/specdojo/standards/git-branching-standard.md +227 -0
- package/docs/ja/specdojo/standards/guide-authoring-standard.md +124 -0
- package/docs/ja/specdojo/standards/id-and-file-naming-standard.md +929 -0
- package/docs/ja/specdojo/standards/job-definition-standard.md +148 -0
- package/docs/ja/specdojo/standards/people-and-organization-definition-standard.md +431 -0
- package/docs/ja/specdojo/standards/philosophy-authoring-standard.md +113 -0
- package/docs/ja/specdojo/standards/recipe-authoring-standard.md +143 -0
- package/docs/ja/specdojo/standards/reference-authoring-standard.md +99 -0
- package/docs/ja/specdojo/standards/rulebook-authoring-standard.md +140 -0
- package/docs/ja/specdojo/standards/sample-authoring-standard.md +151 -0
- package/docs/ja/specdojo/standards/standard-authoring-standard.md +108 -0
- package/docs/ja/specdojo/standards/template-authoring-standard.md +101 -0
- package/docs/ja/specdojo/standards/test-document-scope-standard.md +176 -0
- package/docs/ja/specdojo/templates/cdfd-overview-template.md +199 -0
- package/docs/ja/specdojo/templates/cdfd-template.md +173 -0
- package/docs/ja/specdojo/templates/cdfd-uc-template.md +148 -0
- package/docs/ja/specdojo/templates/dct-architecture-template.yaml +136 -0
- package/docs/ja/specdojo/templates/dct-business-acceptance-criteria-template.yaml +34 -0
- package/docs/ja/specdojo/templates/dct-business-model-bes-template.yaml +75 -0
- package/docs/ja/specdojo/templates/dct-business-model-bps-template.yaml +49 -0
- package/docs/ja/specdojo/templates/dct-business-model-br-template.yaml +50 -0
- package/docs/ja/specdojo/templates/dct-data-flow-template.yaml +40 -0
- package/docs/ja/specdojo/templates/dct-data-model-bdd-template.yaml +46 -0
- package/docs/ja/specdojo/templates/dct-data-model-ccd-template.yaml +46 -0
- package/docs/ja/specdojo/templates/dct-data-model-cdsd-template.yaml +41 -0
- package/docs/ja/specdojo/templates/dct-data-model-cld-template.yaml +38 -0
- package/docs/ja/specdojo/templates/dct-data-model-sld-template.yaml +38 -0
- package/docs/ja/specdojo/templates/dct-data-model-stsd-template.yaml +46 -0
- package/docs/ja/specdojo/templates/dct-external-interface-specs-template.yaml +114 -0
- package/docs/ja/specdojo/templates/dct-glossary-template.yaml +35 -0
- package/docs/ja/specdojo/templates/dct-impact-analysis-template.yaml +138 -0
- package/docs/ja/specdojo/templates/dct-index-template.md +40 -0
- package/docs/ja/specdojo/templates/dct-migration-planning-template.yaml +148 -0
- package/docs/ja/specdojo/templates/dct-non-functional-requirements-template.yaml +222 -0
- package/docs/ja/specdojo/templates/dct-operations-template.yaml +108 -0
- package/docs/ja/specdojo/templates/dct-project-definition-template.yaml +210 -0
- package/docs/ja/specdojo/templates/dct-project-management-template.yaml +423 -0
- package/docs/ja/specdojo/templates/dct-system-acceptance-criteria-template.yaml +37 -0
- package/docs/ja/specdojo/templates/dct-system-design-template.yaml +82 -0
- package/docs/ja/specdojo/templates/dct-system-functions-template.yaml +58 -0
- package/docs/ja/specdojo/templates/dct-test-specs-template.yaml +261 -0
- package/docs/ja/specdojo/templates/dct-user-interface-model-template.yaml +60 -0
- package/docs/ja/specdojo/templates/ifx-cmd-template.yaml +88 -0
- package/docs/ja/specdojo/templates/opr-template.md +85 -0
- package/docs/ja/specdojo/templates/pjr-change-request-template.md +60 -0
- package/docs/ja/specdojo/templates/pjr-decision-template.md +61 -0
- package/docs/ja/specdojo/templates/pjr-index-template.md +49 -0
- package/docs/ja/specdojo/templates/pjr-issue-template.md +50 -0
- package/docs/ja/specdojo/templates/pjr-note-template.md +35 -0
- package/docs/ja/specdojo/templates/pjr-question-template.md +53 -0
- package/docs/ja/specdojo/templates/pjr-risk-template.md +49 -0
- package/docs/ja/specdojo/templates/pjr-todo-template.md +41 -0
- package/docs/ja/specdojo/templates/pjr-views-by-owner-template.md +22 -0
- package/docs/ja/specdojo/templates/pjr-views-by-priority-template.md +22 -0
- package/docs/ja/specdojo/templates/pjr-views-by-status-template.md +22 -0
- package/docs/ja/specdojo/templates/pm-change-request-log-template.md +20 -0
- package/docs/ja/specdojo/templates/pm-communication-plan-template.md +46 -0
- package/docs/ja/specdojo/templates/pm-decision-log-template.md +20 -0
- package/docs/ja/specdojo/templates/pm-issue-log-template.md +20 -0
- package/docs/ja/specdojo/templates/pm-members-template.yaml +105 -0
- package/docs/ja/specdojo/templates/pm-organization-template.md +44 -0
- package/docs/ja/specdojo/templates/pm-plan-template.md +52 -0
- package/docs/ja/specdojo/templates/pm-quality-management-plan-template.md +46 -0
- package/docs/ja/specdojo/templates/pm-raci-template.md +51 -0
- package/docs/ja/specdojo/templates/pm-risk-register-template.md +20 -0
- package/docs/ja/specdojo/templates/pm-roles-template.yaml +53 -0
- package/docs/ja/specdojo/templates/prj-assumptions-constraints-dependencies-template.md +59 -0
- package/docs/ja/specdojo/templates/prj-charter-template.md +116 -0
- package/docs/ja/specdojo/templates/prj-comparison-of-alternatives-template.md +116 -0
- package/docs/ja/specdojo/templates/prj-issues-and-approach-template.md +89 -0
- package/docs/ja/specdojo/templates/prj-overview-template.md +85 -0
- package/docs/ja/specdojo/templates/prj-scope-template.md +75 -0
- package/docs/ja/specdojo/templates/prj-stakeholder-register-template.md +64 -0
- package/docs/ja/specdojo/templates/prj-success-criteria-and-acceptance-criteria-template.md +60 -0
- package/docs/ja/specdojo/templates/stsd-template.md +57 -0
- package/docs/specdojo/schemas/v1/bdd.schema.yaml +230 -0
- package/docs/specdojo/schemas/v1/common-frontmatter.schema.yaml +77 -0
- package/docs/specdojo/schemas/v1/dct-index.schema.yaml +85 -0
- package/docs/specdojo/schemas/v1/dct-plan.schema.yaml +324 -0
- package/docs/specdojo/schemas/v1/dct.schema.yaml +368 -0
- package/docs/specdojo/schemas/v1/deliverable-frontmatter.schema.yaml +91 -0
- package/docs/specdojo/schemas/v1/esil.schema.yaml +142 -0
- package/docs/specdojo/schemas/v1/exec-common.schema.yaml +101 -0
- package/docs/specdojo/schemas/v1/exec-defaults.schema.yaml +272 -0
- package/docs/specdojo/schemas/v1/exec-evidence.schema.yaml +162 -0
- package/docs/specdojo/schemas/v1/exec-plan-frontmatter.schema.yaml +126 -0
- package/docs/specdojo/schemas/v1/exec-reporter-output.schema.yaml +151 -0
- package/docs/specdojo/schemas/v1/exec-result-frontmatter.schema.yaml +144 -0
- package/docs/specdojo/schemas/v1/grade-done-criteria.schema.yaml +79 -0
- package/docs/specdojo/schemas/v1/grade-pipeline-state.schema.yaml +60 -0
- package/docs/specdojo/schemas/v1/grade-result.schema.yaml +118 -0
- package/docs/specdojo/schemas/v1/guide-frontmatter.schema.yaml +19 -0
- package/docs/specdojo/schemas/v1/ifx-cmd.schema.yaml +293 -0
- package/docs/specdojo/schemas/v1/job-run.schema.yaml +90 -0
- package/docs/specdojo/schemas/v1/job.schema.yaml +198 -0
- package/docs/specdojo/schemas/v1/philosophy-frontmatter.schema.yaml +19 -0
- package/docs/specdojo/schemas/v1/pipeline-state.schema.yaml +56 -0
- package/docs/specdojo/schemas/v1/pm-members.schema.yaml +252 -0
- package/docs/specdojo/schemas/v1/pm-review-viewpoints.schema.yaml +387 -0
- package/docs/specdojo/schemas/v1/pm-roles.schema.yaml +106 -0
- package/docs/specdojo/schemas/v1/recipe-frontmatter.schema.yaml +27 -0
- package/docs/specdojo/schemas/v1/reference-frontmatter.schema.yaml +18 -0
- package/docs/specdojo/schemas/v1/register-events.schema.yaml +106 -0
- package/docs/specdojo/schemas/v1/register-item-frontmatter.schema.yaml +204 -0
- package/docs/specdojo/schemas/v1/routine-run.schema.yaml +36 -0
- package/docs/specdojo/schemas/v1/routine.schema.yaml +87 -0
- package/docs/specdojo/schemas/v1/rulebook-frontmatter.schema.yaml +61 -0
- package/docs/specdojo/schemas/v1/sch-common.schema.yaml +258 -0
- package/docs/specdojo/schemas/v1/sch-defaults.schema.yaml +48 -0
- package/docs/specdojo/schemas/v1/sch-milestones.schema.yaml +64 -0
- package/docs/specdojo/schemas/v1/sch-strategy.schema.yaml +772 -0
- package/docs/specdojo/schemas/v1/sch-track.schema.yaml +66 -0
- package/docs/specdojo/schemas/v1/standard-frontmatter.schema.yaml +18 -0
- package/docs/specdojo/schemas/v1/tml-index.schema.yaml +103 -0
- package/package.json +120 -24
- package/templates/claude/README.md +46 -0
- package/templates/claude/agents/claude-expert-review-executor.md +14 -0
- package/templates/claude/agents/claude-review-executor.md +14 -0
- package/templates/claude/settings.edit.json +6 -0
- package/templates/claude/settings.report.json +6 -0
- package/templates/claude/settings.review.json +7 -0
- package/templates/codex/README.md +61 -0
- package/templates/codex/agents/codex-executor.toml +12 -0
- package/templates/codex/agents/codex-expert-executor.toml +12 -0
- package/templates/codex/agents/codex-expert-review-executor.toml +10 -0
- package/templates/codex/agents/codex-review-executor.toml +10 -0
- package/templates/copilot/README.md +41 -0
- package/templates/copilot/exec-defaults-snippet.yaml +28 -0
- package/templates/copilot/pm-members-snippet.yaml +44 -0
- package/templates/opencode/README.md +41 -0
- package/templates/opencode/agents/opencode-executor.md +59 -0
- package/templates/opencode/agents/opencode-reporter.md +26 -0
- package/templates/opencode/agents/opencode-review-executor.md +48 -0
- package/dist/exec-schedule-timeline-render.js +0 -201
- package/dist/exec-schedule-timeline.js +0 -2
|
@@ -0,0 +1,138 @@
|
|
|
1
|
+
# yaml-language-server: $schema=../../../specdojo/schemas/v1/dct.schema.yaml
|
|
2
|
+
# specdojo-schema: validate=false reason=template
|
|
3
|
+
# Template: impact analysis deliverables catalog
|
|
4
|
+
# min_size: deliverable is included only when scaffold --size >= this value
|
|
5
|
+
# Placeholder _PROJECT_ID_ is replaced with the actual project_id on scaffold.
|
|
6
|
+
id: specdojo:dct-impact-analysis-template
|
|
7
|
+
type: template
|
|
8
|
+
status: draft
|
|
9
|
+
title: 成果物カタログ(影響調査)
|
|
10
|
+
rulebook: specdojo:dct-rulebook
|
|
11
|
+
part_of:
|
|
12
|
+
- _PROJECT_ID_:dct-index
|
|
13
|
+
domain: impact-analysis
|
|
14
|
+
base_path: /docs/ja/projects/_PROJECT_ID_/050-impact-analysis
|
|
15
|
+
|
|
16
|
+
groups:
|
|
17
|
+
- name: 影響調査
|
|
18
|
+
deliverables:
|
|
19
|
+
- local_id: imp-business
|
|
20
|
+
name: 影響調査(業務)
|
|
21
|
+
kind: work
|
|
22
|
+
depends_on: []
|
|
23
|
+
overview: 導入・変更が業務へ与える影響を整理
|
|
24
|
+
path: imp-business.md
|
|
25
|
+
rulebook: specdojo:imp-business-rulebook
|
|
26
|
+
done_criteria:
|
|
27
|
+
- text: 影響対象業務・変更要否・影響度が業務観点で整理されていること
|
|
28
|
+
roles: [BA]
|
|
29
|
+
viewpoint: vp-ba-requirements-completeness
|
|
30
|
+
- text: 業務影響の範囲と対応方針を承認できること
|
|
31
|
+
roles: [PO]
|
|
32
|
+
viewpoint: vp-po-decision-readiness
|
|
33
|
+
- text: 技術実装への影響範囲が識別できること
|
|
34
|
+
roles: [ARC]
|
|
35
|
+
viewpoint: vp-arc-technical-constraints
|
|
36
|
+
- text: テスト対象への影響が確認できること
|
|
37
|
+
roles: [QE]
|
|
38
|
+
viewpoint: vp-qe-verifiability
|
|
39
|
+
- text: 実装上の変更影響が確認できること
|
|
40
|
+
roles: [DEV]
|
|
41
|
+
viewpoint: vp-dev-implementation-readiness
|
|
42
|
+
|
|
43
|
+
- local_id: imp-data
|
|
44
|
+
min_size: medium
|
|
45
|
+
name: 影響調査(データ)
|
|
46
|
+
kind: work
|
|
47
|
+
depends_on:
|
|
48
|
+
- imp-business
|
|
49
|
+
overview: 導入・変更がデータへ与える影響を整理
|
|
50
|
+
path: imp-data.md
|
|
51
|
+
rulebook: specdojo:imp-data-rulebook
|
|
52
|
+
done_criteria:
|
|
53
|
+
- text: 影響対象データ・変更要否・影響度が業務観点で整理されていること
|
|
54
|
+
roles: [BA]
|
|
55
|
+
viewpoint: vp-ba-requirements-completeness
|
|
56
|
+
- text: データ影響の範囲と対応方針を承認できること
|
|
57
|
+
roles: [PO]
|
|
58
|
+
viewpoint: vp-po-decision-readiness
|
|
59
|
+
- text: データ構造・整合性への技術的影響が識別できること
|
|
60
|
+
roles: [ARC]
|
|
61
|
+
viewpoint: vp-arc-technical-constraints
|
|
62
|
+
- text: データ検証・移行テストへの影響が確認できること
|
|
63
|
+
roles: [QE]
|
|
64
|
+
viewpoint: vp-qe-verifiability
|
|
65
|
+
- text: データ変更の実装影響が確認できること
|
|
66
|
+
roles: [DEV]
|
|
67
|
+
viewpoint: vp-dev-implementation-readiness
|
|
68
|
+
|
|
69
|
+
- local_id: imp-interface
|
|
70
|
+
min_size: medium
|
|
71
|
+
name: 影響調査(I/F)
|
|
72
|
+
kind: work
|
|
73
|
+
depends_on:
|
|
74
|
+
- imp-business
|
|
75
|
+
overview: 導入・変更がインターフェースへ与える影響を整理
|
|
76
|
+
path: imp-interface.md
|
|
77
|
+
rulebook: specdojo:imp-interface-rulebook
|
|
78
|
+
done_criteria:
|
|
79
|
+
- text: 影響対象I/F・変更要否・影響度が業務観点で整理されていること
|
|
80
|
+
roles: [BA]
|
|
81
|
+
viewpoint: vp-ba-requirements-completeness
|
|
82
|
+
- text: I/F影響の範囲と対応方針を承認できること
|
|
83
|
+
roles: [PO]
|
|
84
|
+
viewpoint: vp-po-decision-readiness
|
|
85
|
+
- text: 外部システム連携への技術的影響が識別できること
|
|
86
|
+
roles: [ARC]
|
|
87
|
+
viewpoint: vp-arc-technical-constraints
|
|
88
|
+
- text: I/Fテストへの影響が確認できること
|
|
89
|
+
roles: [QE]
|
|
90
|
+
viewpoint: vp-qe-verifiability
|
|
91
|
+
|
|
92
|
+
- local_id: imp-test
|
|
93
|
+
name: 影響調査(テスト)
|
|
94
|
+
kind: work
|
|
95
|
+
depends_on:
|
|
96
|
+
- imp-business
|
|
97
|
+
overview: 導入・変更がテストへ与える影響を整理
|
|
98
|
+
path: imp-test.md
|
|
99
|
+
rulebook: specdojo:imp-test-rulebook
|
|
100
|
+
done_criteria:
|
|
101
|
+
- text: 影響対象テスト・変更要否・影響度が業務観点で整理されていること
|
|
102
|
+
roles: [BA]
|
|
103
|
+
viewpoint: vp-ba-requirements-completeness
|
|
104
|
+
- text: テスト影響の範囲と対応方針を承認できること
|
|
105
|
+
roles: [PO]
|
|
106
|
+
viewpoint: vp-po-decision-readiness
|
|
107
|
+
- text: テスト技術的影響(テストデータ・環境・自動化)が識別できること
|
|
108
|
+
roles: [ARC]
|
|
109
|
+
viewpoint: vp-arc-technical-constraints
|
|
110
|
+
- text: 既存テスト資産への影響と追加テスト方針が確認できること
|
|
111
|
+
roles: [QE]
|
|
112
|
+
viewpoint: vp-qe-verifiability
|
|
113
|
+
|
|
114
|
+
- local_id: imp-operations
|
|
115
|
+
min_size: medium
|
|
116
|
+
name: 影響調査(運用)
|
|
117
|
+
kind: work
|
|
118
|
+
depends_on:
|
|
119
|
+
- imp-business
|
|
120
|
+
overview: 導入・変更が運用へ与える影響を整理
|
|
121
|
+
path: imp-operations.md
|
|
122
|
+
rulebook: specdojo:imp-operations-rulebook
|
|
123
|
+
done_criteria:
|
|
124
|
+
- text: 影響対象運用・変更要否・影響度が業務観点で整理されていること
|
|
125
|
+
roles: [BA]
|
|
126
|
+
viewpoint: vp-ba-requirements-completeness
|
|
127
|
+
- text: 運用影響の範囲と対応方針を承認できること
|
|
128
|
+
roles: [PO]
|
|
129
|
+
viewpoint: vp-po-decision-readiness
|
|
130
|
+
- text: 運用技術基盤への影響が識別できること
|
|
131
|
+
roles: [ARC]
|
|
132
|
+
viewpoint: vp-arc-technical-constraints
|
|
133
|
+
- text: 運用テスト・受入への影響が確認できること
|
|
134
|
+
roles: [QE]
|
|
135
|
+
viewpoint: vp-qe-verifiability
|
|
136
|
+
- text: 運用手順・監視設定の変更影響が確認できること
|
|
137
|
+
roles: [OPS]
|
|
138
|
+
viewpoint: vp-ops-operability
|
|
@@ -0,0 +1,40 @@
|
|
|
1
|
+
---
|
|
2
|
+
specdojo:
|
|
3
|
+
id: specdojo:dct-index-template
|
|
4
|
+
type: template
|
|
5
|
+
status: draft
|
|
6
|
+
frontmatter_template:
|
|
7
|
+
specdojo:
|
|
8
|
+
id: _PROJECT_ID_:dct-index
|
|
9
|
+
type: project
|
|
10
|
+
status: _STATUS_
|
|
11
|
+
rulebook: specdojo:dct-index-rulebook
|
|
12
|
+
---
|
|
13
|
+
|
|
14
|
+
# 成果物カタログ
|
|
15
|
+
|
|
16
|
+
Project Deliverables Catalog
|
|
17
|
+
|
|
18
|
+
> このファイルは `dct-index.yaml` と各 `dct-*.yaml` から生成された一覧ビューです。表示名・概要・順序・グループの正本は `dct-index.yaml` であり、このファイルを手編集しても次回の `specdojo catalog build` で失われます。
|
|
19
|
+
|
|
20
|
+
SpecDojo プロジェクトで作成する成果物とその説明をまとめたプロジェクト成果物カタログです。
|
|
21
|
+
ドメイン別成果物カタログへの参照先を一元管理し、成果物体系の参照起点を明確にします。
|
|
22
|
+
個別成果物の詳細情報は各 `dct-<domain>.md` に集約し、本書では共通ルールとドメイン一覧を管理します。
|
|
23
|
+
|
|
24
|
+
## 1. 共通ルール
|
|
25
|
+
|
|
26
|
+
- Frontmatter の `id` は `<project-id>:<local-id>` とします。
|
|
27
|
+
- `ドメイン` は成果物の分類を示すために使用します。また、`DOMAIN` はその短縮名で、Schedule などで使用します。
|
|
28
|
+
- Frontmatter の `based_on` には、直接根拠として参照した文書のみを記載します。
|
|
29
|
+
- `local-id` は成果物の論理名を表し、ファイル名および Frontmatter の `id` の基礎として使用します(例: `prj-overview`)。
|
|
30
|
+
- `ARTIFACT` は `local-id` の短縮名で、Schedule などで使用します。
|
|
31
|
+
- ファイルは以下の形式で命名し、`配置先` に保存します。
|
|
32
|
+
- Markdown の場合は、`<local-id>.md` もしくは `<成果物名>.md`
|
|
33
|
+
- YAML の場合は、`<local-id>.yaml` もしくは `<成果物名>.yaml`
|
|
34
|
+
- `根拠` には、その成果物の検討・作成における主要な依存関係を記載します。
|
|
35
|
+
- `根拠` と `based_on` は原則として一致させますが、必要に応じて差分があっても構いません。
|
|
36
|
+
- 種別は、`work`(作成する成果物)、`control`(管理用のドキュメント)、`generated`(自動生成したドキュメント等)とします。スケジュールへの展開対象は `work` のみです。
|
|
37
|
+
|
|
38
|
+
## 2. 成果物カタログ一覧
|
|
39
|
+
|
|
40
|
+
<!-- specdojo:view-slot=domain-tables -->
|
|
@@ -0,0 +1,148 @@
|
|
|
1
|
+
# yaml-language-server: $schema=../../../specdojo/schemas/v1/dct.schema.yaml
|
|
2
|
+
# specdojo-schema: validate=false reason=template
|
|
3
|
+
# Template: migration planning deliverables catalog
|
|
4
|
+
# min_size: deliverable is included only when scaffold --size >= this value
|
|
5
|
+
# Placeholder _PROJECT_ID_ is replaced with the actual project_id on scaffold.
|
|
6
|
+
id: specdojo:dct-migration-planning-template
|
|
7
|
+
type: template
|
|
8
|
+
status: draft
|
|
9
|
+
title: 成果物カタログ(移行計画)
|
|
10
|
+
rulebook: specdojo:dct-rulebook
|
|
11
|
+
part_of:
|
|
12
|
+
- _PROJECT_ID_:dct-index
|
|
13
|
+
domain: migration-planning
|
|
14
|
+
base_path: /docs/ja/projects/_PROJECT_ID_/060-migration-planning
|
|
15
|
+
|
|
16
|
+
groups:
|
|
17
|
+
- name: 移行計画
|
|
18
|
+
min_size: medium
|
|
19
|
+
deliverables:
|
|
20
|
+
- local_id: mip-index
|
|
21
|
+
name: 移行計画
|
|
22
|
+
kind: work
|
|
23
|
+
depends_on:
|
|
24
|
+
- imp-business
|
|
25
|
+
overview: 移行方針と全体計画を定義し、切替リスクを管理
|
|
26
|
+
path: mip-index.md
|
|
27
|
+
rulebook: specdojo:mip-index-rulebook
|
|
28
|
+
done_criteria:
|
|
29
|
+
- text: 移行範囲・移行方式・スケジュール・リスクが業務観点で確認できること
|
|
30
|
+
roles: [BA]
|
|
31
|
+
viewpoint: vp-ba-business-value
|
|
32
|
+
- text: 移行計画全体を承認できること
|
|
33
|
+
roles: [PO]
|
|
34
|
+
viewpoint: vp-po-decision-readiness
|
|
35
|
+
- text: 技術的移行方式・リスク対策が識別できること
|
|
36
|
+
roles: [ARC]
|
|
37
|
+
viewpoint: vp-arc-technical-constraints
|
|
38
|
+
- text: 移行テスト・受入条件が確認できること
|
|
39
|
+
roles: [QE]
|
|
40
|
+
viewpoint: vp-qe-verifiability
|
|
41
|
+
- text: 移行スケジュールと体制が計画可能な粒度で記述されていること
|
|
42
|
+
roles: [PM]
|
|
43
|
+
viewpoint: vp-pm-plan-feasibility
|
|
44
|
+
- text: 運用切替・ハイパーケア体制が確認できること
|
|
45
|
+
roles: [OPS]
|
|
46
|
+
viewpoint: vp-ops-operability
|
|
47
|
+
|
|
48
|
+
- local_id: dmd-index
|
|
49
|
+
min_size: large
|
|
50
|
+
name: データ移行設計
|
|
51
|
+
kind: work
|
|
52
|
+
depends_on:
|
|
53
|
+
- mip-index
|
|
54
|
+
- imp-data
|
|
55
|
+
overview: データ移行の設計内容を定義し、移行時の整合性を確保
|
|
56
|
+
path: dmd-index.md
|
|
57
|
+
rulebook: specdojo:dmd-index-rulebook
|
|
58
|
+
done_criteria:
|
|
59
|
+
- text: 移行対象データ・変換方針・マッピングが業務観点で確認できること
|
|
60
|
+
roles: [BA]
|
|
61
|
+
viewpoint: vp-ba-requirements-completeness
|
|
62
|
+
- text: データ移行設計を承認できること
|
|
63
|
+
roles: [PO]
|
|
64
|
+
viewpoint: vp-po-decision-readiness
|
|
65
|
+
- text: データ変換・整合性検証の技術方式が識別できること
|
|
66
|
+
roles: [ARC]
|
|
67
|
+
viewpoint: vp-arc-technical-constraints
|
|
68
|
+
- text: データ検証・ロールバック方針が確認できること
|
|
69
|
+
roles: [QE]
|
|
70
|
+
viewpoint: vp-qe-verifiability
|
|
71
|
+
- text: データ移行実装の技術要件が確認できること
|
|
72
|
+
roles: [DEV]
|
|
73
|
+
viewpoint: vp-dev-implementation-readiness
|
|
74
|
+
|
|
75
|
+
- local_id: mtp-index
|
|
76
|
+
min_size: large
|
|
77
|
+
name: 移行テスト計画(リハーサル計画)
|
|
78
|
+
kind: work
|
|
79
|
+
depends_on:
|
|
80
|
+
- mip-index
|
|
81
|
+
overview: 移行リハーサルの実施計画を定義し、切替前に妥当性を検証
|
|
82
|
+
path: mtp-index.md
|
|
83
|
+
done_criteria:
|
|
84
|
+
- text: テスト範囲・シナリオ・判定基準が業務観点で確認できること
|
|
85
|
+
roles: [BA]
|
|
86
|
+
viewpoint: vp-ba-business-value
|
|
87
|
+
- text: 移行テスト計画を承認できること
|
|
88
|
+
roles: [PO]
|
|
89
|
+
viewpoint: vp-po-decision-readiness
|
|
90
|
+
- text: テスト環境・技術的検証方式が識別できること
|
|
91
|
+
roles: [ARC]
|
|
92
|
+
viewpoint: vp-arc-technical-constraints
|
|
93
|
+
- text: 是正計画を含む合格基準が確認できること
|
|
94
|
+
roles: [QE]
|
|
95
|
+
viewpoint: vp-qe-verifiability
|
|
96
|
+
|
|
97
|
+
- local_id: cop-index
|
|
98
|
+
min_size: large
|
|
99
|
+
name: カットオーバー計画(本番切替手順)
|
|
100
|
+
kind: work
|
|
101
|
+
depends_on:
|
|
102
|
+
- mip-index
|
|
103
|
+
- mtp-index
|
|
104
|
+
overview: 本番切替の手順を定義し、停止時間と障害リスクを最小化
|
|
105
|
+
path: cop-index.md
|
|
106
|
+
rulebook: specdojo:cop-index-rulebook
|
|
107
|
+
done_criteria:
|
|
108
|
+
- text: 切替手順・業務停止範囲・判定ポイントが業務観点で確認できること
|
|
109
|
+
roles: [BA]
|
|
110
|
+
viewpoint: vp-ba-business-value
|
|
111
|
+
- text: カットオーバー計画を承認できること
|
|
112
|
+
roles: [PO]
|
|
113
|
+
viewpoint: vp-po-decision-readiness
|
|
114
|
+
- text: 技術的切替手順・切戻し方式が識別できること
|
|
115
|
+
roles: [ARC]
|
|
116
|
+
viewpoint: vp-arc-technical-constraints
|
|
117
|
+
- text: 判定ポイント・エスカレーション・切戻し手順が確認できること
|
|
118
|
+
roles: [QE]
|
|
119
|
+
viewpoint: vp-qe-verifiability
|
|
120
|
+
- text: 運用体制・エスカレーション経路が確認できること
|
|
121
|
+
roles: [OPS]
|
|
122
|
+
viewpoint: vp-ops-operability
|
|
123
|
+
|
|
124
|
+
- local_id: otp-index
|
|
125
|
+
min_size: large
|
|
126
|
+
name: 運用切替計画(ハイパーケア含む)
|
|
127
|
+
kind: work
|
|
128
|
+
depends_on:
|
|
129
|
+
- cop-index
|
|
130
|
+
overview: 切替後の運用移管計画を定義し、安定稼働へ移行
|
|
131
|
+
path: otp-index.md
|
|
132
|
+
rulebook: specdojo:otp-index-rulebook
|
|
133
|
+
done_criteria:
|
|
134
|
+
- text: 運用引継ぎ・ハイパーケア体制が業務観点で確認できること
|
|
135
|
+
roles: [BA]
|
|
136
|
+
viewpoint: vp-ba-business-value
|
|
137
|
+
- text: 運用移管計画を承認できること
|
|
138
|
+
roles: [PO]
|
|
139
|
+
viewpoint: vp-po-decision-readiness
|
|
140
|
+
- text: 技術的監視強化・問い合わせ対応方針が識別できること
|
|
141
|
+
roles: [ARC]
|
|
142
|
+
viewpoint: vp-arc-technical-constraints
|
|
143
|
+
- text: 安定化完了条件・受入判定が確認できること
|
|
144
|
+
roles: [QE]
|
|
145
|
+
viewpoint: vp-qe-verifiability
|
|
146
|
+
- text: 運用体制・手順・ハイパーケア終了条件が確認できること
|
|
147
|
+
roles: [OPS]
|
|
148
|
+
viewpoint: vp-ops-operability
|
|
@@ -0,0 +1,222 @@
|
|
|
1
|
+
# yaml-language-server: $schema=../../../specdojo/schemas/v1/dct.schema.yaml
|
|
2
|
+
# specdojo-schema: validate=false reason=template
|
|
3
|
+
# Template: non-functional requirements deliverables catalog
|
|
4
|
+
id: specdojo:dct-non-functional-requirements-template
|
|
5
|
+
type: template
|
|
6
|
+
status: draft
|
|
7
|
+
title: 成果物カタログ(非機能要件)
|
|
8
|
+
rulebook: specdojo:dct-rulebook
|
|
9
|
+
domain: non-functional-requirements
|
|
10
|
+
base_path: /docs/ja/product/060-non-functional-requirements
|
|
11
|
+
|
|
12
|
+
groups:
|
|
13
|
+
- deliverables:
|
|
14
|
+
- local_id: nfr-index
|
|
15
|
+
name: 非機能要件(全体構成)
|
|
16
|
+
kind: work
|
|
17
|
+
depends_on: []
|
|
18
|
+
overview: 非機能要件を8カテゴリに分冊管理し、測定可能・検証可能な形で一元化する
|
|
19
|
+
path: nfr-index.md
|
|
20
|
+
rulebook: specdojo:nfr-index-rulebook
|
|
21
|
+
done_criteria:
|
|
22
|
+
- text: 非機能要件のカテゴリ構成と優先度が業務観点で確認できること
|
|
23
|
+
roles: [BA]
|
|
24
|
+
viewpoint: vp-ba-requirements-completeness
|
|
25
|
+
- text: 非機能要件の全体方針を承認できること
|
|
26
|
+
roles: [PO]
|
|
27
|
+
viewpoint: vp-po-decision-readiness
|
|
28
|
+
- text: 技術的制約・実現可能性の前提として参照できること
|
|
29
|
+
roles: [ARC]
|
|
30
|
+
viewpoint: vp-arc-technical-constraints
|
|
31
|
+
- text: 非機能テスト計画の起点として参照できること
|
|
32
|
+
roles: [QE]
|
|
33
|
+
viewpoint: vp-qe-verifiability
|
|
34
|
+
|
|
35
|
+
- local_id: nfr-reliability
|
|
36
|
+
name: 非機能要件(信頼性)
|
|
37
|
+
kind: work
|
|
38
|
+
depends_on:
|
|
39
|
+
- nfr-index
|
|
40
|
+
overview: 障害抑止と誤動作防止に関する要件を定義する(故障率・MTBF・エラー率等)
|
|
41
|
+
path: nfr-reliability.md
|
|
42
|
+
rulebook: specdojo:nfr-reliability-rulebook
|
|
43
|
+
done_criteria:
|
|
44
|
+
- text: 信頼性要件が業務継続性の観点で記述されていること
|
|
45
|
+
roles: [BA]
|
|
46
|
+
viewpoint: vp-ba-business-value
|
|
47
|
+
- text: 信頼性目標値を承認できること
|
|
48
|
+
roles: [PO]
|
|
49
|
+
viewpoint: vp-po-decision-readiness
|
|
50
|
+
- text: 技術的実現方式(冗長化・エラーハンドリング)の制約として参照できること
|
|
51
|
+
roles: [ARC]
|
|
52
|
+
viewpoint: vp-arc-technical-constraints
|
|
53
|
+
- text: 信頼性テスト(障害テスト・エラー率検証)の基準として使えること
|
|
54
|
+
roles: [QE]
|
|
55
|
+
viewpoint: vp-qe-verifiability
|
|
56
|
+
|
|
57
|
+
- local_id: nfr-availability
|
|
58
|
+
name: 非機能要件(可用性)
|
|
59
|
+
kind: work
|
|
60
|
+
depends_on:
|
|
61
|
+
- nfr-index
|
|
62
|
+
overview: システム稼働の継続性に関する要件を定義する(稼働率・RTO/RPO・フェイルオーバー等)
|
|
63
|
+
path: nfr-availability.md
|
|
64
|
+
rulebook: specdojo:nfr-availability-rulebook
|
|
65
|
+
done_criteria:
|
|
66
|
+
- text: 稼働率・RTO/RPO要件が業務影響の観点で記述されていること
|
|
67
|
+
roles: [BA]
|
|
68
|
+
viewpoint: vp-ba-business-value
|
|
69
|
+
- text: 可用性目標値を承認できること
|
|
70
|
+
roles: [PO]
|
|
71
|
+
viewpoint: vp-po-decision-readiness
|
|
72
|
+
- text: フェイルオーバー・冗長化設計の制約として参照できること
|
|
73
|
+
roles: [ARC]
|
|
74
|
+
viewpoint: vp-arc-technical-constraints
|
|
75
|
+
- text: 可用性テスト(障害切替・復旧検証)の基準として使えること
|
|
76
|
+
roles: [QE]
|
|
77
|
+
viewpoint: vp-qe-verifiability
|
|
78
|
+
- text: 監視・障害対応設計の前提として参照できること
|
|
79
|
+
roles: [OPS]
|
|
80
|
+
viewpoint: vp-ops-operability
|
|
81
|
+
|
|
82
|
+
- local_id: nfr-maintainability
|
|
83
|
+
min_size: medium
|
|
84
|
+
name: 非機能要件(保守性)
|
|
85
|
+
kind: work
|
|
86
|
+
depends_on:
|
|
87
|
+
- nfr-index
|
|
88
|
+
overview: 変更容易性と復旧容易性に関する要件を定義する(MTTR・変更リードタイム・ログ粒度等)
|
|
89
|
+
path: nfr-maintainability.md
|
|
90
|
+
rulebook: specdojo:nfr-maintainability-rulebook
|
|
91
|
+
done_criteria:
|
|
92
|
+
- text: 保守性要件が運用継続性の観点で記述されていること
|
|
93
|
+
roles: [BA]
|
|
94
|
+
viewpoint: vp-ba-business-value
|
|
95
|
+
- text: 保守性目標値を承認できること
|
|
96
|
+
roles: [PO]
|
|
97
|
+
viewpoint: vp-po-decision-readiness
|
|
98
|
+
- text: ログ粒度・変更設計方針の制約として参照できること
|
|
99
|
+
roles: [ARC]
|
|
100
|
+
viewpoint: vp-arc-technical-constraints
|
|
101
|
+
- text: 保守性テスト(ログ検証・変更影響テスト)の基準として使えること
|
|
102
|
+
roles: [QE]
|
|
103
|
+
viewpoint: vp-qe-verifiability
|
|
104
|
+
|
|
105
|
+
- local_id: nfr-integrity
|
|
106
|
+
min_size: medium
|
|
107
|
+
name: 非機能要件(完全性)
|
|
108
|
+
kind: work
|
|
109
|
+
depends_on:
|
|
110
|
+
- nfr-index
|
|
111
|
+
overview: データ正確性と改ざん防止に関する要件を定義する(整合性検証・監査証跡・トランザクション境界等)
|
|
112
|
+
path: nfr-integrity.md
|
|
113
|
+
rulebook: specdojo:nfr-integrity-rulebook
|
|
114
|
+
done_criteria:
|
|
115
|
+
- text: データ整合性要件が業務データ品質の観点で記述されていること
|
|
116
|
+
roles: [BA]
|
|
117
|
+
viewpoint: vp-ba-business-value
|
|
118
|
+
- text: 完全性目標値を承認できること
|
|
119
|
+
roles: [PO]
|
|
120
|
+
viewpoint: vp-po-decision-readiness
|
|
121
|
+
- text: トランザクション境界・監査ログ設計の制約として参照できること
|
|
122
|
+
roles: [ARC]
|
|
123
|
+
viewpoint: vp-arc-technical-constraints
|
|
124
|
+
- text: データ整合性テスト・監査証跡検証の基準として使えること
|
|
125
|
+
roles: [QE]
|
|
126
|
+
viewpoint: vp-qe-verifiability
|
|
127
|
+
|
|
128
|
+
- local_id: nfr-security-safety
|
|
129
|
+
name: 非機能要件(機密性・安全性)
|
|
130
|
+
kind: work
|
|
131
|
+
depends_on:
|
|
132
|
+
- nfr-index
|
|
133
|
+
overview: 不正利用防止とセキュリティに関する要件を定義する(認証・認可・暗号化・アクセス制御等)
|
|
134
|
+
path: nfr-security-safety.md
|
|
135
|
+
rulebook: specdojo:nfr-security-safety-rulebook
|
|
136
|
+
done_criteria:
|
|
137
|
+
- text: セキュリティ要件が業務データ保護の観点で記述されていること
|
|
138
|
+
roles: [BA]
|
|
139
|
+
viewpoint: vp-ba-business-value
|
|
140
|
+
- text: セキュリティ目標・コンプライアンス要件を承認できること
|
|
141
|
+
roles: [PO]
|
|
142
|
+
viewpoint: vp-po-decision-readiness
|
|
143
|
+
- text: 認証・認可・暗号化設計の制約として参照できること
|
|
144
|
+
roles: [ARC]
|
|
145
|
+
viewpoint: vp-arc-technical-constraints
|
|
146
|
+
- text: セキュリティテスト(脆弱性・侵入テスト)の基準として使えること
|
|
147
|
+
roles: [QE]
|
|
148
|
+
viewpoint: vp-qe-verifiability
|
|
149
|
+
|
|
150
|
+
- local_id: nfr-performance
|
|
151
|
+
name: 非機能要件(性能)
|
|
152
|
+
kind: work
|
|
153
|
+
depends_on:
|
|
154
|
+
- nfr-index
|
|
155
|
+
overview: 応答性と処理能力に関する要件を定義する(P95/P99レイテンシ・RPS・リソース効率等)
|
|
156
|
+
path: nfr-performance.md
|
|
157
|
+
rulebook: specdojo:nfr-performance-rulebook
|
|
158
|
+
done_criteria:
|
|
159
|
+
- text: 性能要件が業務利用の観点で記述されていること
|
|
160
|
+
roles: [BA]
|
|
161
|
+
viewpoint: vp-ba-business-value
|
|
162
|
+
- text: 性能目標値を承認できること
|
|
163
|
+
roles: [PO]
|
|
164
|
+
viewpoint: vp-po-decision-readiness
|
|
165
|
+
- text: キャッシュ・スケーリング・DB最適化設計の制約として参照できること
|
|
166
|
+
roles: [ARC]
|
|
167
|
+
viewpoint: vp-arc-technical-constraints
|
|
168
|
+
- text: 負荷テスト・性能テストの基準として使えること
|
|
169
|
+
roles: [QE]
|
|
170
|
+
viewpoint: vp-qe-verifiability
|
|
171
|
+
|
|
172
|
+
- local_id: nfr-operations
|
|
173
|
+
min_size: medium
|
|
174
|
+
name: 非機能要件(運用)
|
|
175
|
+
kind: work
|
|
176
|
+
depends_on:
|
|
177
|
+
- nfr-index
|
|
178
|
+
overview: 監視・手順・継続運用に関する要件を定義する(アラート検知率・復旧達成率・運用手順充実度等)
|
|
179
|
+
path: nfr-operations.md
|
|
180
|
+
rulebook: specdojo:nfr-operations-rulebook
|
|
181
|
+
done_criteria:
|
|
182
|
+
- text: 運用要件が業務継続性の観点で記述されていること
|
|
183
|
+
roles: [BA]
|
|
184
|
+
viewpoint: vp-ba-business-value
|
|
185
|
+
- text: 運用目標値を承認できること
|
|
186
|
+
roles: [PO]
|
|
187
|
+
viewpoint: vp-po-decision-readiness
|
|
188
|
+
- text: 監視・アラート設計の制約として参照できること
|
|
189
|
+
roles: [ARC]
|
|
190
|
+
viewpoint: vp-arc-technical-constraints
|
|
191
|
+
- text: 運用テスト・障害対応訓練の基準として使えること
|
|
192
|
+
roles: [QE]
|
|
193
|
+
viewpoint: vp-qe-verifiability
|
|
194
|
+
- text: 運用設計・手順整備の前提として参照できること
|
|
195
|
+
roles: [OPS]
|
|
196
|
+
viewpoint: vp-ops-operability
|
|
197
|
+
|
|
198
|
+
- local_id: nfr-usability
|
|
199
|
+
min_size: medium
|
|
200
|
+
name: 非機能要件(操作性)
|
|
201
|
+
kind: work
|
|
202
|
+
depends_on:
|
|
203
|
+
- nfr-index
|
|
204
|
+
overview: 使いやすさと誤操作防止に関する要件を定義する(タスク完了率・誤操作率・エラーメッセージ明確性等)
|
|
205
|
+
path: nfr-usability.md
|
|
206
|
+
rulebook: specdojo:nfr-usability-rulebook
|
|
207
|
+
done_criteria:
|
|
208
|
+
- text: 操作性要件が業務ユーザー観点で記述されていること
|
|
209
|
+
roles: [BA]
|
|
210
|
+
viewpoint: vp-ba-business-value
|
|
211
|
+
- text: 操作性目標値を承認できること
|
|
212
|
+
roles: [PO]
|
|
213
|
+
viewpoint: vp-po-decision-readiness
|
|
214
|
+
- text: UI設計・エラーメッセージ設計の制約として参照できること
|
|
215
|
+
roles: [ARC]
|
|
216
|
+
viewpoint: vp-arc-technical-constraints
|
|
217
|
+
- text: ユーザビリティテストの基準として使えること
|
|
218
|
+
roles: [QE]
|
|
219
|
+
viewpoint: vp-qe-verifiability
|
|
220
|
+
- text: 画面設計・操作フロー設計の前提として参照できること
|
|
221
|
+
roles: [UX]
|
|
222
|
+
viewpoint: vp-ux-readability
|
|
@@ -0,0 +1,108 @@
|
|
|
1
|
+
# yaml-language-server: $schema=../../../specdojo/schemas/v1/dct.schema.yaml
|
|
2
|
+
# specdojo-schema: validate=false reason=template
|
|
3
|
+
# Template: operations deliverables catalog
|
|
4
|
+
id: specdojo:dct-operations-template
|
|
5
|
+
type: template
|
|
6
|
+
status: draft
|
|
7
|
+
title: 成果物カタログ(運用)
|
|
8
|
+
rulebook: specdojo:dct-rulebook
|
|
9
|
+
domain: operations
|
|
10
|
+
base_path: /docs/ja/product/090-operations
|
|
11
|
+
|
|
12
|
+
groups:
|
|
13
|
+
# ── 運用設計 ──────────────────────────────────────────────────────────────
|
|
14
|
+
- name: 運用設計
|
|
15
|
+
deliverables:
|
|
16
|
+
- local_id: opd-index
|
|
17
|
+
name: 運用方針・設計
|
|
18
|
+
kind: work
|
|
19
|
+
depends_on: []
|
|
20
|
+
overview: 切替後の恒常運用を「あるべき姿」として定義し、運用品質(SLO/SLA・責任分界・統制)をSSOT化する
|
|
21
|
+
path: opd-index.md
|
|
22
|
+
rulebook: specdojo:opd-rulebook
|
|
23
|
+
done_criteria:
|
|
24
|
+
- text: SLO/SLA・体制・監視・変更管理・バックアップ方針が業務継続性の観点で記述されていること
|
|
25
|
+
roles: [BA]
|
|
26
|
+
viewpoint: vp-ba-business-value
|
|
27
|
+
- text: 運用方針・品質目標を承認できること
|
|
28
|
+
roles: [PO]
|
|
29
|
+
viewpoint: vp-po-decision-readiness
|
|
30
|
+
- text: 監視・アラート・障害対応・権限管理の技術設計が識別できること
|
|
31
|
+
roles: [ARC]
|
|
32
|
+
viewpoint: vp-arc-technical-constraints
|
|
33
|
+
- text: 運用品質(アラート検知率・復旧達成率)の検証基準が確認できること
|
|
34
|
+
roles: [QE]
|
|
35
|
+
viewpoint: vp-qe-verifiability
|
|
36
|
+
- text: 運用手順・監視・問い合わせ対応の実施基盤として参照できること
|
|
37
|
+
roles: [OPS]
|
|
38
|
+
viewpoint: vp-ops-operability
|
|
39
|
+
|
|
40
|
+
- local_id: opd-_TERM_
|
|
41
|
+
min_size: medium
|
|
42
|
+
name: 運用方針・設計(個別)
|
|
43
|
+
kind: work
|
|
44
|
+
depends_on:
|
|
45
|
+
- opd-index
|
|
46
|
+
overview: 特定の運用テーマ(監視・障害対応等)に関する方針・設計を個別に定義する
|
|
47
|
+
path: opd-_TERM_.md
|
|
48
|
+
rulebook: specdojo:opd-rulebook
|
|
49
|
+
note: "_TERM_ は対象運用テーマの略称(例: monitoring, incident)(kebab-case)"
|
|
50
|
+
done_criteria:
|
|
51
|
+
- text: 個別テーマの運用方針が業務継続性の観点で記述されていること
|
|
52
|
+
roles: [BA]
|
|
53
|
+
viewpoint: vp-ba-business-value
|
|
54
|
+
- text: 個別テーマの技術設計が識別できること
|
|
55
|
+
roles: [ARC]
|
|
56
|
+
viewpoint: vp-arc-technical-constraints
|
|
57
|
+
- text: 運用手順整備の前提として参照できること
|
|
58
|
+
roles: [OPS]
|
|
59
|
+
viewpoint: vp-ops-operability
|
|
60
|
+
|
|
61
|
+
# ── 運用手順 ──────────────────────────────────────────────────────────────
|
|
62
|
+
- name: 運用手順
|
|
63
|
+
deliverables:
|
|
64
|
+
- local_id: opr-index
|
|
65
|
+
name: 運用手順
|
|
66
|
+
kind: work
|
|
67
|
+
depends_on:
|
|
68
|
+
- opd-index
|
|
69
|
+
overview: 運用作業を再現可能な手順として定義し、誰がやっても同じ結果になる状態を作る
|
|
70
|
+
path: opr-index.md
|
|
71
|
+
rulebook: specdojo:opr-rulebook
|
|
72
|
+
done_criteria:
|
|
73
|
+
- text: 日次・週次・月次の定常運用手順が業務観点で記述されていること
|
|
74
|
+
roles: [BA]
|
|
75
|
+
viewpoint: vp-ba-business-value
|
|
76
|
+
- text: 運用手順の妥当性を承認できること
|
|
77
|
+
roles: [PO]
|
|
78
|
+
viewpoint: vp-po-decision-readiness
|
|
79
|
+
- text: 障害対応・アラート対応・バックアップ手順の技術的整合が確認できること
|
|
80
|
+
roles: [ARC]
|
|
81
|
+
viewpoint: vp-arc-technical-constraints
|
|
82
|
+
- text: 手順の網羅性・実施可能性・証跡要件が確認できること
|
|
83
|
+
roles: [QE]
|
|
84
|
+
viewpoint: vp-qe-verifiability
|
|
85
|
+
- text: 誰が実施しても同じ結果になる粒度で手順が記述されていること
|
|
86
|
+
roles: [OPS]
|
|
87
|
+
viewpoint: vp-ops-operability
|
|
88
|
+
|
|
89
|
+
- local_id: opr-_TERM_
|
|
90
|
+
min_size: medium
|
|
91
|
+
name: 運用手順(個別)
|
|
92
|
+
kind: work
|
|
93
|
+
depends_on:
|
|
94
|
+
- opr-index
|
|
95
|
+
overview: 特定の運用作業(障害対応・バックアップ・リストア等)の手順を個別に定義する
|
|
96
|
+
path: opr-_TERM_.md
|
|
97
|
+
rulebook: specdojo:opr-rulebook
|
|
98
|
+
note: "_TERM_ は対象運用作業の略称(例: incident, backup-restore)(kebab-case)"
|
|
99
|
+
done_criteria:
|
|
100
|
+
- text: 個別手順が実施可能な粒度で記述されていること
|
|
101
|
+
roles: [OPS]
|
|
102
|
+
viewpoint: vp-ops-operability
|
|
103
|
+
- text: 手順の技術的正確性が確認できること
|
|
104
|
+
roles: [ARC]
|
|
105
|
+
viewpoint: vp-arc-technical-constraints
|
|
106
|
+
- text: 手順の完了条件・証跡要件が確認できること
|
|
107
|
+
roles: [QE]
|
|
108
|
+
viewpoint: vp-qe-verifiability
|