Held: ,

Back to Outline 12 - Pause for Breath. On to Outline 14 - Codes of Ethics.

Summary

We consider issues in writing correct code, particularly test-driven development and ways to identify code that is likely to have errors.

Related Pages

• http://martinfowler.com/bliki/CodeSmell.html

Overview

• Review: Buggy code.
• Loop invariants.
• Code smells.
• Test-driven development.
• Code coverage.
• Work time.

Administrivia

Upcoming Work

• A bunch of articles for Wednesday
  • Don Gotterbarn, Keith Miller, and Simon Rogerson (October 1999). Computer Society and ACM approve Software Engineering Code of Ethics. IEEE Computer 32(10): 84-88. https://www.computer.org/cms/Computer.org/Publications/code-of-ethics.pdf
  • Peter G. Neumann (February 2015). Inside Risks: Far-sighted thinking about deleterious computer-related events. CACM 58 (2): 30-33. http://www.csl.sri.com/users/neumann/cacm235.pdf
  • ACM Council (October 1992). ACM Code of Ethics and Professional Behavior. http://www.acm.org/about/code-of-ethics/
• Reading Journal for Wednesday (due Tuesday at 8pm)
  • Subject: Reading Journal for Class 14 (Your Name)
  • What was the most familiar idea in today's readings on ethics? Where had you seen that idea before?
  • What surprised you the most in today's readings on ethics? Why was that idea surprising?
  • Are there ways in which agile practices help support ethical behavior or make it more difficult?
  • Any other reactions or points you would like to discuss?
  • These questions were inspired by the work of JLND

Good Things to Do

Academic

• Misc. department stuff
• Sexual Assault Awareness Week Discussion, Monday, 7:30 pm JRC 101
• CS Table, Noon, Tuesday, White PDR.
• State of SHACS Discussion, Tuesday, 7pm JRC 209
• Town Hall, Wednesday, noon or 7:30 pm (I think) JRC 101
• CS Extras Thursday (?)

Peer

• Social Dance Workshop Tuesdays 7:00-8:00 in Bucksbaum Dance Studio (peer like)

Refresher: Incorrect code

What does this program try to do?

class TimeSetter
  def self.convert(d)
    y = 1980
    while (d > 365) do
      if ((y % 400 == 0) || (y % 4 == 0) && (y % 100 != 0))
        if (d > 366)
          d -= 366
          y += 1
        end
      else
        d -= 365
        y += 1
      end
    end
  end
end

What is wrong with this program?

How would we find it?

How would we fix it?

Loop invariants

• The CSC207 part of my brain wants you to fix this with loop invariants.
• So let's remember what loop invariants are. Three main aspects.
• How would the help with this program?

Code smells

• What are they?
• Why do we care?
• What are some useful smells to look for?
  • SOFA (or the inverse thereof - LMMC)
• What are smells that you look for?
• How do we make things smell better?

Unit testing

• Why?
• How?
• Your notes:

Code Coverage

• Basically: How much of the code that we've written actually gets touched by our tests.