CMSC 101 / IS 101Y: Computational Thinking and Design
Building a semantic network
link to Blackboard site
Broad survey of computing topics and fields for new majors, along with the
academic and professional skills necessary to succeed in those fields.
Students will work
with a team to complete a semester design and implementation process.
After this course, students should be able to:
Discuss the characteristics and challenges of key areas of the computing disciplines.
Analyze and present data to support informed decision making.
Write basic programs using variables, conditional logic, and loops.
Demonstrate the skills necessary to succeed as a computing student and professional.
Work effectively in a team to solve a complex technological challenge.
The course schedule is posted here.
Direct link: http://www.csee.umbc.edu/courses/undergraduate/CMSC101/Fall2013/schedule.html
When and Where
CMSC 101-01 (lecture) / CMSC 101-03 (discussion) / IS 101Y-03 (lecture) / IS 101Y-05 (discussion)
- Course instructors: Dr. Marie desJardins and Dr. Susan Martin
- Lecture: Tuesday/Thursday 10-11:15, Sondheim 110
- Discussion: Friday 2-3, IT 229
Instructors and Course Staff
Dr. Marie desJardins
(mariedj < at > cs.umbc.edu)
Dr. Carolyn Seaman
(cseaman < at > umbc.edu) (Instructor of the TTh 1:00 section)
- ITE 337 (x53967)
- Office Hours: Wednesdays 2-3pm, Thursdays 3:30-4:30pm
Dr. Susan Martin (susan < at > umbc.edu)
- ITE 404B (x53937)
- Office Hours: Mon 12-2pm, Thu 2:30-4pm
ITE 452 (x52822)
Office Hours: Tue 11:30am-12:30pm, Thu 8:45-9:45am
All TF office hours will be held in ITE 470.
Dr. desJardins's section (yours!):
Dr. Seaman's section:
- Alec Pulianas (teaching fellow / CE major) -- apul1 < at >
- Office hours: Mon 2:30-3:30pm, Wed 11am-12pm
- Emily Scheerer (teaching fellow / CS major) -- semily1 < at >
- Office hours: Tue 5:30-6:30pm, Thu 11:30am-12:30pm
- Mark Cirincione (peer mentor / IS major) -- markcir1 < at > umbc.edu
- Gloria Diederich (peer mentor / math major, CS minor) -- gdieder1 < at > umbc.edu
- Catherine Liou (peer mentor / IS major) -- catherine.liou < at > umbc.edu
- John Swank (peer mentor / CS major) -- swank1 < at > umbc.edu
- Bhuvana Bellala (teaching fellow / CS major) -- bbella1 < at >
- Office hours: Thu 5:30-6:30pm, Fri 3-4pm
- Amanda Mancuso (teaching fellow / IS major) -- mancuso3 < at >
- Office hours: Mon 11am-12pm, Wed 10-11am
- Austin Cole (peer mentor / IS major) -- acole3 < at > umbc.edu
- Nicole Dawson (peer mentor / IS major) -- nicoled1 < at > umbc.edu
- Brandon Walsh (peer mentor / CS major) -- brando12 < at > umbc.edu
- Max Weinberg (peer mentor / CS major) -- maxwell1 < at > umbc.edu
- Computing for Ordinary Mortals, Robert St. Amant, Oxford, 2013.
- Getting Started with Processing, Casey Reas and Ben Fry, O'Reilly, 2010. ISBN 978-1-449-37980-3
- Making Your Mark (9/e), Lisa Fraser, LDF Publishing, Inc., 2009.
ISBN 987-0973529838 (will be provided to students)
Grades will be based on the following work, with
categories weighted as indicated. (Note: These
category weights were the consensus values as "voted"
by student teams on the first day of class.)
- Individual work - 30%
- Professional development assignments (five journal entries,
surveys, cover letter, and resume)
- Three programming assignments
- Team work - 35%
- Data analysis assignment
- Team project (deliverables: project design, prototype demo,
prototype evaluation, project poster, and project presentation)
- Group peer evaluation - 10%
- Tests and quizzes - 25%
- Quizzes (individual and team grades)
- Midterm exam
- Final exam
Note on Team Grades
Each team deliverable for the project will receive a grade,
but individual students' grades on the deliverables may vary
(i.e., be higher or lower than the deliverable grade), based on
individual contributions to that assignment, as assessed
through peer feedback and self-assessments.
The group peer evaluation grade will be based on your team
members' assessments of each member's contribution to the work
throughout the course of the semester (inside and outside of
class). We will perform several peer evaluations over the
course of the semester, so that you know where you stand on
this measure and have an opportunity to adjust your performance
before the final peer evaluation at the end of the semester.
Late/Missed Work Policy
Assignments are due by the beginning of class on the day listed.
Unless otherwise stated in the assignment itself, late assignments
will not be accepted. Extensions will be granted only
for documented, legitimate reasons (significant illness, death
in the family, athletic or business travel, religious observations)
and must be requested in
advance. Extensions after the fact will only be granted in
extraordinary circumstances, as outlined in the UMBC student
handbook (significant illness with a doctor's note, death
in the family with documentation).
Programming Assignment #1 must be completed on time and cannot
be submitted late. The one exception to the late policy stated
above is that Programming Assignments #2 and #3 may be submitted
late, with a 15% penalty for each 24 hours or fraction thereof.
For example, if you submit Programming Assignment #3 an hour
after class on the day it is due, your grade will receive
a 15% penalty. If you submit it exactly 48 hours late,
your grade will receive a 30% penalty. No credit will be given
for Programming Assignment #1 or #2 if they are submitted more
than one week after the due date.
Missed quizzes and exams can be made up only if arrangements are made
with the instructor in advance, and only if the instructor agrees that
missing the quiz or exam is unavoidable. Quizzes missed because of an
unforeseen emergency cannot be made up. Exams missed because of an
unforeseen emergency will be dealt with on a case-by-case basis.
Students with IEPs (accommodations for documented medical
situations) must discuss all extensions, extended-time
exams, and other accommodations in advance with the
instructor. In particular, exams to be taken with extended
time or in a different room than the usual classroom must
be explicitly scheduled in consultation with the instructor
at least one week in advance. Last-minute accommodations cannot
be granted; it is your responsibility to work in advance to make
the necessary arrangements.
This course adheres to the Provost's statement on academic integrity:
"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."
All individual assignments and exams in the course are expected to be your individual work. You may discuss assignments with anyone, but at no time should you copy someone else's work or allow someone to copy yours. Neither should you copy work or text from published or web sources without proper citation.
Team assignments are expected to be the work of all team members, where interactions outside the team follow guidelines for individual work (i.e., group assignments must be the work of the team, and any help from sources other than team members must be documented). If you are ever in doubt about what constitutes appropriate collaboration, consult with a course staff member.