Modify a text file: $/old/outline61cst112.htm

$/old/outline61cst112.htm

<html><head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"><title> CST112 Course Outline --- Prof. BAM </title>
<script type="text/javascript">

</script>
</head>

<TABLE ALIGN=center XWIDTH=50% BGCOLOR=0 CELLPADDING=0 border=12><TR><TD>
<TABLE BGCOLOR=#99DDFF ALIGN=CENTER CELLPADDING=20><TR><TH>
	<CENTER>
	 
	
	

	COMPUTER SCIENCE DEPT.

STUDENT COURSE OUTLINE 
	
	
	 
	
		
		CST112 -- Introduction to Programming
		 
		2016 Spring Semester
		
	
	
	</CENTER>

</TABLE>
</TABLE /center>

</TABLE>

<blockquote>
<table align="CENTER" bgcolor="#CCDDFF" border="8" cellpadding="10" width="80%" >
<tbody><tr><th align="RIGHT" valign="TOP">INSTRUCTOR:		</th><td>
	<img src="img/tripod-r.gif" align="RIGHT">
	B. A. Martin
	 
	(Adjunct Associate Professor)

</td></tr><tr><th align="RIGHT">COURSE:		</th><td> CST112 -- Introduction to Programming
</td></tr><tr><th align="RIGHT">CREDITS:		</th><td> 4

</td></tr><tr><th align="RIGHT">MEETINGS:		</th><td>

Monday 
	6:00-9:50am /
	Room H203 (Caumsett Hall, Grant Campus)

</td></tr><tr><th align="RIGHT">PREREQUISITE(S):	</th>
	<td> MAT007 or equivalent (Required) 
	 Recommended:	Prior computing experience or CST111	 
	 CST112 and MAT107 are corequisities for students in the Information Technology curriculum.
</td></tr><tr><th align="RIGHT" valign="TOP">OFFICE HOURS:	</th><td> Before or after class and by appointment.
</td></tr>

<tr><th align="RIGHT">EMAIL::	</th><td> bam@suffolk.li
<tr><th align="RIGHT">DEPT. SECRETARY:	</th><td> 851-6770

</tbody></table>
</blockquote>

<table align="CENTER" bgcolor="#EEFFFF" border="1" cellpadding="10" width="90%">
<tbody><tr><td>

<h3><Xu> COLLEGE CATALOG DESCRIPTION </Xu>: </h3>

This course introduces fundamental programming principles to beginners. 
Emphasis is placed on algorithm development, structured programming techniques, flowcharting, coding, debugging and libraries.

It discusses programming concepts such as variables, conditionals, loops, functions, objects, and arrays. 
<img src="img/homer-right.jpg" align="RIGHT" hspace="6" vspace="4" width="70">

Program output may include graphical elements with images, animation and visualization.

The course is designed as a place where many ideas and techniques can mix and is therefore appropriate for a wide audience that includes programmers, as well as people interested in graphical design or analytic fields (science, mathematics, economics, etc.).

<h3><Xu> OBJECTIVES</Xu>: </h3>

<ul>
	After completing this course, the student should be able to:
<li> Use an Integrated Development Environment (IDE),
such as PDE ("Processing Development environment").
</li><li> Develop new, interactive applications using a programming language,
such as Processing.
</li><li> Understand the Object-Oriented / Event-Driven approach to programming.
</li><li> Create user-defined "methods" and "event-handlers".
</li><li> Assign values to object properties and variables (local or form-level).
</li><li> Understand declarations, expression evaluation, scope, types, etc.
</li><li> Understand structured programming,
	and be able to write control statements for selection, looping, etc.
</li></ul>

<!--
++++ Struck:
<pre>
COURSE OBJECTIVES:

At the end of this course, students will be able to:

1. Learn to create and manipulate graphical images using animation and user interaction
2. Know the concepts of writing in the Processing language
3. Recognize and use elements of structured programming including decision-making and
looping
4. Understand computer storage, and use Processing language data types and single-dimensioned
arrays
5. Incorporate input and output disk operations in Processing language programs
6. Learn to create and manipulate user-defined procedures and functions
7. Have had practice in the writing, compiling, executing, and testing programs developed for
web-based applications using images, animation and user interaction.
</pre>
-->

<h3><Xu> STUDENT REQUIREMENTS</Xu>: </h3>

