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

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

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

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

---

## 1. متطلبات الأعمال

**أهداف وغايات الأعمال:**
[ أضف التفاصيل... ]

**تأثير العمليات والإجراءات:**
[ أضف التفاصيل... ]

**قيمة الأعمال ومعايير النجاح:**
[ أضف التفاصيل... ]

---

## 2. متطلبات المعنيين

**ملخص احتياجات المعنيين والمستخدمين:**
[ أضف التفاصيل... ]

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

---

## 3. متطلبات الحل والمتطلبات الفنية

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

**المعمارية الفنية وقيود النظام:**
[ أضف التفاصيل... ]

---

## 4. المتطلبات الانتقالية وغير الوظيفية

**المتطلبات غير الوظيفية (جودة الخدمة):**
[ أضف التفاصيل... ]

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

---

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

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

<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.03 <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.03.schema.json",
  "title": "Completed REQUIREMENTS DOCUMENTATION Data Contract",
  "description": "Additive structural schema validating completed REQUIREMENTS DOCUMENTATION artifact data payloads (PMO-04.02.03).",
  "type": "object",
  "properties": {
    "artifact_id": {
      "type": "string",
      "const": "PMO-04.02.03"
    },
    "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"
      ]
    },
    "business_requirements": {
      "type": "object",
      "properties": {
        "business_objectives_and_goals": {
          "type": "string",
          "minLength": 1,
          "description": "High-level organizational motivations, strategic drivers, and target business problems to solve."
        },
        "business_process_impact": {
          "type": "string",
          "minLength": 1,
          "description": "Current-state vs. target-state operational workflow enhancements and process impacts."
        },
        "business_value_and_success_criteria": {
          "type": "string",
          "minLength": 1,
          "description": "Measurable commercial, operational, or customer value expected upon delivery."
        }
      },
      "required": [
        "business_objectives_and_goals",
        "business_process_impact",
        "business_value_and_success_criteria"
      ]
    },
    "stakeholder_requirements": {
      "type": "object",
      "properties": {
        "user_persona_and_needs_summary": {
          "type": "string",
          "minLength": 1,
          "description": "Detailed operational requirements categorized by specific stakeholder groups and user personas."
        },
        "stakeholder_pain_points_and_expectations": {
          "type": "string",
          "minLength": 1,
          "description": "Critical operational pain points addressed and expected behavioral outcomes."
        }
      },
      "required": [
        "user_persona_and_needs_summary",
        "stakeholder_pain_points_and_expectations"
      ]
    },
    "solution_and_technical_requirements": {
      "type": "object",
      "properties": {
        "functional_requirements_specification": {
          "type": "string",
          "minLength": 1,
          "description": "Detailed capabilities, system interactions, features, and functional behavior."
        },
        "technical_architecture_and_system_constraints": {
          "type": "string",
          "minLength": 1,
          "description": "System interfaces, infrastructure prerequisites, data architecture, and technological boundaries."
        }
      },
      "required": [
        "functional_requirements_specification",
        "technical_architecture_and_system_constraints"
      ]
    },
    "transition_and_non_functional_requirements": {
      "type": "object",
      "properties": {
        "non_functional_requirements_quality_of_service": {
          "type": "string",
          "minLength": 1,
          "description": "Performance thresholds, security standards, availability, scalability, and usability criteria."
        },
        "transition_and_readiness_requirements": {
          "type": "string",
          "minLength": 1,
          "description": "Data migration, end-user training, operational handover, and rollout support prerequisites."
        }
      },
      "required": [
        "non_functional_requirements_quality_of_service",
        "transition_and_readiness_requirements"
      ]
    }
  },
  "required": [
    "artifact_id",
    "metadata",
    "business_requirements",
    "stakeholder_requirements",
    "solution_and_technical_requirements",
    "transition_and_non_functional_requirements"
  ]
}

{
  "form_name": "REQUIREMENTS DOCUMENTATION",
  "document_reference": "PMO-04.02.03",
  "_llm_instructions": "Populate the fields of 'REQUIREMENTS DOCUMENTATION' and write the value of each field under 'Generated Value', based on the project context. Context: the project carrying reference PMO-04.02.03.",
  "project_title": "",
  "date_prepared": "",
  "fields": {
    "f01_Business_Objectives_and_Goals": {
      "section": "Business Requirements",
      "label": "Business Objectives and Goals",
      "guidance": "High-level organizational motivations, strategic drivers, and target business problems to solve.",
      "value": ""
    },
    "f02_Business_Process_Impact": {
      "section": "Business Requirements",
      "label": "Business Process Impact",
      "guidance": "Current-state vs. target-state operational workflow enhancements and process impacts.",
      "value": ""
    },
    "f03_Business_Value_and_Success_Criteria": {
      "section": "Business Requirements",
      "label": "Business Value and Success Criteria",
      "guidance": "Measurable commercial, operational, or customer value expected upon delivery.",
      "value": ""
    },
    "f04_User_Persona_and_Needs_Summary": {
      "section": "Stakeholder Requirements",
      "label": "User Persona and Needs Summary",
      "guidance": "Detailed operational requirements categorized by specific stakeholder groups and user personas.",
      "value": ""
    },
    "f05_Stakeholder_Pain_Points_and_Expectations": {
      "section": "Stakeholder Requirements",
      "label": "Stakeholder Pain Points and Expectations",
      "guidance": "Critical operational pain points addressed and expected behavioral outcomes.",
      "value": ""
    },
    "f06_Functional_Requirements_Specification": {
      "section": "Solution and Technical Requirements",
      "label": "Functional Requirements Specification",
      "guidance": "Detailed capabilities, system interactions, features, and functional behavior.",
      "value": ""
    },
    "f07_Technical_Architecture_and_System_Constraints": {
      "section": "Solution and Technical Requirements",
      "label": "Technical Architecture and System Constraints",
      "guidance": "System interfaces, infrastructure prerequisites, data architecture, and technological boundaries.",
      "value": ""
    },
    "f08_Non_Functional_Requirements_Quality_of_Service": {
      "section": "Transition and Non-Functional Requirements",
      "label": "Non-Functional Requirements (Quality of Service)",
      "guidance": "Performance thresholds, security standards, availability, scalability, and usability criteria.",
      "value": ""
    },
    "f09_Transition_and_Readiness_Requirements": {
      "section": "Transition and Non-Functional Requirements",
      "label": "Transition and Readiness Requirements",
      "guidance": "Data migration, end-user training, operational handover, and rollout support prerequisites.",
      "value": ""
    }
  }
}