Indiana University
Computer Science Department

A112 -- Programming Concepts

Fall 1997 -- Second eight weeks

Final Grades List

Notes

11/19: assignment 4 due date, syllabus, and grading scheme changed.

11/18 5:30pm:

Miracle 1.2, a new version, has just been installed. It fixes the problem of complaints of an undeclared variable when you have edited the variable's declaration.
Whenever a new version of Miracle is installed the version number (e.g. 1.2) will change and the previous version will be available as "old/miracle.html" instead of "miracle.html".
The link to module4 has also been fixed.

General information

Instructor: Christopher Haynes (Chris), phone 855-3376, office LH230F, email chaynes@indiana.edu
Associate Instructor: Horea Abrudan (Horea), email habrudan@indiana.edu
Credit Hours: 1.5
Lecture: Section 1131 meets Monday and Wednesday from 4:00P to 4:50P in LH102
Laboratory: Switching labs: If you need to make up a lab, or you need extra laboratory time, you may attend a laboratory session other than the one you registered for. However, students who have registered for a laboratory get priority if there are not enough computers for everyone.
Office Hours
Class Web Site: www.cs.indiana.edu/classes/a112
Catalog Description: P: A110, A111, or equivalent computing experience. Introduction to programming for users of computer systems. Emphasis on problem solving techniques. Lecture and laboratory. 8-week course.

Relation to other courses

This course is a simple introduction to programming at roughly the level of the old A107 course. Students are assumed to have some experience with computers, equivalent to that of A110, A111, any comparable computer literacy course, or equivalent extra-curricular experience. The course A201 offers a somewhat more challenging introduction programming and is part of the minor in information technology, but but is still not as challenging as C211. The latter course serves as an introduction to a computer science major or minor. Though A201 does not assume prior programming experience, A112 provides a gentle introduction to A201. Ask the instructor if you are in doubt about whether you belong in this course.

Materials and Resources

Several double-sided, high density (DS HD) 3.5" disks. Bring them to laboratory sessions.

A network ID and password. If you do not have a Network ID, you can create one during the first lab session if you know your Student ID Number and your Registration PIN. Bring them to laboratory sessions. Use http://accounts.ucs.indiana.edu to create a student locker account and, if you are using a Windows system, an NT domain account. Assistance in this will be available in the first lab session if necessary, but create these accounts in advance if possible.

Preliminary text material, written by Sharon Heimansohn and Sue Menzel, is available at the White Rabbit copy shop on Indiana between 4th and 5th. This is part of the IU Multi-campus Modular Computing Curriculum, or MMCC, curriculum and is also available on the web at http://www.cs.indiana.edu/hyplan/menzel/mmccc/modulen, where n=1,2,3, and 4. Only the first four modules are available at this time. Modules 5 and 6 will be available before they are needed.

Syllabus

The approximate schedule is one module per week:

Date	Read	Topic and any related links
10/27	Module 1	Command sequencing, with Shakey the robot
11/3	Module 2	Functions, with advanced Shakey the robot
11/10	Module 3	Variables and input/output, with Miracle! PDE
11/17	Module 4	Conditionals, pseudo code example
12/1	Module 5	Loops, quiz 2
12/8	Module 6	Functions, Miracle summary, Christmas tree example

Laboratory assignments:

Due Date	Assignment
10/31	Module 1 Exercise 6
11/7	Module 2 Exercises 3 and 4
11/14	Assignment 3
11/25	Assignment 4
12/8	Assignment 5: Module 5 exercises 3 and 5, note
12/15	Assignment 6 (no late submissions accepted)

Tips

The on-line text materials require a frame-capable browser. The Miracle PDE requires a JavaScript enabled-browser, and Shakey requires a browser that is also Java-enabled. The university Netscape Navigator 3.0 installations should work on Mac and Windows systems. At home you may have to enable JavaScript and Java in your browser.

