The typical IPEP Table of Contents is shown below:

If any process in this document conflicts with any document in the NASA Online Directives Information System (NODIS), this document shall be superseded by the NODIS document.  Any reference document external to NODIS shall be monitored by the Process Owner for current versioning. 

1. Introduction
   1. Document Purpose - Describe the overall IV&V project and define the basic agreements for the partnership between the IV&V Team and the Project.
   2. Intended Audience - Describe the intended audience of the document.
   3. Document Organization - Describe the document’s organization and structure.
2. IV&V Overview
   1. IV&V Goals and Objectives - Describe at a high level what the IV&V efforts are trying to accomplish overall for the mission.
   2. IV&V Approach - Describe the IV&V approach that will be used for validation- and verification-related analyses. Include the artifact types generally required for specific analysis objectives.
   3. IV&V Scope and Focus - Provide the scope and focus of the project. Scope is the parts of the project that should be considered for IV&V assurance services.  Focus is the set of in-scope items that will receive IV&V assurance services.
3. Roles, Responsibilities, and Interfaces
   1. Roles, Responsibilities, and Interfaces - Describe the various roles, responsibilities, and interfaces for the project. These roles and responsibilities may be described in terms of personnel within the IV&V Program and personnel within the Project. Include formal and informal lines of communication.
   2. IV&V Team - Describe the IV&V team with their associated roles and responsibilities. At a minimum, there should be an IV&V Project Manager and IV&V analysts. Provide contact information for the IV&V leadership team.
   3. Project Personnel - Establish that the project will provide an IV&V Point of Contact (POC) for formal interactions between the IV&V Team and the Project. At a minimum, there should be a Project Manager, IV&V POC, and Chief SMA Officer (CSO). Provide contact information for the Project leadership team. 
4. IV&V Products and Communication and Reporting Methods - The IV&V Team generates various products and utilizes various communication and reporting methods/processes throughout the lifecycle. Describe the IV&V products and associated communication and reporting methods/processes.
   1. IV&V Products
      1. Analysis Conclusions - Briefly describe the process for documenting and communicating Assurance Conclusions. Provide a summary of the content to be included in the Assurance Conclusions. Assurance Conclusions should describe the analysis(es) performed and the results, including the associated assurance objectives, technical issues, risks, assumptions, forward work, and other caveats and limitations found or understood during the analysis(es).
      2. Analysis Reports - Briefly describe the process for documenting and communicating Analysis Reports. Provide a summary of the content to be included in the Analysis Reports. Analysis Reports should document the results of the analysis(es) performed and describe the Project artifacts used, a high-level description of the process, approach, tools used, results, and conclusions.)
      3. Technical Issue Memorandums - A TIM is the formal mechanism the IV&V Team uses to document one or more instances of defects (i.e., issues) identified within a development artifact, and subsequently formally communicates defects to the Project. Describe the processes for documenting, reviewing, and tracking TIMs to resolution. Include Impact and Severity Ratings with descriptions. See S3105: Guidelines for Writing IV&V TIMs ⁶¹³.
      4. Risks - Describe how the IV&V Team documents and tracks risks to resolution. Include how the Risks are formally communicated to the Project.
   2. IV&V Communication and Reporting Methods - Briefly describe the communication and reporting methods / processes (formal and informal) between the IV&V Team and the Project. 
      1. Item Tracking, Monitoring, and Escalation - Briefly describe the IV&V team’s process for tracking, monitoring, and escalating all data (including issues, risks, presentations, reports) to the Project.
      2. Lifecycle Review Presentations - Briefly describe the IV&V team’s approach to supporting formal Project milestone reviews and communicating the status of IV&V assurance efforts.  Include the reviews to be supported and the responsible IV&V POC. 
      3. Agency/Mission Directorate/Center Management Briefings - Briefly describe the IV&V team’s approach for providing status to the Project Stakeholders. Include the reviews and boards to be supported and the responsible IV&V POC.
      4. Routine Tag-ups - Briefly describe the IV&V team’s approach for supporting tag-ups (e.g., status, task requests, analysis results).
      5. Development Reviews and Working Groups Support - Briefly describe the IV&V team’s approach for supporting Project working groups or development reviews. Include how analysis results will be communicated through these forums.
      6. NASA Audit, Assessment, and Review Support - Briefly describe the IV&V team’s approach for supporting any NASA led review or audit functions.
