forked from SnistAheads/material
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathcourse_info.html
More file actions
181 lines (157 loc) · 6.82 KB
/
course_info.html
File metadata and controls
181 lines (157 loc) · 6.82 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
<!DOCTYPE html>
<html>
<head>
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Dosis:700|Source+Sans+Pro:400,700">
<link rel="stylesheet" type="text/css" href="styles.css">
<link rel="icon" href="favicon.ico" type="image/x-icon" />
<title>CS 145 | Course Info</title>
</head>
<body>
<section>
<div class="header">
<h1>CS 145</h1>
<h2>Data Management and Data Systems</h2>
<h2>Fall 2018</h2>
</div>
<div class="links">
<table>
<tr>
<th width=50%><a href="index.html">Home</a></th>
<th><a href="course_info.html">Course Info</a></th>
</tr>
</table>
</div>
</section>
<section>
<div class="course-description">
<h3 class="subheader">Course Description</h3>
<b>Overview</b> This course covers:
<ul>
<li>
Database design and the use of databases in applications, with a short introduction to the internals of relational database
engines;
</li>
<li>
The relational model, relational algebra, and SQL;
</li>
<li>
Database design and relational design principles based on dependencies and normal forms;
</li>
<li>
Many additional key database topics from the design and application-building perspective, including indexes, views, transactions,
and integrity constraints;
</li>
<li>
MapReduce framework and key-value stores;
</li>
<li>
A hands-on programming project in SQL+Python -- a key part of the course -- where you will query, visualize and predict from
terabytes of data on <a href="https://cloud.google.com/bigquery/">BigQuery</a>, a popular cloud database part of Google
Cloud Platform.
</li>
</ul>
<p><b>Prerequisites</b> 103 and 107 (or equivalent)</p>
<b>Assessment</b> Projects: 35% (5 + 10 + 20), Midterm Exam: 25%, Final Exam: 40%.
<br>We will be offering extra credit for:
<ul>
<li>in-class and OH participation</li>
<li>high quality answers to fellow student questions in piazza</li>
</ul>
</div>
</section>
<section>
<div class="course-logistics">
<h3 class="subheader">Logistics and Policies</h3>
<p>
<b>Piazza</b> Join our <a href="https://piazza.com/stanford/fall2018/cs145">Piazza</a> to receive important
announcements and get answers to your questions.
</p>
<p>
<b>Homeworks</b> Homeworks are self-paced and do not affect your
course grade. However, they reflect the exam material, so it is in
your best interest to complete them promptly, for each lecture.
Aside from preparing you for the exam, they will assess and reinforce
your understanding of the material.
You can access the homeworks through <a href="http://www.newgradiance.com/services">Gradiance</a>
by creating an account (if you don't already have one) then signing
up for class token <b>E68759F1</b>. Once you have joined the class, navigate
to the Homeworks section on the left. <b>NOTE:</b> when we write "lab"
we indicate that you should do the corresponding lab found in the "Lab Projects" tab,
instead of the Homework tab.
</p>
<b>Exam Dates</b>
<ul>
<li>Midterm: in-class midterm on Nov 1st(Thurs)</li>
<li>
Final: Friday, Dec 14th from 3:30-6:30 p.m. (see <a href="https://registrar.stanford.edu/autumn-quarter-exams">university
final exam scheduling</a>)
</li>
</ul>
<p>
<b>Exam Notes Sheet</b> For the midterm, we allow
students 1 two-sided 8.5x11" piece of paper with typed or written
notes.
For the <i>final exam</i> we will allow students <b>two</b> notes sheets.
</p>
<p>
<b>Late Days</b> You are allowed a total of <b>three</b> late days
shared between all project deadlines. You do not lose any credit when
using a late day. If you run out of late days and submit after the
deadline, you receive a 0. (EDIT: this was increased from 2 to 3 due
to P2 submission difficulties. For more, see piazza post 879).
</p>
<p>
<b>Lectures</b> Lectures occur on Tues/Thurs 4:30-5:50 p.m. in NVIDIA Auditorium. NOTE that while attendance is not mandatory,
we will be giving out extra credit for students with insightful in-class participation.
</p>
<p>
<b>Lecture Videos</b> Lecture videos will be recorded and posted on <a href="https://canvas.stanford.edu/">Canvas</a>.
</p>
<b>Textbook</b> There is no required textbook, but for students who want additional resources, we recommend the following two:
<ul>
<li>Database Systems 2nd Edition by Garcia-Molina</li>
<li>First Course in Database Systems 3rd Edition by Ullman</li>
</ul>
<p>
<b>Accomodations</b> Students who may need an academic accommodation based on the impact of a disability must initiate
the request with the Office of Accessible Education (OAE) and notify us at least 7 days (ONE week) prior to the Midterm
and/or Final Exam.
</p>
<p>
<b>Contacting Course Staff</b> Please use Piazza for public questions. To privately reach the instructors
you can either make a private Piazza post or send an email to:
<br><a href = "mailto: cs145-aut1819-staff@lists.stanford.edu">cs145-aut1819-staff@lists.stanford.edu</a>
</p>
</div>
</section>
<section>
<div class="course-logistics">
<h3 class="subheader">Projects</h3>
<p>
<b>Group Size</b> The first two projects are individual only, but the third project you are allowed
to work in teams of two.
</p>
<p>
<b>Project Submissions</b>
You will submit your projects via Gradescope. Sign up for Gradescope
using your Stanford email address and student ID. The course code is
MJ3ZYR.
Each assignment will include specific instructions regarding what
files to submit.
</p>
<p>
<b>Regrade Policy</b>
If you think that we've made a grading mistake or that the work
you submitted should be regraded, submit a regrade request on
Gradescope within one week of receiving your grade. Be sure that you
prepare a short and convincing argument on Gradescope about why you
think your work was incorrectly graded – we reserve the right to
ignore your regrade request if you don't provide a justification.
If you submit a regrade request, we reserve the right to regrade your
entire assignment. This means that your overall score could go
down.
</p>
</div>
</section>
</body>
</html>