Date: November 18, 1999 Time: 1-3pm Place: B448 Name: APT Project Meeting Attendees: Tony Krueger, Gary Curtis, Dick Shaw, Paul Lee, Sandy Grovesner Minutes: There was a discussion about what we should do to organize and get started on the project. We came up with the following list of items. - Project Scope - vision statement - mission statement - Project Schedule - we talked about the idea of not being tied to HST cycles for software release, but releasing the software on a 3 or 4 month cycle. Try to avoid huge releases with many new features. - Project Team Organization - we talked about the idea of innovators and fielders as put forth in the "Tools of the Future working Group' document. We seemed to agree that the term innovators meant people prototyping/developing software to a state where a fielder could then field the system and maintain it. The innovators would not build a prototype that a fielder would have to throw away. - we talked about using prototypes to minimize risk, explore new ideas (good ideas factory), and to determine the users needs (market survey) - we mentioned the need for balancing research and development - Technical Description of the System - Project Standards, procedures, and proposed techniques and tools - Quality Assurance Plan - Configuration Management Plan - Documentation Plan - Data Management Plan - Resource Management Plan - Test Process/Plan - Training Plan - Security Plan (if Needed) - Risk Management Plan - Maintenance Plan - Transition Plan For Phasing out RPS2 with APT - Need to Identify the classes of users we need to support and how we will get support from them during the APT project. - Wanted to document the current capabilities of RPS2. This will help us in determining what capabilities should persist in the SEA. Helps us come up with a first cut of SEA capabilities. Wanted to document the current SEA capabilities. - Want to evaluate the SEA prototype, Starview 2, and Gator systems so see what might be applicable to APT (code reuse). In evaluating these systems, we would also look at the idea of having a similiar look and feel between the tools, thus giving a more common look and feel to STScI user tools Action Items: - Paul Lee will begin drafting a mission/vision statement - Dick Shaw will begin drafting a document on the different customers APT will have and how we can obtain support/information from them - Chris Burkhardt will begin documenting the major capabilities of RPS2 - Tony Krueger will begin drafting a document on how to evaluate and learn about the software in the SEA, Starview 2, Gator. Next Meeting: - Tony Krueger to set up the next meeting for monday Nov 22 at 10am - The group would also like to move the meetings to Tuesdays from 3-5pm