To successfully complete this course, you must submit required homeworks
 and programming assignmentsts, and demonstrate proficiency on all exams
 and projects. All work submitted must be neatly
presented clearly labeled and identified as to the assignment and what
has been accomplished.

<dt>
		<xfont size="+1">TEXTBOOK:
	</xfont></dt>
	<dd>
	<img align=left src=img/textbook.jpg WIDTH=200 VSPACE=6 >
	<XXXimg align=right src=img/2909195001_9c7d94e1cb_m.jpg WIDTH=125>
	<Ximg src="img/vb7.jpg" align="RIGHT">
<TABLE BACKGROUND=http://wiki.processing.org/skins/processingskin/processing_wiki_back.jpg BORDER=0><TR><TD>
		
		
			<BIG>"Learning Processing</BIG>
		
		           -- A Beginner's Guide to Programming 
		           Images, Animation, and Interaction"

by Daniel Schiffman
		 
		
		(Morgan Kaufmann Series in Computer Graphics) [Paperback];
		 
		ISBN: 978-0-12-373602-4

</TABLE>

<TABLE ALIGN=CENTER CELLPADDING=12 BORDER=6 BGCOLOR=#FFCCFF><TR><TD>
READ THESE FIRST:
 
<UL>

<LI> <A HREF=
http://www.cs.sfu.ca/CourseCentral/166/johnwill/intro.html
TARGET=_BLANK >
Introductory discussion
</A>

<LI> <A HREF=
http://www.cs.sfu.ca/CourseCentral/166/johnwill/first_program.html
TARGET=_BLANK >
Your first program
</A>

</UL>

</TABLE>

</xbr></dd>
	<dt>

</dd>

<dt>
		<xfont size="+1">
		THE PROCESSING.ORG WEBSITE:
	</xfont></dt>
		<A HREF=http://processing.org/>
		<img src="http://processing.org/img/processing2-logo.jpg"
			hspace="12" vspace=12 width="80" align="LEFT" >
		</A>
		<A HREF=http://processing.org/>
		<img src="http://pages.shanti.virginia.edu/Fine_Arts_Library_News/files/2012/07/180px-Processing_Logo_Clipped.svg_.png" 
			hspace="12" vspace=12 width="80" align="RIGHT" >
		</A>

<dd>

		The
		<A HREF=http://processing.org/>
					Processing.org website
		</A>
		contains documentation 
		and other information about 
		
		the Processing language.
		
		To do assignments using other computers, it may be necessary to 
		download and 
		install the
		<A HREF=http://processing.org/download/?processing >
			Processing Development Environment (PDE)
		</A>

<dt>
		<xfont size="+1">READING ASSIGNMENTS:
	</xfont></dt><dd>
Each student is responsible for all material taught or assigned by the instructor.
The student is expected to complete all assigned reading, prior to class meetings.

<dt>
		<xfont size="+1">COMPUTER & INTERNET ACCESS:

</xfont></dt><dd>
		Between classes, the student should have computer access to the internet,
		to obtain assignments, submit homeworks and projects, etc.
			 
			
			
			(NOTE:
			 
			
			If you have ANY difficulty at all in obtaining internet access between classes
			please see the instructor after class to remedy this difficulty.)

<BLOCKQUOTE>

Although computer lab time may be scheduled each week during class time, students should be
aware that additional lab time outside of class will be necessary to complete the requirements of
this course. Students should plan to spend an additional 3 to 6 hours per week 
using other computers, such as those in the Caumsett-211
computer lab.

</BLOCKQUOTE>

</dd>

<dt>
 <xfont size="+1"> MIS-USE OF CLASSROOM COMPUTER EQUIPMENT :
 <dd>

All computer equipment in classrooms and laboratories
is the property of the college,
and NOT intended for computer activites unrelated to the college curriculum
(such as games, entertainment, "instant messager", "surfing the web", etc.)
 <dd>
Use of classroom computers for unrelated activities may result in loss of privileges
and other disciplinary action
(including dis-enrollment).

</dl>
</ul>

<dt>
		<xfont size="+1">CODING STANDARDS & CODE REVIEWS:
	</xfont></dt><dd>

This is a course in computer progamming,
i.e. the development of software "code"
that has two audiences:
<OL>
 <LI> computers, which must compile and execute the code, and
 <LI> human programmers, who must read and understand the code

(e.g. in order to debug or modify it).

</OL>

