The intent of an MVP is to describe the broad outlines of how verification is approached on a complicated program. The benefit of having a technically competent MVP is that it can provide context for the approach, showing how the major activities relate to each other. However, MVP’s can attempt to control too much detail, and can be interpreted as being a contractual constraint.
Modern SE concepts have sometimes taken to the extreme notion that the MVP is the only source of technical information with regard to verification, being contractually superior to specifications. This is one of the distal causes for the reduction of specification Sections 4 (Verification) to rephrasing of the Sections 3 requirements, plus tabular indication of Verification Method. Unfortunately, few MVP’s can afford all of the detail required to properly consider the technical details of verifying CI’s, resulting in loose control over verification intent.