Seminar sylabus PV260 (Groups 01, 02)

Seminar 1 - Introduction, Essential tools

The content of the seminar sessions

The purpose of the seminars is to provide hands-on experience with the topics discussed in the lectures. The seminar content will cover various areas of code refactoring, testing, and static code analysis. The students will analyse and optimize multiple software quality attributes, such as reliability, maintainability, testability or performance with the help of modern open-source tools. The students will work in pairs on exercises during the seminars and on larger assignments (projects) at home. The attendance on the seminars is mandatory. Although, the seminars focus on the Java programming language, the principles discussed in the seminars are generally applicable also in other languages and environments.

Requirements

The maximum number of points to be obtained in the course is 100 and the required minimum for passing is 70. The distribution of the points is as follows:

  • Active participation in lectures: 10 points
  • Achievements in seminars (completing bonus tasks, nice solutions, extra activity etc.): 10 points
  • Projects: 45 points
    • Assignment 1 (Refactoring): 15 points
    • Assignment 2 (Testing): 15 points
    • Assignment 3 (Performance testing, Static Code Analysis): 15 points
    • Special evaluation assignment
  • Final colloquium assessment: 35 points
An additional requirement for passing the course is the completion of all assignments from the seminars.

Penalties

  • Every second (and afterward) unexcused absence (note that one is allowed, and the first seminar session does not count):
    • -7 points.
  • Late submission of project or assignment:
    • -3 points for each team member per day overdue.

Time Schedule:

  • 18.2. [java1+java2] Introduction - maven, git, branching
  • 25.2. [java2] Clean code, SOLID
  • 3.3.   [java1] Clean code, SOLID
  • 10.3. [java2] Code smells, refactoring
  • 17.3. [java1] Code smells, refactoring
  • 24.3. [java2] JUnit extensions, data-driven testing, Mockito, TDD   
  • 31.3. [java1] JUnit extensions, data-driven testing, Mockito, TDD      
  • 7.4.   [java2] Test plan, risk analysis, web app testing, Selenium, Issue processing,  
  • 14.4. [java1] Test plan, risk analysis, web app testing, Selenium, Issue processing,
  • 21.4. [java2]  Profiling, performance testing, Perfcake
  • 28.4. [java1]  Profiling, performance testing, Perfcake
  • 5.5.   [java2] Static Code Analysis,  Checkstyle, Continuous integration, code review
  • 12.5. [java1]  Static Code Analysis Checkstyle, Continuous integration, code review

Projects

  • There will be three larger assignments (separate mini-projects)
  • First will focus on code refactoring, second on unit testing and third on the performance testing and static code analysis
  • The deadline for each assignment will be 2-3 weeks
  • Students will work in pairs
  • Each project will have a set of optional (and more challenging) tasks, whose completion will be awarded by bonus points
  • Additionally, there will be two special coding tasks. The first one will be introduced at the first seminar. Its purpose will be to evaluate students' current ability to write good quality code. The second one will be assigned at the last seminar. Its goal will be to evaluate the improvement of students' coding skills as a result of the course enrollment.

Basic study sources

Books

  • Clean Code: A Handbook of Agile Software Craftsmanship
    • Robert C. Martin
    • Link
  • Clean Architecture: A Craftsman's Guide to Software Structure and Design
    • Robert C. Martin
    • Link
  • Refactoring to Patterns
    • Joshua Kerievsky
    • Link
  • Refactoring: Improving the Design of Existing Code
    • Martin Fowler
    • Link
  • xUnit Test Patterns: Refactoring Test Code
    • Gerard Meszaros
    • Link

Web

Tutorials

Initial evaluation assignment