Syllabus: Spring 2024		Credit hours: 4
Class times: 11:15am – 12:05pm, MoWe		Classroom: Leonard 215
Class times: 11:15am – 12:05pm, TuTh		Classroom: Leonard 107
Class # (on-campus: 370-01): 11259		Class # (on-line: 370-02): 11367
Instructor: Wen-Chen Hu   (my teaching philosophy)		Office: Upson II 366K
: https://und.zoom.us/j/2489867333		Email: wenchen@cs.und.edu
Office hours: 12:30pm – 02:30pm, TuTh
TA: Mohamed Osama Ali Mahmoud	Office: Upson II 223
: https://und.zoom.us/j/3468502524	Email: mohamed.mahmoud.1@und.edu
Office hours: 09:00am – 11:00am, MoTuWe

Prerequisites: CSCI 330 with a grade of C or better, EE 201, and EE 201L (strictly enforced—school policy)

Synchronous class delivery: The class lectures will be delivered synchronously via https://und.zoom.us/j/2489867333, and the Zoom video will be posted on the Blackboard afterwards. Students can watch the video clips anytime they want.

Textbook: Computer Organization and Design MIPS Edition: The Hardware/Software Interface, 6^th ed., David A. Patterson and John L. Hennessy, Morgan Kaufmann, ISBN: 978-0-12-820109-1

^†There is no specific textbook adopted for the assembly language discussed in this course because the lecture notes and the above links provide enough information for us to use.)

Lecture notes: Other than the textbook, award-winning, interactive, complementary, and abridged lecture notes (based on the textbook and other online documents and user manuals) and detailed and precise class instructions will be provided. Collectively, the lecture notes and instructions are more like a small book, which supplies much more information than regular notes do and makes the subject studies much easier. Students will not have problem learning the subjects or taking the exams after studying them and doing the homeworks and programming exercises.

---

Grading: Grade information Programming exercise guidelines Homework guidelines Examination rules and guidelines

---

Announcements:

• Updated constantly: Class notes (calculation):
  • undcemcs02 (most up-to-date and requiring a VPN connection)
  • undcemcs01 (no VPN required, but may not be up-to-date)


• Monday, April 22: Homework IV due
• Tuesday, April 09: Homework IV posted
• Sunday, April 07: Homework III Solutions posted
• Friday, March 29: Homework II Solutions posted
• Tuesday, April 09: Exam II to be held at 6:30pm–8:30pm (CST) for all students
• Wednesday, March 27: Exam II Rules and Question Distribution posted
• Thursday, April 04 (firm): Homework III due
• Thursday, March 20: Homework III posted
• Monday, March 25: Homework II due
• Thursday, March 14: Homework II posted
• Thursday, February 15: Homework I Solutions posted
• Monday, March 25: Programming Exercise II due
• Tuesday, February 13: Programming Exercise II posted
• Tuesday, February 20: Exam I to be held at 6:30pm–8:30pm (CST) for all students
• Thursday, February 08: Exam I Rules and Question Distribution posted
• Thursday, February 15: Programming Exercise I due
• Friday, January 28: Programming Exercise I posted
• Monday, February 12: Homework I due
• Friday, January 28: Homework I posted
• Monday, January 08: Register this course via Course Registration.

---

Tentative Schedule:

Week	Class	Topic	Reading	Due	Where
0		0. Computer Career and Data Research & Technologies
		0.1 A computer career
		0.2 Data research
		0.3 Data technologies
1	01/09 01/10 01/11	1. Introduction to CSCI 370	Chapter 1
		1.1 Course outline
		1.2 Historical perspective	1.12
		1.3 Programming language generations
		1.4 A language processing system
2	01/16 01/17 01/18	2. Computer Abstractions and Technology	Chapter 1
		2.1 Below your program	1.1-1.3
		2.2 Under the covers	1.4
		2.3 Processor technologies	1.5
		2.4 Memory technologies	1.5
	01/18	Last day to add a course or drop without record  Last day to add audit or change to/from audit  Last day to receive a refund on a dropped class  Drops after the last day to add will appear on a transcript.
	01/15	Holiday, Martin Luther King Jr. Day (Monday) — no classes
3	01/22 01/23 01/24 01/25	3. Computer Abstractions and Technology (Cont.)	Chapter 1
		3.1 Performance	1.6
		3.2 The power wall	1.7
		3.3 The sea change	1.8
		3.4 Real stuff	1.9
4	01/29 01/30 01/31 02/01	4. MIPS Assembly Programming	App. A & Ch. 2
		4.1 Programming Exercise I
		4.2 MARS simulator	A.2-A.4
		4.3 MIPS CPU	A.9
		4.4 MIPS assembly language	A.10
5	02/05 02/06 02/07 02/08	5. MIPS Assembly Programming (Cont.)	App. A & Ch. 2
		5.1 Operations and operands	2.1-2.3
		5.2 Data representations	2.4
		5.3 Signed and unsigned numbers	2.4
		5.4 Representing instructions in the computer	2.5
