Welcome to online CS290 Web Development!
I'm Luyao Zhang. You probably already know me from CS162. I will be your instructor for this course. We also have an experienced and professional TA team working with me to support your study. We will do our best to provide you an informative and encouraging course with a great learning experience. If you have any suggestions on this course, you're welcome to contact me anytime.
NOTE: Some links on this page may only be accessible to registered students.
There are no special tools required in this course. You can use your favorite code editor for the assignment in this course. Some of the favorite code editors voted by previous students are Sublime Text, Atom and Visual Studio. You can develop your code locally and make it work on the flip for us to grade.
Each week's module will be posted ahead of time (on Thursday or Friday) for you to get started early. All the contents including the learning goals and requirements, reading materials and lecture videos are put into one session and you will explore them by topics.
Each week you will have one or two graded assignment /activity that related to the skills covered in that week's contents and will due on Sunday night. You will learn most from writing the code on your own. The more you practice, the better you learn.
You will do an individual project which is building a simple website from week 5 to week 6 using the skills you learn in this course and you have a lot of freedom to determine the theme of the website.
There is a proctored final exam at the end of the term. The exam will be open from Monday to Thursday of week 11 for normal term and week 8 for the summer term. Please reserve your proctor as early as possible to make sure you can get the time you want.
Before starting work in this class students should know the fundamentals of object-oriented programming. The following is a list of topic that you should be very comfortable with:
- Basic data types
- This list (Links to an external site.) of data types should be familiar or at least understandable after reading the type description.
- Common object types
- You should know what a string is. You should know if there is a difference between a string and an array. You should know the difference between a string in C and a string object in C++
- Complex data types
- You should know what an array is, what a struct is and what, if any, differences there are between them.
- Flow control primitives
- You must be very comfortable with for, while, if/else, switch and do/while. You should know how they work, you should know what
iis equal to at the completion of a loop if the condition says,
for(i=0, i<5, i++)is it 5 or is it 6?
- No matter where I declare
int fooin your code, you should be able to figure out if any other arbitrary spot in your code can access that variable. You should know what public and private functions are and what happens (and what it means) when variables go out of scope.
- Problem solving
- If a language does not provide you a tool to do something, but you need that tool to make progress, you should be comfortable making it yourself. You should be comfortable making helper functions, even when the requirements don't call for it.
- Organization and documentation
- You should know that all of your source code probably does not belong in a single file and that every public function should have comments.
- Things not on this list
- This is not a comprehensive list, but it is a good start. If you don't know any of these topics, consider reviewing them before the class begins.
Code quality will be discussed on a section by section basis. However, the general rule is that all code should by syntactically valid, consistently formatted in a readable way and produce zero errors, warnings or notices unless OKed before submission.
In this course, we follow the Google style guide for the HTML/CSS/JS code:
7 weeks will be very short for the web development since we have so many things to cover. As the instructor of this course, I wish you could keep up with your coursework and finish the assignments on time. More importantly, be honest to yourself. No cheating anytime.
Please go over all the contents in the "Start Here" module. Read the course policy carefully. Finish the course policy quiz and get full points to unlock week one module. There are some useful links under the resources module. Please check them out as well.
Meet the instructor:
Download the syllabus here: syllabus.pdf
Course Name: Web Development
Course Number: CS 290-400
Terms Offered: Every Term
Prerequisites: CS 162 or CS 165
Luyao Zhang, Instructor
- Email: email@example.com
This course is divided into three main sections which are largely addressed sequentially:
- Layout and Styling
- The first portion of the class focus on the static layout and styling of a web page (HTML/CSS). For some, this may be a review if you have done web publishing in the past. There is quite a bit of information to take in here but the problems to solve are not that intricate.
- Client Side Interaction
- Server Side Interaction
- In this portion of the class, we look at using a very simple database to store data between website visits. The technologies we will be using this term are Node.JS and MySQL. In addition, we look at how we can track a user and data from page to page which is a critical first step in designing more complex systems like shopping carts for an online shopping website.
You can see the assignment due dates on Canvas directly. You can also download it here: schedule.pdf
Topics by Weeks
Web Overview and Intro to Tools
HyperText Markup Language and Cascading Style Sheets
HW1 Node.js and Git, Course policies quiz
Activity1 JS Environment, Activity2 JS Functions, Activity3 JS Objects
JS Functions and Objects
Activity4 Fixing Closure Loop, HW3 Higher-Order Functions and Objects
HW4 DOM and Events
Activity5 Ajax Interactions, Project Proposal
Intro to Node.js
Sessions and HTTP
HW5 GET and POST checker
Activity6 Practice, Project
HW6 Database interactions and UI
Optional: Jon Duckett's "HTML and CSS design and build websites", ISBN-13: 978-1118008188, ISBN-10: 1118008189
This course has three types of assignments:
- HW Assignment:
- You will have six assignments this term, each is given one week to finish (except the last one, you will have 14 days). You will write a website or make some functions working using required techniques to meet the constraints. The assignments will be graded on how well they meet the requirements.
- The activities are graded as pass/fail (10/0) based on efforts. You need to show that you did the required practice and tried your best to make the code working. Generally if 60%+ of the activity is correct you will get a PASS otherwise it will be a fail. For example, if the activity has two requirements and you don't do one of them you would only have 50% of the activity completed so would receive a 0.
- This is a research-based project. You need to build a website based on the knowledge you learn in this course to meet some requirements.
This course has one proctored exam -- the final exam. You can find out more about proctoring at the Ecampus page on exam proctoring.
The final exam window will run from the Monday at the start of finals week through Thursday of finals week. If you are unable to take the exam in that window, you must make arrangements prior to the end of the 2nd week of classes. Beyond this deadline, only emergency situations will be considered for alternate testing times.
Where possible, I suggest using an in-person proctor. Should an issue arise, it is historically a lot easier to get it resolved at a testing center than with other online proctoring service. If you do use and an issue does arise, please document the situation as thoroughly as possible and forward that to the instructor as soon as possible.
|Grade letter||Percentage floor|
The final grade will be computed using a weighted average according to the table above and the weighting below.
In general, assignments are not graded such that each piece is worth some fixed amount of credit. If 40% of the program is non-functional, that generally indicates that there is some important concept that has been missed.
- Activities/Exercise - 25%
- Homework Assignments - 50%
- Project - 10%
- Final Exam - 15%
You should treat me as a client. I will give you a set of requirements. Requirements can be interpreted differently, this is unavoidable. You have to meet my interpretation of the requirements to get an A. If you have any doubt about what a requirement means, you should ask me to clarify.
"Accommodations are collaborative efforts between students, faculty and Disability Access Services (DAS). Students with accommodations approved by DAS are responsible for contacting the faculty member in charge of the course prior to or during the first week of the term to discuss accommodations. Students who believe they are eligible for accommodations but who have not yet obtained approval through DAS should contact DAS immediately at 541-737-4098."
Students with documented disabilities who may need accommodations, who have any emergency medical information the instructor should be aware of, or who need special arrangements in the event of an evacuation, should make an appointment with the instructor as early as possible, and no later than the first week of the term. Class materials will be made available in an accessible format upon request.
If you have a really tough situation that might affect your progress a lot (illness, job duties, family emergency...), you should contact the instructor immediately. Don't wait until the due date or even past the due date to explain your personal situations and ask for extensions. If you are not sure whether to ask for it, better do it.
Requests for extensions are considered on a case by case basis. Non-emergency requests must be submitted via email at least 72 hours before the due time. (Not having enough time to get the assignment done does not, by itself constitute an emergency, sorry!). If you don't know if you will need an extension but might, you should ask for one.
|Time elapsed past due date||Maximum Point Percentage Possible (if no extension is granted)|
|T < 24 hours||90|
|T < 48 hours||80|
|T < 1 week||70|
You have 3 bonus days that you can apply to any activities or assignments (except the final assignment). You can use it all at once for one assignment (if you are late for 3 days), or split it and use one day each for three assignments (no "half" day).
How to apply the bonus day: leave a comment on Canvas under that assignment submission, saying that you would like to apply x bonus days for this late submission, and you have y bonus days left after that. When TAs are applying the late penalty, they will look at your submission time and your comments. If you don't leave a comment there, TAs will directly apply the late penalty.
There is extra credit in some of the assignments. Try to get them when possible. At the end of the term, I will give extra credit (0.5 to 2 maximum points) to those who are active on Piazza answering questions and sharing notes with others.
You will not get in trouble for sharing code with your classmates in order to solve problems. The communication guide actually mandates that you share portions of your code if you want to ask a good question. If you are worried that you are posting too much code, mark it private and ask the instructor to review it. Note that this is a more permissive policy than the standard policy for the program.
You will get a great deal of trouble if you copy code without citing it. See the policy on plagiarism. Code from lectures is not your own, code from StackOverflow is not your own, code from the Mozilla documentation is not your own. If it is not your code, you must cite it. If you cite it, you must provide documentation in very great detail of what it is doing so that I know you understand the code you are using.
In this course, we follow the Google style guide for the HTML/CSS/JS code:
Luyao Zhang, Instructor
- Email: firstname.lastname@example.org
- Office hours by appointment
- Always use your OSU email to contact me. The Canvas mailbox doesn't work very well.
- When you send me an email, you must include the tag "CS 290 Summer 2019" in your email subject.
You should expect a response to emails within 48 hours. Emails sent over the weekend sometimes take longer to respond to.
Post all course-related questions on the Piazza board so the whole class may benefit from our conversation. Please sign up yourself on Piazza sign up. You can use the course Slack channel to ask questions as well.
For grading questions and regrading request, please contact the TA who graded your assignment by posting privately on Piazza. You can include key words like "regrading Assignment # @ TA's name" in the subject to highlight it. Don't post re-grading request on Slack. You should expect your grade to be posted after one week of the due time. If you submit the assignment late, it may take longer for your grade to be released.
We will post some resources that might be used as supplementing materials in the resources page and we will update this page throughout the term.
- Code Sharing Session:
After each assignment is graded, we will select some good code examples and post them in the code sharing session for you to review.
- TA online office hours:
We will have several sessions available each week from week 1 to week 7. Office hour is the best time to get instant and detailed feedback on your code. Make good use of them and get most from it. If none of the time slots work for your schedule, let us know and we can make accommodations. For TAs' email address, office hour time and link, please check the "Instructor & TAs Communication Policy and Information" in the Start Here module.
All of the course discussions will happen on Piazza. We are watching the forum every day. Sometimes, if the question is not about the assignment requirement, we will hold our answers for a while to involve more students in the discussion. You are always encouraged to post on Piazza and participate in the discussions. Students who make contributions to the discussions on Piazza will get extra credit at the end of the term. Please sign yourself on the Piazza forum.
From this term we will use Slack officially in this course as well. We will be watching the course Slack channel and answer your questions in a timely way. The workspace of this course on Slack is class-cs290-400-su19. For more information about Slack, please check Slack-How to in the start here module.
Physical copies exist if you prefer and can be ordered from Amazon. There will be required reading from this book along with programming exercises.
HTML/CSS is another component to this class. Currently the books on the subject are a bit of a mess. The transition to HTML5 is pretty much done but there is a delay between a technology being adopted and publishers actually getting books on the topic to market. In addition it is a less complex topic than many other programming languages. So I am not requiring any books on the subject, instead I will offer several online resources. If you really want a book, I would suggest Jon Duckett's "HTML and CSS design and build websites". It does not have great HTML5 coverage, but is very visual in its presentation of material which can be a big benefit.
Besides the textbooks listed here, we also have a resource page on Canvas: Useful links
There are many useful links organized in this page. I add links that students find to be useful and post on Piazza to this list every term. You should check this list for more resources.
Here is the reading list of the whole term if you want to read ahead:
The syllabus page shows a table-oriented view of the course schedule, and the basics of course grading. You can add any other comments, notes, or thoughts you have about the course structure, course policies or anything else.
To add some comments, click the "Edit" link at the top.