6  Work Breakdown Structure

6.1 Overview

This chapter defines the project Work Breakdown Structure and serves as the central task tracker. Tasks link directly to the sections where work is needed. Status reflects project state as of the current week.

6.2 WBS Tree

• 1.0 SysML v2 MCP Server Project
  • 1.1 Project Management
    • 1.1.1 Planning & Coordination
    • 1.1.2 Technical Reviews (SRR, PDR, CDR)
    • 1.1.3 Risk Management
  • 1.2 Systems Engineering
    • 1.2.1 Systems Engineering Plan (SEP)
    • 1.2.2 Stakeholder Analysis
    • 1.2.3 System Requirements Specification (SyRS)
    • 1.2.4 Architecture Design Description (ADD)
    • 1.2.5 Verification & Validation Plan (VVP)
    • 1.2.6 Requirements Traceability Matrix (RTM)
  • 1.3 Software Development
    • 1.3.1 Phase 0: Core MCP Server
      • 1.3.1.1 Server scaffold (Go, MCP SDK)
      • 1.3.1.2 Basic sysml_parse tool
      • 1.3.1.3 Example resources
    • 1.3.2 Phase 1: GitLab Integration
      • 1.3.2.1 GitLab API client
      • 1.3.2.2 gitlab_read_file tool
      • 1.3.2.3 gitlab_list_models tool
      • 1.3.2.4 Authentication (PAT)
    • 1.3.3 Phase 2: SysML v2 API Integration
      • 1.3.3.1 SysML v2 API client
      • 1.3.3.2 sysml_validate tool
      • 1.3.3.3 sysml_query tool
      • 1.3.3.4 Write operations (commit, MR)
    • 1.3.4 Phase 3: HTTP Transport
      • 1.3.4.1 Streamable HTTP server
      • 1.3.4.2 CORS configuration
  • 1.4 Infrastructure
    • 1.4.1 Repository Setup
    • 1.4.2 CI/CD Pipeline (software)
    • 1.4.3 CI/CD Pipeline (documentation)
    • 1.4.4 Container Build & Registry
  • 1.5 Documentation
    • 1.5.1 Quarto Book Setup
    • 1.5.2 Chapter Authoring
    • 1.5.3 GitLab Pages Deployment
    • 1.5.4 Software README/CONTRIBUTING
  • 1.6 External Deliverables
    • 1.6.1 GVSETS Abstract
    • 1.6.2 GVSETS Draft Paper (Mar 5)
    • 1.6.3 GVSETS Final Paper (Apr)
    • 1.6.4 Capstone Submission

6.3 1.1 Project Management

6.3.1 1.1.1 Project Planning

Per [1, Sec. 2.3.4.1].

• Define project objectives, scope, constraints - Section 5.1
• Develop breakdown structures (WBS) - This chapter
• Establish schedule with milestones - Section 5.5
• Generate SEMP/SEP - Section 5.2

6.3.2 1.1.2 Technical Reviews

Per [1, Sec. 2.1.4].

• SRR (Week 2) - Section 5.9
• PDR (Week 4) - Section 5.9
• CDR (Week 12) - Section 5.9

6.3.3 1.1.3 Risk Management

Per [1, Sec. 2.3.4.4].

• Identify risks and opportunities - Section 5.8
• Establish risk thresholds and categories - Section 5.8
• Define treatment strategies - Section 5.8

6.4 1.2 Systems Engineering

6.4.1 1.2.1 SEP

Per [1, Sec. 2.3.4.1].

• Life cycle model definition - Section 5.2
• Technical review entry/exit criteria - Section 5.3
• Configuration management approach - Section 5.7

6.4.2 1.2.2 Stakeholder Analysis

Per [1, Sec. 2.3.5.2].

• Identify stakeholders with interests - Section 7.1
• Establish stakeholder management approach - Section 7.2
• Develop operational concept - Section 7.3
• Define stakeholder needs - Section 7.4
• Transform needs to stakeholder requirements - Section 7.5

6.4.3 1.2.3 SyRS

Per [1, Sec. 2.3.5.3].

• Define functional boundary of system - Section 8.2
• Define system functions with performance - Section 8.3.1
• Define constraints (operational, regulatory) - Section 8.5
• Define verification criteria per requirement - Section 8.6
• Analyze requirements (complete, consistent, feasible) - Section 8.7

