Next: 3 Future Plans
Up: secp_02
Previous: 1 Background
Over the course of the last year, a number of actions have been taken. In particular,
- Weekly discussions of McConnell's, Software Project Survival Guide.
- Weekly discussions of Robertson and Robertson, Mastering the Requirements Process.
- Construx two-day training course titled, Software Project Survival Guide, followed by a one-day consulting session. A list of tasks was identified to understand and improve software process at NCAR. These are included in appendix B.
- Presentations to CCSM scientists, at the SEWG meetings, and to the SSC with respect to CCSM software engineering process improvement.
- Establishment of an atmospheric model change review board. This board has started to meet and is slowly spinning up.
- Implementation of a formal CVS repository request process.
- Implementation of a CCSM CVS policy.
- Initiation of a project to update the CCSM GUI/scripts using formal software process. This project is currently in the requirements collection phase.
- Hiring of a software engineer to focus primarily on infrastructure support and tools.
- Hiring of a software engineer to focus primarily on testing and performance issues.
All of these items have had a positive impact on CCSM software engineering capability and quality. In the following section, follow-ons to these items will be addressed.
Next: 3 Future Plans
Up: secp_02
Previous: 1 Background
tcraig@ucar.edu