Skip to content

Interface Management

Interface Management supports system-level interfaces, IDS artifacts, ICD records, matrix views, and import/export operations.

Why this matters

Interface quality directly affects architecture consistency, scope planning, and downstream verification readiness.

What You Can Do

  • Manage interface records across the selected project.
  • Use N2 matrix visualizations.
  • Create and maintain IDS and ICD artifacts.
  • Import and export interface, IDS, and ICD data.
  • Generate cross-project interface reports.

Typical Workflow

  1. Create or import core interface records.
  2. Use interface detail pages to enrich metadata.
  3. Maintain IDS and ICD records aligned to interface definitions.
  4. Use N2 matrix views to detect missing or inconsistent interactions.
  5. Export records for external review or downstream teams.

Interface Management Flow

flowchart TD
    A[Create or Import Interfaces] --> B[Enrich Interface Details]
    B --> C[Maintain IDS and ICD]
    C --> D[Review N2 Matrix]
    D --> E[Run Cross-Project Report]
    E --> F[Export Approved Data]

Key Pages

  • Interface dashboard and list.
  • Interface CRUD, import, export, cross-project report.
  • IDS list and CRUD with import/export.
  • ICD list and CRUD with import/export.
Collapsed consistency check

Keep interface identifiers stable between imports to prevent duplicate or orphaned relationship records.

Practical Tips

  • Keep naming conventions stable between interface and project-interface modules.
  • Validate matrix outputs before release milestones.
  • Use API-backed system element selectors carefully after hierarchy updates.

Common pitfall

Re-importing without identifier hygiene can fragment traceability and complicate coverage reporting.