NASA Logo, National Aeronautics and Space Administration
Intelligent Systems Division Banner

Phase A: Concept and Technology Development

During the Concept and Technology Development, the project team is formed to fully develop a baseline concept of operations and begin or assume responsibility for the development of the needed software technologies. This work, along with interactions with customers and other potential stakeholders, helps with the baselining of an operations concept and high-level project requirements. These activities culminate in a Project Plan and, if appropriate, a System Requirements Review (SRR). A list of common project documentation for this phase is provided below.

Common Project Planning technical activities:

  • Develop preliminary system-level (and lower-level, as needed) requirements.
  • Develop and document a preliminary or baseline Concept of Operations (including key risk drivers and mitigation options and mission descope options).
  • Prior to the project independent life-cycle reviews for this phase, conduct internal reviews as defined by the project’s planned software assurance activities.
  • Plan, prepare for, and support the project independent life-cycle reviews for this phase in accordance with NPR 7123.1, Center practices, and the requirements of this document.
  • As early as practical, prepare and finalize required work agreements.
  • Prepare a preliminary Project Plan that follows the appropriate template provided by the Code TI Project Asset Library.

Common Project Planning Documentation

  • Project Plan
  • Concept of Operations
  • Customer Agreements (e.g., Intercenter Task Agreements, Program Plans, Mission Plans)
  • Minutes and Agendas from Project Planning meetings

Common Requirements Definition technical activities:

  • Baseline the system-level requirements in a Requirements Specification document and develop the subsystem and lower-level technical requirements leading to the PDR baseline.
  • Develop and document a baseline Configuration Management Plan.
  • Identify any risk drivers (and proposed mitigation plans for each risk).
  • Develop a list of descope options.
  • Prior to the project independent life-cycle reviews for this phase, conduct internal reviews as defined by the project’s planned software assurance activities.
  • Plan, prepare for, and support the project independent life-cycle reviews for this phase in accordance with NPR 7123.1, Center practices, and the requirements of this document.
  • Complete and obtain approval of the Project Plan that follows the appropriate template provided by the Code TI Project Asset Library. See Page TBD for a list of common Project Documentation assets and their required maturity by phase.

Common Requirements Documentation

Common Phase A Transition Reviews

Common Phase Transition Reviews

  • Preliminary Design Review



First Gov logo
NASA Logo - nasa.gov