Pandoc Transformation Project

This is an example project to use Pandoc to translate files to rst and later to sphinx-needs.

Contents

• Copyright notice
• Acknowledgement
• Derivative works
• Document distribution
• Change requests
• Trademark notice
• Document history
• Table of contents
• List of Figures
  • List of Tables
• 1. Introduction
  • 1.1. Scope
  • 1.2. Terminology
  • 1.3. Abbreviations
• 2. Statement of compliance
• 3. Process capability determination
  • 3.1. Process reference model
    • 3.1.1. Primary life cycle processes category
    • 3.1.2. Supporting life cycle processes category
    • 3.1.3. Organizational life cycle processes category
  • 3.2. Measurement framework
    • 3.2.1. Process capability levels and process attributes
    • 3.2.2. Process attribute rating
      • 3.2.2.1. Rating scale
    • 3.2.3. Rating and aggregation method
    • 3.2.4. Process capability level model
  • 3.3. Process assessment model
    • 3.3.1. Assessment indicators
      • Assessment Indicators
      • 1. Base practices (BP), applying to capability level 1
      • 2. Generic practices (GP), applying to capability levels 1 to 5
    • 3.3.2. Understanding information Items and work products
      • 3.3.2.1. Information items versus work products
      • information item
      • work product
      • 3.3.2.2. Types of work products
    • 3.3.3. Understanding the level of abstraction of a PAM
    • 3.3.4. Why a PRM and PAM are not a lifecycle model or development process blueprint
• 4. Process reference model and performance indicators (Level 1)
  • 4.1. Acquisition process group (ACQ)
    • 4.1.1. ACQ.4 Supplier Monitoring
  • 4.2. Supply process group (SPL)
    • 4.2.1. SPL.2 Product Release
  • 4.3. System engineering process group (SYS)
    • 4.3.1. SYS.1 Requirements Elicitation
    • 4.3.2. SYS.2 System Requirements Analysis
    • 4.3.3. SYS.3 System Architectural Design
    • 4.3.4. SYS.4 System Integration and Integration Verification
    • 4.3.5. SYS.5 System Verification
  • 4.4. Software engineering process group (SWE)
    • 4.4.1. SWE.1 Software Requirements Analysis
    • 4.4.2. SWE.2 Software Architectural Design
    • 4.4.3. SWE.3 Software Detailed Design and Unit Construction
    • 4.4.4. SWE.4 Software Unit Verification
    • 4.4.5. SWE.5 Software Component Verification and Integration Verification
    • 4.4.6. SWE.6 Software Verification
  • 4.5. Validation process group (VAL)
    • 4.5.1. VAL.1 Validation
  • 4.6. Machine Learning Engineering process group (MLE)
    • 4.6.1. MLE.1 Machine Learning Requirements Analysis
    • 4.6.2. MLE.2 Machine Learning Architecture
    • 4.6.3. MLE.3 Machine Learning Training
    • 4.6.4. MLE.4 Machine Learning Model Testing
  • 4.7. Hardware Engineering process group (HWE)
    • 4.7.1. HWE.1 Hardware Requirements Analysis
    • 4.7.2. HWE.2 Hardware Design
    • 4.7.3. HWE.3 Verification against Hardware Design
    • 4.7.4. HWE.4 Verification against Hardware Requirements
  • 4.8. Supporting process group (SUP)
    • 4.8.1. SUP.1 Quality Assurance
    • 4.8.2. SUP.8 Configuration Management
    • 4.8.3. SUP.9 Problem Resolution Management
    • 4.8.4. SUP.10 Change Request Management
    • 4.8.5. SUP.11 Machine Learning Data Management
  • 4.9. Management process group (MAN)
    • 4.9.1. MAN.3 Project Management
    • 4.9.2. MAN.5 Risk Management
    • 4.9.3. MAN.6 Measurement
  • 4.10. Process improvement process group (PIM)
    • 4.10.1. PIM.3 Process Improvement
  • 4.11. Reuse process group (REU)
    • 4.11.1. REU.2 Management of Products for Reuse
• 5. Process capability levels and process attributes
  • 5.1. Process capability level 0: Incomplete process
  • 5.2. Process capability Level 1: Performed process
    • 5.2.1. PA 1.1 Process performance process attribute
  • 5.3. Process capability Level 2: Managed process
    • 5.3.1. PA 2.1 Process performance management process attribute
    • 5.3.2. PA 2.2 Work product management process attribute
  • 5.4. Process capability Level 3: Established process
    • 5.4.1. PA 3.1 Process definition process attribute
    • 5.4.2. PA 3.2 Process deployment process attribute
  • 5.5. Process capability Level 4: Predictable process
    • 5.5.1. PA 4.1 Quantitative analysis process attribute
    • 5.5.2. PA 4.2 Quantitative control process attribute
  • 5.6. Process capability Level 5: Innovating process
    • 5.6.1. PA 5.1 Process innovation process attribute
    • 5.6.2. PA 5.2 Process innovation implementation process attribute
• Annex A Conformity statements
  • Annex A.1 Introduction
  • Annex A.2 Conformance to the requirements for process reference models
    • Clause 5.3, “Requirements for process reference models”
    • Clause 5.4, “Process descriptions”
  • Annex A.3 Conformance to the requirements for process assessment models
    • Clause 6.1, “Introduction”
    • Clause 6.2, “Process assessment model scope”
    • Clause 6.3, “Requirements for process assessment models”
    • Clause 6.3.1, “Assessment indicators”
    • Clause 6.3.2, “Mapping process assessment models to process reference models”
    • Clause 6.3.3, “Expression of assessment results”
  • Annex A.4 Conformance to the requirements for measurement frameworks
• Annex B Information Item Characteristics
• Annex C Key concepts and guidance
  • Annex C.1 The “Plug-in” concept
  • Annex C.2 “Element”, “Component”, and “Unit”
  • Annex C.3 Integration of Machine Learning Engineering Processes
  • Annex C.4 Example of an ML Architecture
  • Annex C.5 Traceability and consistency
  • Annex C.6 “Agree” and “Summarize and Communicate”
  • Annex C.7 Key Changes in Automotive SPICE 4.0
    • Terminology – “Measure” vs. “Metric”
    • Terminology – “Affected Party” (Level 1) vs. “Involved Party” (Level 2)
    • Terminology – “Verification” instead of “Testing”
• Annex D Reference standards
• Test of rst Syntax
  • With an empty comment
  • Syntax which works fine
  • Quoted Block
  • List with Block Quote
  • List table with Block Quote