Domain Applications¶

Purpose¶

Map module ownership clearly so contributors know where to implement changes.

Page scope

This page focuses on ownership boundaries and where code belongs. For lifecycle capability flow, use Platform Capabilities. For detailed module capabilities, use Module Capability Matrix.

When To Use This Page¶

identifying the owner of a feature/workflow
planning cross-module changes
reviewing architecture boundaries

OpenSESA is organized into domain modules registered in app/app/settings.py and mounted by prefix in app/app/urls.py.

Domain Map¶

flowchart TD
    Core["core"]
    Gov["portfolio_mgmt\nscope_mgmt"]
    Design["sysdef_mgmt\nsysarch_mgmt\ndiagrams_mgmt"]
    Control["interface_mgmt\nproject_interface_mgmt\nrequirements_mgmt"]
    Evidence["verification_validation_mgmt\nsafety_assurance\nanalysis_mgmt"]
    Release["baseline_mgmt\nimpact_assessment\nops_mgmt"]

    Core --> Gov
    Core --> Design
    Core --> Control
    Core --> Evidence
    Core --> Release
    Gov --> Design --> Control --> Evidence --> Release

Responsibilities by Module¶

Module	Responsibility
`core`	shared middleware, security/auth context, dashboard shell
`portfolio_mgmt`	project/program governance structure
`scope_mgmt`	scope allocation and design package control
`sysdef_mgmt`	system definition model
`sysarch_mgmt`	architecture representation and governance
`diagrams_mgmt`	model diagram authoring/synchronization
`interface_mgmt`	interface lifecycle records
`project_interface_mgmt`	project-level interface and ID coordination
`requirements_mgmt`	requirement lifecycle and quality/trace analysis
`verification_validation_mgmt`	plans/cases/results/defects/reporting
`safety_assurance`	assurance evidence and support views
`analysis_mgmt`	engineering analysis workflows
`baseline_mgmt`	baseline/release history and packaging
`impact_assessment`	impact evaluation and reporting
`ops_mgmt`	readiness items, milestones, dependencies, ops diagrams

Route Ownership¶

See Reference: URL Map for full prefix-level ownership.

Practical contributor rule

Keep routes/templates/tests within the owning domain module unless the behavior is explicitly shared platform concern.