Therefore, 
good programming practice
depends not only upon how the computer processes the code,
but also upon the ability of other programmers to read and understand the code
(perhaps in order to debug or modify it).

For coding assignments,
grading will be based not only on 
whether the code compiles correctly and performs the assigned tasks,
but also upon
its organization, clarity, 
and -- most of all -- "readability".

These and other aspects of 
programming practices,
as well as adherance to 
"coding standards" 
(to ensure testability, maintainability, etc.)
will be introduced and discussed in the textbook and in class.

<TABLE ALIGN=CENTER BGCOLOR=333399 BORDER=0 CELLPADDING=4 CELLSPACNG=0 BACKGROUND="http://processing.org/img/processing-web.png" ><TR>
<TD WIDTH=50> 
<TD>


"Any fool can write code that a computer can understand. 

 

  
Good programmers write code that humans can understand." 


<TD WIDTH=50> 
</TABLE>

<dt>
CODE REVIEWS:
<dd>
One technique that is very effective in promting good software is the "code review"
wherein several programmers examine and critique software code that is being developed by some or all of them.

During this process,
while there may be criticism of specific lines of code,
it must always be "constructive criticism"
and never employed to blame or disparage the author(s) of the code under review.

Remember that computer source code is not some sort of "private communication" only with the computer,
kept secret from others.
Instead, source code should be thought of as intended for "publication", 
meant for the eyes of others of humans!
In a code review, colleagues often examine a "rough draft" or a "work in progress"
in order to help with problems, make suggestions, etc. 
-- and perhaps also to learn something new.

</dd>

</dl>

<h3><Xu> COURSE POLICIES</Xu>: </h3>

ATTENDANCE POLICY:

Attention is directed to the following statement of college policy.

<p class="western" style="border-style: solid none solid solid; border-color: rgb(0, 0, 0) -moz-use-text-color rgb(0, 0, 0) rgb(0, 0, 0); border-width: 1px medium 1px 1px; margin: 0.05in 0.5in 0.19in;
padding: 0.1in 0in 0.1in 0.1in;">
	<img src="img/sccc-wall.png" align="LEFT" HSPACE=8 >
"The
college expects that each student will exercise personal
responsibility with regard to class attendance. All students are
expected to attend every class session of each course for which they
are registered. Students are responsible for all that transpires in
class whether or not they are in attendance." 

Consequently, each
student in this course is strongly advised to make standing
arrangements with another individual student to take detailed notes,
collect handouts, relay announcements, etc., in the event 'e doesn't
show up at class. While you are encouraged to contact the instructor
for advice before (or after) missing a class, it is more effective to
have your "buddy" take detailed notes, and the student
remains responsible for "all that transpires in class".

Find a "buddy" to cover for you!

 
 
 

Do it now, not after missing a class.

This instructor does
not give credit for mere attendance, nor is credit lost for absence.
Attendance is not a direct factor in grading policy,
but it may indirectly affect the "participation" component.

College
policy defines "Excessive Absence or Lateness" as
"more than the equivalent of one week of class meetings".
While attendance is not a component of grading policy for this class,
a student missing more than one week of consecutive classes - without
making any contact with the instructor - may be removed from the
class roster and given either a "W" or an "F" grade,
at the instuctor's option.

</li>

<li>
	CODE OF CONDUCT:

 
 
<xbr>
	*** Please take note ***

<td bgcolor="#b3b3b3" height="181" valign="top" width="658">
			
	SCCC STUDENT CODE OF CONDUCT

	<img src="img/image24.gif" align="RIGHT" width="150">

... Although
			not all-inclusive, the following actions, activities or behaviors
			are expressly prohibited:

<blockquote>
			
			"Unauthorized or illegal use of College computer facilities
			or equipment, such as hacking; duplication or unauthorized use of
			copyrighted software; destruction, unauthorized transfer or
			alteration of files; unauthorized use of another individual's
			identification, password or work."
			</blockquote>

Any
			student guilty of the above may receive a failing grade in that
			class, be dismissed from class
and/or
			be referred to the Dean of Students for further discipline
			proceedings.

</td>
	</tr>
</tbody></table>

</xbr></li></ul>

<hr>

</td></tr></tbody></table>

<A HREF="http://suffolk.li/cst112/19cst112/students/bam/api.html" TARGET=api>
http://suffolk.li/cst112/19cst112/students/bam/api.html
</A>