REG NASA-LLIS-1467-2003 Lessons Learned Accident Investigations Software Tool Selection.pdf

1、Lessons Learned Entry: 1467Lesson Info:a71 Lesson Number: 1467a71 Lesson Date: 2003-08-31a71 Submitting Organization: JSCa71 Submitted by: David LengyelSubject: Accident Investigations/Software Tool Selection Abstract: A set of prioritized requirements should be considered in the decision process fo

2、r selecting an accident investigation software tool, or tools, to meet the varying needs of users.Description of Driving Event: Due to the urgent need to quickly select and implement a software tool to support the Columbia Accident Investigation Board (CAIB), the tool designated to be the single int

3、erface to the Board was selected based on brief demonstrations of the key features of various tools, including a generic collaborative environment tool already in use within the NASA community for non-sensitive data, and a NASA-developed mishap investigation specific tool. At the time, the collabora

4、tive environment tool was in the process of being expanded to include enhanced security for storing sensitive data, namely, two-factor- strong authentication. Two-factor-strong authentication was identified as an IT requirement, and it allowed remote access to sensitive data over the Internet - a fe

5、ature not offered by other alternative software solutions. The collaborative environment tool was selected because of the enhanced security with remote access, the built-in generic database capability, and the overall ease of use. A best- effort approach was undertaken to implement the enhanced secu

6、rity features ahead of schedule to meet the needs of the board. However, implementing the enhanced security features caused initial problems with normal operation of the tool, which resulted in delays in implementing the library and action tracking databases. In addition, while the ease of use of th

7、e tool was attractive, this came at the expense of advance functionality required by the CM and library support staff, which required custom software engineering to meet their needs causing delays in functionality and frustration on behalf of the end users. Provided by IHSNot for ResaleNo reproducti

8、on or networking permitted without license from IHS-,-,-Lesson(s) Learned: Different levels of software functionality are required by members of the investigation board and support staff (e.g., top-level board members vs. library support staff). A thorough review of software alternatives based on a

9、clear set of functional requirements should precede selection of a tool. Criteria, such as having a single user interface, ease of use, remote access, security, etc., should be prioritized and considered in the decision-making process to select a tool, or set of tools, to meet the needs of the users

10、Recommendation(s): Have representative members of an investigation board and representative end users of critical functionality (e.g., library support staff) review criteria for selection of a software tool, and the associated advantages and disadvantages, before tool selection. Specifically, consi

11、der the following “must have” requirements when selecting a library/data management software tool to support large-scale accident investigations: a71 implements IT security (e.g., single-factor vs. two-factor strong authentication) that is consistent with the level of safeguarding required and the i

12、nvestigations need for simplicity and rapid startup,a71 allows for easy storage and retrieval of very large data files that are an order of magnitude larger than what would currently be considered a big data file for every day use (e.g., by todays standard, allow for 100 to 300MB PowerPoint files),a

13、71 allows for secure remote access (consistent with an accident investigation boards needs) to stored files for download to local PCs by investigation board members while on travel or in a dispersed location environment,a71 has strong keyword search capability, preferably full text search capability

14、a71 has advanced capability adaptable to new functional requirements on-the-fly without requiring customized software engineering, yet still be easy to learn, easy to use, and compatible with other software applications,a71 is comprised of proven COTS software solutions (when possible),a71 incorpor

15、ates the functional capability to store, read, and manipulate all flavors of detailed 3-D engineering models/drawings in use at NASA, anda71 is adequately tested and implemented prior to future investigations for full buy-in by representative investigation board and support staff members.Evidence of

16、 Recurrence Control Effectiveness: TBD NASA ResponseDocuments Related to Lesson: Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Agency Contingency Action Plan for Space Flight OperationsMission Directorate(s): a71 Space Operationsa71 Exploration Sys

17、temsAdditional Key Phrase(s): a71 Accident Investigationa71 Administration/Organizationa71 Computersa71 Configuration Managementa71 Information Technology/Systemsa71 NASA Standardsa71 Policy & Planninga71 Safety & Mission Assurancea71 SecurityAdditional Info: Approval Info: a71 Approval Date: 2004-06-16a71 Approval Name: Ronald Montaguea71 Approval Organization: JSCa71 Approval Phone Number: 281-483-8576Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-