| Ada Documents and Programs |
| Assembly Language Documents and Programs |
| 2_sample.txt 2_sample.txt |
| 3_sample.txt 3_sample.txt |
| calc.txt calc.txt |
| factorial.txt factorial.txt |
| COBOL Documents and Programs |
| DATET.COB.txt |
| DATEP.COB.txt |
| DATEW.COB.txt |
| Fortran Documents and Programs |
| alscal.f90.txt |
| bayes_beta.f90.txt |
| Modules and Module Procedures |
| PL/I Documents and Programs |
| IBM Enterprise PL/I - internet link |
| PLI_programming_language.htm |
| RHolt.fatal_disease.article |
| Languages Related To PLI |
| Grading | ||
| In class degree of engagement
(e.g., preparedness, participation, active listening) |
10% | |
| Quiz (1 at 10%) | 10% | |
| Java Notebook | 15% | |
| Team Reports on Assigned Papers (3 at 15% each) | 45% | |
| Final Exam | 20% | |
Assessment
Evaluation of each assignment will use the specific criteria discussed in this syllabus and discussed in class. The following rubric will be used to evaluate the team reports, quiz, and exam answers:
An Outstanding Report/Paper (grade of A) is a well organized paper that can be understood without explanation from the author, is well-written, clearly conceptualized, addresses all stated criteria, reflects a great deal of time investment in the assignment, is carefully crafted, and adds at least one additional criteria. Be sure to identify in your report the added item, lest I should miss it.
A Good Report/Paper (grade of B) is well organized, can be understood without explanation from the author, is well written and clearly conceptualized, and addresses all the stated criteria.
A Satisfactory Report/Paper (grade of C) is organized but not especially well organized, can be understood only with some effort or explanation from the author, addresses most or all the stated criteria. If your assignment merely meets the requirements you will receive a C.
Poor Report/Paper (grade of D or below) is unorganized, poorly written/conceptualized, is missing criteria.
In order to encourage the development of good communication skills which are essential in the business environment, sloppy or incorrect English in any assignment will affect your grade.
Letter grades are assigned based on the percentage of available points obtained by a student. 100% to 90% guarantees an A, 89% to 80% guarantees a B, and so on. The instructor reserves the option of relaxing the cut-offs for a letter grade in special circumstances. Plus and minus grades will be used for this course.
Course Requirements
Team Reports
You are expected to participate in three reports over the course of the semester. One of these should be in a team of two, one of these in a team of 2 or 3, and one of these in a team of 3. This guideline may be changed in class depending on the number of students enrolled.
You can select from one of the prepared project descriptions or create your own project. More details on the team reports are provided in class and in the Trem Reports Resources table on this web page.
Java Notebook: What to do when reading the text book
Many students are not familiar with all the programming languages sited in the text book - such as Snobol, Ada, Euclid, APL, C, C++, Pascal, and even if familiar, may not be able to understand the particular nuance being illustrated. However, all students taking this course are familiar with Java.
Therefore, when reading of a lnaguage feature, determine the Java "story" with regard to that feature. For example, Section 3.2.3 (page 114) is about garbage collection. Your notes for that day would include an item such as: Garbage Collection: Java implements it; automatically runs as needed to reclaim space in the heap, you can call it with System.gc().> and so on about what you know about Java garbage collection.
You may modify you notebook before, during, and after each class session.
Turn in your notebook as indicated on the syllabus.
The structure of each class session and in-class participation
We will form in-class discussion groups. The groups will be assigned by the instructor and will remain in place for two weeks.
The group will first process the textbook review questions (TRQ) that were assigned and prepare to provide answers when called upon. Textbook review questions (TRQ) are fact-based questions and are based on the reading assignment. These questions will be reviewed in class as they form the basis for follow-on discussions.
The small groups will then process the other textbook assignments in the same manner.
These in-class discussions of the textbook review questions (TRQ) and the other textbook exercises (i.e., TE) require your preparation. Before class you should prepare an answer to each question assigned. Your preparation may consist of answering the question completely or providing an answer outline. As part of your answer, list any parts you do not understand, and any extensions (in the form of: "Therefore...) that occur to you. In either case, references textbook pages are appropriate and useful. These answers will not be collected but are your basis for in-class discussion, study guide and reference.
We will typically have a theme, problem, or issue that the reading material addresses. We will apply what we have read to the issue, theme, or problem.
Attendance Policy
Your attendance at all class sessions is crucial. The class will be driven by your participation, thoughtful reflection, and experience, not solely by the instructor's expertise. Attend ALL class sessions, complete the weekly readings and prepare the assignments. You will have one (sorry, just one) personal day for absence, should you need it. For each additional class period missed, your course grade will be reduced by one letter grade (e.g., from A to B).
Academic Integrity Policy
The assignments that you create are your way of telling the instructor about your mastery of this course. All of the assignments must represent a unique and special effort on your part. All assignments are individual in nature unless otherwise noted. Any cases involving suspected academic dishonesty result in a grade of zero for the assignment. See Student Responsibilities - Academic Honesty at http://www.unca.edu/catalog/academicregs.html#grading.
Information
You should budget at least 6 hours outside of class per week for assignments, study and reading for this course.
Return to the UNCA Computer Science home page