├── README.md
├── hw1
├── .gitignore
├── README.md
├── python
│ ├── .gitignore
│ ├── LICENSE.txt
│ ├── NOTICE.txt
│ ├── baby1994.html
│ ├── babyname_parser.py
│ └── run.py
└── typescript
│ ├── .gitignore
│ ├── form.html
│ ├── form.ts
│ ├── images
│ ├── fail_popup.png
│ └── plain.png
│ └── tsconfig.json
├── hw2
├── .gitignore
├── README.md
└── skeleton
│ ├── .editorconfig
│ ├── .gitignore
│ ├── README.md
│ ├── angular.json
│ ├── e2e
│ ├── protractor.conf.js
│ ├── src
│ │ ├── app.e2e-spec.ts
│ │ └── app.po.ts
│ └── tsconfig.e2e.json
│ ├── package-lock.json
│ ├── package.json
│ ├── src
│ ├── app
│ │ ├── app.component.css
│ │ ├── app.component.html
│ │ ├── app.component.spec.ts
│ │ ├── app.component.ts
│ │ ├── app.module.ts
│ │ └── in-memory-data.service.ts
│ ├── assets
│ │ └── .gitkeep
│ ├── browserslist
│ ├── environments
│ │ ├── environment.prod.ts
│ │ └── environment.ts
│ ├── favicon.ico
│ ├── index.html
│ ├── karma.conf.js
│ ├── main.ts
│ ├── polyfills.ts
│ ├── styles.css
│ ├── test.ts
│ ├── tsconfig.app.json
│ ├── tsconfig.spec.json
│ └── tslint.json
│ ├── tsconfig.json
│ └── tslint.json
├── hw3
├── .gitignore
├── LICENSE
├── README.md
├── arc.pdf
└── skeleton
│ ├── blog
│ ├── __init__.py
│ ├── admin.py
│ ├── apps.py
│ ├── migrations
│ │ └── __init__.py
│ ├── models.py
│ ├── tests.py
│ ├── urls.py
│ └── views.py
│ ├── manage.py
│ └── myblog
│ ├── __init__.py
│ ├── settings.py
│ ├── urls.py
│ └── wsgi.py
└── project
├── README.md
├── design-and-planning-examples
└── Design_and_Planning_example.pdf
├── design-and-planning.md
├── postersession.md
├── project-requirements-and-specification.md
├── projectproposal.md
├── proposal-examples
├── Team1 - BusyWrite.pdf
└── Team8 - You&Meet - X.pdf
└── sprint-instructions.md
/README.md:
--------------------------------------------------------------------------------
1 | # M1522.000100 Principles and Practices of Software Development
2 |
3 | ## Announcements
4 |
5 | - Team formation due 9/12 (Wed) 9pm
6 | - Project proposal due 9/19 (Wed) 9pm
7 | - Sep. 03 : Homework 1 is posted!
8 | - Sep. 06 : Skeleton code of Homework 1 python is updated (to import os package)
9 | - Sep. 07 : [Project guideline](project/README.md) is posted!
10 | - Sep. 19 : Homework 2 is posted!
11 | - Oct. 12 : Homework 3 is posted!
12 | - Oct. 22 : Sprint 2 report due is extended due to the Github service disruption.
13 |
14 | ## Assignments
15 |
16 | - Sep. 03 : [homework 1](hw1) is out
17 | - **Due : 9/21 (Fri) 20:59 (hard deadline)**
18 | - This is an individual assignment
19 |
20 | - Sep. 19 : [homework 2](hw2) is out
21 | - **Due : 10/12 (Fri) 23:59 (hard deadline)**
22 | - This is an individual assignment
23 |
24 | - Oct. 12 : [homework 3](hw3) is out
25 | - **Due : 11/2 (Fri) 20:59 (hard deadline)**
26 | - This is an individual assignment
27 |
28 | ## [Project Guideline](project)
29 |
30 | ## Schedule (TBD)
31 | | Week | Lecture | Practice Session | Homework / Project / Exam |
32 | |-------|---------|------------------|--------------------|
33 | |9/4,6 | Introduction - what softwares do, requirements and challenges to make them good, safe, and reliable | Environment setup | HW1 out |
34 | |9/11,13| How to collaborate as a team and the methods and tools for it | Git + GitHub practice with basic javascript + python coding examples | Team formation due 9/12 (Wed) 9pm; |
35 | |9/18,20 | Good coding habits. Comments and code conventions | Typescript + Front-end lecture (with a sample provided backend) | Project proposal due 9/19 (Wed) 9pm, HW 1 due 9/21 9pm |
36 | |9/25(추석),27 | Complexity problem and software structures | Typescript + Front-end lecture cont’d | Project sprint 1 begin (bi-weekly meetings with TAs at the end of sprint) |
37 | |10/2,4 | Complexity problem and software structures | | |
38 | |10/9,11 | Testing and throwing exceptions, Requirements and specification | Python + Creating backend for the created front-end from previous week | HW 2 due 10/12 11:59 pm, Project sprint 2 begin |
39 | |10/16,18 | Software development processes, Design patterns I | Python + Creating backend for the created front-end, Testing and CI | |
40 | |10/23,25 | Software structure and modeling | Design pattern practice 1 | Project sprint 3 begin |
41 | |10/30,11/1 | Code refactoring | Mid-project check | HW 3 due 11/2 9pm |
42 | |11/6,8 | Design patterns 2 | Design pattern practice 2, Code refactoring | Project sprint 4 begin |
43 | |11/13,15 | Design patterns 3 | Design pattern practice 3 | |
44 | |11/20,22 | Operation | Connecting DB and the backend, Performance layer | Project sprint 5 begin |
45 | |11/27,29 | Operation (load testing, security) | Scaling | Coding exams (2 hours) |
46 | |12/4,6 | Code optimization | | Project sprint 6 begin |
47 | |12/11,13 | TBD | | |
48 | |12/18 | Project poster session | | Project final report (due 12/20 8:59 pm) |
49 |
50 | ## Office hours
51 | **Professor** :
52 | - Office: Bldg. 302, Rm. 322
53 | - TuTh 11AM-12PM, by appointment
54 |
55 | **TAs** :
56 |
57 | Sanha Lee
58 | - Email: sanhaleehana@snu.ac.kr
59 | - Office: Bldg. 302, Rm. 420
60 | - Office hour: Tuesday 15:00~16:00
61 |
62 | Ahnjae Shin
63 | - Email: yuyupopo@snu.ac.kr
64 | - Office: Bldg. 302, Rm. 420
65 | - Office hour: Thursday 16:00~17:00
66 |
67 | Jae Hyeon Park
68 | - Email: skystar@snu.ac.kr
69 | - Office: Bldg. 302, Rm. 420
70 | - Office hour: Tuesday 17:00-18:00
71 |
72 | (Please send TAs an email ahead of time, we can set up a specific time and place)
73 |
74 |
--------------------------------------------------------------------------------
/hw1/.gitignore:
--------------------------------------------------------------------------------
1 | .DS_Store
2 | solution
3 |
--------------------------------------------------------------------------------
/hw1/README.md:
--------------------------------------------------------------------------------
1 | # Homework 1 - Python and TypeScript Basics
2 |
3 | **Due: 9/21 (Fri) 20:59 (This is a hard deadline)**
4 |
5 | This assignment is for you to become familiar with Python and TypeScript.
6 | You will be using Python to build a backend system, and TypeScript will be used to build a (separated) frontend system, using the Angular2 framework.
7 | This is an **individual** assignment.
8 |
9 | From the beginning to the end of the development, you must use **GitHub** for version control.
10 | This will be used for your submission as well, so please keep it in mind.
11 |
12 | ## Python
13 |
14 | ### Objective
15 | In this assignment, you will implement an html file parser and find the common popular names for females and males in a year based on the skeleton code.
16 | You don't have to understand the implemented methods provided in the skeleton code, but studying them can be useful for your future term project.
17 | This is a modification of google's [Baby Names Python Exercise](https://developers.google.com/edu/python/exercises/baby-names).
18 |
19 | The goal of this assignment is to practice using various functions provided by the python language.
20 | In this assignment, you will get familiar with:
21 |
22 | - Built-in functions
23 | - Python provides many useful built-in functions. You can write code more efficiently and effectively if you are fluent with such functions.
24 | - Class
25 | - You will need to modularize and encapsulate your code to neatly manage your project. Class is a core concept to achieve such objectives. It is an important component in design patterns that you will learn in future classes.
26 | Since you will be defining your own models with classes in homework 3, you should be familiar with it.
27 | - Decorator
28 | - [Decorator](https://www.python.org/dev/peps/pep-0318/) is a special syntax in python for transforming functions using closure. It is also an important feature for applying design patterns in python, such as defining static methods or class methods.
29 | Many functions from Django are provided as decorators as well, especially with user authentication, which you will be using in homework 3.
30 | - Lambda function
31 | - Lambda function helps you write your python code in a functional programming style. In certain situations, functional style makes your code more concise and easy to modularize.
32 | For more information, read [Functional Programming HowTo](https://docs.python.org/3/howto/functional.html).
33 |
34 | ### 1. Implement `BabynameParser`
35 | You need to Implement the babyname parser class that parses the popular names and their ranks from an html file.
36 | In your skeleton code, `BabyParser` class is defined in `babyname_parser.py`. To complete the parser, you should implement the following functions:
37 |
38 | **1) `check_filename_existence`**
39 |
40 | At first, you need to implement a decorator that checks whether the file exists or not.
41 | This decorator will decorate the `__init__` of the parser to prevent constructing a parser with non-existing file name.
42 | This method should be implemented as a decorator in order to be easily applied to other methods.
43 | Please check out [this document](https://www.programiz.com/python-programming/decorator) to understand how to implement python decorator.
44 |
45 | For debuggability, defining your own exception and intentionally raising the exception is useful because you can identify the root cause of the exception and distinguish the exception from others.
46 | We provide `BabynameFileNotFoundException` for this purpose.
47 | If there is no such file with the given filename argument of the function to decorate, this decorator has to raise the custom `BabynameFileNotFoundException` with custom error message: `No such babyname file or directory: {filename}`.
48 | You can assueme that the `filename` argument is the first argument (right after the `self`) for the function to decorate.
49 | Also, we will not grade your decorator with it's stack trace but just test the class of the raised exception and it's message.
50 |
51 | For detailed information, check the execution example below.
52 |
53 | **2) `__init__`**
54 |
55 | This method is the constructor of the parser. In this method, you need to extract a list of the tuples of (rank, male-name, female-name) from the given html file.
56 | For your convinience, year extracting code is provided. You can refer the way to use regular expression in this code.
57 |
58 | **3) `parse`**
59 |
60 | This method applies a given lambda function to all of the extracted tuples and returns the results.
61 |
62 | **Usage**
63 |
64 | When you are done, you can parse any information about the popluar name ranks in a year by using the implemented parser.
65 | In the python console, you can test your code with the provided `baby1994.html` file like below.
66 |
67 | ```
68 | >>> from babyname_parser import BabynameParser
69 | >>> parser = BabynameParser("baby1994.html")
70 | >>> parser.year
71 | '1994'
72 | >>> parser.rank_to_names_tuples
73 | [('1', 'Michael', 'Jessica'), ('2', 'Christopher', 'Ashley'), ('3', 'Matthew', 'Emily'), ...]
74 | >>> parser.parse(lambda rank_to_names_tuple: rank_to_names_tuple[0])
75 | ['1', '2', '3', '4', '5', '6', '7', '8', '9', '10', ...]
76 | >>> BabynameParser("EmptyFileName")
77 | Traceback (most recent call last):
78 | File "", line 1, in
79 | File "/{YOUR_HW_PATH}/babyname_parser.py", line {EXCEPTION_RAISED_LINE}, in {DECORATOR_WRAPPER_NAME}
80 | raise BabynameFileNotFoundException("No such babyname file or directory: {0}".format(filename))
81 | babyname_parser.BabynameFileNotFoundException: No such babyname file or directory: EmptyFileName
82 | ```
83 |
84 | You should **NOT** edit parts other than those marked as `TODO`s in your skeleton code when you submit your assignment, because we will grade your `BabynameParser` implementation by not only running `run.py` file but also importing the class and test the methods like above (with different files and lambdas, of course).
85 | Also, the error message that comes out when the entered file does not exist must be
86 | `No such babyname file or directory: {filename}` and the result of `parse` method must be a list of all processed tuples.
87 |
88 | ### 2. Fill the run script
89 |
90 | In `run.py` file, a skeleton code using the parser is provided.
91 | Your task is to complete the code to parse an html file that contains the popular baby names in a year by using `BabynameParser`, sort them and find the common popular names with their rank.
92 |
93 | When you are done, the script must show results like below for the given `baby1994.html` file:
94 |
95 | ```
96 | $ python solution/run.py baby1994.html
97 | Common popular babynames in 1994 (Count: 85)
98 | Common babyname: male rank, female rank
99 | Addison: 554, 800
100 | Adrian: 98, 834
101 | Alex: 50, 581
102 | Alexis: 227, 18
103 | Ali: 461, 674
104 | Angel: 104, 176
105 | Ariel: 480, 144
106 | Ashley: 957, 2
107 | ...
108 | ```
109 |
110 | ## TypeScript
111 |
112 | ### How to run TypeScript programs
113 |
114 | 1. We assume that typescript is installed through npm: `$ npm install -g typescript`
115 | 2. With this set up, you can compile the typescript program as followings: `$ tsc`, under the directory you are working on. It will generate a new `form.js` file.
116 | 3. Validate that you have the newly generated `form.js` file, and you can use it in `form.html`, as provided in the skeleton code. In our case, you will simply need to open `form.html` on your favorite browser.
117 |
118 | Each of the files serve the following roles:
119 |
120 | - `form.html` : HTML file for layout for the form checking page.
121 | - `form.ts` : TypeScript file for form checking and using JS components.
122 |
123 | We provide `form.html` completely so you don't need to modify the file, but it would be helpful to know the contents for following HWs and your term project.
124 | You must only alter the code in the sections marked as TODO in the skeleton code and submit your code using GitHub. Do NOT alter the names of the forms in the provided HTML file. Refer to the HTML file to infer the form names.
125 | Also, please follow the instructions below, such as message format, to enable us to automatize the grading. If not, your homework may not be graded properly.
126 |
127 | To customize your compile option, please modify `tsconfig.json` file. For more detail, please check [tsconfig handbook](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html).
128 |
129 | TIP: You will find `console.log()` function useful for printing and debugging. You will be able to access the console by using the developer tools and JavaScript console provided in each of the different browsers.
130 |
131 | ### TypeScript Form Checker
132 |
133 | To complete this assignment, you will have to implement a form checker, with tooltips, and modal pop-ups using TypeScript. Through this assignment, we expect you to be able to:
134 |
135 | - See usages of JavaScript/TypeScript
136 | - Try out basic and most common usages of JavaScript/TypeScript
137 | - Compare and learn the advantages of using TypeScript compared to JavaScript
138 | - Some taste of TypeScript before diving into Angular2 with HW2.
139 |
140 | When you just compile the skeleton typescript file and open `form.html`, you will see the following screen on your browser.
141 |
142 | 
143 |
144 | In here, each input box receives user's input. There are labels right after every input box but they are not presented because they don't have contents yet.
145 | If you push the "check" button, you will see an empty popup.
146 |
147 | You need to provide following features by completing `form.ts`:
148 |
149 | **1) form validation popup**
150 |
151 | With the given form, upon clicking on the `check` button, it should first produce a pop-up listing out which forms to check and correct (see requirements).
152 | If there is no problem with the form, it should show a modal indicating that it had been successfully submitted.
153 | Specific **requirements** are as listed below.
154 | - Email: characters@characters.domain (characters other than @ or whitespace followed by an @ sign, followed by more characters (not '@', '.', or whitespace: co.kr is not allowed in this case), and then a ".". After the ".", you can only write 2 to 3 letters from a to z).
155 | - Password: Must contain at least one number and one uppercase and one lowercase letter, and at least 8 or more characters.
156 | - Password Confirmation: Must match password.
157 | - Phone number: nnn-nnnn-nnnn: three numbers, then "-", followed by four numbers and a "-", then four numbers.
158 | - First name (English) : Start with a capital letter, followed by one or more lowercase letters. Should only contain alphabets (A-Z, a-z)
159 | - Last name (English) : Start with a capital letter, followed by one or more lowercase letters. Should only contain alphabets (A-Z, a-z)
160 | - Age : Must be a number between 0 and 200 (inclusive).
161 | - Birth date (Month) : Must be one of "January", "February", ..., "December"
162 | - Birth date (Day) : Must be a number of one or two digits.
163 | - Birth date (Year) : Must be a number between 1800 and 2018 (inclusive).
164 |
165 | If the form does not satisfy the requirements (for example, if Email, Password, and Password Confirmation fail), the alert message **must** be like:
166 | ```
167 | You must correct:
168 |
169 | Email
170 | Password
171 | Password Confirmation
172 | ```
173 | In here, the name of each entry of the validation failed input list must be identical with the name right after each ` ` in the `form.html` like above.
174 |
175 | If the form satisfies the requirements, the alert message **must** be:
176 | ```
177 | Successfully Submitted!
178 | ```
179 |
180 | **2) correct label and tooltip**
181 |
182 | Even when closing the pop-up, it should tell once something is wrong with the form, with an 'X' icon next to each fields. Hovering the mouse over the icon should tell what is wrong with a tooltip like below.
183 |
184 | 
185 |
186 | The error message in that tooltip **must** be identical with each requirement above.
187 | Also, if an entry becomes valid after another check, the 'X' label have to be disappeared.
188 |
189 | Tip: using regex might be useful for detecting wrong forms
190 |
191 | ## Grading
192 |
193 | ### Python (10 points)
194 |
195 | We will test your code under Python 3.6.
196 |
197 | - `check_filename_existence` decorator method in `babyname_parser.py` (2 points)
198 | - `parse` method in `babyname_parser.py` (4 points) (automatically include the `__init__` constructor)
199 | - `run.py` (4 points)
200 | - Partial points for minor errors
201 |
202 | ### TypeScript (10 points)
203 |
204 | We will grade the `form.ts` and `form.html` file under the `typescript` directory in your GitHub repository.
205 | We will see the outputs to validate your answers.
206 | We will compile your `form.ts` by running command `tsc` (version 3.0.3) with your `tsconfig.json` file.
207 |
208 | - Valid form checking with proper alert message (5 points)
209 | - Label (proper 'X') and modal tooltips (5 points)
210 | - Partial points for minor errors
211 |
212 |
213 | ## Submission
214 |
215 | Due: 9/21 (Fri) 20:59 (This is a hard deadline)
216 |
217 | You must create your own *private* repository under your account.
218 | **Be sure to add the TAs as collaborators in your repository settings!** (Detailed instructions below).
219 | We will check the snapshot of the *master* branch of your Github repository at the deadline and grade it.
220 | Please create a `python` and `typescript` folders, and put your homework files in them appropriately.
221 | Because there are many students in this class, we need to automatize the grading process, so your homework may not be graded properly if your directory hierarchy doesn't look like this:
222 | ```
223 | repository_root/
224 | README.md (this file)
225 | python/
226 | baby1994.html
227 | babyname_parser.py
228 | run.py
229 | ...
230 | typescript/
231 | form.html
232 | form.ts
233 | ...
234 | ```
235 | Also, make sure to push your work on Github on time.
236 |
237 | ### Instructions on creating a private repository
238 |
239 | #### I. Get GitHub Student Developer Pack
240 |
241 | 1. Go to `https://education.github.com`.
242 | 2. Follow instructions to `Request a discount`.
243 |
244 | #### II. Make your private repository
245 |
246 | 1. Go to your github profile: `https://github.com/YOUR_USERNAME`.
247 | 2. Under `Repositories`, click on `New`.
248 | 3. Fill in `swpp-hw1-USERNAME` as your repository name, and mark is as `Private`. (e.g., `swpp-hw1-sanha`)
249 | 4. Hit `Create repository`.
250 | 5. In terminal, go to the directory that you will be working in (e.g., `~/workspace/swpp-hw1-USERNAME` or `~/swpp-hw1-USERNAME`)
251 | 6. Type in and run the following commands, which is also shown on the page that you will be looking at after step 4:
252 |
253 | ```
254 | echo "# asdf" >> README.md
255 | git init
256 | git add README.md
257 | git commit -m "first commit"
258 | git remote add origin https://github.com/USERNAME/swpp-hw1-USERNAME
259 | git push -u origin master
260 | ```
261 |
262 | 7. Under `Settings` then `Collaborators` tab, Add TAs as your collaborators: `sanha`, `yuyupopo`, and `skystar-p`.
263 | 8. You're all set! After finishing your homework, push your contents to your repository on time!
264 |
--------------------------------------------------------------------------------
/hw1/python/.gitignore:
--------------------------------------------------------------------------------
1 | .idea
2 | __pycache__
3 |
--------------------------------------------------------------------------------
/hw1/python/LICENSE.txt:
--------------------------------------------------------------------------------
1 |
2 | Apache License
3 | Version 2.0, January 2004
4 | http://www.apache.org/licenses/
5 |
6 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7 |
8 | 1. Definitions.
9 |
10 | "License" shall mean the terms and conditions for use, reproduction,
11 | and distribution as defined by Sections 1 through 9 of this document.
12 |
13 | "Licensor" shall mean the copyright owner or entity authorized by
14 | the copyright owner that is granting the License.
15 |
16 | "Legal Entity" shall mean the union of the acting entity and all
17 | other entities that control, are controlled by, or are under common
18 | control with that entity. For the purposes of this definition,
19 | "control" means (i) the power, direct or indirect, to cause the
20 | direction or management of such entity, whether by contract or
21 | otherwise, or (ii) ownership of fifty percent (50%) or more of the
22 | outstanding shares, or (iii) beneficial ownership of such entity.
23 |
24 | "You" (or "Your") shall mean an individual or Legal Entity
25 | exercising permissions granted by this License.
26 |
27 | "Source" form shall mean the preferred form for making modifications,
28 | including but not limited to software source code, documentation
29 | source, and configuration files.
30 |
31 | "Object" form shall mean any form resulting from mechanical
32 | transformation or translation of a Source form, including but
33 | not limited to compiled object code, generated documentation,
34 | and conversions to other media types.
35 |
36 | "Work" shall mean the work of authorship, whether in Source or
37 | Object form, made available under the License, as indicated by a
38 | copyright notice that is included in or attached to the work
39 | (an example is provided in the Appendix below).
40 |
41 | "Derivative Works" shall mean any work, whether in Source or Object
42 | form, that is based on (or derived from) the Work and for which the
43 | editorial revisions, annotations, elaborations, or other modifications
44 | represent, as a whole, an original work of authorship. For the purposes
45 | of this License, Derivative Works shall not include works that remain
46 | separable from, or merely link (or bind by name) to the interfaces of,
47 | the Work and Derivative Works thereof.
48 |
49 | "Contribution" shall mean any work of authorship, including
50 | the original version of the Work and any modifications or additions
51 | to that Work or Derivative Works thereof, that is intentionally
52 | submitted to Licensor for inclusion in the Work by the copyright owner
53 | or by an individual or Legal Entity authorized to submit on behalf of
54 | the copyright owner. For the purposes of this definition, "submitted"
55 | means any form of electronic, verbal, or written communication sent
56 | to the Licensor or its representatives, including but not limited to
57 | communication on electronic mailing lists, source code control systems,
58 | and issue tracking systems that are managed by, or on behalf of, the
59 | Licensor for the purpose of discussing and improving the Work, but
60 | excluding communication that is conspicuously marked or otherwise
61 | designated in writing by the copyright owner as "Not a Contribution."
62 |
63 | "Contributor" shall mean Licensor and any individual or Legal Entity
64 | on behalf of whom a Contribution has been received by Licensor and
65 | subsequently incorporated within the Work.
66 |
67 | 2. Grant of Copyright License. Subject to the terms and conditions of
68 | this License, each Contributor hereby grants to You a perpetual,
69 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70 | copyright license to reproduce, prepare Derivative Works of,
71 | publicly display, publicly perform, sublicense, and distribute the
72 | Work and such Derivative Works in Source or Object form.
73 |
74 | 3. Grant of Patent License. Subject to the terms and conditions of
75 | this License, each Contributor hereby grants to You a perpetual,
76 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77 | (except as stated in this section) patent license to make, have made,
78 | use, offer to sell, sell, import, and otherwise transfer the Work,
79 | where such license applies only to those patent claims licensable
80 | by such Contributor that are necessarily infringed by their
81 | Contribution(s) alone or by combination of their Contribution(s)
82 | with the Work to which such Contribution(s) was submitted. If You
83 | institute patent litigation against any entity (including a
84 | cross-claim or counterclaim in a lawsuit) alleging that the Work
85 | or a Contribution incorporated within the Work constitutes direct
86 | or contributory patent infringement, then any patent licenses
87 | granted to You under this License for that Work shall terminate
88 | as of the date such litigation is filed.
89 |
90 | 4. Redistribution. You may reproduce and distribute copies of the
91 | Work or Derivative Works thereof in any medium, with or without
92 | modifications, and in Source or Object form, provided that You
93 | meet the following conditions:
94 |
95 | (a) You must give any other recipients of the Work or
96 | Derivative Works a copy of this License; and
97 |
98 | (b) You must cause any modified files to carry prominent notices
99 | stating that You changed the files; and
100 |
101 | (c) You must retain, in the Source form of any Derivative Works
102 | that You distribute, all copyright, patent, trademark, and
103 | attribution notices from the Source form of the Work,
104 | excluding those notices that do not pertain to any part of
105 | the Derivative Works; and
106 |
107 | (d) If the Work includes a "NOTICE" text file as part of its
108 | distribution, then any Derivative Works that You distribute must
109 | include a readable copy of the attribution notices contained
110 | within such NOTICE file, excluding those notices that do not
111 | pertain to any part of the Derivative Works, in at least one
112 | of the following places: within a NOTICE text file distributed
113 | as part of the Derivative Works; within the Source form or
114 | documentation, if provided along with the Derivative Works; or,
115 | within a display generated by the Derivative Works, if and
116 | wherever such third-party notices normally appear. The contents
117 | of the NOTICE file are for informational purposes only and
118 | do not modify the License. You may add Your own attribution
119 | notices within Derivative Works that You distribute, alongside
120 | or as an addendum to the NOTICE text from the Work, provided
121 | that such additional attribution notices cannot be construed
122 | as modifying the License.
123 |
124 | You may add Your own copyright statement to Your modifications and
125 | may provide additional or different license terms and conditions
126 | for use, reproduction, or distribution of Your modifications, or
127 | for any such Derivative Works as a whole, provided Your use,
128 | reproduction, and distribution of the Work otherwise complies with
129 | the conditions stated in this License.
130 |
131 | 5. Submission of Contributions. Unless You explicitly state otherwise,
132 | any Contribution intentionally submitted for inclusion in the Work
133 | by You to the Licensor shall be under the terms and conditions of
134 | this License, without any additional terms or conditions.
135 | Notwithstanding the above, nothing herein shall supersede or modify
136 | the terms of any separate license agreement you may have executed
137 | with Licensor regarding such Contributions.
138 |
139 | 6. Trademarks. This License does not grant permission to use the trade
140 | names, trademarks, service marks, or product names of the Licensor,
141 | except as required for reasonable and customary use in describing the
142 | origin of the Work and reproducing the content of the NOTICE file.
143 |
144 | 7. Disclaimer of Warranty. Unless required by applicable law or
145 | agreed to in writing, Licensor provides the Work (and each
146 | Contributor provides its Contributions) on an "AS IS" BASIS,
147 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148 | implied, including, without limitation, any warranties or conditions
149 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150 | PARTICULAR PURPOSE. You are solely responsible for determining the
151 | appropriateness of using or redistributing the Work and assume any
152 | risks associated with Your exercise of permissions under this License.
153 |
154 | 8. Limitation of Liability. In no event and under no legal theory,
155 | whether in tort (including negligence), contract, or otherwise,
156 | unless required by applicable law (such as deliberate and grossly
157 | negligent acts) or agreed to in writing, shall any Contributor be
158 | liable to You for damages, including any direct, indirect, special,
159 | incidental, or consequential damages of any character arising as a
160 | result of this License or out of the use or inability to use the
161 | Work (including but not limited to damages for loss of goodwill,
162 | work stoppage, computer failure or malfunction, or any and all
163 | other commercial damages or losses), even if such Contributor
164 | has been advised of the possibility of such damages.
165 |
166 | 9. Accepting Warranty or Additional Liability. While redistributing
167 | the Work or Derivative Works thereof, You may choose to offer,
168 | and charge a fee for, acceptance of support, warranty, indemnity,
169 | or other liability obligations and/or rights consistent with this
170 | License. However, in accepting such obligations, You may act only
171 | on Your own behalf and on Your sole responsibility, not on behalf
172 | of any other Contributor, and only if You agree to indemnify,
173 | defend, and hold each Contributor harmless for any liability
174 | incurred by, or claims asserted against, such Contributor by reason
175 | of your accepting any such warranty or additional liability.
176 |
177 | END OF TERMS AND CONDITIONS
178 |
179 | APPENDIX: How to apply the Apache License to your work.
180 |
181 | To apply the Apache License to your work, attach the following
182 | boilerplate notice, with the fields enclosed by brackets "[]"
183 | replaced with your own identifying information. (Don't include
184 | the brackets!) The text should be enclosed in the appropriate
185 | comment syntax for the file format. We also recommend that a
186 | file or class name and description of purpose be included on the
187 | same "printed page" as the copyright notice for easier
188 | identification within third-party archives.
189 |
190 | Copyright [yyyy] [name of copyright owner]
191 |
192 | Licensed under the Apache License, Version 2.0 (the "License");
193 | you may not use this file except in compliance with the License.
194 | You may obtain a copy of the License at
195 |
196 | http://www.apache.org/licenses/LICENSE-2.0
197 |
198 | Unless required by applicable law or agreed to in writing, software
199 | distributed under the License is distributed on an "AS IS" BASIS,
200 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201 | See the License for the specific language governing permissions and
202 | limitations under the License.
203 |
--------------------------------------------------------------------------------
/hw1/python/NOTICE.txt:
--------------------------------------------------------------------------------
1 | Code for Google's Python Class
2 | Copyright 2010 Google Inc.
3 |
4 | This code developed by Nick Parlante
5 | at Google Inc, and modified by Sanha Lee
6 | at SNU Software Platform Lab
7 | for SWPP fall 2018 lecture.
8 |
--------------------------------------------------------------------------------
/hw1/python/baby1994.html:
--------------------------------------------------------------------------------
1 | Popular Baby Names
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
26 | 