1 / 70

GLPR 7150.1A

GLPR 7150.1A. GRC Software Engineering Requirements 1/29/2013. Training Objectives. recognize when to apply this GLPR navigate through the GLPR document, processes and templates recognize their role and responsibilities and the roles of others involved in implementing this GLPR

kmedrano
Download Presentation

GLPR 7150.1A

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GLPR 7150.1A GRC Software Engineering Requirements 1/29/2013

  2. Training Objectives • recognize when to apply this GLPR • navigate through the GLPR document, processes and templates • recognize their role and responsibilities and the roles of others involved in implementing this GLPR • find resources through Software@Glenn • After this presentation, GLPR users will be able to: GLPR 7150.1A

  3. Accessing the GLPR • Visit Software@Glenn • Go to http://software.grc.nasa.gov OR… • Type “software” in the transporter from the WING page • Navigate to “Controlling Documents & Authority” using the menu on the left side of the page • Scroll down to “Glenn Research Center Controlling Documents” and the latest GLPR revision is the first document in the list • Note: The document is hosted on the knowledgeshare website, which has limited access to users outside the NDC NASA domain.

  4. How Do I Know I Am in Compliance? GRC Space Flight Project Document Hierarchy NPRs define what we must do … GLPR 7150.1A

  5. How Do I Know I Am in Compliance? • NASA Procedural Requirements (NPRs) • Issued from NASA HQ http://nodis.hg.nasa.gov/ • Not a recent phenomena • Defined in the form of shall statements NPRs are… NPR7123.1 Systems Engineering Processes & Reqts NPR7120.5 Space Flight Prog/ProjReqts NPR7120.8 NASA Research and Technology Prog/ProjReqts NPR7120.7 NASA IT and Institutional Infrastructure Prog/ProjReqts NPR7150.2 Software Engineering Reqts GLPR 7150.1A

  6. How Do I Know I Am in Compliance? • In contract vernacular, the shallsare the true requirements of the NPRs • Significant findings against the Center will require a corrective action plan from the Center to HQ OCE with progress reporting Why should I care? GRC Space Flight Project Document Hierarchy GLPR 7150.1A

  7. Glenn Procedural Requirements (GLPRs) Is there a process for this? Yes… GLPRs are documents that define how we will do what we do. GLPR s GLPR 7120.5.10 GRC Space Flight Projects Formulation & Implementation Requirements GLPR 7150.1A

  8. Glenn Procedural Requirements (GLPRs) • Center Management • Space Flight Program/Project Management • Engineering • Safety and Mission Assurance • Software Engineering GLPR s • There are GLPRs for: GLPR 7150.1A

  9. 4.0 Engineering Practices • This training will focus on GLPR 7150.1A • Training for the other GLPRs is available GLPR 7150.1 Software Engineering Requirements GLPR 7150.1A

  10. GRC Engineering Technical Authority Responsible for establishing, maintaining, and implementing those design processes, specifications, rules, and best practices that are necessary at the Center to ensure the design, development, and operation of space flight systems, which fulfill all their performance requirements. GLPR 7150.1A

  11. GRC Engineering Technical Authority GLPR 7150.1A

  12. Software Technical Authority • What is the role of the Software Technical Authority? • Provide guidance and advisement on meeting NPR 7150.2A requirements • Particularly on P(Center) requirements • Approve a project’s Compliance Matrix • Approve deviations and waivers to NPR 7150.2A requirements • Review and approve software classifications • Meet with the Software Project Lead at the start and end of the project • Depending on the project, interim meetings may also be held ✔ GLPR 7150.1A

  13. GLPR 7150.1A Applicability, Effectivity • Section P.2: • This Glenn Procedural Requirement (GLPR) applies to all NASA GRC Space, Aeronautics, and Research programs, projects, subprojects, and tasks that are developing or acquiring software. • This includes infrastructure related (Facility control software, ODIN support software, etc.) software (code) efforts. • This GLPR also applies to the development of complex electronics up to the test procedures if the complex electronics has a processor in it. • The requirements of this GLPR are applicable to existing programs and projects started after the initial date of this GLPR. GLPR 7150.1A

  14. GLPR 7150.1A Usage • Chapter 1 – Introduction • Projects are required to comply with NPR 7150.2 • Records Management requirements • Chapter 2 – Responsibilities • GRC Program/Project/Subproject/Task Managers • Responsible for ensuring adherence to NPRs and GLPRs • Software Project Lead • Leads the software effort; ensures NPR and GLPR in plans • Software Team • Carries out the Software Plan • Assurance Team • Responsible for GLPR 8739.1 implementation on a project • Software Technical Authority • Provides guidance to projects for NPR compliance • Chief Engineer Office • Responsible for process development, implementation, audits GLPR 7150.1A

  15. GLPR 7150.1A Usage • Chapter 3 - Project and Software Life-cycles • NASA Project Life-cycle • Software Life-cycle • Approved Life-cycles • Waterfall • Evolutionary • Spiral • Agile Software@Glenn provides links to further details GLPR 7150.1A

  16. GLPR 7150.1A Usage • Chapter 4 – Project Life-cycles • Section 4.1 - Formulation • Determine classification of the software (4.1.1) • Overview on next slide; more detailed descriptions are in the backup slides • NPR 7150.2A Appendix E contains the full definitions • NPR 7150.2A Handbook Classification Tool can assist • https://swehb.nasa.gov/display/7150/7.2+-+Classification+Tool+and+Safety-Critical+Assessment+Tool • Get the classification approved by the SW Technical Authority (TA) and verified by Software Assurance (SA) • Determine if the software is safety-critical per NASA-STD-8739.8 • Work with Software Assurance • The SEPG provides the following process and template on Software@Glenn • GRC-SW-7150.3 – Software Project Planning • GRC-SW-TPLT-SMP– Software Management Plan Template GLPR 7150.1A

  17. GLPR 7150.1A Usage • 8 Software Classifications defined in NPR 7150.2A • Identified by the letters A through H • A-E: Engineering, Research • F-H: Business and IT Infrastructure • Detailed definitions are provided in the backup slides • Classification + Safety Criticality = Degree to which NPR 7150.2A requirements need to be met GLPR 7150.1A

  18. GLPR 7150.1A Usage • Chapter 4 – Project Life-cycles • Section 4.1 - Formulation • Determine Applicability of NPR 7150.2 Requirements (4.1.2) • See the Requirements Mapping Matrix (Appendix C) • Classes A and B are not included since they are required to meet all requirements • Legend: • X – Required • P(Center) – non-null subset required • Blank – not required • Develop NPR 7150.2A Compliance Matrix • Templates for each software class and safety-criticality available from Software@Glenn • Document how and where the requirements will be met GLPR 7150.1A

  19. GLPR 7150.1A Usage • What is P(Center)??? • From NPR 7150.2A • Software Classification (A, B,…) determine which NPR requirements apply • Appendix D of NPR 7150.2A is a Requirements Mapping Matrix • Use it to determine which requirements apply to a given classification • Appendix C of the GLPR captures this information and organizes the requirements by project phase GLPR 7150.1A

  20. Helpful Resources • Compliance matrices already exist for each class of software and safety-criticality, and help you determine what is needed once you’ve determined the software class • http://software.grc.nasa.gov/cda.html • NASA Software Engineering Handbook provides requirements rationale, guidance, small project guidance, resources, and lessons learned for each requirement • https://swehb.nasa.gov/display/7150/Book+B.+7150+Requirements+Guidance

  21. GLPR 7150.1A Usage • Chapter 4 – Project Life-cycles • Section 4.1 - Formulation • Document Deviations and Waivers (4.1.3) • Use GLPR 7120.5.20, “GRC Project Deviation/Waiver Process” for deviations and waivers • Center or HQ OCE TA needs to approve • Tailor the requirements to provide necessary level of rigor • Document reason for tailoring in the Compliance Matrix • Have SW TA approve Compliance Matrix GLPR 7150.1A

  22. GLPR 7150.1A Usage • Chapter 4 – Project Life-cycles • Section 4.1 - Formulation • Review Compliance Matrix with Technical Authority (4.1.4) • Software TA documents acceptance and approval of the Compliance Matrix • Includes decisions on waivers, deviations, P(Center) decisions • Implementation of P(Center) requirements shall be fully documented • Contributes to a Center-wide approach • Useful for future projects • Resource for TAs to consult GLPR 7150.1A

  23. GLPR 7150.1A Usage • Chapter 4 – Project Life-cycles • Section 4.1 - Formulation • Planning (4.1.5) • See Appendices C.1 and C.2 for requirements • Develop plans for the project • Plans may be standalone documents or combined • Which plans to develop depends on: • Software Classification • Software Safety Criticality GLPR 7150.1A

  24. GLPR 7150.1A Usage • Appendix C.1 Management GLPR 7150.1A

  25. GLPR 7150.1A Usage • Appendix C.2 Planning GLPR 7150.1A

  26. GLPR 7150.1A Usage • Appendix C.2 Planning (continued) GLPR 7150.1A

  27. GLPR 7150.1A Usage • Appendix C.2 Planning (continued) GLPR 7150.1A

  28. GLPR 7150.1A Usage • SEPG provides the following processes and templates • Available on Software@Glenn GLPR 7150.1A

  29. GLPR 7150.1A Usage • Chapter 4 – Project Life-cycles • Section 4.1 - Formulation • Plan Acquisition Activities (4.1.6) • See Appendix C.3 for requirements • Plan for software acquisitions including off-the-shelf software • The SEPG provides the following processes on Software@Glenn • GRC-SW-7150.14 – Software Acquisition Statement of Work Guideline • GRC-SW-7150.15 – Software Acquisition Planning GLPR 7150.1A

  30. GLPR 7150.1A Usage • Appendix C.3 Acquisition GLPR 7150.1A

  31. GLPR 7150.1A Usage • Chapter 4 – Project Life-cycles • Section 4.1 - Formulation • Requirements (4.1.7) • See Appendix C.4 for requirements • Develop software requirements from higher level requirements • Perform inspections and reviews • Incorporate safety, system and software specific development processes into the requirements • For safety critical software, perform safety analysis on functional requirements • Start planning for acceptance tests, operations, maintenance, and retirement • Verify/document bidirectional traceability to higher level requirements • Manage the requirements as the project progresses GLPR 7150.1A

  32. GLPR 7150.1A Usage • Appendix C.4 Requirements GLPR 7150.1A

  33. GLPR 7150.1A Usage • SEPG provides the following processes and templates • Available on Software@Glenn GLPR 7150.1A

  34. GLPR 7150.1A Usage • Chapter 4 – Project Life-cycles • Section 4.2 - Implementation • Design (4.2.1) • See Appendix C.5 for requirements • Transform system and software level requirements into an architectural design • Alternate architectures may be developed • Perform rapid prototyping trade studies • Select an optimal solution • Further refine the architectural design into a detailed design • Write Software system level test plans and procedures • Perform inspections and reviews • Verify and maintain bidirectional traceability • The SEPG provides the following templates on Software@Glenn • GRC-SW-TPLT-IDD – Interface Design Description Template • GRC-SW-TPLT-SDD – Software Design Description Template 4.2.1 Design 4.2.2 Coding & Test 4.2.3 Release, Maintenance, and Retirement GLPR 7150.1A

  35. GLPR 7150.1A Usage • Appendix C.5 Design GLPR 7150.1A

  36. GLPR 7150.1A Usage • Chapter 4 – Project Life-cycles • Section 4.2 - Implementation • Coding & Test (4.2.3) • See Appendix C.6 for requirements • Code the software • Devise, perform unit-level and integration tests • Document defects found and track to closure • Document changes to requirements, design and code resulting from fixed defects • Finalize, release integration and software system-level test procedures • Perform V&V of software models, sims, and analysis tools to be used to V&V the software • Verify and maintain traceability between design and code • Document evaluation of test results in the test report • For safety critical software, demonstrate, record, and report on safety functions • Verify and maintain bidirectional traceability • The SEPG provides the following templates on Software@Glenn • GRC-SW-TPLT-STP – Software Test Plan Template • GRC-SW-TPLT-STPr– Software Test Procedure Template • GRC-SW-TPLT-STR – Software Test Results Template 4.2.1 Design 4.2.2 Coding & Test 4.2.3 Release, Maintenance, and Retirement GLPR 7150.1A

  37. GLPR 7150.1A Usage • Appendix C.6 Code & Test GLPR 7150.1A

  38. GLPR 7150.1A Usage • Appendix C.6 Code & Test (continued) GLPR 7150.1A

  39. GLPR 7150.1A Usage • Chapter 4 – Project Life-cycles • Section 4.2 - Implementation • Release, Maintenance, and Retirement (4.2.3) • See Appendix C.7 for requirements • Perform customer demonstrations and tests per the software test plans • Document defects found and track to closure • Document changes to requirements, design and code resulting from fixed defects • Record and store the released version • Provide a version description document and other documents needed for operations and maintenance • Carry out plans for software operations; implement the maintenance plan • Plan for software retirement • Record lessons learned • The SEPG provides the following templates on Software@Glenn • GRC-SW-TPLT-SMntP – Software Maintenance Plan Template • GRC-SW-TPLT-SUM– Software User Manual Template • GRC-SW-TPLT-SVD – Software Version Description Template 4.2.1 Design 4.2.2 Coding & Test 4.2.3 Release, Maintenance, and Retirement GLPR 7150.1A

  40. GLPR 7150.1A Usage • Appendix C.7 Release & Maintenance GLPR 7150.1A

  41. GLPR 7150.1A Usage • Chapter 4 – Project Life-cycles • Section 4.3 – Supporting Life-cycle Activities • Configuration Management (4.3.1) • See Appendix C.10 for requirements • Purpose is to establish and maintain the integrity of work products • The SEPG provides the following process and template on Software@Glenn • GRC-SW-7150.9 – Software Configuration Management • GRC-SW-TPLT-SCMP– Software Configuration Management Plan Template • Acquisition (4.3.2) • See Appendix C.3 for requirements • Purpose is to conduct supplier management, complete activities for product acceptance, complete activities for transitioning acquired products into project use • The SEPG provides the following processes on Software@Glenn • GRC-SW-7150.4 – Software Project Monitoring and Control • GRC-SW-7150.15 – Software Acquisition Planning GLPR 7150.1A

  42. GLPR 7150.1A Usage • Appendix C.10 Configuration Management • CI – Configuration Item GLPR 7150.1A

  43. GLPR 7150.1A Usage • Chapter 4 – Project Life-cycles • Section 4.3 – Supporting Life-cycle Activities • Off-the-shelf (4.3.3) • See Appendix C.3 for requirements • Purpose is to ensure successful acquisition of COTS/GOTS/MOTS products • Commercial/Government/Modified Off-the-shelf • Document project technical requirements for the OTS software • Validated OTS software to the same level of confidence as developed software • Plan for follow on support and maintenance • Ensure licensing and property rights • Document OTS software to the same level as developed software • Risk Management (4.3.4) • See Appendix C.8 for requirements • Purpose is to identify potential problems and manage their mitigation • Refer to NPR 8000.4, Agency Risk Management Procedural Requirements GLPR 7150.1A

  44. GLPR 7150.1A Usage • Appendix C.8 Risk Management GLPR 7150.1A

  45. GLPR 7150.1A Usage • Chapter 4 – Project Life-cycles • Section 4.3 – Supporting Life-cycle Activities • Verification and Validation (4.3.5) • See Appendix C.9 for requirements • Purpose is to ensure fulfillment of requirements in the product and the right product is built • Refer to GLPR 7123.22, Product Verification and/or Validation • The SEPG provides the following process on Software@Glenn • GRC-SW-7150.12 – Formal Inspection and Peer Review • Project Monitoring and Control (4.3.6) • See Appendix C.11 for requirements • Purpose is to provide an understanding of the project’s progress so appropriate corrective action can be taken to ensure integrity of work products • The SEPG provides the following process on Software@Glenn • GRC-SW-7150.4 – Software Project Monitoring and Control GLPR 7150.1A

  46. GLPR 7150.1A Usage • Appendix C.9 Verification & Validation • Appendix C.11 Project Monitoring and Control GLPR 7150.1A

  47. GLPR 7150.1A Usage • Chapter 4 – Project Life-cycles • Section 4.3 – Supporting Life-cycle Activities • Metrics (4.3.7) • See Appendix C.12 for requirements • Purpose is to develop and utilize a measurement capability to support management information needs • Project metrics to address Software Progress, Software Quality, Software Functionality, and Requirements Volatility are required • Projects are to record project characteristics and submit them to the software inventory • The SEPG provides the following processes and template on Software@Glenn • GRC-SW-7150.7 – Managing the Measurement of Software Process and Product • GRC-SW-7150.8 – Performing the Measurement of Software Process and Product • GRC-SW-TPLT-MMMS – Master Monthly Metrics Spreadsheet GLPR 7150.1A

  48. GLPR 7150.1A Usage • Appendix C.12 Metrics GLPR 7150.1A

  49. GLPR 7150.1A Usage • Chapter 5 – Process Improvement • Section 5.1 – Determine Changes • Project Manager, Project Chief Engineer, Lead Systems Engineer, Software Project Lead are to analyze defined process documents and work products resulting from this GLPR and suggest improvement changes • Defined process – A process used by a project that is the result of the tailoring of a standard process • Section 5.2 – Submit Feedback • Use the feedback on Software@Glenn to provide feedback form the analysis performed above. Optionally, meet with the SEPG to discuss the feedback. • Use the CPAR System to provide comments/feedback on this GLPR GLPR 7150.1A

  50. GLPR 7150.1A Appendices • Appendix A – Definitions • Appendix B – Acronyms • Appendix C – Requirements Mapping Matrix • Maps NPR 7150.2A requirements to software classes • Organized into process areas • Class A, B, and requirement wording omitted GLPR 7150.1A

More Related