Team SoftwareEngineering.Ca

• Olivier Clift-Noël
• Jean-Philippe Daigle
• Jason Kealey
• Jordan McManus
• Étienne Tremblay

• Tracing a path through a system of objects to explain a causal sequence

• Goal: Usability
• Goal: Maintainability
• Goal: Better documentation

• Mockup screenshots (Eclipse)
• Functionality screenshots: elements, paths (mockups)

Goals

• Generic
• Guide our vision
• Make client happy

Requirements

• Specific
• Define functionality

• How do we test this?
• Usability goals:
  • Following Eclipse UI guidelines
  • For this project, formal usability testing is not required; we can already guarantee a dramatic usability improvement over the current version.
  • Evaluating usability: for first version, testing by a few users (Personas: programmers that may or may not know Eclipse / UCMs) and the client.

• Using the Eclipse framework forces us into a few highly-maintainable patterns & coding standards. (lucky us!)
• Evaluating maintainability: code reviews and a few metrics
  • Time between assignment of an enhancement task -> resolution
  • Repository stats for modifications: problem areas

• Our client provides feedback allowing us to be assured that documentation meets quality requirements.
• We use TWiki to foster conversation between developers and the client
• Documents changes / history
• Place to put dev documentation / easy to maintain

• System build process
  • Continuous integration
  • Email reports

• Testing that requirements are met
• We're lucky to have existing UCMs as a reference
• 
• Question to answer: Can system support creation of existing UCMs with the new tool?

• Diagram elements
  • Manipulating the model
  • JUnit tests are possible / a bit of scripting

• Editor commands
  • Manual testing
  • Some automated unit tests possible
    • Examples?
  • Model serialization will help us with automated testing
    • Guard against regressions
    • Test undo / redo functionality

• View aspects
  • Mostly manual verification

Help & Documentation

• Manual review by client, who provides timely feedback
• Quality is somewhat subjective

• Java version
  • Building on J2 SE? 1.5 (Java 5.0)
  • Other tests passing implies it works under this platform target.

Reporting

• Remember we get automated notifications of tests having passed / failed on each build.

Who does what: (clean up)

• ET: architecture
• Jord: coding standards
• JP: UI, usability, deployment
• Oli: General QA, Documentation goals
• JK: Targeting of bugs with releases, Delivery validation (building the right thing?)