bannerd

Search

Search

Help

Page 1 of 4. Showing 36 results (0.02 seconds)

  1. 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 preparing
  2. 7.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 new
  3. 7.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 Description
  4. SWE-111 - Software Design Description

    1. Requirements 5.2.3.1 The Software Design Description shall include: [SWE-111]       a. Computer Software Configuration Item (CSCI)-wide design decisions/trade decisions.       b. CSCI architectural design.       c. CSCI decomposition and interrelationship between components:         (1) CSCI components
  5. SWE-058 - Detailed Design

    12 1. Requirements 3.2.3 The project shall develop, record, and maintain a detailed design based on the software architectural design … to the safety-critical aspects of the software. 2. Rationale The detailed design, as an extension of the architectural design, provides detailed descriptions
  6. SWE-056 - Document Design

    1. Requirements 3.2.1 The project shall document and maintain the software design. 1.1 Notes The requirement for the content of a Software Design Description document and an interface design description document are defined in Chapter 5 [of NPR 7150.2, NASA Software Engineering Requirements, section 5.2.3
  7. SWE-057 - Software Architecture

    12 1. Requirements 3.2.2 The project shall transform the allocated and derived requirements into a documented software architectural design … early decisions about high-level design, and allows reuse of design components and patterns between projects. 1.2 Applicability Across Classes Classes C through
  8. SWE-023 - Software Safety

    that safety is designed into developed or acquired software, and that safety is maintained throughout the software and system life cycle. NASA-STD-8719.13 "specifies … that causes, controls, mitigates, or contributes to hazards. Identify and clearly mark software safety design features and methods in design documents
  9. 7.09 - Entrance and Exit Criteria

    strategy. Technical plans to achieve next phase. Conceptual life cycle. Preliminary requirements. Draft cost and schedule estimates. Conceptual system design … defined and stated, unambiguous, and internally consistent. Conceptual system design meets mission requirements, and the various system elements are compatible
  10. SWE-037 - Software Milestones

    for reviewing and auditing contractor progress were in place. cd smproj sdr sa pr sre sse srr swrr ansc asc bsc bnsc csc cnsc dsc dnsc design g f esc ll