It is not possible to edit Shakey programs. If you make a mistake, start over (not unreasonable for the short programs we do). To save a Shakey program, highlight the program text, copy it to the system clip board, past it into a text editor window, and print it using the text editor after adding identification and any required crediting information at the top.

Laboratory assignments will be posted in the syllabus section above. If you are able to do the assignments on your own, you do not need to attend laboratory sessions. However, if you do not attend laboratory sessions, do not expect extensive help from your instructor or AI at other times. Also, we start slowly because some students have much more difficulty than others with the initial concepts, but the material becomes more challenging as the course proceeds. If you find the first few weeks easily, do not assume you can neglect this course because it will all be easy!

You may obtain help from others on laboratory assignments (if you give credit, as noted below). In fact, you are strongly encouraged to do so. However, do not become overly dependent on such help: make your best effort to learn programming skills. Help will not be available on quizzes or exams, and the project must be substantially independent work (possibly with one partner).

Please do not hesitate to come to our office hours for help. Bring as much information as you can pertaining to your difficulty. If you have been working on a program that does not work, bring a printed copy of the program if at all possible.

Develop programs in stages. Start with a program that only does a small part of the assignment, but work. Add more functionality a little at a time and check that the program still works at each stage.

Grading

The following is a tentative guide for evaluation, with approximate percentage contributions to the final grade.

Class period quizzes (may be unannounced): 10%. There are no quiz makeups. The lowest quiz grade will be dropped. If more than one quiz is missed, documentation of illness or other serious circumstance is required for absence to be excused. Expect a quiz on Shakey programming on November 10th.
Graded laboratory exercises: 45%.
Final exam, 2:45P-4:45P, F December 19 in LH102: 45%. Sample questions.

The final and quizzes are open-book and open-notes, but no help from friends. You may obtain help from others on your laboratory exercises, but you must credit with a comment at the beginning of your submission anyone who has helped you, and independently submit your work. Crediting comments should briefly indicate the nature and extent of the help received. Projects may be the joint work of two partners, though somewhat more will be expected of group projects.

Assignments and projects may be turned in during laboratory sessions or they may be deposited in the assignment box below the faculty mailboxes in the hall outside LH215. Be sure your name, laboratory section number, AI name, and course number are clearly displayed at the top of your submission.

There is a penalty of 10% per business day for late project or laboratory assignment submission. Submissions are not accepted after 5pm on the third business day after the due date.

The most important factor in grading programs in assignments and exams will be correctness (whether the program works as specified), but style is also a factor. Good programming style makes programs easy to understand. This includes logical organization, appropriate use of comments (especially when the code is not very self-explanatory), and good indentation. Some credit will be taken off on quizes and exams for improper syntax: bring your notes to class to remind you of correct syntax. Little credit will be given for assignments with syntax errors, since you have the assistance of the system in generating correct syntax and locating incorrect syntax.

Administrivia

Incompletes: An incomplete (I) final grade will be given only by prior arrangement in exceptional circumstances conforming to departmental policy in which the bulk of course work has been completed in passing fashion.

Possibly Important Dates

F November 7-- Last day to Pass/Fail the course.
M November 24-- Last day to drop the course on your own.
M December 8-- Last day to drop the course with a Dean's approval.

Final makeup: Makeup final exams will be given only with documentation of sufficiently serious circumstances. Makeup exams may be oral. They must also be pre-arranged with the instructor if at all possible.

Academic integrity: The standard penalty for any form of academic dishonesty in this course is failure in the course. Providing or receiving help during exams or laboratory tests, or submitting the work of another as your own, both constitute academic dishonesty. There are no "small" offenses. The Computer Science Department statement on academic integrity provides further information.

Course Evaluation

Before the end of the course, you are strongly encouraged to complete the electronic course evaluation form for A112. You will need a password which is emailed to you at username@indiana.edu. Email cseval@cs.indiana.edu if you have not received this email or need other assistance with the course evaluation system.

Chris Haynes / chaynes@indiana.edu

Indiana University Computer Science Department