Automated System of Systems baseline creation reduced requirements overhead by 85%

Sharing our implementation of automated baseline creation for System of Systems requirements that eliminated 85% of manual baseline overhead. Previously, creating baselines across our 12 subsystem projects took 6-8 hours per release cycle with high error rates.

We built automation using Polarion’s SOS template capabilities combined with auto-baseline triggers and LiveDoc inheritance. When any subsystem creates a release baseline, the system automatically generates corresponding SOS-level baselines that inherit the subsystem requirements. Variant parameters handle different product configurations, and approval gates ensure quality before baseline finalization.

The automation reduced baseline creation from 6-8 hours to under 45 minutes, with zero manual errors. Requirements traceability across the system of systems improved dramatically since baselines are now consistent and complete. Implementation took about 3 weeks but ROI was immediate.

The approval gates are configured at both subsystem and SOS levels. Subsystem baselines must pass quality checks and get approval from subsystem leads before they’re marked as eligible for SOS baseline generation. The SOS auto-baseline process only triggers when subsystem baselines have approved status. This two-tier approval ensures quality propagates correctly.

Impressive time savings! How did you handle the variant parameters across different subsystem configurations? We have similar complexity with optional modules that vary by customer.

What about approval gates? How do you ensure subsystem baselines are properly reviewed before they trigger SOS baseline creation? We’re concerned about propagating errors upstream.