1、Lessons Learned Entry: 0911Lesson Info:a71 Lesson Number: 0911a71 Lesson Date: 2000-09-06a71 Submitting Organization: GSFCa71 Submitted by: Richard BerrySubject: Provide Detailed WBS for Flight Software in the RFP Description of Driving Event: The Work Breakdown Structure (WBS) in the Request for Pr
2、oposal (RFP) will become the basis for the Contractors Project organizational structure and job order numbers. If not mandated via the WBS, the Contractor may choose to organizationally segregate flight software from the spacecraft subsystems it is controlling.Lesson(s) Learned: This organizational
3、segregation of flight software from the spacecraft subsystems leads to a “lack of ownership“ of the subsystem flight software by the Subsystem Manager. Typically, the Subsystem Manager is only concerned that he finalize his requirements and design prior to Spacecraft CDR. This in turn leads to late
4、delivery of flight software ICDs, requirements, design algorithms, data constants, and test cases from the subsystem to the Flight Software Manager.Recommendation(s): Force a “Software Team“ approach by specifying in the software portion of the WBS that at least one representative from every subsyst
5、em organization which has active flight software (typically C&DH, GN&C, Power, maybe Thermal, Instruments) be co-located to the software group. These Subsystem Analysts will report to the Flight Software Manager, not the Subsystem Manager, and be responsible for the software deliverables.Evidence of
6、 Recurrence Control Effectiveness: N/AProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Documents Related to Lesson: N/AMission Directorate(s): a71 ScienceAdditional Key Phrase(s): a71 SoftwareAdditional Info: Approval Info: a71 Approval Date: 2000-09-18a71 Approval Name: Eric Raynora71 Approval Organization: QSa71 Approval Phone Number: 202-358-4738Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-
