![Transcription Center logo](/themes/custom/tc_theme/assets/image/logo.png)
This transcription has been completed. Contact us with corrections.
Clifton B. Phillips, 4/23/95 11:26 PM,Issues for 24 Apr 95 team leader meeting 1 Date: Sun, 23 Apr 95 16:26:32 -0700 X-Sender: phillips@macvax.ucsd.edu Mime-Version: 1.0 To: kidsat_lead@deimos.ucsd.edu From: phillips@ucsd.edu (Clifton B. Phillips) Subject: Issues for 24 Apr 95 team leader meeting KidSat Team, (1) Master Schedule There is a preliminary UCSD KidSat MCG Master Schedule up for review. Please comment on it by Wednesday, April 26, so the Master Schedule issue can get closed soon. (2) Functional Requirements Document All teams need to support the systems engineering effort this week. Kris Langham will be distributing forms for all UCSD MCG and SMOC functional processes. Please use your up to date expertise and get these forms turned in to him by Friday April 28. (3)Internal Systems Review Over the next two weeks, we should see our systems engineering efforts mature towards unified technical goals. By then the requirements effort should be fairly complete. Each group should be brainstorming their sub systems and be engaged in trade studies to satisfy their functional requirements. At this point I suggest an internal systems review (Propose end of first or second week in May). Our project advisors and mentors can help by giving us a sanity check. Each team should show their progress and near term plans toward realizing the system architecture of UCSD MCG. This will be the basis for the preliminary design review with JPL. We can build on the internal systems review for the PDR charts. (4)TIM & Design Review Formats Lessons learned from last TIM showed we need to implement some corrective action.This week some one from the Management team will prepare some templates for TIM and Design reviews. These templates will be reviewed with project advisors and team leaders. The templates will look something like Fred Peters suggestion; a common cover page, the name of the presenter, common format, etc. (5)KidSat File Archiving Is there a data file back up system being implemented now? We are all at the point where stuff is being produced. Next Fridays meeting should have a 5 minute blurb on what we should expect for file archiving (i.e. frequency, stack rotation policy, etc.). (6) Communication There is a new communication policy. The scope of this policy covers electronic and hard copies of important external deliverable documentation, announcements, meeting agendas, etc.. Details at the team leader meeting. Cliff Printed for sride@ucsd.edu (Sally K. Ride) 1