specdojo 0.1.0 → 0.2.1
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 +142 -35
- 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 +990 -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 +54 -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 +33 -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 +56 -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 +472 -0
- package/docs/ja/specdojo/guides/register-operation-guide.md +418 -0
- package/docs/ja/specdojo/guides/remote-host-development-guide.md +163 -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 +121 -24
- package/templates/antigravity/README.md +35 -0
- package/templates/antigravity/exec-defaults-snippet.yaml +38 -0
- package/templates/antigravity/orchestrator.md +146 -0
- package/templates/antigravity/pm-members-snippet.yaml +55 -0
- 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/agents/specdojo-orchestrator.md +153 -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/codex/agents/specdojo-orchestrator.toml +154 -0
- package/templates/codex/orchestrator.md +146 -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/templates/opencode/agents/specdojo-orchestrator.md +193 -0
- package/dist/exec-schedule-timeline-render.js +0 -201
- package/dist/exec-schedule-timeline.js +0 -2
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
# yaml-language-server: $schema=../../../specdojo/schemas/v1/dct.schema.yaml
|
|
2
|
+
# specdojo-schema: validate=false reason=template
|
|
3
|
+
# Template: business acceptance criteria deliverables catalog
|
|
4
|
+
id: specdojo:dct-business-acceptance-criteria-template
|
|
5
|
+
type: template
|
|
6
|
+
status: draft
|
|
7
|
+
title: 成果物カタログ(業務受入基準)
|
|
8
|
+
rulebook: specdojo:dct-rulebook
|
|
9
|
+
domain: business-acceptance-criteria
|
|
10
|
+
base_path: /docs/ja/product/050-business-acceptance-criteria
|
|
11
|
+
|
|
12
|
+
groups:
|
|
13
|
+
- deliverables:
|
|
14
|
+
- local_id: bac-_TERM_
|
|
15
|
+
name: 業務受入条件
|
|
16
|
+
kind: work
|
|
17
|
+
depends_on: []
|
|
18
|
+
overview: 業務として受け入れ可能であることを示す条件・シナリオ・判定方法を定義する
|
|
19
|
+
path: bac-_TERM_.md
|
|
20
|
+
rulebook: specdojo:bac-rulebook
|
|
21
|
+
note: "_TERM_ は対象業務シナリオ・機能名の略称(kebab-case)"
|
|
22
|
+
done_criteria:
|
|
23
|
+
- text: 業務シナリオ・受入条件・前提・期待結果が業務観点で記述されていること
|
|
24
|
+
roles: [BA]
|
|
25
|
+
viewpoint: vp-ba-requirements-completeness
|
|
26
|
+
- text: 受入条件の業務的妥当性と判定基準を承認できること
|
|
27
|
+
roles: [PO]
|
|
28
|
+
viewpoint: vp-po-decision-readiness
|
|
29
|
+
- text: システム実装が受入条件を満たせる設計になっていること
|
|
30
|
+
roles: [ARC]
|
|
31
|
+
viewpoint: vp-arc-technical-constraints
|
|
32
|
+
- text: 受入テスト設計の基礎として活用できること
|
|
33
|
+
roles: [QE]
|
|
34
|
+
viewpoint: vp-qe-verifiability
|
|
@@ -0,0 +1,75 @@
|
|
|
1
|
+
# yaml-language-server: $schema=../../../specdojo/schemas/v1/dct.schema.yaml
|
|
2
|
+
# specdojo-schema: validate=false reason=template
|
|
3
|
+
# Template: business model deliverables catalog (business event spec)
|
|
4
|
+
# Placeholder _PROJECT_ID_ is not used for product-level templates.
|
|
5
|
+
# base_path is fixed to the product document directory.
|
|
6
|
+
#
|
|
7
|
+
# This file is one physical part of the business-model domain. It shares domain
|
|
8
|
+
# `business-model` with the other dct-business-model-<part>-template.yaml files;
|
|
9
|
+
# catalog build merges same-domain parts and combines same-name groups (in sorted
|
|
10
|
+
# file order) into one dct-business-model.md.
|
|
11
|
+
#
|
|
12
|
+
# bes-index は _TERM_ を持たない全体構成(単一)で、個別イベント bes-_TERM_ と
|
|
13
|
+
# 同じ業務イベントファミリーのため、この1ファイルにまとめる。
|
|
14
|
+
#
|
|
15
|
+
# local_id の _TERM_ 反復方針(複数業務領域への複製 / 単一領域を複数項目に分割)は
|
|
16
|
+
# dct-rulebook.md の「業務領域テンプレートの反復方針(_TERM_ の使い分け)」を正とする。
|
|
17
|
+
id: specdojo:dct-business-model-bes-template
|
|
18
|
+
type: template
|
|
19
|
+
status: draft
|
|
20
|
+
title: 成果物カタログ(業務モデル/業務イベント仕様)
|
|
21
|
+
rulebook: specdojo:dct-rulebook
|
|
22
|
+
domain: business-model
|
|
23
|
+
base_path: /docs/ja/product/010-business-specs/030-business-model
|
|
24
|
+
|
|
25
|
+
groups:
|
|
26
|
+
# ── 業務イベント ──────────────────────────────────────────────────────────
|
|
27
|
+
- name: 業務イベント
|
|
28
|
+
deliverables:
|
|
29
|
+
- local_id: bes-index
|
|
30
|
+
name: 業務イベント仕様(全体構成)
|
|
31
|
+
kind: work
|
|
32
|
+
depends_on: []
|
|
33
|
+
overview: 業務上で発生する主要なイベントを一覧で定義する
|
|
34
|
+
path: bes-index.md
|
|
35
|
+
rulebook: specdojo:bes-index-rulebook
|
|
36
|
+
done_criteria:
|
|
37
|
+
- text: 主要な業務イベントが業務観点で網羅的に一覧化されていること
|
|
38
|
+
roles: [BA]
|
|
39
|
+
viewpoint: vp-ba-requirements-completeness
|
|
40
|
+
- text: イベント一覧のスコープを承認できること
|
|
41
|
+
roles: [PO]
|
|
42
|
+
viewpoint: vp-po-purpose-alignment
|
|
43
|
+
- text: イベント駆動設計・メッセージング設計の入力として参照できること
|
|
44
|
+
roles: [ARC]
|
|
45
|
+
viewpoint: vp-arc-technical-constraints
|
|
46
|
+
- text: イベントベースのテスト設計への網羅性が確認できること
|
|
47
|
+
roles: [QE]
|
|
48
|
+
viewpoint: vp-qe-omissions-consistency
|
|
49
|
+
|
|
50
|
+
- local_id: bes-_TERM_
|
|
51
|
+
min_size: medium
|
|
52
|
+
name: 業務イベント仕様(個別)
|
|
53
|
+
kind: work
|
|
54
|
+
depends_on:
|
|
55
|
+
- bes-index
|
|
56
|
+
overview: 業務上で発生する主要なイベントを個別に詳細定義する
|
|
57
|
+
path: bes-_TERM_.md
|
|
58
|
+
rulebook: specdojo:bes-rulebook
|
|
59
|
+
note: "_TERM_ は対象イベント名の略称(kebab-case)"
|
|
60
|
+
done_criteria:
|
|
61
|
+
- text: イベント内容・発生条件・タイミングが業務観点で正確に記述されていること
|
|
62
|
+
roles: [BA]
|
|
63
|
+
viewpoint: vp-ba-requirements-completeness
|
|
64
|
+
- text: イベント仕様の業務的妥当性を承認できること
|
|
65
|
+
roles: [PO]
|
|
66
|
+
viewpoint: vp-po-purpose-alignment
|
|
67
|
+
- text: イベント処理実装・メッセージ設計の基礎として参照できること
|
|
68
|
+
roles: [ARC]
|
|
69
|
+
viewpoint: vp-arc-technical-constraints
|
|
70
|
+
- text: イベントテスト設計への活用が確認できること
|
|
71
|
+
roles: [QE]
|
|
72
|
+
viewpoint: vp-qe-verifiability
|
|
73
|
+
- text: イベントハンドラ・パブリッシャー実装の参照として使えること
|
|
74
|
+
roles: [DEV]
|
|
75
|
+
viewpoint: vp-dev-implementation-readiness
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
# yaml-language-server: $schema=../../../specdojo/schemas/v1/dct.schema.yaml
|
|
2
|
+
# specdojo-schema: validate=false reason=template
|
|
3
|
+
# Template: business model deliverables catalog (business process spec)
|
|
4
|
+
# Placeholder _PROJECT_ID_ is not used for product-level templates.
|
|
5
|
+
# base_path is fixed to the product document directory.
|
|
6
|
+
#
|
|
7
|
+
# This file is one physical part of the business-model domain. It shares domain
|
|
8
|
+
# `business-model` with the other dct-business-model-<part>-template.yaml files;
|
|
9
|
+
# catalog build merges same-domain parts and combines same-name groups (in sorted
|
|
10
|
+
# file order) into one dct-business-model.md.
|
|
11
|
+
#
|
|
12
|
+
# local_id の _TERM_ 反復方針(複数業務領域への複製 / 単一領域を複数項目に分割)は
|
|
13
|
+
# dct-rulebook.md の「業務領域テンプレートの反復方針(_TERM_ の使い分け)」を正とする。
|
|
14
|
+
id: specdojo:dct-business-model-bps-template
|
|
15
|
+
type: template
|
|
16
|
+
status: draft
|
|
17
|
+
title: 成果物カタログ(業務モデル/業務プロセス仕様)
|
|
18
|
+
rulebook: specdojo:dct-rulebook
|
|
19
|
+
domain: business-model
|
|
20
|
+
base_path: /docs/ja/product/010-business-specs/030-business-model
|
|
21
|
+
|
|
22
|
+
groups:
|
|
23
|
+
# ── 業務プロセス ──────────────────────────────────────────────────────────
|
|
24
|
+
- name: 業務プロセス
|
|
25
|
+
deliverables:
|
|
26
|
+
- local_id: bps-_TERM_
|
|
27
|
+
name: 業務プロセス仕様
|
|
28
|
+
kind: work
|
|
29
|
+
depends_on: []
|
|
30
|
+
overview: 業務プロセスのトリガー・入力・処理・出力・前提を定義する
|
|
31
|
+
path: bps-_TERM_.md
|
|
32
|
+
rulebook: specdojo:bps-rulebook
|
|
33
|
+
note: "_TERM_ は対象プロセス名の略称(kebab-case)"
|
|
34
|
+
done_criteria:
|
|
35
|
+
- text: トリガー・前提・入力・処理・出力が業務観点で正確に記述されていること
|
|
36
|
+
roles: [BA]
|
|
37
|
+
viewpoint: vp-ba-requirements-completeness
|
|
38
|
+
- text: プロセスのスコープと業務的妥当性を承認できること
|
|
39
|
+
roles: [PO]
|
|
40
|
+
viewpoint: vp-po-purpose-alignment
|
|
41
|
+
- text: システム設計・機能設計の入力として参照できること
|
|
42
|
+
roles: [ARC]
|
|
43
|
+
viewpoint: vp-arc-technical-constraints
|
|
44
|
+
- text: テストシナリオ設計・受入条件との対応が確認できること
|
|
45
|
+
roles: [QE]
|
|
46
|
+
viewpoint: vp-qe-verifiability
|
|
47
|
+
- text: 実装設計(サービス・ユースケース)の基礎として参照できること
|
|
48
|
+
roles: [DEV]
|
|
49
|
+
viewpoint: vp-dev-implementation-readiness
|
|
@@ -0,0 +1,50 @@
|
|
|
1
|
+
# yaml-language-server: $schema=../../../specdojo/schemas/v1/dct.schema.yaml
|
|
2
|
+
# specdojo-schema: validate=false reason=template
|
|
3
|
+
# Template: business model deliverables catalog (business rule)
|
|
4
|
+
# Placeholder _PROJECT_ID_ is not used for product-level templates.
|
|
5
|
+
# base_path is fixed to the product document directory.
|
|
6
|
+
#
|
|
7
|
+
# This file is one physical part of the business-model domain. It shares domain
|
|
8
|
+
# `business-model` with the other dct-business-model-<part>-template.yaml files;
|
|
9
|
+
# catalog build merges same-domain parts and combines same-name groups (in sorted
|
|
10
|
+
# file order) into one dct-business-model.md.
|
|
11
|
+
#
|
|
12
|
+
# local_id の _TERM_ 反復方針(複数業務領域への複製 / 単一領域を複数項目に分割)は
|
|
13
|
+
# dct-rulebook.md の「業務領域テンプレートの反復方針(_TERM_ の使い分け)」を正とする。
|
|
14
|
+
id: specdojo:dct-business-model-br-template
|
|
15
|
+
type: template
|
|
16
|
+
status: draft
|
|
17
|
+
title: 成果物カタログ(業務モデル/ビジネスルール)
|
|
18
|
+
rulebook: specdojo:dct-rulebook
|
|
19
|
+
domain: business-model
|
|
20
|
+
base_path: /docs/ja/product/010-business-specs/030-business-model
|
|
21
|
+
|
|
22
|
+
groups:
|
|
23
|
+
# ── 業務プロセス ──────────────────────────────────────────────────────────
|
|
24
|
+
- name: 業務プロセス
|
|
25
|
+
deliverables:
|
|
26
|
+
- local_id: br-_TERM_
|
|
27
|
+
min_size: medium
|
|
28
|
+
name: ビジネスルール
|
|
29
|
+
kind: work
|
|
30
|
+
depends_on: []
|
|
31
|
+
overview: 複数プロセスから参照される横断的な業務判断・条件を定義する
|
|
32
|
+
path: br-_TERM_.md
|
|
33
|
+
rulebook: specdojo:br-rulebook
|
|
34
|
+
note: "_TERM_ は対象ルール名の略称(kebab-case)"
|
|
35
|
+
done_criteria:
|
|
36
|
+
- text: ルール・入力・出力・例外が業務観点で明確に記述されていること
|
|
37
|
+
roles: [BA]
|
|
38
|
+
viewpoint: vp-ba-requirements-completeness
|
|
39
|
+
- text: ルールの業務的妥当性と適用範囲を承認できること
|
|
40
|
+
roles: [PO]
|
|
41
|
+
viewpoint: vp-po-purpose-alignment
|
|
42
|
+
- text: ルール実装(バリデーション・ドメインロジック)の基礎として参照できること
|
|
43
|
+
roles: [ARC]
|
|
44
|
+
viewpoint: vp-arc-technical-constraints
|
|
45
|
+
- text: ルールベースのテストケース設計に活用できること
|
|
46
|
+
roles: [QE]
|
|
47
|
+
viewpoint: vp-qe-verifiability
|
|
48
|
+
- text: ビジネスロジック実装の参照として使えること
|
|
49
|
+
roles: [DEV]
|
|
50
|
+
viewpoint: vp-dev-implementation-readiness
|
|
@@ -0,0 +1,40 @@
|
|
|
1
|
+
# yaml-language-server: $schema=../../../specdojo/schemas/v1/dct.schema.yaml
|
|
2
|
+
# specdojo-schema: validate=false reason=template
|
|
3
|
+
# Template: data flow deliverables catalog
|
|
4
|
+
# Placeholder _PROJECT_ID_ is not used for product-level templates.
|
|
5
|
+
# base_path is fixed to the product document directory.
|
|
6
|
+
#
|
|
7
|
+
# local_id の _TERM_ 反復方針(複数業務領域への複製 / 単一領域を複数のデータフロー
|
|
8
|
+
# に分割)は dct-rulebook.md の「業務領域テンプレートの反復方針(_TERM_ の使い分け)」
|
|
9
|
+
# を正とする。
|
|
10
|
+
id: specdojo:dct-data-flow-template
|
|
11
|
+
type: template
|
|
12
|
+
status: draft
|
|
13
|
+
title: 成果物カタログ(データフロー)
|
|
14
|
+
rulebook: specdojo:dct-rulebook
|
|
15
|
+
domain: data-flow
|
|
16
|
+
base_path: /docs/ja/product/010-business-specs/010-data-flow
|
|
17
|
+
|
|
18
|
+
groups:
|
|
19
|
+
- deliverables:
|
|
20
|
+
- local_id: cdfd-_TERM_
|
|
21
|
+
name: 概念データフロー図
|
|
22
|
+
kind: work
|
|
23
|
+
depends_on: []
|
|
24
|
+
overview: 対象業務の全体構成・情報の流れ・業務主体を可視化し定義する
|
|
25
|
+
path: cdfd-_TERM_.md
|
|
26
|
+
rulebook: specdojo:cdfd-rulebook
|
|
27
|
+
note: "_TERM_ は対象業務名の略称(kebab-case)。単一領域を複数のデータフローに分割する場合は dct-rulebook.md の「業務領域テンプレートの反復方針(_TERM_ の使い分け)」を参照し、この1件を削除してデータフローごとに固定 local_id を記載する"
|
|
28
|
+
done_criteria:
|
|
29
|
+
- text: 業務プロセス・情報の流れ・業務主体が業務観点で正確に表現されていること
|
|
30
|
+
roles: [BA]
|
|
31
|
+
viewpoint: vp-ba-business-value
|
|
32
|
+
- text: 対象業務のスコープと境界を承認できること
|
|
33
|
+
roles: [PO]
|
|
34
|
+
viewpoint: vp-po-purpose-alignment
|
|
35
|
+
- text: システム設計・アーキテクチャの入力として参照できること
|
|
36
|
+
roles: [ARC]
|
|
37
|
+
viewpoint: vp-arc-technical-constraints
|
|
38
|
+
- text: テスト対象業務フローが識別できること
|
|
39
|
+
roles: [QE]
|
|
40
|
+
viewpoint: vp-qe-verifiability
|
|
@@ -0,0 +1,46 @@
|
|
|
1
|
+
# yaml-language-server: $schema=../../../specdojo/schemas/v1/dct.schema.yaml
|
|
2
|
+
# specdojo-schema: validate=false reason=template
|
|
3
|
+
# Template: data model deliverables catalog (business data dictionary)
|
|
4
|
+
# Placeholder _PROJECT_ID_ is not used for product-level templates.
|
|
5
|
+
# base_path is fixed to the product document directory.
|
|
6
|
+
#
|
|
7
|
+
# This is the bdd physical part of the data-model domain. Catalog build merges
|
|
8
|
+
# all dct-data-model-*-template parts by same-name group in sorted file order.
|
|
9
|
+
#
|
|
10
|
+
# local_id の _TERM_ 反復方針(複数業務領域への複製 / 単一領域を複数項目に分割)は
|
|
11
|
+
# dct-rulebook.md の「業務領域テンプレートの反復方針(_TERM_ の使い分け)」を正とする。
|
|
12
|
+
id: specdojo:dct-data-model-bdd-template
|
|
13
|
+
type: template
|
|
14
|
+
status: draft
|
|
15
|
+
title: 成果物カタログ(データモデル/業務データ辞書)
|
|
16
|
+
rulebook: specdojo:dct-rulebook
|
|
17
|
+
domain: data-model
|
|
18
|
+
base_path: /docs/ja/product/010-business-specs/020-data-model
|
|
19
|
+
|
|
20
|
+
groups:
|
|
21
|
+
- name: 業務データ辞書
|
|
22
|
+
deliverables:
|
|
23
|
+
- local_id: bdd-_TERM_
|
|
24
|
+
name: 業務データ辞書
|
|
25
|
+
kind: work
|
|
26
|
+
depends_on: []
|
|
27
|
+
overview: 業務上の管理単位(エンティティ)とその属性の論理名・説明・制約を定義する
|
|
28
|
+
path: bdd-_TERM_.yaml
|
|
29
|
+
rulebook: specdojo:bdd-rulebook
|
|
30
|
+
note: "_TERM_ は対象業務領域の略称(kebab-case)"
|
|
31
|
+
done_criteria:
|
|
32
|
+
- text: エンティティ・属性の業務的定義が正確に記述されていること
|
|
33
|
+
roles: [BA]
|
|
34
|
+
viewpoint: vp-ba-requirements-completeness
|
|
35
|
+
- text: データスコープとエンティティ境界を承認できること
|
|
36
|
+
roles: [PO]
|
|
37
|
+
viewpoint: vp-po-purpose-alignment
|
|
38
|
+
- text: DB設計・システム設計の入力として参照できること
|
|
39
|
+
roles: [ARC]
|
|
40
|
+
viewpoint: vp-arc-technical-constraints
|
|
41
|
+
- text: データ検証ルール・制約が確認できること
|
|
42
|
+
roles: [QE]
|
|
43
|
+
viewpoint: vp-qe-verifiability
|
|
44
|
+
- text: 実装(テーブル設計・モデル定義)の基礎として参照できること
|
|
45
|
+
roles: [DEV]
|
|
46
|
+
viewpoint: vp-dev-implementation-readiness
|
|
@@ -0,0 +1,46 @@
|
|
|
1
|
+
# yaml-language-server: $schema=../../../specdojo/schemas/v1/dct.schema.yaml
|
|
2
|
+
# specdojo-schema: validate=false reason=template
|
|
3
|
+
# Template: data model deliverables catalog (conceptual class diagram)
|
|
4
|
+
# Placeholder _PROJECT_ID_ is not used for product-level templates.
|
|
5
|
+
# base_path is fixed to the product document directory.
|
|
6
|
+
#
|
|
7
|
+
# This is the ccd physical part of the data-model domain. Catalog build merges
|
|
8
|
+
# all dct-data-model-*-template parts by same-name group in sorted file order.
|
|
9
|
+
#
|
|
10
|
+
# local_id の _TERM_ 反復方針(複数業務領域への複製 / 単一領域を複数項目に分割)は
|
|
11
|
+
# dct-rulebook.md の「業務領域テンプレートの反復方針(_TERM_ の使い分け)」を正とする。
|
|
12
|
+
id: specdojo:dct-data-model-ccd-template
|
|
13
|
+
type: template
|
|
14
|
+
status: draft
|
|
15
|
+
title: 成果物カタログ(データモデル/概念クラス図)
|
|
16
|
+
rulebook: specdojo:dct-rulebook
|
|
17
|
+
domain: data-model
|
|
18
|
+
base_path: /docs/ja/product/010-business-specs/020-data-model
|
|
19
|
+
|
|
20
|
+
groups:
|
|
21
|
+
- name: 概念モデル
|
|
22
|
+
deliverables:
|
|
23
|
+
- local_id: ccd-_TERM_
|
|
24
|
+
name: 概念クラス図
|
|
25
|
+
kind: work
|
|
26
|
+
depends_on: []
|
|
27
|
+
overview: 業務上のエンティティ関係・継承・属性を図で定義する
|
|
28
|
+
path: ccd-_TERM_.md
|
|
29
|
+
rulebook: specdojo:ccd-mermaid-rulebook
|
|
30
|
+
note: "_TERM_ は対象業務領域の略称(kebab-case)"
|
|
31
|
+
done_criteria:
|
|
32
|
+
- text: エンティティ関係・属性が業務観点で正確に表現されていること
|
|
33
|
+
roles: [BA]
|
|
34
|
+
viewpoint: vp-ba-requirements-completeness
|
|
35
|
+
- text: スコープ範囲のエンティティを承認できること
|
|
36
|
+
roles: [PO]
|
|
37
|
+
viewpoint: vp-po-purpose-alignment
|
|
38
|
+
- text: データモデル・クラス設計の入力として参照できること
|
|
39
|
+
roles: [ARC]
|
|
40
|
+
viewpoint: vp-arc-technical-constraints
|
|
41
|
+
- text: テストデータ設計・整合性検証に活用できること
|
|
42
|
+
roles: [QE]
|
|
43
|
+
viewpoint: vp-qe-verifiability
|
|
44
|
+
- text: ER図・実装モデルの基礎として参照できること
|
|
45
|
+
roles: [DEV]
|
|
46
|
+
viewpoint: vp-dev-implementation-readiness
|
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
# yaml-language-server: $schema=../../../specdojo/schemas/v1/dct.schema.yaml
|
|
2
|
+
# specdojo-schema: validate=false reason=template
|
|
3
|
+
# Template: data model deliverables catalog (conceptual data store definition)
|
|
4
|
+
# Placeholder _PROJECT_ID_ is not used for product-level templates.
|
|
5
|
+
# base_path is fixed to the product document directory.
|
|
6
|
+
#
|
|
7
|
+
# This is the cdsd physical part of the data-model domain. Catalog build merges
|
|
8
|
+
# all dct-data-model-*-template parts by same-name group in sorted file order.
|
|
9
|
+
#
|
|
10
|
+
# local_id の _TERM_ 反復方針(複数業務領域への複製 / 単一領域を複数項目に分割)は
|
|
11
|
+
# dct-rulebook.md の「業務領域テンプレートの反復方針(_TERM_ の使い分け)」を正とする。
|
|
12
|
+
id: specdojo:dct-data-model-cdsd-template
|
|
13
|
+
type: template
|
|
14
|
+
status: draft
|
|
15
|
+
title: 成果物カタログ(データモデル/概念データストア定義)
|
|
16
|
+
rulebook: specdojo:dct-rulebook
|
|
17
|
+
domain: data-model
|
|
18
|
+
base_path: /docs/ja/product/010-business-specs/020-data-model
|
|
19
|
+
|
|
20
|
+
groups:
|
|
21
|
+
- name: 業務データ辞書
|
|
22
|
+
deliverables:
|
|
23
|
+
- local_id: cdsd-_TERM_
|
|
24
|
+
min_size: medium
|
|
25
|
+
name: 概念データストア定義
|
|
26
|
+
kind: work
|
|
27
|
+
depends_on: []
|
|
28
|
+
overview: 概念データストア(情報の保管場所)を一覧で定義する
|
|
29
|
+
path: cdsd-_TERM_.md
|
|
30
|
+
rulebook: specdojo:cdsd-rulebook
|
|
31
|
+
note: "_TERM_ は対象業務領域の略称(kebab-case)"
|
|
32
|
+
done_criteria:
|
|
33
|
+
- text: データストアの業務的役割・内容・粒度が記述されていること
|
|
34
|
+
roles: [BA]
|
|
35
|
+
viewpoint: vp-ba-requirements-completeness
|
|
36
|
+
- text: データストア構成を設計の基礎として参照できること
|
|
37
|
+
roles: [ARC]
|
|
38
|
+
viewpoint: vp-arc-technical-constraints
|
|
39
|
+
- text: データ検証・整合性確認の対象が識別できること
|
|
40
|
+
roles: [QE]
|
|
41
|
+
viewpoint: vp-qe-verifiability
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
# yaml-language-server: $schema=../../../specdojo/schemas/v1/dct.schema.yaml
|
|
2
|
+
# specdojo-schema: validate=false reason=template
|
|
3
|
+
# Template: data model deliverables catalog (classification definition)
|
|
4
|
+
# Placeholder _PROJECT_ID_ is not used for product-level templates.
|
|
5
|
+
# base_path is fixed to the product document directory.
|
|
6
|
+
#
|
|
7
|
+
# This is the cld physical part of the data-model domain. Catalog build merges
|
|
8
|
+
# all dct-data-model-*-template parts by same-name group in sorted file order.
|
|
9
|
+
#
|
|
10
|
+
# local_id の _TERM_ 反復方針(複数業務領域への複製 / 単一領域を複数項目に分割)は
|
|
11
|
+
# dct-rulebook.md の「業務領域テンプレートの反復方針(_TERM_ の使い分け)」を正とする。
|
|
12
|
+
id: specdojo:dct-data-model-cld-template
|
|
13
|
+
type: template
|
|
14
|
+
status: draft
|
|
15
|
+
title: 成果物カタログ(データモデル/分類定義)
|
|
16
|
+
rulebook: specdojo:dct-rulebook
|
|
17
|
+
domain: data-model
|
|
18
|
+
base_path: /docs/ja/product/010-business-specs/020-data-model
|
|
19
|
+
|
|
20
|
+
groups:
|
|
21
|
+
- name: 業務データ辞書
|
|
22
|
+
deliverables:
|
|
23
|
+
- local_id: cld-_TERM_
|
|
24
|
+
min_size: medium
|
|
25
|
+
name: 分類定義
|
|
26
|
+
kind: work
|
|
27
|
+
depends_on: []
|
|
28
|
+
overview: 業務上の分類(カテゴリ・種別・区分など)を一覧で定義する
|
|
29
|
+
path: cld-_TERM_.md
|
|
30
|
+
rulebook: specdojo:cld-rulebook
|
|
31
|
+
note: "_TERM_ は対象分類体系の略称(kebab-case)"
|
|
32
|
+
done_criteria:
|
|
33
|
+
- text: 分類名・説明が業務観点で正確に定義されていること
|
|
34
|
+
roles: [BA]
|
|
35
|
+
viewpoint: vp-ba-requirements-completeness
|
|
36
|
+
- text: 分類実装(マスタデータ・コード値)の基礎として参照できること
|
|
37
|
+
roles: [DEV]
|
|
38
|
+
viewpoint: vp-dev-implementation-readiness
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
# yaml-language-server: $schema=../../../specdojo/schemas/v1/dct.schema.yaml
|
|
2
|
+
# specdojo-schema: validate=false reason=template
|
|
3
|
+
# Template: data model deliverables catalog (storage location definition)
|
|
4
|
+
# Placeholder _PROJECT_ID_ is not used for product-level templates.
|
|
5
|
+
# base_path is fixed to the product document directory.
|
|
6
|
+
#
|
|
7
|
+
# This is the sld physical part of the data-model domain. Catalog build merges
|
|
8
|
+
# all dct-data-model-*-template parts by same-name group in sorted file order.
|
|
9
|
+
#
|
|
10
|
+
# local_id の _TERM_ 反復方針(複数業務領域への複製 / 単一領域を複数項目に分割)は
|
|
11
|
+
# dct-rulebook.md の「業務領域テンプレートの反復方針(_TERM_ の使い分け)」を正とする。
|
|
12
|
+
id: specdojo:dct-data-model-sld-template
|
|
13
|
+
type: template
|
|
14
|
+
status: draft
|
|
15
|
+
title: 成果物カタログ(データモデル/保管場所定義)
|
|
16
|
+
rulebook: specdojo:dct-rulebook
|
|
17
|
+
domain: data-model
|
|
18
|
+
base_path: /docs/ja/product/010-business-specs/020-data-model
|
|
19
|
+
|
|
20
|
+
groups:
|
|
21
|
+
- name: 業務データ辞書
|
|
22
|
+
deliverables:
|
|
23
|
+
- local_id: sld-_TERM_
|
|
24
|
+
min_size: medium
|
|
25
|
+
name: 保管場所定義
|
|
26
|
+
kind: work
|
|
27
|
+
depends_on: []
|
|
28
|
+
overview: 業務対象となる物の物理的な保管場所を一覧で定義する
|
|
29
|
+
path: sld-_TERM_.md
|
|
30
|
+
rulebook: specdojo:sld-rulebook
|
|
31
|
+
note: "_TERM_ は対象業務領域の略称(kebab-case)"
|
|
32
|
+
done_criteria:
|
|
33
|
+
- text: 保管場所・保管対象・管理頻度が業務観点で記述されていること
|
|
34
|
+
roles: [BA]
|
|
35
|
+
viewpoint: vp-ba-requirements-completeness
|
|
36
|
+
- text: 保管場所の運用・管理方針が確認できること
|
|
37
|
+
roles: [QE]
|
|
38
|
+
viewpoint: vp-qe-verifiability
|
|
@@ -0,0 +1,46 @@
|
|
|
1
|
+
# yaml-language-server: $schema=../../../specdojo/schemas/v1/dct.schema.yaml
|
|
2
|
+
# specdojo-schema: validate=false reason=template
|
|
3
|
+
# Template: data model deliverables catalog (status definition)
|
|
4
|
+
# Placeholder _PROJECT_ID_ is not used for product-level templates.
|
|
5
|
+
# base_path is fixed to the product document directory.
|
|
6
|
+
#
|
|
7
|
+
# This is the stsd physical part of the data-model domain. Catalog build merges
|
|
8
|
+
# all dct-data-model-*-template parts by same-name group in sorted file order.
|
|
9
|
+
#
|
|
10
|
+
# local_id の _TERM_ 反復方針(複数業務領域への複製 / 単一領域を複数項目に分割)は
|
|
11
|
+
# dct-rulebook.md の「業務領域テンプレートの反復方針(_TERM_ の使い分け)」を正とする。
|
|
12
|
+
id: specdojo:dct-data-model-stsd-template
|
|
13
|
+
type: template
|
|
14
|
+
status: draft
|
|
15
|
+
title: 成果物カタログ(データモデル/ステータス定義・状態遷移)
|
|
16
|
+
rulebook: specdojo:dct-rulebook
|
|
17
|
+
domain: data-model
|
|
18
|
+
base_path: /docs/ja/product/010-business-specs/020-data-model
|
|
19
|
+
|
|
20
|
+
groups:
|
|
21
|
+
- name: 業務データ辞書
|
|
22
|
+
deliverables:
|
|
23
|
+
- local_id: stsd-_TERM_
|
|
24
|
+
name: ステータス定義
|
|
25
|
+
kind: work
|
|
26
|
+
depends_on: []
|
|
27
|
+
overview: 業務上のエンティティが取り得る状態(ステータス)と状態遷移を一覧・図で定義する
|
|
28
|
+
path: stsd-_TERM_.md
|
|
29
|
+
rulebook: specdojo:stsd-rulebook
|
|
30
|
+
note: "_TERM_ は対象エンティティ・ライフサイクルの略称(kebab-case)"
|
|
31
|
+
done_criteria:
|
|
32
|
+
- text: ステータス名・意味・成立条件と、遷移・イベント・条件が業務観点で正確に定義されていること
|
|
33
|
+
roles: [BA]
|
|
34
|
+
viewpoint: vp-ba-requirements-completeness
|
|
35
|
+
- text: 状態遷移の業務的妥当性を承認できること
|
|
36
|
+
roles: [PO]
|
|
37
|
+
viewpoint: vp-po-purpose-alignment
|
|
38
|
+
- text: 状態遷移実装の基礎として参照できること
|
|
39
|
+
roles: [ARC]
|
|
40
|
+
viewpoint: vp-arc-technical-constraints
|
|
41
|
+
- text: 状態・遷移ベースのテスト設計に活用できること
|
|
42
|
+
roles: [QE]
|
|
43
|
+
viewpoint: vp-qe-verifiability
|
|
44
|
+
- text: 状態管理・遷移ロジック実装の参照として使えること
|
|
45
|
+
roles: [DEV]
|
|
46
|
+
viewpoint: vp-dev-implementation-readiness
|
|
@@ -0,0 +1,114 @@
|
|
|
1
|
+
# yaml-language-server: $schema=../../../specdojo/schemas/v1/dct.schema.yaml
|
|
2
|
+
# specdojo-schema: validate=false reason=template
|
|
3
|
+
# Template: external IF specifications deliverables catalog
|
|
4
|
+
id: specdojo:dct-external-interface-specs-template
|
|
5
|
+
type: template
|
|
6
|
+
status: draft
|
|
7
|
+
title: 成果物カタログ(外部IF仕様)
|
|
8
|
+
rulebook: specdojo:dct-rulebook
|
|
9
|
+
domain: external-interface-specs
|
|
10
|
+
base_path: /docs/ja/product/020-external-interface-specs
|
|
11
|
+
|
|
12
|
+
groups:
|
|
13
|
+
- deliverables:
|
|
14
|
+
- local_id: ifx-index
|
|
15
|
+
name: 外部システムI/F一覧
|
|
16
|
+
kind: work
|
|
17
|
+
depends_on: []
|
|
18
|
+
overview: 外部システムとの連携を一覧(YAML)で定義する
|
|
19
|
+
path: ifx-index.yaml
|
|
20
|
+
rulebook: specdojo:ifx-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-purpose-alignment
|
|
28
|
+
- text: 外部システム連携設計(プロトコル・認証・エラー処理)の入力として参照できること
|
|
29
|
+
roles: [ARC]
|
|
30
|
+
viewpoint: vp-arc-technical-constraints
|
|
31
|
+
- text: 外部結合テストの対象が識別できること
|
|
32
|
+
roles: [QE]
|
|
33
|
+
viewpoint: vp-qe-verifiability
|
|
34
|
+
- text: 外部I/F実装スコープの参照として使えること
|
|
35
|
+
roles: [DEV]
|
|
36
|
+
viewpoint: vp-dev-implementation-readiness
|
|
37
|
+
|
|
38
|
+
- local_id: ifx-api-_TERM_
|
|
39
|
+
min_size: medium
|
|
40
|
+
name: 外部API仕様
|
|
41
|
+
kind: work
|
|
42
|
+
depends_on:
|
|
43
|
+
- ifx-index
|
|
44
|
+
overview: 外部システムとのAPI連携をOpenAPI形式(YAML)で定義する
|
|
45
|
+
path: ifx-api-_TERM_.yaml
|
|
46
|
+
rulebook: specdojo:ifx-api-rulebook
|
|
47
|
+
note: "_TERM_ は対象外部システム名の略称(kebab-case)"
|
|
48
|
+
done_criteria:
|
|
49
|
+
- text: APIのエンドポイント・リクエスト・レスポンスが業務利用観点で確認できること
|
|
50
|
+
roles: [BA]
|
|
51
|
+
viewpoint: vp-ba-requirements-completeness
|
|
52
|
+
- text: API連携方式を承認できること
|
|
53
|
+
roles: [PO]
|
|
54
|
+
viewpoint: vp-po-decision-readiness
|
|
55
|
+
- text: OpenAPIスキーマとして参照可能であること
|
|
56
|
+
roles: [ARC]
|
|
57
|
+
viewpoint: vp-arc-document-structure
|
|
58
|
+
- text: API契約テスト・外部結合テスト設計に活用できること
|
|
59
|
+
roles: [QE]
|
|
60
|
+
viewpoint: vp-qe-verifiability
|
|
61
|
+
- text: APIクライアント実装の基礎として参照できること
|
|
62
|
+
roles: [DEV]
|
|
63
|
+
viewpoint: vp-dev-implementation-readiness
|
|
64
|
+
|
|
65
|
+
- local_id: ifx-file-_TERM_
|
|
66
|
+
min_size: medium
|
|
67
|
+
name: 外部ファイル連携仕様
|
|
68
|
+
kind: work
|
|
69
|
+
depends_on:
|
|
70
|
+
- ifx-index
|
|
71
|
+
overview: 外部システムとのファイル連携をYAMLで定義する
|
|
72
|
+
path: ifx-file-_TERM_.yaml
|
|
73
|
+
rulebook: specdojo:ifx-file-rulebook
|
|
74
|
+
note: "_TERM_ は対象ファイル連携名の略称(kebab-case)"
|
|
75
|
+
done_criteria:
|
|
76
|
+
- text: ファイル形式・伝送方法・スケジュール・項目が業務観点で記述されていること
|
|
77
|
+
roles: [BA]
|
|
78
|
+
viewpoint: vp-ba-requirements-completeness
|
|
79
|
+
- text: ファイル連携仕様を承認できること
|
|
80
|
+
roles: [PO]
|
|
81
|
+
viewpoint: vp-po-decision-readiness
|
|
82
|
+
- text: ファイル処理設計(転送・パース・エラー処理)の入力として参照できること
|
|
83
|
+
roles: [ARC]
|
|
84
|
+
viewpoint: vp-arc-technical-constraints
|
|
85
|
+
- text: ファイル連携テスト設計に活用できること
|
|
86
|
+
roles: [QE]
|
|
87
|
+
viewpoint: vp-qe-verifiability
|
|
88
|
+
|
|
89
|
+
- local_id: ifx-msg-_TERM_
|
|
90
|
+
min_size: medium
|
|
91
|
+
name: 外部メッセージ仕様
|
|
92
|
+
kind: work
|
|
93
|
+
depends_on:
|
|
94
|
+
- ifx-index
|
|
95
|
+
overview: 他システムとのイベント・キューのメッセージ連携をAsyncAPI + CloudEvents(YAML)で定義する
|
|
96
|
+
path: ifx-msg-_TERM_.yaml
|
|
97
|
+
rulebook: specdojo:ifx-msg-rulebook
|
|
98
|
+
note: "_TERM_ は対象メッセージ・イベント名の略称(kebab-case)"
|
|
99
|
+
done_criteria:
|
|
100
|
+
- text: メッセージ内容・チャネル・タイミングが業務観点で確認できること
|
|
101
|
+
roles: [BA]
|
|
102
|
+
viewpoint: vp-ba-requirements-completeness
|
|
103
|
+
- text: メッセージ連携方式を承認できること
|
|
104
|
+
roles: [PO]
|
|
105
|
+
viewpoint: vp-po-decision-readiness
|
|
106
|
+
- text: AsyncAPIスキーマとして参照可能であること
|
|
107
|
+
roles: [ARC]
|
|
108
|
+
viewpoint: vp-arc-document-structure
|
|
109
|
+
- text: メッセージ処理テスト・非同期テスト設計に活用できること
|
|
110
|
+
roles: [QE]
|
|
111
|
+
viewpoint: vp-qe-verifiability
|
|
112
|
+
- text: メッセージパブリッシャー・コンシューマ実装の基礎として参照できること
|
|
113
|
+
roles: [DEV]
|
|
114
|
+
viewpoint: vp-dev-implementation-readiness
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
# yaml-language-server: $schema=../../../specdojo/schemas/v1/dct.schema.yaml
|
|
2
|
+
# specdojo-schema: validate=false reason=template
|
|
3
|
+
# Template: glossary deliverables catalog
|
|
4
|
+
id: specdojo:dct-glossary-template
|
|
5
|
+
type: template
|
|
6
|
+
status: draft
|
|
7
|
+
title: 成果物カタログ(用語集)
|
|
8
|
+
rulebook: specdojo:dct-rulebook
|
|
9
|
+
domain: glossary
|
|
10
|
+
base_path: /docs/ja/product/010-business-specs/060-glossary
|
|
11
|
+
|
|
12
|
+
groups:
|
|
13
|
+
- name: 用語集
|
|
14
|
+
deliverables:
|
|
15
|
+
- local_id: gl-_DOMAIN_
|
|
16
|
+
name: 用語集
|
|
17
|
+
kind: work
|
|
18
|
+
depends_on: []
|
|
19
|
+
overview: 業務・システムで使用する用語の意味を統一的に定義する
|
|
20
|
+
path: gl-_DOMAIN_.md
|
|
21
|
+
rulebook: specdojo:gl-rulebook
|
|
22
|
+
note: "_DOMAIN_ は対象業務領域の略称(kebab-case)"
|
|
23
|
+
done_criteria:
|
|
24
|
+
- text: 業務上の主要用語の定義・別名・分類が正確に記述されていること
|
|
25
|
+
roles: [BA]
|
|
26
|
+
viewpoint: vp-ba-requirements-completeness
|
|
27
|
+
- text: 用語スコープと定義の妥当性を承認できること
|
|
28
|
+
roles: [PO]
|
|
29
|
+
viewpoint: vp-po-purpose-alignment
|
|
30
|
+
- text: 技術実装・API命名・DBカラム名の参照として使えること
|
|
31
|
+
roles: [ARC]
|
|
32
|
+
viewpoint: vp-arc-cross-document-consistency
|
|
33
|
+
- text: ドキュメント間の用語の一貫性が確認できること
|
|
34
|
+
roles: [QE]
|
|
35
|
+
viewpoint: vp-qe-omissions-consistency
|