CMSC122, Section 0101, Pedram's Section (Fall 2022)
Introduction to Computer Programming via the Web
This class provides an introduction to computer programming in the context of developing full featured dynamic web sites.
It uses a problem solving approach to teach basics of program design and implementation using
and limits of web-based information sources for use in research. Intended to help relate a
student’s major to these emerging technologies.
Course Topics (Subject to Change)
- History of the Web/Internet
- Internet and Society
- Research-quality Web Searching
- Web Page Evaluation
- Problem solving skills in procedural programming languages
- Basics of usability and art theory in web page design
- Basics of e-commerce and tool integration in the web
||Semester Exams (2), (15% and 15%)
Once we have graded any class material (e.g., exams, projects, etc.)
we will post an announcement and a deadline by which you must submit
any regrade request (if necessary). It is your responsibility
to submit regrade requests by the specified deadline; no regrade
requests will be processed afterwards.
- Deadlines -
All projects are due at 11:30 pm and you have until 11:30 pm of
the next day to submit your project with a 10%
penalty. Notice that after the late period, you will not receive
any points for your project. For example,
if a project is due on Wednesday at 11:30 pm, you have until Thursday
at 11:30 pm to submit a late project with a 10% penalty. Any submission
after Thursday 11:30 pm will receive 0 pts.
- Submit Server -
You need to use the
submit server for class
assignments (projects and paper). We will not accept assignments submitted otherwise (e.g.,
- Which Project Gets Graded -
The last submission provided. If you have both an on-time and late submission,
only the late submission will be graded.
- Closed Projects -
All programming assignments in this course are to be written
individually (unless explicitly indicated otherwise). Cooperation
between students is a violation of the Code of Academic Integrity.
Regarding Posting of Project Implementations
Do not post your assignments' implementation online (e.g.,
GitHub, PasteBin) where they can be seen by others. Making your
code accessible to others can lead to academic integrity violations.
Posting of your projects in a private repository where only selected
people (e.g., potential employers) can see them is OK. Just make
sure it is not a public site.
Even if the course is over, do not make your code publicly available
- We constantly monitor online sources.
TA Room/Office Hours
Office hours get extremely busy the day before a project deadline.
Therefore do not wait to start your projects. Regarding office
hours and the TA Room:
Once you have been helped by a TA please leave the TA room. We
have a large number of students in all of our classes and the TA
room is really crowded.
If there is a line of students waiting, a TA should spent at most
10 minutes with a student. Please remind TAs about this rule.
When you meet with a TA, please be ready to ask specific question(s). Just telling the TA that your code does not work is not a specific question. Remember, that it is ultimately YOUR responsibilty to debug your code. The TA will try to point you in the correct direction, but we can not guarantee that your issue will be fully resolved after meeting with a TA.
If you have a basic question, for example if you need clarification on the project requirement, just post in Piazza. Please allow us to reserve office hour time for students that have specific questions about the code they have written.
You need to keep backups of your projects as you develop them.
No extensions will be granted because you accidentally erased
your project. Feel free to use the submit server as a backup
tool by submitting often. You can also use tools like git, etc.
Do not post code in any online system that is accessible to
others (e.g., GitHub).
We will be using (Piazza) for class
communication. You will not be able to register to Piazza yourself.
Your instructor will register you using the e-mail you have in the school
See the section titled "Attendance and Missed Assignments"
available at Course Related Policies.
See the section titled "Accessibility" available at
Note that academic dishonesty includes not only cheating, fabrication,
and plagiarism, but also includes helping other students commit acts of
academic dishonesty by allowing them to obtain copies of your work. In
short, all submitted work must be your own. Cases of academic dishonesty
will be pursued to the fullest extent possible as stipulated by the
Office of Student Conduct.
The CS Department takes academic integrity seriously. Information on how
the CS Department views and handle academic integrity matters can be
found at Academic Integrity.
The following are examples of academic integrity violations:
Hardcoding of results in a project assignment. Hardcoding
refers to attempting to make a program appear as if it works
correctly (e.g., printing expected results for a test).
Using any code available on the internet/web or any other
source. For example, using code from Sourceforge, Stack Overflow, etc..
Hiring any online service to complete an assignment for you. For example, using Chegg to complete an assignment is not allowed.
Sharing your code or your student tests with any student.
Using online forums (other than Piazza) in order to ask for
help regarding our assignments.
Additional information can be found in the sections titled
"Academic Integrity" and "Student Conduct" available at
Course Related Policies.
All course materials are copyright UMCP, Department of Computer Science
© 2022. All rights reserved. Students are permitted to use course
materials for their own personal use only. Course materials may not be
distributed publicly or provided to others (excepting other students in
the course), in any way or format.