<!-- تعليمات للنموذج الذكي: قم بتعبئة العناصر النائبة [ أضف التفاصيل... ] بناءً على سياق المشروع.

تعليمات الأقسام بالتفصيل:
- جمع المتطلبات وتحليلها: قدّم بيانات شاملة ودقيقة لكافة الحقول المطلوبة في هذا القسم.
- تصنيف وتوثيق المتطلبات: قدّم بيانات شاملة ودقيقة لكافة الحقول المطلوبة في هذا القسم.
- تحديد الأولويات والمقاييس: قدّم بيانات شاملة ودقيقة لكافة الحقول المطلوبة في هذا القسم.
- تتبع المتطلبات وإدارة التكوين: قدّم بيانات شاملة ودقيقة لكافة الحقول المطلوبة في هذا القسم.
- استراتيجية التحقق والاعتماد: قدّم بيانات شاملة ودقيقة لكافة الحقول المطلوبة في هذا القسم.
-->

<h3 align="left">{{اسم_الشركة}}</h3>
<h2 align="left">{{اسم_المشروع}} - {{معرف_المشروع}}</h2>
<h1 align="center">خطة إدارة المتطلبات</h1>

| **تاريخ الإعداد:** {{التاريخ_الحالي}} | **مدير المشروع:** {{اسم_مدير_المشروع}} | **تم الإعداد بواسطة:** {{تم_الإعداد_بواسطة}} |
| ---: | ---: | ---: |

---

## 1. جمع المتطلبات وتحليلها

**تقنيات استدراج وجمع المتطلبات:**
[ أضف التفاصيل... ]

**تحليل وتفصيل المتطلبات:**
[ أضف التفاصيل... ]

**إشراك المعنيين في المتطلبات:**
[ أضف التفاصيل... ]

---

## 2. تصنيف وتوثيق المتطلبات

**تصنيف وتبويب المتطلبات:**
[ أضف التفاصيل... ]

**معايير توثيق المتطلبات:**
[ أضف التفاصيل... ]

---

## 3. تحديد الأولويات والمقاييس

**مخطط تحديد أولويات المتطلبات:**
[ أضف التفاصيل... ]

**مقاييس أداء المتطلبات:**
[ أضف التفاصيل... ]

---

## 4. تتبع المتطلبات وإدارة التكوين

**هيكلية وسمات التتبع:**
[ أضف التفاصيل... ]

**إدارة تكوين وضبط المتطلبات:**
[ أضف التفاصيل... ]

---

## 5. استراتيجية التحقق والاعتماد

**منهجية التحقق من المتطلبات:**
[ أضف التفاصيل... ]

**استراتيجية الاعتماد والقبول النهائي:**
[ أضف التفاصيل... ]

---

### الاعتماد والموافقات

| الدور | الاسم | التوقيع | التاريخ |
| ---: | ---: | ---: | ---: |
| **كبير محللي الأعمال** | {{اسم_كبير_محللي_الأعمال}} | _______________________ | [.... -.... -.... ] |
| **مدير المشروع** | {{اسم_مدير_المشروع}} | _______________________ | [.... -.... -.... ] |
| **مالك المنتج / العميل** | {{اسم_مالك_المنتج}} | _______________________ | [.... -.... -.... ] |
---

<div align="left" style="margin-top: 20px; font-size: 12px; color: #7f8c8d;">
  <span>سجل التدقيق الإلكتروني: Hash SHA256: {{رمز_تجزئة_التدقيق_SHA256}}</span> <br>
 <strong>القالب:</strong> خطة إدارة المتطلبات | <strong>المرجع:</strong> PMO-04.02.02 <br>
 <i>تم التوليد في: {{الطابع_الزمني_الحالي}}، بواسطة <a href="https://github.com/fakhruldeen/Tasleemat/" style="color: #7f8c8d;">تسليمات</a></i>
</div>

