RAMS ENGINEERING · RAILWAY · DEFENSE · AUTOMOTIVE
RAMS engineering and software certification,
from system definition to the Safety Case
Safety software for railway on-board and wayside systems must follow IEC 62278 (EN 50126), IEC 62279 (EN 50128) and its successor EN 50716, and IEC 62425 (EN 50129), with defined activities and deliverables at every lifecycle phase.
One team at WellTech Lab handles the certification deliverables and testing — from plans and the System Definition through software requirements and design, static and dynamic testing, to the Safety Case. With experience at every level from SIL 0 to SIL 4, we let developers focus on development while certification takes the least possible time and cost.
- Deliverables for the whole lifecycle (Plan → System Definition → … → Safety Case)
- Covers software and UPIC (User Programmable Integrated Circuit: FPGA, CPLD, etc.) deliverables
- Static testing with MISRA, CWE and CERT; dynamic testing with LDRA (Statement / Branch / MC/DC)
- Support through certification-body assessments and audits
- Experience beyond railway: defense (weapon-system software reliability testing) and automotive (ISO 26262)
LIFECYCLE
Support across the entire V-model lifecycle
Our scope within the EN 50126 system lifecycle and the EN 50128 / EN 50716 software lifecycle.
← Swipe to see the full diagram →
- System deliverables
- Software deliverables
- Static testing
- Dynamic testing
- Validation · Safety Case · Assessment
SERVICES
Services
Certification deliverables
We write the plans, specifications, designs and verification documents required by EN 50126 / 50128 (50716) / 50129, matched to the project SIL.
- Planning (quality assurance, configuration management, verification and validation plans)
- System Definition, risk analysis, Hazard Log management
- Software requirements, architecture and design specifications with traceability
- Safety Case and supporting evidence
Static testing
Coding rules and static analysis catch latent defects during implementation.
- Coding-rule selection (MISRA, CWE, CERT, etc.)
- Detection of rule violations and runtime errors
- Design and data-flow review with call and flow graphs
- Re-analysis after fixes and reporting
Dynamic testing
Requirements- and structure-based tests on the real target reach the coverage goals.
- Test plans and test-case design (requirements- and structure-based)
- Target-linked environment identical to development
- Statement / Branch / MC/DC coverage testing with LDRA
- Requirement and function coverage; support for accredited test certificates
Validation and assessment
We prepare the evidence required by independent safety assessment (ISA) and certification bodies, and join the audits.
- Review of software integration test reports and explanations of unmet items
- Audit checklists for static and dynamic testing
- Consistency of tool versions, target files and target environment
- Support for customer and certification-body acceptance schedules
DELIVERABLES
Key deliverables by phase
Adjusted to project scope and SIL. UPICs (e.g. FPGA) are covered with requirements, design and verification deliverables following the UPIC lifecycle in EN 50129 Annex F.
01 · Planning
Plan
- RAMS / Safety Plan
- Software Quality Assurance Plan
- Software Configuration Management Plan
- Software Verification Plan
- Software Validation Plan
02 · System
System
- System Definition
- Preliminary Hazard Analysis
- Hazard Log
- System (Safety) Requirements Specification
- FMECA / FTA
03 · SW requirements · design
Specification
- Software Requirements Specification
- Software Architecture Specification
- Software Design Specification
- Software Interface Specifications
- Software Component Design Specification
- Verification Reports per phase
04 · Testing
Test
- Overall Software Test Specification
- Software Integration Test Specification / Report
- Software/Hardware Integration Test Specification / Report
- Software Component Test Specification / Report
- Static and dynamic test reports
05 · Validation · deployment
Validation
- Overall Software Test Report
- Software Validation Report
- Tools Validation Report
- Release Note · Deployment Records
06 · Safety demonstration
Safety Case
- Safety Case (EN 50129)
- Software Assessment support materials
- Records of ISA findings and actions
- Certification submission package
SAFETY INTEGRITY LEVEL
Experience at every level, SIL 0 to SIL 4
Higher SILs demand stricter techniques, independence and coverage. We know the requirements of each level and plan for them from day one.
- SIL 0Basic Integrity
- SIL 1Safety Integrity
- SIL 2Safety Integrity
- SIL 3Safety Integrity
- SIL 4Safety Integrity
Requirements get stricter to the right · Experience at every level
PROCESS
Process
- Scope · SIL review
- Schedule · criteria
- Deliverables · testing
- Assessment · certification
STANDARDS & TOOLS
Standards and tools
TRACK RECORD
Track record
We have delivered software certification deliverables and testing in railway signaling, communications and rolling stock, defense weapon systems, and automotive and mobility.
- 2026GA/SA for 1 SIL 4 and 2 SIL 2 certification support projects
- 2025GA/SA for 3 SIL 4 certification support projects · train fire detection software development, certification and testing
Under non-disclosure agreements with our clients, details are not published. Please contact us for more information.


※ Only clients who have agreed to be listed are shown.
INDUSTRIES
Railway, defense and automotive — each to its own standards
Centered on coding-rule checks and structural coverage testing, we deliver documents and tests to each industry’s standards and integrity levels.
RAILWAY
Railway
EN 50126 / 50128 / 50716 / 50129
- Certification deliverables at SIL 0–4
- Static and dynamic testing, Safety Case
- Software and UPIC (e.g. FPGA)
DEFENSE
Defense
DAPA “Weapon System Software Development and Management Manual” (Korea)
- Weapon-system software reliability testing
- Static (coding rules) and dynamic (code coverage) tests with targets per software grade
- Re-testing after code changes, reports and audit support
- Migration and development of defense equipment operating software (VxWorks)
AUTOMOTIVE · MOBILITY
Automotive · Mobility
ISO 26262 functional safety (ASIL A–D)
- Automotive and mobility software testing
- Coding guidelines such as MISRA C applied and checked
- Statement, branch and MC/DC structural coverage per ASIL; requirements-based testing
FAQ · GLOSSARY
FAQ and glossary
Can you join a project that is already under way?
Yes. We review the existing deliverables and the required SIL, list the missing activities and documents, and continue with you from the remaining phases.
Can we order only deliverables, or only testing?
Yes. Choose just what you need — deliverables, static testing, dynamic testing or assessment support.
How is project information protected?
Every project runs under an NDA, and we never disclose client names or project details without consent.
SIL (Safety Integrity Level)
Safety integrity level, graded 0–4 by the risk if a function fails; the higher the level, the stricter the development and verification requirements.
ISA (Independent Safety Assessment)
An assessor independent of the development organization evaluates whether lifecycle activities and deliverables meet the standard.
V&V (Verification & Validation)
Checking that each phase meets the previous phase’s requirements (verification) and that the final result fits its intended use (validation).
MC/DC (Modified Condition / Decision Coverage)
Structural coverage showing that each condition independently affects the decision outcome — stricter than statement or branch coverage and common at high integrity levels.
UPIC (User Programmable Integrated Circuit)
Integrated circuits such as FPGAs and CPLDs whose logic is designed by the user; in railway, EN 50129 Annex F covers the UPIC lifecycle and verification.
EN 50716
The railway software standard published in 2023, unifying EN 50128 (signaling and control) and EN 50657 (on-board rolling stock).
Safety Case
A structured argument, with evidence (analyses, test results, management records), that the system meets its required safety level — the key submission for certification.