Coding Exercises
(due at end of semester, as per team sakai assignments submission)

• P4B.1 Pair Programming
  • choose a module of sufficient complexity (to justify pair programming)
  • decide on your respective roles
  • ensure that all commit comments respect the respective contributions of each developer
  • write up a report on:
    • the roles you assumed, and why you felt those to be good choices
    • how effectively each person's time and skills were used
    • the speed and quality of the development process (vs working alone)
    • pleasant and unpleasant aspects of the experience
    • what you would do differently next time
• P4B.2 Code Review
  • choose a module of sufficient complexity (to be worthy of review)
  • prior to testing:
    • prepare a review package and submit it for review by other team members
    • conduct a review, producing a written report
    • address all raised issues from the review
  • complete the testing
  • document how the testing went, and what (if any) problems were subsequently found (in either unit-testing or integration)
• P4B.3 Test Driven Devlopment
  • choose a module of sufficient complexity (to requre a significant number of non-trivial test cases)
  • consider the order in which you should implement your methods and classes (some may not be testable until others are available)
  • write and commit each test case before committing the code to be tested.
  • when you commit the (successfully running) code, describe the tests that have been passed and whether or not those tests turned up any problems in the initial code.
  • when you write up your report, discuss how efficient and helpful you found the process to be, and the circumstances under which you would or would not use it in the future