This question might seems vague but heres the context:
When we are focusing on HCI we would most likely be interested on knowing first how the user usually deals with a certain object. We then try to see how our system could take away one of the tasks he would do himself and try to do it itself.
The object of my interest here is a simple paper catalogue. How would you measure its usability (paper one).
Then, how would you map it to a system interface? How would you measure the usability now on the system?
How would you compare the two usabilities measures?
This question narrows down this approach which is suggested on Stones book - User Interface and Evaluation.
What the catalogue is about is not the point, that why I left it without a description: To avoid suggestions trying to measure what the catalogue is about. My focus here is on the particular mapping of this kind of object on the real world as a simple paper and when it is mapped to a system interface. Assume the catalogue to consist of rows and tables, where each matching row and table gives you a suggestion and you must first reason about each row and each column to see if it suits you (Perhaps you would suggest another template for the catalogue?).