01219245-58

This is a course homepage for 01219245/01219246 Individual Software Process and Individual Software Process Lab for 2nd semester, academic year 2558.

Lectures

• Week 1 (Jan 22):
  • Introduction. (slides)
  • Modern software development:
    • Business Model Canvas Explained is a nice clip that tells you what business thinks when developing a new product.
      • A more detailed introduction on how to creating business model Ep1, Ep2, Ep3, Ep4, Ep5, Ep6
    • Agile Product Ownership in a Nutshell (by Henrik Kniberg) gives an overall view on how software development is a collaboration between developers and stakeholders (users) and how important communication is.
  • Coding convention. (slides)
  • Practice on task breakdown. (slides)

• Week 2 (Feb 12):
  • Incremental & iterative development (slides)
  • Planning 1. (slides)

• Week 3 (Feb 19):
  • Game design principles. (slides)
    • Game design slides by Andrea Resmini: lecture1, lecture2, lecture3, lecture4
  • Clean code: Meaningful names. (slides)
  • Software testing, Unit testing, TDD (slides)
  • Unit testing in JavaScript (slides)

• Week 4 (Mar 4):
  • Project planning (slides)
  • Clean code: functions (slides)
  • Unit testing in JavaScript (cont.)
    • Template for TDD practice: 219245-practice.zip

• Week 5 (Mar 11):
  • Project-related practices: remote repository setup, 1st iteration task breakdown, time tracking, game mechanic test cases.

• Week 6 (Mar 18):
  • Test design techniques (slides)
  • Practice: KU Student status

• Week 7 (Apr 1):
  • Estimation (slides)
  • Planning for the 2nd iteration (slides)
  • Code cleaning practice

• Week 8 (Apr 8):
  • PSP
  • Code smells cheat sheet from Industrial Logic.

Labs

Preparations

Various practical skills (we will discuss these topic in class as well.)

• Command-line shell: In the modern era of computing, we usually enjoy using nice GUI program to work with our files and folder. However, command-line interface still wins in many aspects. It can be much faster and more accurate. In many cases, e.g., in server maintenance and in many DevOps's activities, command-line interface is the only choice. Here are a few how-to:
  • Windows:
    • by AxiomSecurityLabs: part1, part2
    • by DrapsTV (slower): part1, part2, part3
  • Linux:
    • by tutoraLinux
    • in Thai Intro Unix CLI
  • Mac OS:
    • youtube by SysAdmGirl
    • youtube by Penn State MacAdmins (slower)
• Master your Editor/IDE:

Git

• Version control system with Git

JavaScript

• Getting Started with JavaScript
  • After you finish each tutorial, you should try to work on its quiz to make sure that you grasp core concepts of each tutorial.
  • Tutorial 1: Number guessing game
    • Self quiz after finishing the tutorial: self-quiz-tut1.pdf
  • Tutorial 2: Event-driven programming
    • Self quiz: self-quiz-tut2.pdf
  • Tutorial 3: 21 Game
  • Tutorial 4: Hangman

Cococs2d-JS

We will use Cocos2d-JS as a game development framework.

• Getting started
• Tutorial 100 - sprites
• Tutorial 101: Sprites 2 - Flappy Dot
  • Small Tutorial 102: Actions, spritesheets, sound effects
• Tutorial 103: PacMan
• Guide 200: Platform game without physics engine

• Empty template: cocos-emptyproject.zip

Video clips

• Git
  • Part 1 - covers the following commands: init, status, add, commit, diff, log
  • Part 2 - covers how to ignore files
  • Part 3 - covers basic branching mode and how to move the HEAD around the commit graphs
• JavaScript: basic
  • Part 1 - introduction, variables, control flows.
  • Part 2 - functions, I/O with alert() and prompt()
  • Part 3 - how to generate random numbers

Links

• Course home page from year 2556, Course home page from year 2557.
• JavaScript
  • Style guides: idiomatic.js, jQuery style guide, Crockford's code convention, Google JavaScript Style Guide