<!--#set var="PAGE_TITLE" value="Syllabus" -->
<!--#include virtual="../header.shtml"-->

<h1><!--#echo var="PAGE_TITLE" --></h1>

  <h2>Overview</h2>
  This course examines the syntax and semantics of programming languages. Topics include: 
history and fundamentals of programing languages, formal specifications of 
syntax and semantics; the implementation and execution of programs; and 
object-oriented, functional, and logic programming. Programming assignments 
and projects will provide experience in a number of languages. Prerequisites: 
You must have completed CMSC 202 and CMSC 203 with a grade of C or better.

  <h2>Objectives</h2>

The key learning objectives for this course are:

<ul>
  <li> To understand how programming languages have and continue to evolve</li>
  <li>To learn about formal definition and specification of programming 
      languages</li>
  <li>To learn about different programming paradigms, and gain some experience 
      in several</li>
  <li>To study how programming languages are implemented</li>
  <li>To experience new ideas that are appearing in programming languages</li>
</ul>

<h2>Required Textbook</h2>
<p>
  <blockquote>
    <p><strong>Concepts of Programming Languages</strong>,
    latest edition (11th ed.), Robert W. Sebesta.
    Available new and used from the UMBC Bookstore and Amazon (can also be
    rented at a reasonable price).
    The tenth edition is still available, and is acceptable. </p>
    <p><img src="cover11e.png" width="242" height="305" alt=""/></p>
    <p>&nbsp;</p>
  </blockquote>
</p>

<h2>Class participation</h2>

Education works better when we're all actively engaged in it. It's more 
effective and more interesting when there are questions, comments, challenges, 
and occasional rants. These can take place in class but also on line via the 
Piazza discussion forum for the class.

<h2>Exams and quizzes</h2>

We will have a mid-term  examination in class and a comprehensive final 
examination. There may be several online quizzes and surveys.

<h2>Homeworks and Projects</h2>

There will be roughly one homework assignment every other week (see the syllabus for 
details). One or more of the homeworks may involve reading articles or papers 
and writing short essays.

<h2>Expectations</h2>

<p>
Unless otherwise specified, all assignments are to be turned in by 11:59pm on
the day they are due (which is given in the schedule). It is your 
responsibility to contact the instructor or TA in advance if this will not be 
possible. There will be a penalty for every day an assignment is late.

Students are expected to adhere to all university policies regarding student 
conduct, academic and otherwise, as posted on the University web site and in 
the Student Handbook. Academic dishonesty of any kind will be handled in 
accordance with University policy.
<p>

<blockquote style="margin:20px">
    "By enrolling in this course, each student assumes the responsibilities of an active participant in UMBC's scholarly community, in which everyone's academic work and behavior are held to the highest standards of honesty. Cheating, fabrication, plagiarism, and helping others to commit these acts are all forms of academic dishonesty, and they are wrong. Academic misconduct could result in disciplinary action that may include, but is not limited to, suspension or dismissal. To read the full Student Academic Conduct Policy, consult the UMBC Student Handbook, the Faculty Handbook, or the UMBC Policies section of the UMBC Directory."<br/>
    [Statement adopted by UMBC's Undergraduate Council and Provost's Office.]
</blockquote>
<p>

Regular class attendance is expected.

<h2>Grading Policy</h2>

Semester grades will be based on the following components. The percentages are 
initial estimates and subject to change to reflect the actual number and 
complexity of the quizzes, homework assignments and projects.

<ul>
<li> Class and online participation 5%</li> 
<li> Homework assignments 	45%</li> 
<li> Midterm exam 	20%</li> 
<li> Final exam 	30%</li>
</ul>
	
<h2>Assignments</h2>

We will have approximately 6 to 10 homework assignments. Doing these is critical 
to learning the material. Consequently, your performance on the homework 
assignments will count towards about 45% of your grade. Homework assigments 
will have a strict due date and penalties will be applied for late homeworks 
according to the following scale:

