Page 1 of 4. Showing 36 results (0.008 seconds)
7.07 - Software Architecture Description
requirements associated with software architecture and design preparation (e.g., SWE-056, SWE-057, SWE-058, SWE-059, and SWE-111.) According to IEEE Standard 1471 … , embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution." In preparing7.12 - Qualification of Flight Software
in the proposal phase when the qualification approach is defined: Continue it during the design and development phase where detailed qualification planning … . Resources 5.1 Tools sra records sa sre sm cm design frr orr pi pm c-i v-v prod_desc sar Migration of unmigrated content due to installation of a newSWE-054 - Corrective Action for Inconsistencies
with expert and experienced programmers, each new software program presents new technical challenges. Changing methodology and requirements during the design … with preferred software review practices, identify software that is mission critical (for which staff must participate in major design reviews, walk throughs and reviewSWE-134 - Safety Critical Software Requirements
(requirements, design elements, code components, and interfaces) are uniquely identified as safety critical. n. Incorporate requirements in the coding methods … is determined by the project and conditions designed into the safety-critical system. Safety-critical software commands are commands that can cause or contribute7.08 - Maturity of Life Cycle Products at Milestone Reviews
Dictionary P B Software Design Description (Architectual Design) B U U Software Design Description (Detailed Design) P B U Interface Design DescriptionSWE-059 - Bidirectional Traceability Between Software Requirements and Software Design
1. Requirements 3.2.4 The project shall perform and maintain bidirectional traceability between the software requirements and the software design. 1.1 Notes … not apply to off-the-shelf software for these classes. 2. Rationale Software design is created based on the software requirements and some assuranceSWE-060 - Coding Software
12 1. Requirements 3.3.1 The project shall implement the software design into software code. 1.1 Notes NPR 7150.2, NASA Software … implementation consists of implementing the requirements and design into code, data, and documentation. Software implementation also consists of following codingSWE-084 - Configuration Audits
, the requirements specified in its functional baseline documentation approved at the Preliminary Design Review (PDR) and Critical Design Review (CDR). FCAs … . "A review of all approved changes. "A review of updates to previously delivered documents. "A sampling of design review outputs. "A comparison of codeSWE-082 - Authorizing Changes
implemented change. Capturing all CIs affected by the change (requirements, design, tests, source code, documentation, etc.). Using the features of CM tools … ." cd smproj procedure pr sre ansc asc bsc bnsc csc cm dsc design g f esc ll h pi pm c-i v-v Migration of unmigrated content due to installationSWE-083 - Status Accounting
ansc asc bsc bnsc csc cnsc cm dsc design g f esc h pi pm c-i v-v pm-c Migration of unmigrated content due to installation of a new plugin
