I would say from a SCM perspective you have no responsibility with being familiar with the requirements. The testers and the business analyst and the end user will determine if the requirements were bet during user acceptance testing.
I am doing a cleanup of a projects unorganized configuration of their software product(s). I am working very closely with software/hardware quality. They recommended I look at the requirements for the products. I don't have a problem looking at them but I just don't want the project to think I will eventually be responsible with ensurinig their software is meeting their requirments. What if any level of responsibilty should I set to review or be familiar with their requirments?