Why don't DO guidelines have examples? 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?
RTCA documents are not FAA documents, although the FAA is usually a member of the Special Committee that creates the documents. If an example is to be added, it is the decision of the SC, not of the FAA. 

The reason that no examples are given is that the recommendation is clear by itself. A good V&amp;V engineer will read this recommendation and use his skill, experience and creativity to find an other acceptable means to validate the software requirements that can not be validated in a realistic environment. This alternative means is then documented in the SVP.

Giving an example is not helpful at all, since the solution will depend completely on the software under test and the nature of the requirements.

If the hardware is not available, an emulator may be the solution.

In other cases artificial test inputs have to be generated, because failing a test in a realistic environment may prove to be catastrophic.