Sandy Graham

1
Sandy Graham

• Documentation Conventions Programming Style

2
Curriculum Requirements

• From Skills Processes
• Use descriptive naming conventions for constants,
  variables, and expressions
• Incorporate internal documentation to a specific
  set of standards to ensure clarity and
  maintainability
• Validate a program using appropriate data

3
Why is Style Important?

• Readability, maintenance, sharing, debugging
• A programmers product is not an executable
  program but its source code.
• Professional
• It counts for MARKS!

4
Create Your Own Style Sheet

• Ideally use the same style sheet in all courses
  within the school
• The 32-bits of Stylehttp//www.skylit.com/style/
  index.html

5
Grade 10 Style Sheet

• Order
• Spacing Indentation
• Internal Documentation
• Naming Conventions
• Miscellaneous

6
Systematic Testing

• Typical Case(s)
• Boundary Cases
• Black Box vs. White Box testing
• Marking
• stating test cases
• demonstrations