CSci 241: Spring 2023 Syllabus


Instructor details

Instructor Andy Clifton
Email aclifton@fullcoll.edu
Student (office) hours Mon/Wed 4:15 — 5:45 PM
Tues 8:30 — 9:15 AM
Thurs 8:15 — 9:15 AM
Office Room 611-02
Office phone 714-992-7418
Website Instructor website
CSci Lab hours Mon/Wed 9:30 — 11:30 AM

(If you contact me by email I will try to reply the same day, but it may be up to a few days, depending on circumstances.)

Course details

CourseCSci 241, Computer Org. and Assembly Language Prog. (21842), 4 units
Room618 (600 building)
PrerequisiteCSCI 133 or 223 with a grade of ‘C’ or better.
Website Course Website
ScheduleMon/Wed, 11:45 AM — 1:50 PM
TextAssembly Language for Intel Based Computers, Kip Irvine
Last day to drop (without a ‘W’)Sunday, Feb. 5
Last day to withdrawSunday, Apr. 23
Final examWednesday, May 17

Student Learning Outcome: 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.

Course Description

“This course is an introduction to assembly language programming. It includes reviews of computer organization, programming techniques and concepts, addressing techniques, input/output, hardware architecture, and data structures.”

Student responsibilities

  1. Attendance will be taken during class. Students who arrive late are responsible for ensuring that their attendance is counted.

  2. If the instructor is more than fifteen minutes late for class, the entire class is excused for that day.

  3. Any student who misses the first class meeting with out making prior arrangements may be dropped. (But note that, if you wish to drop the class, the responsibility is on you to make sure you are officially dropped. Don’t just not show up and expect me to do it for you.) An unexcused absence may be expunged by using one token (see below).

Prerequisites: CSci 133 or 223 with a grade of ‘C’ or better.

I will use Canvas to post your grades. You will submit your assignments via the department’s computer science server (fccsci.fullcoll.edu:5150).

Grading

This course will use a system known as specifications grading. We will have approximately 8 assignments, the grades for which go into a pool of “assignment points”. We will also have every-other-week quizzes, a midterm in the middle of the semester, and a final exam; the grades for these go into an “exam points” pool. At the end of the semester, your final grade for the course is the smaller of your assignment grade and exam grade, however, in order to get a passing grade you must also complete:

Topics covered

Roughly in chronological order:

A note on collaboration and cheating

Computer science is a fundamentally collaborative subject, thus it’s not surprising that you will want to work together and help each other. While this is expected and allowed, the grade you are assigned at the end of the semester is intended to reflect your individual knowledge, not the gestalt knowledge that is formed when you and some friends get together. Consequently, I ask that you respect the “principle of the erased whiteboard”. The idea is to imagine, whenever you are working together, that you are writing things together on a whiteboard. When you are done, the imaginary whiteboard must be erased, without copying anything down or taking pictures of it. The only thing you are allowed to take away is the understanding you have gained.

My cheating policy for this class is quite simple: cheating on an assignment or test results in a grade of 0 for that assignment/test, with no opportunity for makeup. Cheating is defined as submitting anything that is not your own original work; this includes the output of AI/machine learning tools.

The college’s official policy on cheating and student behavior is as follows:

Academic Honesty Policy

Students are expected to abide by ethical standards in preparing and presenting material which demonstrates their level of knowledge and which is used to determine grades. Such standards are founded on basic concepts of integrity and honesty. These include, but are not limited to, the following areas:

Instructors may deal with academic dishonesty in one or more of the following ways:

  1. Assign an appropriate academic penalty such as an oral reprimand or point reduction.
  2. Assign an “F” on all or part of a particular paper, project, or exam.
  3. Report to the appropriate administrators, with notification of same to the student(s), for disciplinary action by the College. Such a report will be accompanied by supporting evidence and documentation.

Repeated violations may result in students receiving an “F” in the course, suspension or dismissal from the College.

Standards of Student Conduct and Discipline Policy

The standards of student conduct and disciplinary action for violation of Board Policy 5500 were approved by the NOCCCD Board on January 28, 2003, and were drawn in compliance with Sections 66300, 76030, 76033, 76034, 76036 of the State Education Code. Students are expected to respect and obey civil and criminal law and shall be subject to the legal penalties for violation of the city, county, state, and national law(s). Student conduct must conform to Board Policy and college regulations and procedures. As cited in BP5500, “A student who violates the standards of student conduct shall be subject to disciplinary action including, but not limited to, the removal, suspension or expulsion of the student.”