5. IV&V Capability-Level Software Risk Assessment Results - Based on the mission objectives, provide the results and rationale of the capability-level risk assessment. For each Capability, include the Impact Score, Likelihood Score, and Risk Score.
6. IV&V Entity-Level Software Risk Assessment Results - Based on the Capability-Level Software Risk Assessment, provide the results of the software entity-level risk assessment, which extends the risk assessment to the software components (i.e., entities) that implement the system behaviors necessary to accomplish mission capabilities. For each Entity, include the Impact Score, Likelihood Score, and Risk Score.
7. IV&V Heritage Review  & Applicable Lessons Learned - Briefly describe the process for completing a heritage review and communicating the results.  Provide a summary of the content to be included. An IV&V heritage review is intended to survey prior IV&V projects for applicability of their results to the current project and to document references to applicable project results for use in planning and scoping activities, along with early IV&V analysis activities.  The process for completing an IV&V heritage review should include an assessment of the current project’s assertion of mission heritage, a survey of former IV&V projects for those missions and listing of missions with similar characteristics, and a survey of previous IV&V risk assessments, issues, risks, and lessons learned documented for each of these missions, where available, to determine their applicability to the current project.
   
   The purpose of the Heritage Review (HR) process is to learn from our collective experiences to maximize the value of IV&V’s contributions to NASA and other stakeholders. It also ensures that a promotion of faults do not cascade from one project to another through inherited or reuse of hardware interfaces and software. IV&V’s promotion of due diligence necessitates this review in an effort to promote knowledge that understanding may be gained of previous faults, past developer assumptions and on-orbit anomaly impacts. It is with this foundational visage a more complete system understanding of the new project can be obtained, leading to higher fidelity planning and scoping, analysis and ultimately assurance provided to the mission and Agency. A Heritage Review template is available at: https://www.nasa.gov/wp-content/uploads/2023/08/ivv-t2104-ver-basic-07-28-2022.docx?emrc=6e4e35 
   
   
8. Assurance Design - Define the assurance design. Include Assurance Objectives, an outline of focus areas, and the approaches considered for performing technical tasks. Provide a summary of each IV&V activity to be performed. The content for this section may be in a separate document or embedded directly into this one. Identify the relevant document(s) and include a link to the location. 
9. Reference Documentation - Identify titles, numbers, locations, and/or versions of documentation specified in the plan. Also, include any other relevant Project documentation.
10. Acronyms - In alphabetic order, define all abbreviations and acronyms used in the plan.
11. Fiscal Year <XX> IV&V Summary - Recommended.
    1. FY <XX> Assurance Goals and Objectives - Identify at a high level the assurance goals and objectives of the IV&V efforts for the applicable FY.
    2. FY <XX> Targeted External Milestones - List the key development project milestones. Depending on the development project, this may include milestones such as SRR, PDR, CDR, MRR, ORR, Launch Date, etc.
    3. FY<XX> Internal Milestones - List key internal milestones for the IV&V efforts. These will vary depending on the project, but may include mid-year risk assessment update, IV&V kickoff meeting, next year planning meeting with development Project, etc.
    4. FY <XX> Schedule - Provide a snapshot or summary of the IV&V Schedule for the applicable FY efforts.
       
    5. FY <XX> Risks - Provide a listing of perceived risks associated with the execution of the plan for the applicable year. This data only needs to be at the summary level as these risks will be managed via the IV&V Risk Review Board.
    6. FY <XX> IV&V Technical Reports - List specific technical reports planned for the fiscal year. These should be included in the FY <XX> Schedule. For relative dates, use working days unless there is a true requirement for calendar days to be used, e.g., a contractual or legal requirement.  Regardless, be specific as to the type of days intended.
       

NASA users find this in the Tools Library in the Software Processes Across NASA (SPAN) site of the Software Engineering Community in NEN. 

The list is informational only and does not represent an “approved tool list”, nor does it represent an endorsement of any particular tool.  The purpose is to provide examples of tools being used across the Agency and to help projects and centers decide what tools to consider.