Survery DB Schema

[DBAStriker]

I am trying to modify a survey DB schema created by OOP(Object Oriented Programming) snobs who had their heads so far up their ass(in my opinion).
This is current schema created by them.

Diagram 1 (OOP snobs version)
http://forums.databasejournal.com/clear.gif

Actually there aren't a several foreign keys as they are shown in the picture, but that's what they(OOP snobs) are doing to the table "Response". They are inserting question_collection_id and its name as well as question_id and its name to Response table. However, it was not ill-intended, "We just wanted to load the report quickly"(OOP snobs).
But I really recommend this schema, Because of its simplicity.

Diagram 2 (My version)
http://forums.databasejournal.com/clear.gif

Yet I haven't proven that my schema will provide report just as quickly as OOP snobs' version. As mentioned earlier, since they don't have foreign key constraints accordingly, I do find quite number of discrepancy on values of "question" columns between "Question" and "Response" tables and "question_collection" columns between "question_collection" and "Response" table. I can provide schedule task to eliminate those problems. But I really prefer my schema than theirs. So far, I can explain mine is better just because of its simplicity and DBA's gut instinct. I'd like to hear Superior Expert's opinion which schema is better and why one is better than the other.