Skip to content

Functional User Guide Overview

This guide explains how to use OpenSESA functionally across modules, from project setup through engineering execution, assurance, and release.

How to use this guide

Start with the recommended order below for new projects. For existing projects, jump directly to the module page you are actively operating.

Collapsed quick-start checklist
  • Select the active project context.
  • Validate system definition and architecture structure.
  • Confirm requirements traceability and quality status.
  • Review verification, assurance, and baseline readiness.
  1. Portfolio and Project Setup
  2. System Definition (system elements)
  3. System Architecture (architectures and nodes)
  4. Requirements Management
  5. Interface and Project Interface Management
  6. Scope and Design Package Management
  7. Verification and Validation
  8. Safety Assurance
  9. Baseline, Release, and Evidence Packs
  10. Impact Assessment
  11. Operations Management

End-to-End Functional Flow

flowchart LR
    A[Portfolio Setup] --> B[System Definition]
    B --> C[System Architecture]
    C --> D[Requirements]
    D --> E[Interfaces and Scope]
    E --> F[Verification and Validation]
    F --> G[Safety Assurance]
    G --> H[Baseline and Release]
    H --> I[Impact Assessment]
    I --> J[Operations Management]

Common Platform Concepts

  • Most module pages are scoped by selected project.
  • Dashboard pages provide module-level status snapshots.
  • Import and export flows are available in many modules for spreadsheet-driven workflows.
  • Traceability links across modules are used for coverage, quality, and impact analysis.

Roles and Permissions

Typical role patterns:

  • Viewer: read access to project data.
  • Editor/Contributor: create and update records.
  • Admin/Lead: governance actions such as baseline freezing, release workflows, and settings.

Good Practice

  • Select the project before entering deep module workflows.
  • Use module dashboards for prioritization before record-level edits.
  • Run imports in smaller batches first, then full loads.
  • Review analysis and quality reports before baseline freeze or release activities.