</div>

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://tasleemat.pmo/schemas/completed/PMO-04.02.02.schema.json",
  "title": "Completed REQUIREMENTS MANAGEMENT PLAN Data Contract",
  "description": "Additive structural schema validating completed REQUIREMENTS MANAGEMENT PLAN artifact data payloads (PMO-04.02.02).",
  "type": "object",
  "properties": {
    "artifact_id": {
      "type": "string",
      "const": "PMO-04.02.02"
    },
    "metadata": {
      "type": "object",
      "properties": {
        "project_name": {
          "type": "string",
          "minLength": 1
        },
        "project_code": {
          "type": "string"
        },
        "date_prepared": {
          "type": "string",
          "format": "date"
        },
        "project_manager": {
          "type": "string",
          "minLength": 1
        },
        "prepared_by": {
          "type": "string",
          "minLength": 1
        },
        "version": {
          "type": "string"
        },
        "status": {
          "type": "string",
          "enum": [
            "draft",
            "baselined",
            "in_review",
            "approved"
          ]
        }
      },
      "required": [
        "project_name",
        "date_prepared",
        "project_manager",
        "prepared_by"
      ]
    },
    "requirements_collection_and_analysis": {
      "type": "object",
      "properties": {
        "requirements_elicitation_techniques": {
          "type": "string",
          "minLength": 1,
          "description": "Methods used to gather stakeholder needs including interviews, focus groups, and surveys."
        },
        "requirements_analysis_and_elaboration": {
          "type": "string",
          "minLength": 1,
          "description": "Analytical processes applied to structure, clarify, and model requirements."
        },
        "stakeholder_engagement_for_requirements": {
          "type": "string",
          "minLength": 1,
          "description": "Strategy for maintaining active stakeholder participation throughout requirements definition."
        }
      },
      "required": [
        "requirements_elicitation_techniques",
        "requirements_analysis_and_elaboration",
        "stakeholder_engagement_for_requirements"
      ]
    },
    "requirements_categorization_and_documentation": {
      "type": "object",
      "properties": {
        "requirements_taxonomy_and_categories": {
          "type": "string",
          "minLength": 1,
          "description": "Classification scheme covering business, stakeholder, solution, functional, and non-functional requirements."
        },
        "requirements_documentation_standards": {
          "type": "string",
          "minLength": 1,
          "description": "Formatting guidelines and documentation artifacts used to record verified requirements."
        }
      },
      "required": [
        "requirements_taxonomy_and_categories",
        "requirements_documentation_standards"
      ]
    },
    "prioritization_and_metrics": {
      "type": "object",
      "properties": {
        "requirements_prioritization_scheme": {
          "type": "string",
          "minLength": 1,
          "description": "Ranking methodology (such as MoSCoW, weighted scoring, or value ranking) to prioritize scope."
        },
        "requirements_product_metrics": {
          "type": "string",
          "minLength": 1,
          "description": "Quantitative metrics measuring requirements volatility, defect density, and coverage."
        }
      },
      "required": [
        "requirements_prioritization_scheme",
        "requirements_product_metrics"
      ]
    },
    "traceability_and_configuration_management": {
      "type": "object",
      "properties": {
        "traceability_structure_and_attributes": {
          "type": "string",
          "minLength": 1,
          "description": "Attributes and linkages tracked across the requirements lifecycle to ensure bidirectional traceability."
        },
        "requirements_configuration_control": {
          "type": "string",
          "minLength": 1,
          "description": "Procedures for baseline versioning and evaluating changes to documented requirements."
        }
      },
      "required": [
        "traceability_structure_and_attributes",
        "requirements_configuration_control"
      ]
    },
    "verification_and_validation_strategy": {
      "type": "object",
      "properties": {
        "requirements_verification_method": {
          "type": "string",
          "minLength": 1,
          "description": "Techniques ensuring requirements are complete, consistent, unambiguous, and testable."
        },
        "validation_and_user_acceptance_strategy": {
          "type": "string",
          "minLength": 1,
          "description": "Approach for validating that final deliverables fulfill underlying business objectives."
        }
      },
      "required": [
        "requirements_verification_method",
        "validation_and_user_acceptance_strategy"
      ]
    }
  },
  "required": [
    "artifact_id",
    "metadata",
    "requirements_collection_and_analysis",
    "requirements_categorization_and_documentation",
    "prioritization_and_metrics",
    "traceability_and_configuration_management",
    "verification_and_validation_strategy"
  ]
}

