So you don't know what's in the standard, but you make assertions and continue to support them? That's a fairly disappointing level of discourse for HN. It requires a very similar software development process to all other functional safety standards, in which verification and validation are key steps.
Here is a paper from Mathworks describing verification and validation according to ISO 26262:
Here is a paper from Mathworks describing verification and validation according to ISO 26262:
http://www.mathworks.com/tagteam/71300_1D-4.pdf