REG NASA-LLIS-1346-2003 Lessons Learned ADEOS-II NASA Ground Network (NGN) Development and Early Operations -- Central Standard Autonomous File Server (CSAFS SAFS) Lessons Learned.pdf

1、Lessons Learned Entry: 1346Lesson Info:a71 Lesson Number: 1346a71 Lesson Date: 2003-07-15a71 Submitting Organization: GSFCa71 Submitted by: Mathew SchwallerSubject: ADEOS-II NASA Ground Network (NGN) Development and Early Operations - Central/Standard Autonomous File Server (CSAFS/SAFS) Lessons Lear

2、ned Description of Driving Event: The purpose of the Standard Autonomous File Server (SAFS) is to provide automated management of large data files without interfering with the assets involved in the acquisition of the data. It operates as a stand-alone solution, monitoring itself, and providing an a

3、utomated level of fail-over processing to enhance reliability. The successful integration of COTS products into the SAFS system has been key to its becoming accepted as a NASA standard resource for file distribution, and leading to its nomination for NASAs Software of the Year Award in 1999.Lesson(s

4、) Learned: 1. Match COTS tools to project requirements. Deciding to use a COTS product as the basis of system software design is potentially risky, but the potential benefits include quicker delivery, less cost, and more reliability in the final product. The following lessons were learned in the def

5、inition phase of the SAFS/CSAFS development.a71 Use COTS products and re-use previously developed internal products.a71 Create a prioritized list of desired COTS features.a71 Talk with local experts having experience in similar areas.a71 Conduct frequent peer and design reviews.a71 Obtain demonstrat

6、ion versions of COTS products.a71 Obtain customer references from vendors.a71 Select a product appropriately sized for your application.a71 Choose a product closely aligned with your projects requirements.a71 Select a vendor whose size will permit a working relationship.a71 Use vendor tutorials, doc

7、umentation, and vendor contacts during COTS evaluation period.Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-2. Test and prototype COTS products in the lab. The prototyping and test phase of the COTS evaluation allows problems to be identified as th

8、e system design to matures. These problems can be mitigated (often with the help and cooperation of the COTS vendor) well before the field-testing phase at which time it may be too costly or impossible to retrofit a solution. The following lessons were learned in the prototyping and test phase of th

9、e SAFS/CSAFS development.a71 Prototype your systems hardware and software in a lab setting as similar to the field environment as possible; simulate how the product will work on various customer platforms; model the field operations; develop in stages with ongoing integration and testinga71 Pass per

10、tinent information on to your customersa71 Accommodate your customers, where possible, by building in alternative optionsa71 Dont approve all requests for additional options by customers or new projects that come on line.a71 Select the best COTS components for product performance even if they are fr

11、om multiple vendors.a71 Consider the expansion capability of any COTS producta71 Determine if the vendors support is adequate for your requirements3. Install, operate and maintain the COTS field and lab components. The following lessons were learned in the installation and operation phase of the SAF

12、S/CSAFS development.a71 Personally perform on-site installations whenever possible.a71 Have support/maintenance contracts for hardware and software through development, deployment, and first year of operationa71 Create visual representations of system interactions where possible.a71 Obtain feedback

13、from end usersa71 Maintain the prototype system after deployment.a71 Select COTS products with the ability to do internal logginga71 Recommendation(s): 1. Match COTS tools to project requirements. Recommendation: It is essential to conduct a thorough evaluation of project requirements and to compare

14、 these requirements against COTS features and vendor capabilities.2. Test and prototype COTS products in the lab. Recommendation: Prototype COTS hardware and software in a lab setting as similar to the field environment as possible. Develop the prototype system in stages in the lab environment with

15、on-going integration and testing through the designs maturity.3. Install, operate and maintain the COTS field and lab components. Recommendation: It is essential to be physically present when performing on-site installations, and that support/maintenance contracts be in place for COTS hardware and s

16、oftware. It is also recommended Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-that a lab-based prototype system be maintained and staffed to permit the test of enhancements, upgrades and configuration changes to COTS software prior to field deliver

17、y of these upgrades.4. Evidence of Recurrence Control Effectiveness: N/ADocuments Related to Lesson: N/AMission Directorate(s): a71 Sciencea71 Space Operationsa71 Exploration SystemsAdditional Key Phrase(s): a71 Administration/Organizationa71 Communication Systemsa71 Computersa71 Ground Equipmenta71

18、 Ground Operationsa71 Information Technology/Systemsa71 Softwarea71 Test & VerificationAdditional Info: Approval Info: a71 Approval Date: 2003-07-28a71 Approval Name: Al Galloa71 Approval Organization: GSFCa71 Approval Phone Number: 301-286-3756Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-