本文へ移動
cccskills
無料GitHub で公開

doe-sem

Knowledge base from DOE Systems Engineering Methodology (SEM) Version 3 — the DOE SDLC for IT investments. Use for staged systems lifecycle planning through maintenance, Stage Exits, Structured Walkthroughs, In-Stage Assessments, requirements traceability, and CMM-aligned process discipline. Covers SEM3 (2002) guidance only; does not replace modern DevSecOps tooling standards, DOE O 413.3B capital-asset directives, or current CIO policy supersessions.

インストール方法を見る

含まれるファイル(13)

  • SKILL.md5.6 KB
  • chapters/ch01-sem-purpose-and-context.md3.5 KB
  • chapters/ch02-lifecycle-model-and-quality-reviews.md3.9 KB
  • chapters/ch03-planning-stage.md3.6 KB
  • chapters/ch04-requirements-and-functional-design.md3.7 KB
  • chapters/ch05-system-design-and-construction.md3.6 KB
  • chapters/ch06-integration-test-and-acceptance.md3.4 KB
  • chapters/ch07-maintenance-stage.md3.2 KB
  • cheatsheet.md2.3 KB
  • glossary.md2.2 KB
  • LICENSE1.1 KB
  • PACK.yaml1.4 KB
  • patterns.md2.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

<!-- argument-hint: [topic, stage, or chapter number] -->

DOE Systems Engineering Methodology (SEM) Version 3

Source: DOE SEM3 / DOE G 200.1-1A (US Government work, public domain) | Chapters: 7

When to use

Reach for this pack when planning or assessing a DOE-style systems development lifecycle for IT investments — especially stage gates (Stage Exits), peer Structured Walkthroughs, independent In-Stage Assessments, planning/QA/CM plan triad, requirements traceability, construction vs design boundaries, acceptance, or the nested maintenance process model.

Prerequisites: none — plain Markdown; no MCP server, API key, or licence tier needed at runtime.

How to Use This Skill

  • Without arguments — load the core frameworks below.
  • With a topic — ask about lifecycle stages, Stage Exit, walkthroughs, planning, requirements, design, construction, test/acceptance, or maintenance.
  • With a chapter — ask for ch01 through ch07.

Supporting files: glossary.md, patterns.md, cheatsheet.md.

Core Frameworks & Mental Models

What SEM is

DOE’s Systems Development Lifecycle guidance for IT investments (Office of the CIO). Version 3 renames software-centric SEM to systems engineering for IT projects and aligns practices with SEI CMM-SW Level 2/3 process areas.

Eight lifecycle stages

  1. Planning
  2. Requirements Definition
  3. Functional Design
  4. System Design
  5. Construction (formerly Programming)
  6. Integration and Testing
  7. Installation and Acceptance
  8. Maintenance (nested change lifecycle)

Quality machinery (every development stage)

MechanismRole
Structured WalkthroughPeer technical review of work products
In-Stage AssessmentIndependent QA review of stage deliverables
Stage ExitOwner/stakeholder go / continue / abandon decision

Planning triad

Project Plan + Quality Assurance Plan + Configuration Management Plan baseline how the project will be managed, assured, and controlled.

Traceability

Requirements Traceability Matrix links needs → requirements → design → test → acceptance evidence.

Modern use note

Source date is September 2002. Keep stage intents, gates, and CM/QA discipline; modernize tools (cloud, CI/CD, agile increments) without dropping exits and baselining.

Chapter Index

#SectionKey content
ch01Purpose and ContextSEM scope, v3 changes, CMM alignment, DOE CIO context
ch02Lifecycle Model & Quality ReviewsEight stages; walkthroughs; assessments; Stage Exits; tailoring
ch03Planning StageFeasibility, plans triad, risk, EA, performance measures
ch04Requirements & Functional DesignRTM, baselines, logical design
ch05System Design & ConstructionPhysical design, build, unit verification, CM
ch06Integration Test & AcceptanceSystem test, install, owner acceptance, training
ch07MaintenanceNested change process model and metrics

Topic Index

  • Acceptance / owner decision → ch06
  • CMM-SW alignment → ch01, ch02
  • Configuration management plan → ch03, ch05, ch07
  • Construction stage → ch05
  • COTS considerations → ch05, ch07
  • Enterprise Architecture (DOE EA) → ch03
  • Feasibility analysis → ch03
  • Functional design → ch04
  • In-Stage Assessment → ch02
  • Installation → ch06
  • Integration and testing → ch06
  • Lifecycle stages overview → ch02
  • Maintenance process model → ch07
  • Performance measures → ch03, ch06
  • Planning stage → ch03
  • Project plan → ch03
  • Quality assurance plan → ch03
  • Requirements definition → ch04
  • Requirements traceability matrix (RTM) → ch04, ch06
  • Risk management → ch03
  • Stage Exit → ch02, ch06
  • Structured Walkthrough → ch02
  • System design → ch05
  • System owner / users → ch03, ch06
  • Tailoring by project size → ch02, ch07

