This page contains links to minutes for GMAT's weekly team meeting. The minutes are stored as individual Google Documents. They are also collected into the GMAT Meeting Minutes shared folder.
Previous minutes are located at the GMAT Forums. The minutes were started based on this template, though generally each week is just copied over to the next. The template has not been kept up to date.
The process of recording meeting minutes is as follows:
Send out an email to everyone with a link to the new document.
See the System QA Tracking page for status tracking and links to the working documents
We are in the end-game phase for GMAT v1.0 and our work product is R2013a (Production Release). To reach this goal, our primary work is to:
The first step is to simply explore the feature and document what you find. There is a placeholder in the "Explore" section of the feature spec to record a complete list of all known issues during the exploration phase. We use this list to do a pre-triage/sanity check to determine the state of the feature.
The goals of the documentation effort are:
The basic workflow for documentation is illustrated below. Begin by consolidating existing material from old documents in working specifications and then update the specification for style and completeness. Completed draft specs are inspected by a developer, tester, and possibly another engineer. After all issues in the specs are resolved, the material relevant to users is included in end-user documentation and you can use the spec to evaluate existing test coverage.
Historical and old documenation is currently listed in html help files and in a pdf file that we used to call "Quick Tables". While this information is not complete, it will provide a good start for completing specs described in the next section. Here are links to useful, but out of date, functional documentation:
In this section,we'll discuss how to write working specs that will be used to (1) define R2013a behavior, (2) evaluate existing test coverage, and (3) to write end-user documentation. We'll discuss each section of the working spec (Requirements, Functional Specifications, and Field Specifications) below. You'll need the following templates and historical documents for this work.
Move requirements from the GMAT Requirements spreadsheet show above into the appropriate section in the working spec. Inspect the requirements asking the following questions:
Send any issues found when reviewing to the SPH for CCB Analysis.
After specs are inspected and all issue are resolved, material relevant to the user is included in the User's Guide. We'll get to this later so I have not documented this step yet. -SPH