Documentation vs Model
Explain the end-to-end systems engineering process and its application to system (and lower level) requirements definition, allocation, validation, and verification.
Describe the purpose and scope of key documents required in the validation and verification processes, and describe typical errors committed.
Describe various methods of verification, and determine when they are appropriate and how they are used as part of a verification plan
Risk vs Functional list ( advice to designers )
Provide risk-based performance requirements that provide flexibility for the project Software Assurance and Software Safety activities.
Improve the risk, issue and finding reporting from the Space Systems Software Assurance and Software Safety organizations.
Add value for Software Assurance and Software Safety activities and demonstrate the importance of the Space Systems Software Assurance activities.
Software Assurances
Provide standard tools and services for Software Assurances activities on projects. ( MATLAB, LabView , TASTE Etc )
Provide measurable Software Assurance process improvement. ( Measure , Optimise, control )
Improve the use of data and metrics on all Space Systems Software Assurance activities. ( Measure with Scale, who provides Scale???? )
Focus Software Assurance activities on known software issues, including targeting Software Assurance and Software Safety research activities. ( Bring Domain Knowledge expert advice in to system, or use LLM for the same. but who will provide LLM?? )
Training and Tool set: Establish a Software Assurance services and tool sharing capability. Improve Software Assurance training and training requirements in the Safety and Mission Assurance Technical Excellence Program and across the agency.
Apply processes and techniques in a hands-on workshop associated with a system of interest. Identify applicable NASA, ECCS, DoD, and industry standards and lessons learned to support system verification decisions and activities.
