As per DO-178 C section 6.2 Overview of Software Verification Activity
b. When it is not possible to verify specific software requirements by exercising the software on a realistic test environment, other means should be provided and their justification for satisfying the software process objectives defined in the Software Verification Plan or Software Verification Results.
After reading this every/most of verification engineers would understand it as other verification methods like Analysis, Inspection etc...
As per the discussion and Arguments "The real intent of this objective is how do we verify the software when hardware is unavailable" like, using simulator to verify the software needs to be documented under SVP for this objective satisfaction.
The question is, DO (document Order) as evaluated from version A, B to C now and still have ambiguities and different understandings. Why don't FAA/JAA can come up with examples or layman language explanations for each objective?