Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to content
X as Code (XaC) documentation
Light Logo Dark Logo

Knowledge

  • Tutorials
    • Setting Up a Sphinx-Needs Project
    • Setting Up PlantUML for Sphinx-Needs
    • Creating Powerful Dashboards
    • Setting Up ubCode and ubConnect Licenses
  • How To Guides
    • Writing Requirements
    • Tracing Source Code
    • Mermaid Integration
    • Draw.io Integration
    • Architecture Diagrams
    • Architecture Documentation with arc42
    • Jira and other Links
    • How to integrate External Needs
    • GitHub Actions Integration
    • Test Management and Traceability
      • Test Requirements
  • Explanation
    • Why X-as-Code Beats Multi-Tool Chaos
    • The Review Process: From ALM to Git
    • Access Management Strategies
  • Reference
  • FAQ & BEST PRACTICES

Community

  • Contribute
Back to top
View this page
Edit this page

Explanation¶

Understanding the principles and concepts behind X-as-Code workflows.

  • Why X-as-Code Beats Multi-Tool Chaos
  • The Review Process: From ALM to Git
  • Access Management Strategies

Note

Coming soon:

  • Requirement Engineering with XaC: Dos and Don’ts

  • Tool overview about Engineering as Code Tools

Next
Why X-as-Code Beats Multi-Tool Chaos
Previous
Test Requirements
Copyright © 2026, team useblocks
Made with Sphinx and @pradyunsg's Furo