<ul>
<li>    -10% 	up to one day late</li> 
<li>    -20% 	up to two days late</li> 
<li>    -30% 	up to three days late</li> 
<li><strong>No credit will be given for homeworks over 3 days late</strong></li>
</ul>
So, if an assignment is marked as being due by April 1, it must be
submitted by 4/1@11:59pm to get full credit.  If you were to submit it
on 4/2@12:01am, it would incur a 10% penalty, and if on 4/3@12:01am (i.e,
1 day and 2 minutes late), a 20% penalty.
</p>
<p>
  You will submit most of your assignments online.
  Network and computer failures at UMBC are a fact of life. They are out of
  your control and out of our control. However, they are not an excuse for a
  homework or project to be submitted late, nor are they a reason for deadlines to
  be extended, even if the outage occurs on the due date. Plan
  accordingly. Waiting to submit your assignment until 5 minutes before it
  is due is a recipe for disaster. In the event of network outages or
  computer failures, <strong>you are still responsible for submitting your
  assignments on time</strong>.  There are labs on campus even if your home
  internet or <a href="http://resnet.umbc.edu/">ResNet</a> connection is
  down. Also, it is your responsibility to take care of any problems with your
  account, such as quota overages, which interfere with your ability to
  complete and submit projects for the course.  Project extensions will not be
  given for such problems.
</p>


<h2>Lectures and Readings</h2>
<p>
  You are expected to attend all lectures for this course. Although all
  sections will cover the same general topics, you are responsible for the
  specifics given during <strong>your section</strong>.
</p>
<p>
  You are responsible for all material covered in class, even if not found in
  the on-line class presentation materials. If you should happen to miss a
  class, you are responsible for getting any missed notes or
  announcements from a classmate.
</p>
<p>
  You are required to prepare for each class by having read all of the
  assigned materials beforehand.  Even though it sounds childish, the
  professor is not above giving a pop quiz if he has started to feel
  depressed about the level of preparedness among the students.
</p>


<h2>Schedule</h2>
<p>
  The <a href="../schedule/">online schedule</a> includes lecture
  topics/notes, reading assignments, midterm and final exam dates,
  and homework and project due dates.  Except for the final exam date,
  the remainder of the timeline should be considered somewhat fluid
  in order to allow us to adapt to any unanticipated events.
  The specific dates will become much more firm as we get closer
  to the relevant time period.
</p>


<h2>Course BlackBoard, and Piazza</h2>
<p>
  In addition to the course web pages, which will be the primary channel
  for disseminating information and course materials,
  Blackboard is available for all CMSC 331 students in all
  sections.  Blackboard will be used to post student lab grades.
  We will be using the Piazza system to support
  course discussion forums.  Discussion forums will be created for general
  questions about course material, C++, and for general questions about
  programming and tools.  A discussion forum will also be created for each project in
  this course.
</p>
<p>
  N.B.: Postings on the Piazza discussion forums are to be limited to 
  specific technical and logistical discussions about the coursework;
  you may use your own Facebook page or other personal resource,
  to gripe about how unfair the workload is, discuss the personal
  habits of fellow students or the instructors, etc.;
  we will monitor the Piazza forums
  to keep the signal-to-noise ratio at an acceptably high level.
</p>
<p>
  If you have difficulty accessing the CMSC 331 Blackboard site or your
  Piazza account, e-mail your instructor.
</p>


<h2>Academic integrity</h2>

<p>Here is some guidance on what we expect from you. Some of this was adopted 
from David Matuszek's policies at UPenn.</p>
<p><strong>You may: </strong></p>
<ul>
   <li> Discuss the assignments with one another.
   <ul>
     <li> If you don't understand something about the assignment, ask.</li>
     <li>The best people to ask are the instructor and TA, but there is no 
         harm in talking to other students about the assignments.</li>
     <li>You can and should use an appropriate discussion board on Piazza 
         to do this. We'll watch the lists and try to answer questions and 
         provide clarification.</li>
     <li>You should not post code, other than tiny snippetts, or partial 
         answers to problems on the discussion lists, of course. </li>
   </ul>
   <li> Help others debug their work.
     <ul>
       <li> Sometimes other people will notice immediately something that you 
            have spent hours trying to find. Maybe they've had the same 
            problem. Being "stuck" for long periods is not a good way to learn.
       </li>
       <li>More often than not, your errors become obvious when you try to 
           explain your program to someone else. The other person doesn't even
           have to be a programmer; in fact, it's probably better if they 
           aren't a programmer. It's often said that explaining your program 
           to your dog can be a big help.         </li>
       <li>If you help someone else, don't overdo it--don't write their 
           program for them. Help them understand their errors and how to fix 
           them, but don't do it for them. Teach them how to catch a fish 
           rather than buying them a flounder and cooking it with a white wine 
           sauce.         </li>
       <li>If someone is helping you, do not let them take a copy of your 
           program. Not everyone is honest. </li>
     </ul>
   </li>
   <li> Use, without attribution, anything we post to the Web.
     <ul>
       <li>If we post it, it's so that you can use it. We will know where it 
           came from.         </li>
       <li>However, it's an important habit in general to give credit to any 
           source that you "borrow" code from -- it's the honest thing to do. 
       </li>
     </ul>
   </ul>