{
  "form_name": "REQUIREMENTS MANAGEMENT PLAN",
  "document_reference": "PMO-04.02.02",
  "_llm_instructions": "Populate the fields of 'REQUIREMENTS MANAGEMENT PLAN' and write the value of each field under 'Generated Value', based on the project context. Context: the project carrying reference PMO-04.02.02.",
  "project_title": "",
  "date_prepared": "",
  "fields": {
    "f01_Requirements_Elicitation_Techniques": {
      "section": "Requirements Collection and Analysis",
      "label": "Requirements Elicitation Techniques",
      "guidance": "Methods used to gather stakeholder needs including interviews, focus groups, and surveys.",
      "value": ""
    },
    "f02_Requirements_Analysis_and_Elaboration": {
      "section": "Requirements Collection and Analysis",
      "label": "Requirements Analysis and Elaboration",
      "guidance": "Analytical processes applied to structure, clarify, and model requirements.",
      "value": ""
    },
    "f03_Stakeholder_Engagement_for_Requirements": {
      "section": "Requirements Collection and Analysis",
      "label": "Stakeholder Engagement for Requirements",
      "guidance": "Strategy for maintaining active stakeholder participation throughout requirements definition.",
      "value": ""
    },
    "f04_Requirements_Taxonomy_and_Categories": {
      "section": "Requirements Categorization and Documentation",
      "label": "Requirements Taxonomy and Categories",
      "guidance": "Classification scheme covering business, stakeholder, solution, functional, and non-functional requirements.",
      "value": ""
    },
    "f05_Requirements_Documentation_Standards": {
      "section": "Requirements Categorization and Documentation",
      "label": "Requirements Documentation Standards",
      "guidance": "Formatting guidelines and documentation artifacts used to record verified requirements.",
      "value": ""
    },
    "f06_Requirements_Prioritization_Scheme": {
      "section": "Prioritization and Metrics",
      "label": "Requirements Prioritization Scheme",
      "guidance": "Ranking methodology (such as MoSCoW, weighted scoring, or value ranking) to prioritize scope.",
      "value": ""
    },
    "f07_Requirements_Product_Metrics": {
      "section": "Prioritization and Metrics",
      "label": "Requirements Product Metrics",
      "guidance": "Quantitative metrics measuring requirements volatility, defect density, and coverage.",
      "value": ""
    },
    "f08_Traceability_Structure_and_Attributes": {
      "section": "Traceability and Configuration Management",
      "label": "Traceability Structure and Attributes",
      "guidance": "Attributes and linkages tracked across the requirements lifecycle to ensure bidirectional traceability.",
      "value": ""
    },
    "f09_Requirements_Configuration_Control": {
      "section": "Traceability and Configuration Management",
      "label": "Requirements Configuration Control",
      "guidance": "Procedures for baseline versioning and evaluating changes to documented requirements.",
      "value": ""
    },
    "f10_Requirements_Verification_Method": {
      "section": "Verification and Validation Strategy",
      "label": "Requirements Verification Method",
      "guidance": "Techniques ensuring requirements are complete, consistent, unambiguous, and testable.",
      "value": ""
    },
    "f11_Validation_and_User_Acceptance_Strategy": {
      "section": "Verification and Validation Strategy",
      "label": "Validation and User Acceptance Strategy",
      "guidance": "Approach for validating that final deliverables fulfill underlying business objectives.",
      "value": ""
    }
  }
}