SysML-driven MBSE framework for autonomous UAV design.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add hiyenwong/ai_collection --skill sysml-driven-uav-design-framework --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Sysml Driven Uav Design Framework?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hiyenwong-sysml-driven-uav-design-framework-ai-collection)More formats (shields.io, HTML) on the badges page.
---
name: sysml-driven-uav-design-framework
version: v1.0.0
last_updated: 2026-08-12
description: "SysML-driven MBSE framework for autonomous UAV design."
---
# Model-Based Systems Engineering Framework for SysML-Driven UAV Design
## Description
This framework proposes a four-layer SysML-driven approach for designing autonomous UAVs, mapping requirements to ROS 2 architecture while supporting traceability and verification throughout the development lifecycle.
## Activation Keywords
- sysml uav design
- mbse autonomous uav
- sysml ros2 integration
- uav systems engineering
- model-based uav design
- 无人机系统工程
- 基于模型的无人机设计
- SysML ROS2集成
## Tools Used
- `terminal`: For running SysML modeling tools and ROS 2 simulations
- `read_file`: For accessing SysML models and ROS 2 configuration files
- `write_file`: For generating documentation and traceability matrices
## Workflow
### Step 1: Requirements Layer
1. Define high-level system requirements using SysML requirements diagrams
2. Establish functional and non-functional requirements for autonomous UAV operations
3. Create requirement traceability links to higher-level mission objectives
### Step 2: Architecture Layer
1. Develop system architecture using SysML block definition diagrams (BDD)
2. Define subsystem interfaces and communication protocols
3. Map architectural components to physical UAV hardware constraints
### Step 3: Behavior Layer
1. Model system behavior using SysML activity diagrams and state machines
2. Define autonomous decision-making logic and mission planning workflows
3. Specify safety-critical behaviors and fault handling procedures
### Step 4: Implementation Layer
1. Generate ROS 2 node specifications from SysML models
2. Implement component interfaces using ROS 2 message types and services
3. Create deployment configurations for UAV hardware platforms
### Step 5: Verification and Validation
1. Perform model-based testing using SysML simulation capabilities
2. Validate ROS 2 implementation against SysML behavioral models
3. Maintain traceability from requirements through implementation to test cases
## Resources
- Paper: https://arxiv.org/abs/2608.09547
- Tools: SysML modeling tools, ROS 2 development environment
- Standards: OMG SysML specification, ROS 2 best practices
## Best Practices
1. **Layer Integration**: Ensure seamless flow of information between all four layers
2. **Traceability**: Maintain bidirectional traceability links throughout development
3. **Incremental Development**: Use iterative refinement across all layers
4. **Tool Integration**: Integrate SysML tools with ROS 2 development environment
5. **Verification Early**: Start verification activities as early as possible in the lifecycle
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!