<p><strong>You may not: </strong></p>
<li> Work together on the same program.
  <ul>
    <li>We emphasize this one because this is where we always hear, "but I 
        didn't understand."      </li>
    <li>Talking about the program is fine, but when it comes to writing the 
        program, do it by yourself.      </li>
    <li>Writing programs jointly is unacceptable. You will very probably be 
        caught and that will be grounds for failing the course.</li>
    <li>If you write a program jointly and try to hide the fact by making 
        cosmetic changes, this will be regarded as further evidence that you 
        know the rules and are being deliberately dishonest.      </li>
    <li>Working together may be acceptable in your home culture, and it is 
        usually encouraged in business; however, working together is not 
        acceptable in this educational system.      </li>
    <li>If you discuss your assignment extensively with another student, and 
        make reasonably detailed plans about how you will do it, and then go 
        off and each write each program separately, you will be surprised at 
        how different they turn out. We have never had a problem with programs 
        that were "accidentally" the same. </li>
  </ul>
<li> Copy anothers code.
  <ul>
    <li>If you copy someone else's program -- even just a part of it -- that
        fact will be noticed. </li>
  </ul>
<li> Allow your code to be copied.
  <ul>
    <li>Fair or not, this is the rule. If you and someone else turn in the 
        same program, both of you are guilty, regardless of who did the actual
        work. </li>
  </ul>
<li> Lend your code to someone else.
  <ul>
    <li>There is no good reason to do this, and if they copy your program, 
        you are at fault. </li>
  </ul>
<li> Leave your code lying around where someone else may copy it.
  <ul>
    <li>Please be careful with your disks, flash drives and your program 
        listings. Please.</li>
    <li>If you lose a disk, just tell us. Tell us right away. So long as we
        know about it before we discover that someone else has turned in the 
        same program, you won't be in any trouble. </li>
  </ul>
<li> Use any code from textbooks or the Web without our permission.
  <ul>
    <li>Let's be clear. There is no problem with looking up how to do 
        something, and copying two or three lines to, say, open a file, or 
        create a Frame. Even an entire method of, say, ten lines, should be 
        OK -- particularly if it's a general-purpose thing that might be used 
        in a lot of different programs.</li>
    <li>Finding code that does a significant part of your assignment, and 
        using it, particularly if you use it without attribution, is a 
        violation.      </li>
    <li>For the most part, it should be pretty obvious what is 
        assignment-specific and what is general-purpose. If in doubt, ask me. 
        </li>
  </ul>
<li> Have someone else write your program for you.
  <ul>
    <li> This one is pretty obvious. </li>
  </ul>
  If you think you may have accidentally broken a rule, come and talk to us 
about it. You will be much better off than if we discover it ourselves.  
</p>
<p>
  Students who violate this academic integrity policy will at least
  receive a grade of 0 for that assignment, but might face a harsher
  penalty depending on how egregious the violation was.
  A second violation will also result in
  a reduction of one full letter grade in the student's final course grade.
</p>
<p>
  In the case where one student copies the program of another student,
  both students are considered to have violated this policy.
  Here, copying includes not just programs that are verbatim copies,
  but also programs that are substantially similar and could not
  have been produced independently. Furthermore, all parties concerned
  will have their prior homework and programs checked. Violations of this
  policy may be reported to the University's Academic Conduct Committee
  for further action. Egregious cases of cheating will be written up
  as a "more serious" infraction. In this case, you will not be allowed
  to drop the course. Also, a "more serious" infraction would appear as
  a permanent part of your student record and would be seen by potential
  employers when they ask for an official copy of your transcript.
</p>
<p>
  The UMBC Undergraduate Student Academic Conduct Policy is available at:
  <a href="http://www.umbc.edu/undergrad_ed/ai/documents/ACC2011.pdf">
  http://www.umbc.edu/undergrad_ed/ai/documents/ACC2011.pdf</a>
</p>


<!--#include virtual="../footer.shtml"-->