6.4.4 1.2.4 ADD

Per [1, Sec. 2.3.5.4].

• Identify architecture viewpoints - Section 9.1
• Define system context and boundary - Section 9.2
• Synthesize candidate architectures - Section 9.3
• Select architecture via trade study - Section 9.4
• Define interfaces (internal/external) - Section 9.8
• Allocate requirements to elements - Section 9.9

6.4.5 1.2.5 VVP

Per [1, Secs. 2.3.5.9, 2.3.5.11].

• Define verification scope and strategy - Section 10.1
• Select verification methods per requirement - Section 10.2
• Define verification success criteria - Section 10.3
• Plan enabling systems (test tools, CI) - Section 10.4
• Define validation approach (stakeholder acceptance) - Section 10.8

6.4.6 1.2.6 RTM

Per [1, Sec. 3.2.3].

• Stakeholder needs → Stakeholder requirements - Section 15.1
• Stakeholder requirements → System requirements - Section 15.2
• System requirements → Architecture elements - Section 15.3
• System requirements → Test cases - Section 15.4

6.5 1.3 Software Development

6.5.1 Phase 0: Core MCP Server (Complete)

• 1.3.1.1 Server scaffold (Go, MCP SDK)
• 1.3.1.2 Basic sysml_parse tool
• 1.3.1.3 Example resources

6.5.2 Phase 1: GitLab Integration

• 1.3.2.1 GitLab API client - Week 5
• 1.3.2.2 gitlab_read_file tool - Week 5
• 1.3.2.3 gitlab_list_models tool - Week 5
• 1.3.2.4 Authentication (PAT support) - Week 6

6.5.3 Phase 2: SysML v2 API Integration

• 1.3.3.1 SysML v2 API client - Week 7
• 1.3.3.2 sysml_validate tool - Week 8
• 1.3.3.3 sysml_query tool - Week 8
• 1.3.3.4 Write operations (gitlab_commit, gitlab_create_mr) - Week 9

6.5.4 Phase 3: HTTP Transport

• 1.3.4.1 Streamable HTTP server - Week 9
• 1.3.4.2 CORS configuration - Week 9

6.6 1.4 Infrastructure

• 1.4.1 Repository Setup - Complete
• 1.4.2 CI/CD Pipeline (software)
• 1.4.3 CI/CD Pipeline (documentation) - Complete (HTML + PDF)
• 1.4.4 Container Build & Registry

6.7 1.5 Documentation

• 1.5.1 Quarto Book Setup - Complete
• 1.5.2 Chapter Authoring - Ongoing
• 1.5.3 GitLab Pages Deployment - Complete
• 1.5.4 Software README/CONTRIBUTING

6.8 1.6 External Deliverables

• 1.6.1 GVSETS Abstract
• 1.6.2 GVSETS Draft Paper - Due Mar 5
• 1.6.3 GVSETS Final Paper - Due Apr 7
• 1.6.4 Capstone Submission - Due Apr 14

6.9 Milestones

Week	Date	Milestone	Status
1	Jan 12-18	Plan finalized, repos set up	Complete
2	Jan 19-25	SRR - SEP, SyRS baselined	In Progress
4	Feb 2-8	PDR - ADD, VVP approved	Pending
7	Mar 2-8	GVSETS draft submitted	Pending
10	Mar 23-29	Full tool suite complete	Pending
12	Mar 30-Apr 5	CDR - V&V complete	Pending
15	Apr 20-25	Final delivery	Pending

6.10 Risk Summary

See Section 5.8 for full risk register.

ID	Risk	Likelihood	Impact	Mitigation
R1	SysML v2 API server difficult to deploy	Medium	High	GitLab-only tools first; API is Phase 2
R2	GVSETS deadline aggressive	Medium	Medium	Submit draft even if incomplete
R4	Go MCP SDK limitations	Low	High	SDK is mature; fallback to TypeScript
R5	Container testing blocked locally	High	Low	CI-only validation; document in VVP
R6	Scope creep	Medium	Medium	Defer benchmarking to future work

[1]

INCOSE, INCOSE systems engineering handbook, 5th ed. Wiley, 2023.