You should instrument your program to determine the response time for each terminal request (i.e., job) and average them over to report the mean response time, as desired. Then you should carry out an operational check to verify that the mean response time you found this way is indeed correct. To do this, the problem statement asks you to calculate the mean response time using the SMPL provided report (it is up to you to figure out how to do this), and then verify that it is very close to the mean response time that you computed by instrumenting the program. It probably won't be exactly equal because of the use of randomness and short run of the simulation. So don't worry if it is not exact, but should be very close. Closer estimations are possible by longer simulations, naturally!
Mean no. of terminal requests in the system means how many terminal requests on an average reside in the computer system (the dotted box in the figure). This number should be less than or equal to 16. Hint: you can evaluate this from the SMPL generated report. No real need to write additional code.
You may have some trouble in interpreting the report SMPL generates. They seem to use some awkward terminology sometimes. In the report, UTIL. is utilization (U), MEAN BUSY PERIOD is mean service time (1/m), and MEAN QUEUE LENGTH is, well, mean queue length (Q). In OPERATION COUNT, RELEASE means #service completions or #departures (C), and QUEUE means #customers finding the server busy when the made the request. So, the ratio of QUEUE and RELEASE is the fraction of customers that had to wait in the queue.
Turn in your commented source code, program output and your analysis/answers.