Students have an obligation to familiarize themselves with the College’s policies, rules and regulations and to conduct themselves in a reasonable, respectful manner, which is conducive toward attaining their educational goal. Upon registration, each student should obtain a copy of the College Policies and Regulations: Standards of Student Conduct and Discipline Policy. Contained therein are the policies approved by the Board of Trustees governing student behavior and the applicable penalties for violations of these policies. Copies are available in the Student Affairs Office, the Office of Equity and Diversity, all division offices, and the Student Services office.

Student Complaints

Students should attempt to resolve issues directly with the faculty or staff member involved in the complaint. For serious or ongoing complaints, students may file a formal Student Complaint. The process for doing so is described in the Catalog.

Semester Calendar

Date Subject Assignment
Week 1
Mon, Jan. 23 Introduction; Terminology; Digital Circuits
Wed, Jan. 25 Basic assembly; converting between numeric representations Group Project 1
Week 2
Mon, Jan. 30 Registers and simple loops
Wed, Feb. 01 Arithmetic operations; simple functions Assignment 1
Week 3
Mon, Feb. 06 Branching
Wed, Feb. 08 Branching and conditions – applications
Week 4
Mon, Feb. 13 Functions and the stack Group Project 2
Wed, Feb. 15 Functions continued
Week 5
Mon, Feb. 20 President’s Day Holiday
Wed, Feb. 22 Functions continued
(Lecture files to date)
Week 6
Mon, Feb. 27 Interop. with C; Floating-point operations
Wed, Mar. 01 Floating point and vector operations
Week 7
Mon, Mar. 06 Floating point, continued Group Project 3
Wed, Mar. 08 Instruction-level parallelism; pipelining on MIPS
Week 8
Mon, Mar. 13 Bitwise operations Group Project 4
Wed, Mar. 15 Midterm Review Midterm practice exam
(Solutions)
Week 9
March 20 — 24 Spring Recess
March 20 — 24 Spring Recess
Week 10
Mon, Mar. 27 Midterm exam
Wed, Mar. 29 Midterm Recap; Computer Organization and Caching
Week 11
Mon, Apr. 03 C-compatible structures; alignment and packing Assignment 2
Wed, Apr. 05 C-compatible structures continued
Week 12
Mon, Apr. 10 Assembly on the Z80 processor
Wed, Apr. 12 C-style strings; string operations
Week 13
Mon, Apr. 17 Macros part 1
Wed, Apr. 19 Macros part 2 Group Project 5
Week 14
Mon, Apr. 24 Macros part 3 Assignment 3
Wed, Apr. 26 Instruction formats
Week 15
Mon, May. 01 Memory Management
Wed, May. 03 Operating systems part 1: the boot process
Week 16
Mon, May. 08 Operating systems pt. 2: boot process continued
Wed, May. 10 Operating systems pt. 3: 32-bit mode
Week 17
Mon, May. 15 Final review Final practice exam
(Solutions)
Wed, May. 17 Final exam Assignment 4
Assignment 5


Other college policies

Various other college policies, which I am required to present to you, are as follows:

I am committed to creating a course that is inclusive in its design. If you encounter barriers, please let me know as soon as possible so that we can determine if there is a design adjustment that can be made or if a disability accommodation might be needed to overcome the limitations of the design. I am always happy to consider creative solutions as long as they do not compromise the intent of the assessment or learning activity. You are welcome to contact the Disability Support Services (DSS) Office to begin this conversation or to establish disability accommodations for this or other courses. DSS can be contacted at 714.992.7099 or dsp@fullcoll.edu. I welcome feedback that will assist me in improving the usability and experience for all students.

Americans with Disabilities Act (ADA) Statement

Fullerton College is committed to providing educational accommodations for students with disabilities upon the timely request by the student to the instructor. Verification of the disability must also be provided. The Disability Support Services office functions as a resource for students and faculty in the determination and provision of educational accommodations.

Fullerton College Catalog and Class Schedule

The Fullerton College Catalog and the Class Schedule contain a number of policies relating to students that are important to you. Please be sure that you have read these publications thoroughly. You may purchase copies of these publications at the campus bookstore, or you may read them online at the Fullerton College website, www.fullcoll.edu.

Grade Appeals

While the instructor is the final authority in determining grades that are assigned to students and that appear in their permanent record, students have a right to inquire how their grade was determined, and a Grade Appeal Procedure is described in the Catalog.

Wait Time for Late Instructors

If, due to unforeseen emergencies, the instructor does not arrive at the scheduled start time for class, students are to wait for fifteen minutes (unless otherwise notified by the division). If they do not receive notification to wait for their instructor to arrive, after 15 minutes the students may leave with no penalty for absence or assigned work due for that class meeting.