General Information

Instructor:

Geoffrey Towell
Park Science Building
526-5064
gtowell at brynmawr dot edu
http://cs.brynmawr.edu/~gtowell

Lecture Hours: Monday / Thursday 8:10-9:30
Room: Park 180
Lab: Thursday 9:40-11:00
Office Hours: 4-6pm Wednesday and Thursday
Office hours will be by zoom. Meeting code: 232 840 6920. I have provided the password in email


Text

Introduction to Data Technologies by Paul Murrell

Available as PDF at https://www.stat.auckland.ac.nz/~paul/ItDT/itdt-2019-03-06.pdf
Also a good book, I recommend it if you like to look things up in books and read well organized explanations (I would like it even better if it had more examples)
 
Beginning PHP and MySQL by W. Jason Gilmore

Course Description:

Introduction to the creation of interactive and dynamic web content. Students study the technologies and concepts for adding interactive content to web pages (client-side programming), and receive, store, read, and supply information clients (server-side programming). In this context, thcourse will cover client-side concepts like HTML, CSS, and Javascript. On the server side, we will cover server-side programming languages, data storage, and databases. Finally, we will discuss design and development of apps (Android/iOS) as an alternative to browser-based systems.

Video Overview
Course Intro Errata: early on I say my email is gtowell@brynmawr.com it is, of course, gtowell@brynmawr.edu


Important Dates


Assignments

Assignments will be specified in terms of IO behavior. That said, we will be discussing specific programming approaches and languages in class. The expectation is that you will use those things discussed in class to accomplish the assignments. If you wish to go another direction and do somethinhg totally different I will likely approve your request. But do ask first. .

As a general rule I will not closely grade program code. I will, however, read it and expect to be able to understand what I read. Therefore, the code should be commented to the level that an independent, intelligent, and motivated person can review and understand what was done and -- potentially -- extend or fix the program. Comments should be written at the level such that, if you picked up your own code 2 years from now you could understand what you did and how the program works.

There will be several small-ish introductory assignments (approximately 1 week) that are intended to get everyone on a common footing with respect to the topic area. After that, the class will be broken into groups each of whom may get a different assignment. For each of the group assignments I will give a some suggestions; you will choose from among these suggestions. You may also suggest something of your own. Each person will present to the class on a group project once. There will be 3 of these group assignments.


Labs

Labs are intended to take about 90 minutes. If you cannot complete the lab in 90 minutes, stop; turn in what you have completed and say that you ran out of time. You might want to finish on your own, but this is not required.

Additional Readings

If I assign (or suggest) additional readings, they will be listed here. At the very least, some stuff about PHP will be here

Lectures

Course Policies

Communication

Participation includes asking questions, contributing answers, proposing ideas, and providing constructive comments.

As you will discover, I am a proponent of two-way communication and I welcome feedback during the semester about the course. I am available to answer questions, listen to concerns, and talk about any course-related topic (or otherwise!). Come to office hours (via zoom. While the weather cooperates we can also meet outside in the Park courtyard). (In the Fall of 2020 office hours will be virtual and through zoom.

Please stay in touch with me, particularly if you feel stuck on a topic or assignment and can't figure out how to proceed. Often a quick e-mail, or face-to-face (via zoom in fall 2020) conference can reveal solutions to problems and generate renewed creative and scholarly energy. It is essential that you begin assignments early.

Grading


At the end of the semester, final grades will be calculated as a weighted average of all grades according to the following weights. (These weights are subject to change, without notice.)

PercentTopic
24%3 1-week(ish) solo assignments at the start of the course
60%3 3 week(ish) small group assignments
4%1 presentation on a group project
8%2 3-5 minute in class presentations topics I assign
4%Labs and Class Participation

Incomplete grades will be given only for verifiable medical illness or other such dire circumstances.

ALL work submitted for grading should be entirely YOUR OWN (or that of a group if you are working in a group). Sharing of programs, code snippets, etc. is not permitted under ANY circumstances.

Submission, Late Policy, and Making Up Past Work


No assignment will be accepted after it is past due. However, you will have 2 24 hour late pass. This late pass can be used by simply sending me email -- before the due date. The late passes cannot be used to delay in-class presentation.

No past work can be "made up" after it is due.

No regrade requests will be entertained one week after the graded work is returned in class.

Exams

If you have any questions as to what types of collaborations are allowed, please feel free to ask.


Links


Learning Accommodations

Students requesting accommodations in this course because of the impact of disability are encouraged to meet with me privately early in the semester with a verification letter. Students not yet approved to receive accommodations should also contact Deb Alder, Coordinator of Accessibility Services, at 610-526-7351 in Guild Hall, as soon as possible, to verify their eligibility for reasonable accommodations. Early contact will help avoid unnecessary inconvenience and delays.

This class may be recorded.


Created on August 2020. Subject to constant revision.