What You Will Achieve
By the end of this tutorial, you will understand how the Aerospace Safety Solution implements the V-Model development lifecycle for the Flight Control Computer project. You will navigate the V-Model Process Guide, explore how requirements, safety analysis, and verification artifacts connect across all system levels, and understand how each engineering role interacts with the model throughout a certification project.Prerequisites
- The Aerospace Safety Solution is installed and configured (see Install the Aerospace Safety Solution)
- You have completed Create Your First Functional Hazard Assessment
- You have access to the Polarion project as at least a viewer role
Step 1: Open the V-Model Process Guide
From the project Home dashboard, locate the left sidebar and select V-Model Process Guide from the Role Dashboards section. The V-Model Process Guide page loads with an interactive diagram showing the full development lifecycle in three tracks:- Left side — Definition: Customer Requirements → System Requirements → Design Requirements → Characteristics/Functions
- Bottom — Implementation: System Element decomposition across all components
- Right side — Verification: Test Cases linked back to each requirement level
Color coding on the diagram is consistent throughout the project: blue for definition phases, green for implementation, and purple for verification.
Step 2: Read the Phase Evidence Mapping Table
Scroll below the V-Model diagram to find the Phase Evidence Mapping table. This table is your certification audit index. It maps each V-Model lifecycle phase to concrete Polarion artifacts:| Column | Meaning |
|---|---|
| Phase | Lifecycle phase name (e.g., System Requirements, Design Verification) |
| Side | Definition, Implementation, or Verification |
| Description | What activities occur in this phase |
| Evidence Links | PS (PowerSheet, blue), RS (Risksheet, red), RPT (Report, green) |
Step 3: Explore Requirements Traceability
Click the Whole RTM link from either the V-Model diagram or the PowerSheets sidebar entry. The Whole RTM PowerSheet opens with four color-coded column groups spanning the full decomposition hierarchy:- Customer Requirements (green) — 25 items
- System Requirements (purple) — 31 items
- Subsystem Requirements (teal)
- Design Requirements (blue) — 15 items
Step 4: Review the Safety Analysis Cascade
The V-Model safety analysis follows an ARP 4761 cascade. Navigate to Risksheets in the sidebar. The safety assessment documents are ordered by lifecycle phase:- FHA (Functional Hazard Assessment) — 6 failure conditions, each with classification and DAL allocation
- PSSA (Preliminary System Safety Assessment) — links FHA conditions to system architecture
- SSA (System Safety Assessment) — verifies safety requirements are met
- SFMEA (System FMEA) — 260 failure modes across system and subsystem levels
- DFMEA (Design FMEA) — component-level analysis for all 8 components
- FTA / CCA — fault tree and common cause analysis
| RPN Range | Color | Meaning |
|---|---|---|
| > 30 | Red | High priority — action required |
| 11–30 | Yellow | Medium — monitor and plan mitigation |
| ≤ 10 | Green | Low — acceptable residual risk |
Step 5: Check Standards Compliance Coverage
Navigate to Standards Compliance from the sidebar. The compliance matrix shows 7 standards side by side:DO-326A (Airborne Security) may show N/A if the security threat analysis has not yet been populated for your project instance.
Step 6: Navigate Role-Specific Dashboards
The V-Model is lived daily by five engineering roles. Select your role from the sidebar dashboards to see your tailored KPI view:- Program Manager — Overall readiness percentage across all 7 standards, document approval status
- Safety Engineer — RPN distribution, failure conditions requiring attention, risk controls pending implementation
- Design Engineer — Design requirement classification status, DFMEA assignments filtered to your work items
- V&V Engineer — Test execution status (pass/fail/not-run), verification coverage gaps per requirement level
- Configuration Manager — Document version status, baseline tracking, change request workflow
Project Structure Reference
The Aero1 Flight Control Computer follows a 3-level decomposition:
Next Steps
You have completed the Getting Started sequence. From here, explore the documentation by discipline:- Concepts — Understand the underlying safety standards (ARP 4761, ARP 4754A, DO-178C, DAL classification)
- How-To Guides — Step-by-step procedures for FHA, SFMEA, DFMEA, fault tree analysis, and certification reporting
- Reference — Configuration reference, data model, and field definitions
- FAQ — Answers to common certification and configuration questions
Source References (dev)
Source References (dev)
Code:
.polarion/pages/spaces/_default/V-Model Process Guide/page.xml (0.58) · .polarion/nextedy/sheet-configurations/ARP 4754A System Development Assurance.yaml (0.47) · .polarion/pages/spaces/_default/Program Manager Dashboard/page.xml, Safety Engineer Dashboard/page.xml, Design Engineer Dashboard/page.xml, VandV Engineer Dashboard/page.xml, Config Manager Dashboard/page.xml (0.43) · .polarion/pages/spaces/_default/Data Model/page.xml (0.41) · .polarion/polarion-project.xml, .polarion/context.properties, .polarion/security/user-roles.xml, .claude/PROJECT.md, TODO.md (0.41) · .polarion/nextedy/sheet-configurations/Whole RTM Config.yaml (0.40) · datasets/sol-aero-ui-walkthrough/summary.md, navigation.md, dashboards/home-dashboard.md, dashboards/role-dashboards.md, dashboards/standards-compliance.md, risksheet-views/risksheet-views.md, work-item-types/data-model.md (0.40)