• Protein Structure Prediction Paradigms:
• Statement (I): Ab initio method predicts protein structures based on sequence homology with known structures. $\implies$ False.
• Ab initio (de novo) structure prediction predicts 3D tertiary structure from physicochemical principles and amino acid sequences without using known homologous template structures.
• Statement (II): Homology modeling, also known as comparative modeling attempts to produce all-atom protein models based on sequence information alone without the aid of known protein structures. $\implies$ False.
• Homology (comparative) modeling constructs models strictly dependent on experimentally resolved 3D structures (templates from PDB) sharing significant sequence similarity.
• The definitions in the two statements are mutually inverted.
• Conclusion: Both Statement (I) and Statement (II) are false (Option 2).

Correct option: (2) Both Statement (I) and Statement (II) are false.

• Structural Biology & Bioinformatics Software Tools:
• Procheck $\to$ (II): Assesses stereochemical quality and dihedral angles ($\\phi, \\psi$) of a protein model via Ramachandran plot analysis.
• ClustalW $\to$ (I): Classic progressive multiple sequence alignment (MSA) software.
• Swiss-Model $\to$ (V): Premier automated homology/comparative protein modeling server.
• Cn3D $\to$ (III): NCBI's helper molecular visualization tool displaying 3D macromolecular structures and sequence alignments simultaneously.
• Affinity $\to$ (IV): Computational molecular docking software that predicts binding modes and ligand-receptor interactions.
• Matching Result: (A) - (II), (B) - (I), (C) - (V), (D) - (III), (E) - (IV) (Option 1).

Correct option: (1) (A) - (Il), (B) - (1), (C) - (V), (D) - (ill), (E)- (IY)

• Software Deterioration and Entropy (Pressman):
• Physical hardware wears out due to physical friction, heat, and environmental fatigue.
• Software does not suffer physical wear-out; however, it deteriorates over time as it evolves because:
• Repeated maintenance cycles, bug patches, and new feature requests introduce architectural entropy.
• Unanticipated side effects and dependencies emerge between interacting components, increasing complexity and error rates.
• Conclusion: Multiple change requests introduce errors in component interactions (Option 3).

Correct option: (3) Multiple change requests introduce errors in component interactions.