Instructor: Zuoliu Ding
Schedule: 7:00 PM - 9:05 PM, Tuesday and Thursday
Voice: (909) 274-0012|
Classroom: North Science - FC 618
Text: "Assembly Language for x86 Processors", by Kip R. Irvine (6th Edition), Prentice-Hall, 2010.
Course Prerequisite: CSCI 133 or CSCI 223 or equivalent with grade "C" or better.
Student Learning Outcomes: Upon successful completion of CSCI 241 F Comp Org & Assembly Lang Prog, the student will be able to analyze the architecture and use the instruction set of one or more processing platforms (e.g., Intel), and to write computer programs using the native instructions for a target processor.
Development environment: Using Microsoft Visual Studio IDE in teaching and learning x86 Assembly Language on Windows. Most programs created here only can be run on Windows. To be familiar with Visual Studio IDE and Windows OS is strongly preferred.
Attendance: As a comprehensive, demanding course, your attendance is taken at each class session. A student who misses over four classes may be dropped. If you cannot attend class due to serious illness or other extraordinary circumstances, please contact me via email or other ways in advance. You may be asked to document your absences. If you wish to drop this course, it is entirely your responsibility to complete all the necessary paperwork. I'll be available for help at some time; and if you need to see me, please feel free to contact me to make an appointment. If I am more than fifteen minutes late for class, the entire class is excused for that day.
General Policy: This course will cover most of the chapters in the book, although some may receive more attention than others. A tentative Course Schedule of topics is available for your preparation and content preview is strongly recommended. Concept understanding, programming capability, and problem solving are highly emphasized throughout the whole course. The class work required consists of four categories. The weight of each category is estimated as follows and may be adjusted in teaching. Final grading is not only based on the points, but from a comprehensive view of the student's performance.
|Category||# of Times||Points||Percent|
|Required Programming Exercises||About 20||About 100||24.1%|
|Section Review Questions||About 20||N/A||N/A|
|Optional Programming Exercises (Extra Credits)||Variable||Added||Added|
|Lab Attendance||One hour per week||15||3.6%|
|Total (Without Extra Credits)||-||415+||100+%|
* Note that attendance does not relate to the grade you are getting, so grading standards are based on the percentage:
|A: 90%+||B: 80-89%||C: 70-79%||D: 60-69%||F: Below 60%|
Examinations: There will be two mid-term tests and one final. Each of these exams is worth 100 points. There will be no make-ups. Midterm 1 will cover Chapters 1 - 5; Midterm 2 will cover Chapters 6 - 9. The final will cover Chapters 10 - 13. Parts of the Chapter 14, 15, 16, or 17 may be considered as selective. The format of these exams will consist of multiple choice, fill-in-the-blanks, code tracing, diagramming, and function designing and implementations.
Programming Exercises: There will be small problems to solve in programming for each class session (a two-hour lesson), which are mainly selected from the Programming Exercises in the text. They are worth about 5 points each. I may provide starter kits downloadable from Assignments for some projects. You can create your own design to solve the problem without caring starter kits, as long as you follow assignment requirements. You must submit your assignment for both code and documented explanations required in the textbook. Submitting your programming work in Email is highly preferred. The assignments will be graded on organization, correctness, and level of professional quality. You may be required to answer questions regarding your code to make sure that you understand the problem and you do the programming yourself. Copying others' program is considered as cheating with zero point received.
Section Review Questions: These are self-test and no turn-in required but also important homework. The questions are selected from the Section Review in textbook in each chapter. You can find the answers available in the text to verify by yourself. The Section Review Questions help you understand concepts in teaching materials and in tests. A strong recommendation is that you do all the Section Review after class and make sure your answers are correct. You are free to bring any problem to the beginning of next class, if necessary.
Extra Credits: We have optional programming exercises nearly for each chapter, which can be additional problems to consider with bonus points. You are encouraged to solve these problems to obtain extra credits, as long as you have potential to face more challenges. There might be essays assigned to write for designated topics that will evaluate your ability in analysis and comprehension of concepts. The seminars or quizzes might be scheduled according to teaching pace and content. You are always encouraged to present your own opinion, point of view, and code description in your assignments, as well as in classroom discussions.
Assignment Turn-in Policy:
1. Any assignment including Programming and Extra Exercises, will be expected within one week. During this period, the maximum score is full points.
2. A grace period of the second week turn-in: When submitting in the second week, your maximum score is 80% of the full points.
3. Not acceptable after the second week.
Final Exam: 05/22/2014, 7:00 PM - 9:05 PM, FC 618
Laboratory Hours: As part of this course, students are required to spend one hour per week outside of class time engaged in instructional activities related to the course. You must use the Computer Science Lab to meet this requirement. Please contact CS Lab for actual open hours. If you miss a week, you may make it up the following week. Totally in the semester, 12 lab hours are expected.
College Policies: Please read College Policies (http://math.fullcoll.edu/downloads/division-policies-10-08.pdf) carefully about Academic Honesty, Americans with Disabilities Act (ADA) Statement, Emergency Response Statement, Student behavior/conduct, Grievance/Grade Appeal Procedure, etc.
Information and Resources: You can click the hot links on the left pane to know more about the class and your progress.