Phil Weinstein / Annual Review Notes: July 2012 through June 2013

Summary of major development work:

1. Scenarios: Manager Dialog Port and User Interface Enhancements analysis, design and development / Scenario Playbox, several iterations. [July-Aug and Jan-Mar. L1, L2, L3, L4]
2. Series Slots with Periodic Input, several iterations. Plus migration function. [July-Aug].
3. Diagnostic Output Message Filtering. [Aug].
4. Smart Linker tool [Nov]

Qt4 Port:

Several iterations of analysis and development were completed, with an eye towards shrinking the scope of the remaining porting work -- (provisionally supporting the possibility of farming-out some of the work). Here are some of the porting project management summary pages and documents:

• [Sep]: Building Qt 4.8.3 and Qwt 5.2.2 for RiverWare 6.3
• [Oct]: Dialogs containing major widgets to be ported from Q3 to Qt4
• [Oct]: Open Object Dialog:
  • [A] Porting Lists from Qt3 to Qt4
  • [B] Slot Ordering and Conditional Showing Controls
• [Jan]: Conversion of DbDmi Qt3 UI files to Qt4
• [May]: SCT Port
• [May]: Completion of the Qt3-to-Qt4 Port

Other RiverWare and CADSWES work:

• [Jul]: Accounts Manager Dialog, Account Equal Priority Allocation
• [Jul]: minor Study Manager Plugins: DMI and MRM "events". Also study manager icons [Dec].
• Various significant performance enhancements, e.g. for display lists of series values; and run-time dispatching [Oct].
• Several dozen bug fixes (esp. for RiverWare 6.3 preparation) and unit scheme testing.
• Maintenance of our Online Payment System, and migration to a new server.

General Comments:

I maintain project management notes in my staff web area, and refer to those resources in internal communications, e.g. cited in my daily reports and monthly activity reports. This works well for my own work. I believe there would be benefit to having an internal web space (perhaps a browser-accessible CMS supporting hyperlinks) for overall project management which all developers could use and which could be referred to from our written accomplishments reports. Apart from that, major GUIs and non-GUI modules could perhaps have an official area for "longitudinally" tracking changes, with reference screenshots. Of course, some of our internal documentation conventions (\\alamosa\projects\riverware\doc, and our online help document) provide some of these needs, but don't support our internal project management and development work as well as they might.

Apart from my project-related project management notes (organized by year), as of the recent RiverWare release, I'm maintaining a major-change log for RiverWare 6.3 patches and RiverWare 6.4 development:

• http://cadswes2.colorado.edu/~philw/Rw63/changes.html
• http://cadswes2.colorado.edu/~philw/Rw64/dev.html

--- (end) ---