8  Stakeholder Analysis

8.1 Stakeholder Identification

Per [1, Sec. 2.3.5.2], the stakeholder needs and requirements definition process identifies stakeholders and their needs throughout the system lifecycle.

Stakeholder Power Interest Strategy Success Criteria
Academic Advisor High High Manage Closely Complete SE artifacts, proper methodology
Capstone Collaborator High High Manage Closely Shared workload, defensible deliverables
Open Source Community Medium High Keep Satisfied Working software, good documentation
GitLab (Author Affiliation) Medium Medium Keep Informed Working demonstration, GVSETS presentation
MBSE Practitioners Medium High Keep Satisfied Solves real workflow problems
SysML v2 Implementers Medium Medium Keep Informed Correct API usage, grammar conformance
INCOSE/SE Community Low Medium Keep Informed Novel contribution, reproducible results
Sensmetry (Sysand) Low Medium Keep Informed Interoperability, grammar contribution

8.2 Team & Responsibilities

Role Person Affiliation
Technical Lead Andrew Dunn GitLab Public Sector
SE Lead Greg Pappas DoD, Army, AFC-DEVCOM
Advisor Dr. Stephen Rapp Wayne State University, ISE
WBS Element Andrew Greg Dr. Rapp
Planning & Reviews R C A
SEP, SyRS, VVP, RTM C R A
ADD R C A
Software Development R I I
Quarto Book C R I
Papers (GVSETS, INCOSE) R R C

Legend: R=Responsible, A=Accountable, C=Consulted, I=Informed

8.3 Stakeholder Needs

ID Stakeholder Need
SN-001 OSS Community Git provider API integration for existing repositories
SN-002 OSS Community Truly open source (MIT license)
SN-003 MBSE Practitioners CI/CD integration examples
SN-004 GitLab Demonstrate AI-augmented MBSE for GVSETS
SN-005 Advisor Follow INCOSE SE processes
SN-006 Advisor Formal technical reviews (SRR, PDR, CDR)
SN-007 MBSE Practitioners Easy installation (single binary)
SN-008 MBSE Practitioners Clear documentation with examples
SN-009 DevOps Engineers Container deployment support
SN-010 MBSE Practitioners Natural language model queries
SN-011 MBSE Practitioners Self-hosted Git provider support
SN-012 MBSE Practitioners Model validation against SysML v2 spec
SN-013 Tool Vendors Open standards, complement commercial tools
SN-014 SysML v2 Implementers OMG spec conformance
SN-015 SysML v2 Implementers Parse errors with location info

8.4 Stakeholder Requirements

ID Traces To Requirement
SR-001 SN-001 Integrate with Git provider REST APIs (GitLab as reference)
SR-002 SN-002 MIT open source license
SR-003 SN-003 CI/CD integration examples (GitLab CI as reference)
SR-004 SN-005 Produce SE artifacts per INCOSE Handbook
SR-005 SN-006 Conduct SRR, PDR, CDR with documented criteria
SR-006 SN-007 Single static binary, no external dependencies
SR-007 SN-008 README with installation/configuration instructions
SR-008 SN-008 Example SysML v2 models demonstrating capabilities
SR-009 SN-009 OCI-compliant container image
SR-010 SN-011 Self-hosted Git provider support via configurable URL
SR-011 SN-012 SysML v2 syntax validation via API integration
SR-012 SN-010 Parse SysML v2 textual notation, extract elements
SR-013 SN-014 Parse SysML v2 conforming to OMG grammar spec
SR-014 SN-015 Parse errors include file, line, column
SR-015 SN-014 Documented subset coverage

8.5 Validation Criteria

Requirement Validation Acceptance Criteria
SR-001 Demo Read file from GitLab repository
SR-002 Inspect MIT LICENSE present
SR-003 Demo CI pipeline example executes
SR-004 Inspect SE artifacts present, INCOSE-aligned
SR-005 Inspect Review records document criteria
SR-006 Demo Binary runs without dependencies
SR-007–008 Inspect README complete, examples work
SR-009 Demo Container builds and runs
SR-010 Demo Connect to self-hosted instance
SR-011–015 Test Parser/API tests pass

Detailed verification procedures in Section 11.8. Operational concept and use cases in Section 10.2.