Syllabus - UMBC-CMSC104/General GitHub Wiki
Teacher: Michael Wilson
E-mail: [email protected]
Meeting time: Tuesday/Thursday: 5:30 PM - 6:45 PM
Office Hours: ITE 201A - Tuesday/Thursday 7:00 PM - 8:00 PM
This course is designed to provide a gentle introduction to problem solving and computer programming without previous programming experience. This includes:
- Elementary problem solving skills and algorithm development
- Programming environment usage
- Basic programming concepts (loops, control statements, functions, arrays)
- UNIX operating system fundamentals
- General computer science concepts
Note: This course does not meet any requirements for the computer science major. If you have already received credit for another class in a high level programming language, you will not receive credit for this course. This includes CMSC 201, CMSC 202, and sections of CMSC 291 that cover programming topics.
| Grades | Percentage |
|---|---|
| Classwork | 14% |
| Homework | 26% |
| Quizzes | 30% |
| Final Exam | 30% |
Problem Solving and Program Design in C, 6th Edition Jeri Hanly and Elliot Koffman, Addison Wesley, 2009.
ISBN: 0321535421
In addition to this book, there are a multiple of online references one can look at. My favorite is the C Reference on [http://www.cppreference.com/](CPP Reference).
Attendance will not be mandatory. You will be responsible for all the material covered in the class.
Classwork is to be turned in by the end of class. There are no makeups for classwork. If you're not finished, you should submit what you have. You can submit a finished version of your classwork for up to a 10% improvement by the next class period. You cannot take advantage of this policy if you did not turn in anything by the end of the class period, however.
Homework will be assigned throughout the semester. In addition to correctness (correct output), neatness will also count. That is, your code must be easy to read. Please refer to the coding standards for more information.
When you submit your homework and classwork, you are stating that the work was created by your own individual effort, or in the case of a group assignment, created solely by the effort of members of your group.
Receiving help from the Computer Science Help Center does not violate this academic integrity policy.
You may also receive help from other sources. However, this help must be limited to:
Discussions about the meaning of the assignment. Identifying syntax errors in your program. Identifying simple logic errors in your program. The following is a non-exhaustive list of actions that clearly violate this academic integrity policy:
Someone else is typing code in your program. You are cutting and pasting more than a single line of code (from a program that was not distributed by the instructor). You are looking at someone else's program while you are typing in your code. You receive someone else's program by email, hard copy, text message, instant message, ... You make your program available to another student in CMSC104 directly or indirectly by email, hard copy, text message, instant message, ... This policy recognizes that students can learn productively from many sources including from other students in the class. Thus, this policy allows small amounts of help but prohibits outright copying. Although, this leaves a gray area between "small amounts of help" and "outright copying", it is better that we live with some ambiguity than to have a clear-cut policy that deprives the students of productive learning opportunities. Students who have doubts about the propriety of an activity should consult the instructor.
Students who violate this academic integrity policy once will receive a loss of one letter grade in the course. A second occurrence will result in class failure. 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.
For a more complete description of academic dishonesty, refer to the UMBC Undergraduate Student Academic Conduct Policy.