Supporting Files

  • glossary.md — SEM lifecycle terms with chapter references
  • patterns.md — implementation patterns (When/How/Trade-offs)
  • cheatsheet.md — decision rules, stage map, tells & smells

Scope & Limits

This pack covers DOE Systems Engineering Methodology Version 3 (SEM3_1231.pdf, September 2002, DOE G 200.1-1A) — the DOE SDLC for IT investments — as synthesized reference notes. Extracted page count recorded in PACK.yaml is 318. It does not cover: current superseding DOE CIO directives if any; DOE O 413.3B capital asset project management in full; agile/DevSecOps toolchains as mandates; or non-IT nuclear/facility systems engineering methods. US Government public domain work. No source-material download link is published. In-PDF third-party copyright check at build found no copyright notices (IEEE/SEI are citations only).

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Signpost (not a knowledge pack) for the automotive standards landscape: ISO 26262, ASPICE, SAE J3016, UNECE R155, UNECE R156, and the NHTSA vehicle set. Contains NO source content: designation, edition, owner, status, and an official catalogue URL only. Use when you need to identify or locate an automotive standard. Most are paywalled or carry no redistribution grant and cannot be packaged; the one open path is the nhtsa-vehicle pack.

日本語の概要は準備中です。原文の説明を表示しています。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月9日 更新

cisa-cpg

無料

Knowledge base from CISA Cross-Sector Cybersecurity Performance Goals 2.0. Use for prioritized IT/OT baseline cyber goals aligned to NIST CSF 2.0 (including GOVERN), critical-infrastructure hygiene, MSP/supply-chain expectations, and board-friendly outcome language. Covers CPG 2.0 goals only; does not replace full CSF programs, sector-specific goals (SSGs), or CSET tooling detail.

日本語の概要は準備中です。原文の説明を表示しています。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月9日 更新

Knowledge base from DAFMAN 63-119 (15 April 2021), Mission-Oriented Test Readiness Certification. Use for continuous MOTRC replacing single-point OTRR thinking: framework/applicability, Certification Official vs PM roles, review cycle and exit criteria, certification memo/decertify gates, DT&E/contractor evidence, ITT integration and cyber resiliency, and the 31-template matrix. DAF T&E readiness process only—does not replace DoDI 5000.89, AFI 99-103, or multi-service lead policies.

日本語の概要は準備中です。原文の説明を表示しています。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月9日 更新

Knowledge base from the DoD Systems Engineering Guidebook (OUSD R&E, February 2022). Use for the DoD SE process model — the 16 SE processes (8 technical management + 8 technical) mapped to ISO/IEC/IEEE 15288, the event-driven technical reviews and audits across the Major Capability Acquisition life cycle (ASR, SRR, SFR, PDR, CDR, SVR/FCA, PRR, PCA), the Systems Engineering Plan (SEP), risk/issue/opportunity management, TPMs and leading indicators, system-of-systems and digital engineering, and the 24 design considerations (RAM, system safety, HSI, system security engineering, MOSA, supportability, etc.). Acquisition-program oriented: thin on detailed cost estimating, contracting law, and non-DoD or commercial life cycles.

日本語の概要は準備中です。原文の説明を表示しています。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月9日 更新

Knowledge pack from 'Towards Digital Engineering: The Advent of Digital Systems Engineering' (Huang et al., Old Dominion University, arXiv:2002.11672, 2020). Use when reasoning about digital engineering, the DoD Digital Engineering Strategy and its five goals, the Authoritative Source of Truth, digitalization vs. digitization, digital augmentation, digitalized models, provenance, unique identification, and the four-level (vision/strategy/action/foundation) DSE research framework. Covers the conceptual/vision layer of the field. SCOPE LIMITS: this is a single ~28-page vision paper, not a methods handbook — it is thin on step-by-step procedures, tooling, case studies, and quantitative evaluation, and it predates 2020 so it does not cover later digital-engineering standards or recent AI/LLM advances. Use the sebok pack for established SE canon and MBSE depth.

日本語の概要は準備中です。原文の説明を表示しています。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月9日 更新

Knowledge base from the DoD Digital Engineering Strategy (2018, OUSD/ODASD(SE)). Use for the Department of Defense's five digital engineering goals — (1) formalize the development, integration, and use of models; (2) provide an enduring authoritative source of truth; (3) incorporate technological innovation; (4) establish supporting infrastructure and environments; (5) transform the culture and workforce — plus their focus areas, the document-to-model and design-build-test→model-analyze-build shifts, model formalisms/provenance, governance and access control of the authoritative source of truth, and the coordinate→plan→pilot→sustain rollout. A vision-and-policy strategy, deliberately non-prescriptive. Does NOT provide a how-to method, tool tutorials, MBSE/SysML mechanics, or implementation-plan content; thin on metrics, acquisition-policy detail, and step-by-step procedure. Excludes the CAC-gated Digital Engineering Body of Knowledge (DEBoK).

日本語の概要は準備中です。原文の説明を表示しています。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月9日 更新

jgsystemsconsulting のスキルをすべて見る

このスキルの問題を報告する