Last updated 01 April, 2023

CS271 -- Computer Architecture/Assembly Language

Spring 2023
CRN: 44747
Credits: 4
Instructor: Joseph Jess
email: jessj@linnbenton.edu

Initial class note: We are not in an introduction course to computer science (CS) anymore, and there will be topics that can be quite tough to understand at first exposure; this is perfectly normal! It may take a few looks at a structure or algorithm, potentially from multiple presenters, for all of its components to start making sense. We continue to add to the design, testing, and implementation concepts covered in earlier classes that use a programming language as a learning tool. We should expect to do much reading and research, much practicing, and much discussion of the topics we cover in class and in the coursework.

---

1. LBCC catalog course description, including pre-requisites/co-requisites:

Introduces functional organization and architecture of digital computers. Topics include digital logic; machine arithmetic and logical functions; component construction and interconnections. Coverage of assembly language: addressing, stacks, argument passing, arithmetic operations, decisions, and modularization is also provided.

Prerequisites: CS 161 Introduction to Computer Science I with a grade of "C" or better.

---

2. Class Time-space:

1. Note: This class is delivered in a flexible format (you will not need to attend live sessions).
2. Lecture + demo + lab: MW 1400 -- 1550, flexible, see Moodle for details

---

3. Measurable student learning outcomes:

On completion of this course, students will be able to:

1. Understand basic computer organization.
2. Understand basic computer architecture.
3. Demonstrate knowledge of digital logic.
4. Demonstrate knowledge of machine arithmetic operations.
5. Demonstrate knowledge of system structures and devices.
6. Write a simple program in machine language.

---

4. Learning resources:

1. Note: All class materials and storage will be freely available in a digital format
2. The Elements of Computing Systems
   Authors: Noam Nisan and Shimon Schocken
   ISBN-13: 978-0-262-64068-8
   Publisher: MIT Press
   (Note: the book chapters are freely available online and shared in my course materials)
3. I recommend the IDE VSCode; most editors would be fine.
4. We will discuss some capabilities of smart code editors during the course.
5. (strongly recommended) A desire to learn, experiment, design, test, and problem solve with code (both on and off of a computer).

---

5. Grading:

1. Scores for assignments will be available when the instructor gets to it... usually within the week of the due date. Grades will be made available through the Moodle gradebook.
2. Students will be required to turn in all coursework items before 23:59 (Pacific Time Zone) on the date that they are due (generally the first meeting day of the week in my courses)... though I have an extremely forgiving option for making up for missed work at the end of the term.
3. To earn a passing grade in this course you must pass each of the following coursework categories:

   1. Demonstration: Discussion, quizzes, and weekly assignments and projects -- 50% There are a number of discussion questions (usually turned in as a part of the programming projects), quizzes, and programming projects to be completed for this class, designed to challenge and solidify design, coding, and testing skills. Projects are generally graded based on the following rubric:

      1. Program Design (20%)

         Rating	Criteria
         20	Solution well thought out
         10	Solution partially planned out
         0	ad hoc solution; program was "designed at the keyboard" or no design submitted

      2. Program Execution (20%)

         Rating	Criteria
         20	Program runs very well under a variety of conditions, as submitted
         10	Program runs much of the time, may be missing required files or instructions for libraries used
         0	Program runs very poorly, not at all, or requires several modifications or files before it runs

      3. Specification Satisfaction (20%)

         Rating	Criteria
         20	Program satisfies specification completely and correctly
         10	Important parts of the specification not implemented
         0	Program poorly satisfies specification, or not at all

      4. Coding Style (20%)

         Rating	Criteria
         20	Well-formatted, understandable code and appropriate use of language capabilities
         10	Code difficult to follow in one reading or poor use of language capabilities
         0	Incomprehensible code, poor use of language capabilities, or a need to scroll up and down repeatedly

      5. Comments and Documentation (20%)

         Rating	Criteria
         20	Concise, meaningful, and well-formatted comments and docstrings
         10	Partial, poorly written, or poorly formatted comments
         0	Wordy, unnecessary, incorrect, badly written or formatted, or none or nearly no comments

   2. Final: Final project design and final project implementation -- 50%

      1. There will be a final project to test the overall ability to understand, design, implement, test, and reflect on the problem solving and programming knowledge and skills covered in the class.

      2. The final project will be a mix of "in-class" (initial design, testing, and implementation discussion) and take-home (finalizing design, testing, and implementation) elements.

Note: careful design, systematic testing, consistent style, and readability of code are important software quality factors (all of which are subject to interpretation but graded by the instructor based on the spirit and letter of the requirements, so be sure to explain your decisions).

Note well: Your submission should be explained and able to be compiled and run from just your submitted files in your final submission for that project. This means that you need to include any files provided to you that are necessary for your project to compile or run.

Note very well: Source code and related documents submitted must be designed and implemented by the student submitting the work and any code must compile and run on one of the instructor's machines in order to be graded. (to create a working program quickly: get it working simply, then add to it; if at some point it stops compiling you will better know where an error was introduced)

4. Make-up Work: I do not care when you learn it, as long as you learn it. To support this idea I allow missing work, even after the term for many, to be made up for in the final project (just be sure I know you are trying to make it up in the final project submission!).

5. Final grades will be given out based on the following based on score in the class:
   90-100%: A
   80-89%: B
   70-79%: C
   60-69%: D
   00-59%: F

6. Reminder: A passing grade in order to count for course requirements for CS classes is generally a C or above.

---

6. Other Administrative Information:

For a list of general administration information (note that this list is not intended to be exhaustive), such as:

1. contacting me,
2. accessibility resources,
3. expectations of student conduct,
4. communications,
5. student assistance,
6. miscellany,
7. nondiscrimination & nonharrasment,

(each section contains a number of sub-sections and is not meant to be exhaustive of all situations)
see my administrative information document: Additional Administrative Information.

Changelog:

1. 31 December, 2020, v1.0.0: initial release
2. 01 April, 2023, v1.0.1: markdown for GitHub viewing