CddBranchInternal

Revision as of 07:49, 18 March 2008 by Aleitner (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Project Internal Stuff

Schedule

  • 04.01.2008: Final experiment definition (questions to ask, how to conduct experiment)
  • 08.01.2008: Finalized list of features to go in release (including logging and log submission)
  • 27.01.2008: Beta 1 (feature complete version online)
  • 04.02.2008: Beta 2 (designated testers test release, # > 3)
  • 11.02.2008: Beta tester feedback in
  • 11.02.2008: Beta 3
  • 18.02.2008: Final 1 release
  • 19.02.2008: Initial Questionnaire
  • 20.02.2008: Final 1 handover to ISG
  • 22.02.2008: Final 1 installed on students machines
  • 29.02.2008: Final 2 release
  • 05.03.2008: Final 2 handover to ISG
  • 07.03.2008: Final 2 installed on students machines
  • 25.03.2008: Midterm Questionnaire
  • 19.05.2008: Final Questionnaire
  • 20.05.2008: Having all data
  • 06.06.2008: Finished analysis

Stefans Master Plan

  • MA Start ca 17.12.2007
  • MA End ca 17.6.2008
  • Testing the tester
    • System level test for CDD (incl. framework)
    • Recreating existing unit test suite with CDD
    • Large scale validation of CDD
      • Info 4 and/or Software Engineering
      • Questions
        • Does testing (manual/extracted) increase developer productivity?
        • How many tests do ppl end up with (manual/extracted)?
        • ...

Various

Things we need from estudio

  • Invariants should be checked during debugging equally to pre- and post conditions (they could also be visualised in the flat view the same way like pre- and post conditions are)
  • The information whether some call is a creation call or a normal routine call (Not sure if this is really necessary, what if we assume every call to some creation procedure is always a creation call?)
  • Support for multiple open targets

Old Documentation

Documentation for the release of CDD for EiffelStudio version 5.7 is available from CddOldDocumentation.