Erinevus lehekülje "Java Fundamentals" redaktsioonide vahel

Allikas: Kursused
Mine navigeerimisribale Mine otsikasti
P
 
(ei näidata sama kasutaja 5 vahepealset redaktsiooni)
1. rida: 1. rida:
 +
'''!!!!! Exam info !!!!!'''
 +
 +
Exam times:
 +
* May 22nd - ICT-315, ICT-312 @12.00
 +
* May 29th - ICT-A1, ICT-A2 @12.00
 +
Format:
 +
* Written part
 +
** 25 multiple choice questions (choose one)
 +
** 45 minutes
 +
* Oral part
 +
** 2 questions
 +
** 10-15 minutes each
 +
* You will receive your grade immediately
 +
 +
 
'''Course Introduction'''
 
'''Course Introduction'''
  
38. rida: 53. rida:
 
The exam will be:
 
The exam will be:
 
* 60% written (multiple-choice questions)
 
* 60% written (multiple-choice questions)
* 40% oral (3 questions)
+
* 40% oral (2+1 questions)
 
*  NB! Prerequisite: must get at least 6 points for Homework
 
*  NB! Prerequisite: must get at least 6 points for Homework
  
109. rida: 124. rida:
 
** Link: [https://github.com/JavaFundamentalsZT/jf-hw-classloaders https://github.com/JavaFundamentalsZT/jf-hw-classloaders]
 
** Link: [https://github.com/JavaFundamentalsZT/jf-hw-classloaders https://github.com/JavaFundamentalsZT/jf-hw-classloaders]
 
** Deadline: Sunday, April 2 23:59 EEST
 
** Deadline: Sunday, April 2 23:59 EEST
 +
** General feedback:
 +
*** Very many of you print the stacktrace before throwing a new exception or returning null.The convention in the industry is to have exception logging (print it out in some sort) at one single location at some higher part of the calling chain. In your catch sections I would either handle the exception (some logic) or re throw.
 +
*** Make sure you close your streams! Classloaders are usually quite hot, meaning that they process a ton of files. If you happen to leak a handle each time then the leak can be substantial! Don’t forget to close them in the finally block or using the more convenient try-with-resources approach.
 +
*** Test your submission before you send them in! Out of the 22 submissions 4 threw an exception with the supplied input files.
 
Lecture 10
 
Lecture 10
 
* Slides: [[Meedia:JavaFundamentals - Lecture 10 - Java Memory Management.pdf|JavaFundamentals - Lecture 10 - Java Memory Management.pdf]]
 
* Slides: [[Meedia:JavaFundamentals - Lecture 10 - Java Memory Management.pdf|JavaFundamentals - Lecture 10 - Java Memory Management.pdf]]
124. rida: 143. rida:
 
** Link: https://github.com/JavaFundamentalsZT/jf-hw-javassist
 
** Link: https://github.com/JavaFundamentalsZT/jf-hw-javassist
 
** Deadline: Sunday, April 23 23:59 EEST
 
** Deadline: Sunday, April 23 23:59 EEST
 +
Lecture 13
 +
*  Slides: [[Meedia:JavaFundamentals - Lecture 13 - Networking.pdf]]
 +
* Homework
 +
** Link: https://github.com/JavaFundamentalsZT/jf-hw-net
 +
** Deadline: Sunday, April 30 23:59 EEST
 +
Lecture 14
 +
*  Slides: [[Meedia:JavaFundamentals - Lecture 14 - Java Troubleshooting and Performance.pdf]]
 +
* Homework
 +
** Link: https://github.com/JavaFundamentalsZT/jf-hw-performance
 +
** Deadline: Sunday, May 14 23:59 EEST
 +
Lecture 15
 +
*  Slides: [[Meedia:JavaFundamentals - Lecture 15 - Java 9 and Beyond.pdf]]

Viimane redaktsioon: 15. mai 2017, kell 10:43

!!!!! Exam info !!!!!

Exam times:

  • May 22nd - ICT-315, ICT-312 @12.00
  • May 29th - ICT-A1, ICT-A2 @12.00

Format:

  • Written part
    • 25 multiple choice questions (choose one)
    • 45 minutes
  • Oral part
    • 2 questions
    • 10-15 minutes each
  • You will receive your grade immediately


Course Introduction

Offered by ZeroTurnaround in Spring semester 2017. The course will be taught in English.

  • Course code: ITI8905
  • Credits: 3 EAP
  • Time: Lectures on Mondays 12:00-13:30. First meeting on January 30.
  • Place: ICT-315 (ICT building is at Akadeemia tee 15a)

The course is targeted to students who (think they) already know Java. It is not a beginner's course!

NB! The number of places is limited to 40! Sign up ASAP! When we cannot find any evidence of you having taken some Java courses in the past, we may vacate the place to other students.

Students from TUT should register in ÕIS (registration will be opened on January 11 January 30). Students from Tallinn University and IT College, who are interested in taking the course should send an e-mail to Siiri Taveter (siiri.taveter@ttu.ee) mentioning ITI8905 in the subject line.


Final Grade

Your final grade will consist of:

  • 50% Homework
  • 50% Exam


Homework

There are 14 homework assignments total for Lectures 1-14. The last lecture (lecture 15) will not have a homework assignment. Each assignment submission will be scored between 0.0 - 1.0. For a perfect score for homeworks you need at least 12 points out of the 14. So there is some buffer if you happen to miss a homework or if you didn't get a great score for each of them. For those of you that happen to get more than 12 points, we will make your life easier on the exam :).

Homework assignments for the lectures will be given out at the end of each lecture (Monday) and each one, except for the first one, will need to be submitted by Sunday 23:59 EEST same week. This means you have 6 days for solving the homework and submitting it to us for grading. Don't be late - if you are late then you'll get 0 points and we won't even look at it!

No cheating:

  • Copying solutions from a friend is forbidden - if we see two identical submissions, they both get a 0.
  • Copying solutions from StackOverflow is forbidden - its okay to look at solutions for ideas, but don't blatantly copy.

Use the Java Standard Library unless homework assignment itself uses some other libraries


Exam

The exam will be:

  • 60% written (multiple-choice questions)
  • 40% oral (2+1 questions)
  • NB! Prerequisite: must get at least 6 points for Homework


Lectures

Lecture 1

Lecture 2

Lecture 3

Lecture 4

Lecture 5

Lecture 6

Lecture 7

Lecture 8

Lecture 9

  • Slides: JavaFundamentals - Lecture 9 - Classloaders.pdf
  • Homework
    • Link: https://github.com/JavaFundamentalsZT/jf-hw-classloaders
    • Deadline: Sunday, April 2 23:59 EEST
    • General feedback:
      • Very many of you print the stacktrace before throwing a new exception or returning null.The convention in the industry is to have exception logging (print it out in some sort) at one single location at some higher part of the calling chain. In your catch sections I would either handle the exception (some logic) or re throw.
      • Make sure you close your streams! Classloaders are usually quite hot, meaning that they process a ton of files. If you happen to leak a handle each time then the leak can be substantial! Don’t forget to close them in the finally block or using the more convenient try-with-resources approach.
      • Test your submission before you send them in! Out of the 22 submissions 4 threw an exception with the supplied input files.

Lecture 10

Lecture 11

Lecture 12

Lecture 13

Lecture 14

Lecture 15