SCORE Rules for Bazel

rules_score provides Bazel build rules for structuring and documenting safety-critical software according to S-CORE process guidelines. It covers the full artefact lifecycle — from requirements and architecture through safety analysis to the top-level SEooC assembly.

Overview

• Overview
  • Architecture diagram

Usage

• User Guide
  • General Information
  • Requirements
  • Architectural Design
  • Software Unit Design
  • Dependability Analysis
• Rule Reference
  • Documentation Rules
  • Artifact Rules
  • Structural Rules

Validation

• Bazel Component Specification
  • Purpose
  • What is Validated
  • Failure Cases
  • PlantUML Stereotype Reference
  • Debug Output
• Class Design Implementation Specification
  • Purpose
  • What is Validated
  • Failure Cases
  • Debug Output
• Component Internal API Specification
  • Purpose
  • What is Validated
  • Failure Cases
  • Debug Output
• Component Sequence Specification
  • Purpose
  • What is Validated
  • Failure Cases
  • Debug Output
• Sequence Internal API Specification
  • Purpose
  • What is Validated
  • Failure Cases
  • Debug Output

Development

• Integration Guide
  • Toolchain Setup
  • Cross-module dependencies
  • Complete Example
  • Design Rationale
  • Hermetic Diagram Tools (Graphviz and PlantUML)
• Architecture
  • Three layers
  • Rule → tool invocation map
  • Tool inventory
  • How the tools interrelate — the traceability data flow
  • Two-phase Sphinx build
  • Safety analysis document pipeline
  • Hermetic tool path resolution
• Tool Reference
  • Manual Analysis
  • AI Checker
  • TRLC
  • PlantUML Parser
  • Validation Core
  • Clickable PlantUML
  • Bazel
  • Lobster Bazel (Source Tracing)
  • LOBSTER

Tool Qualification

• Requirements
  • Requirements
• Traceability Report
• Quality Report
  • Code Coverage