6	02/12 02/13 02/14 02/15	6. MIPS Assembly Programming (Cont.)	App. A & Ch. 2
		6.1 Memory usage	A.5	HW I
		6.2 Logical operations	2.6
		6.3 Instructions for making decisions	2.7
		6.4 Supporting procedures in computer hardware	2.8	EX I
7	02/21 02/22	7. MIPS Assembly Programming (Cont.)	App. A & Ch. 2
		7.1 Procedure call convention	A.6
		7.2 Communicating with people	2.9
		7.3 MIPS addressing for 32-bit immediates and addresses	2.10
		7.4 Translating and starting a program	2.12
	02/19	Holiday, Presidents’ Day (Monday) — no classes
	02/20	Exam I (for both on-campus and on-line students; 6:30pm – 8:30pm, Tuesday)
8	02/26 02/27 02/28 02/29	8. Arithmetic for Computers	Chapter 3
		8.1 Introduction	3.1
		8.2 Addition and subtraction	3.2
		8.3 Multiplication	3.3
		8.4 Division	3.4
9	03/04 – 03/08	Spring Break — no classes
10	03/11 03/12 03/13 03/14	10. Arithmetic for Computers (Cont.)	Chapter 3
		10.1 Floating point representation	3.5
		10.2 Floating-point addition and subtraction	3.5
		10.3 Floating-point multiplication	3.5
		10.4 The guard, round, and sticky bits	3.5
11	03/18 03/19 03/20 03/21	11. The Processor	Chapter 4
		11.1 Introduction	4.1
		11.2 Logic design conventions	4.2
		11.3 Building a datapath	4.3
		11.4 Creating a single datapath	4.3
12	03/25 03/26 03/27 03/28	12. The Processor (Cont.)	Chapter 4
		12.1 A simple implementation scheme	4.4	HW II
		12.2 Operation of the datapath	4.4	EX II
		12.3 The ALU control	4.4
		12.4 Designing the main control unit	4.4
13	04/02 04/03 04/04	13. The Processor (Cont.)	Chapter 4
		13.1 Pipelining overview	4.6
		13.2 Pipeline hazards	4.6
		13.3 Pipelined datapath	4.7
		13.4 Pipelined control	4.7	HW III
	04/05	Last day to change to or from S/U grading  Last day to change to or from audit grading  Last day to drop a full-term course or withdraw from school
	04/01	Easter holiday (Monday) — no classes
14	04/08 04/10 04/11	14. The Processor (Cont.)	Chapter 4
		14.1 Data hazards	4.8
		14.2 Forwarding versus stalling	4.8
		14.3 Control hazards	4.9
		14.4 Dynamic branch prediction	4.9
	04/09	Exam II (for both on-campus and on-line students; 6:30pm – 8:30pm, Tuesday)
15	04/15 04/16 04/17 04/18	15. Exploiting Memory Hierarchy	Chapter 5
		15.1 Introduction	5.1
		15.2 Memory technologies	5.2
		15.3 The basics of caches	5.3
		15.4 Accessing a cache	5.3
16	04/22 04/23 04/24 04/25	16. Exploiting Memory Hierarchy (Cont.)	Chapter 5
		16.1 Measuring cache performance	5.4	HW IV
		16.2 Improving cache performance	5.4
		16.3 Virtual memory	5.7
		16.4 Virtual memory performance	5.7
17	04/29 04/30 05/01 05/02	17. Exploiting Memory Hierarchy (Cont.)	Chapter 5
		17.1 TLB	5.7
		17.2 A common framework	5.8
		17.3 A summary	5.8
		17.4 Wrapping up
18	05/07	Final exam (for both on-campus and on-line students; 06:30pm – 08:30pm, Tuesday)
19	05/14	Grades posted before noon, Tuesday

Instructor’s qualification: The instructor has been teaching computer architecture for more than 10 years, so he is well familiar with the topics. In addition, he taught an assembly-language course for 7 years and designed and implemented a POPLOG virtual machine for which both LISP and PROLOG compilers generate code.

University of North Dakota Course Description (CSCI 370) —
Computer structure, machine presentation of numbers and characters, instruction codes and assembly systems. Introduction to hardware methodologies and software extensions to hardware in computers. Some topics on hardware and software selection will be discussed.

Computer Architecture from Wikipedia —
Computer architecture in computer engineering is the conceptual design and fundamental operational structure of a computer system. It is a blueprint and functional description of requirements and design implementations for the various parts of a computer, focusing largely on the way by which the central processing unit (CPU) performs internally and accesses addresses in memory.

Assembly Language from webopedia.com —
Assembly language is once removed from a computer’s machine language. Machine languages consist entirely of numbers and are almost impossible for humans to read and write. Assembly languages have the same structure and set of commands as machine languages, but they enable programmers to use names instead of numbers. Each type of CPU has its own machine language and assembly language, so an assembly language program written for one type of CPU will not run on another. In the early days of programming, all programs were written in assembly language. Now, most programs are written in a high-level language such as FORTRAN or C. Programmers still use assembly language when speed is essential or when they need to perform an operation that isn’t possible in a high-level language.

A System Structure of Basic Computer Systems —