Course Information

CSCI 136
Fundamentals of Computer Science II
Spring 2019

COURSE SYLLABUS

Description:

A continuation of CSCI 135 . Explores the finer and more subtle elements of a programming language. Programming techniques and structures include arrays, records, and linked lists. Prerequisite: CSCI 135. CRN: 34606.

Instructor:

Michele Van Dyne

(406) 496-4855
Museum 204B (behind Tami's office and the Network Lab)
Office hours: Monday 2:00-3:00, Wednesday and Friday 1:00-2:00

Classes:	Monday	11:00 - 11:50am	Lecture	Science and Engr. 308
	Wednesday	02:00 - 4:50pm	Lab	Science and Engr. 308
	Friday	11:00 - 11:50am	Lecture	Science and Engr. 308

Resources:	Optional Reading	Java: An Introduction to Problem Solving and Programming 8th edition by Walter Savitch
	Optional Reading	Head First Java 2nd edition by Kathy Sierra and Bert Bates
	Class web page	http://katie.mtech.edu/classes/csci136/
	Grades and assignment submission	See Moodle link at top of page
	Software	We recommend the freely available Eclipse integrated development environment (IDE). Eclipse is installed on the Museum, Engineering, and Main lab computers. You can also install it on your own computer (see the resources page).

Grading:	Take Home Exam #1	16 2/3%
	Take Home Exam #2	16 2/3%
	Take Home Exam #3	16 2/3%
	Programming assignments	50%
	Staff discretion (participation and extra-credit)	±?%

Letter Grades:	93-100%	A
	90-92.99%	A-
	88-89.99%	B+
	83-87.99%	B
	80-82.99%	B-
	78-79.99%	C+
	73-77.99%	C
	70-72.99%	C-
	68-69.99%	D+
	63-67.99%	D
	60-62.99%	D-
	Below 60%	F

Late policy:

Exams must be taken at the scheduled date and time. Make up exams will not be provided without a very valid reason. See the assignments page for the late policy regarding assignments.

Academic honesty:

Cheating will not be tolerated and can result in failure of the course. Submitted programs must be entirely your own work. Under no circumstances should you copy another person's code. Exams are to be strictly your own effort. Unless specified, no electronic devices are allowed in written exams. Programming exams must be completed without communication with any non-staff member.

General:
Any student who may need an accommodation due to a disability, please make an appointment to see me during my office hours. A letter from a Montana Tech Disability Coordinator authorizing your accommodations is needed.

Expectations:

E1. Students should have basic problem solving skills and be able to apply those skills to create an algorithmic solution for a given programming problem. (CSCI 135)
E2. Students should be able to create programs using assignments, control constructs, and routines and be able to find and correct any syntax errors to produce a running executable. (CSCI 135)
E3. Students should be able to test their programs, find any logic errors, and correct these flaws to produce a working program. (CSCI 135)

Course Outcomes:

R1. Students are proficient in a programming language and know basic error-handling, testing and debugging techniques. (CAC-c, i, j, k; EAC-k)
R2. Students use advanced programming techniques, including recursion, file I/O, abstraction, multi-file programs, and programming language libraries. (CAC-c, i, j, k; EAC-k)
R3. Students use and implement simple data structures, including stacks, queues, arrays, and linked lists. (CAC-c, i, j, k; EAC-k)
R4. Students use basic object-oriented programming methodologies including object-oriented problem decomposition, class design/implementation, and object creation/usage. (CAC-b, c, i, j, k; EAC-c, k)
R5. Students write defensive programs using an integrated design language and coding standard and basic error detection and reporting techniques with an emphasis on the responsibilities that computer professionals have for ensuring software quality. (CAC-b, c, i, j, k; EAC-c, k)
R6. Students understand and implement multi-threaded solutions to achieve provably correct synchronization among threads operating on shared resources. (CAC-c, i, j; EAC-k)
R7. Students integrate third party applications into their projects through socket connection/communications protocol, method API's, and command line interfaces. (CAC-c, i, j; EAC-k)
R8. Students implement client-server architectures which communicate over the Web using TCP and the sockets interface. (CAC-c, i, j; EAC-k)

Page last updated: December 20, 2019