This preview shows pages 1–3. Sign up to view the full content.
This preview has intentionally blurred sections. Sign up to view the full version.View Full Document
Unformatted text preview: Q0 Q1 Q2 Q3 Q4 Q5 Q6 Q7 Q8 Exam 1 Page 1 of 7 EE 312 - University of Texas at Austin - Sample Your Name ______________________________Unique Section # [1 pt.] ________________ Test taking instructions. No calculators, laptops or other assisting devices are allowed. Write your answers on these sheets. You can use the back of the last page as scratch paper if needed. Wherever code is required, write C statements in the blank areas provided, or by modifying the given code in place. You are not required to follow the coding style guidelines when writing code on the exam, but be as neat as possible. Questions about the meaning of an exam question will not be answered during the test! Therefore, if you are unsure of the meaning of a specific test question, write down your assumptions and proceed to answer the question on that basis. If you see a typo or syntax error on the exam, fix it, circle it, and if you are right you will get a bonus point for each one fixed. In your programming solutions on this test you may use any of the functions that you know from the standard function library. Use of flowcharts, pseudocode and writing code snippets for problem solutions MAY result in partial credit. You have 55 minutes to complete this exam. 0. Program Measurements [1 pt.] For your programming assignment 2 fill in the table below by providing the data required to answer: - how big was your program (in SLOCs/statements)? - how many hours of effort did you expend on it (in approximate person hours)? - how many serious logic defects did you have to fix to get it working? Assignment # of SLOC Person hours # of logic defects 2 SLOC (source lines of code) Each physical line (or statement) in the source code listing counts as 1 SLOC. However, lines which are only comments and blank lines are not included in this count. Code modules included from the C libraries do not count, but the include statement does. Only SLOC delivered in the final submitted .c file for grading should be counted. The unit of measure for effort is a person hour; defined as: " an hour of time expended by you in the course of doing the assignment". A defect is a flaw in your program that causes it to not work properly. This includes both syntax errors and logic errors. We are interested in the number of serious logic errors that you encountered and had to fix in completing the assignments. Serious means that it was not immediately obvious what the problem was. Page 2 of 7 1. Terminology [22 pts.] Answer each of the following questions by choosing the best answer from the list below....
View Full Document
This note was uploaded on 03/15/2010 for the course EE 16005 taught by Professor Krasner during the Spring '10 term at University of Texas at Austin.
- Spring '10