نفس مصدر الإدارات والموديولات والـWorkflows؛ يتم تحميل 20 قصة فقط في كل صفحة.
632 نتيجة من نفس الـSRS Graphصفحة 6 من 32الكتالوج الكامل 632 Story فريدة
HRM-V1-E11-US008
الموارد البشرية والإدارة · موديول Epic 11: Time offHRM V1.0c · المصدر الأساسي
بصفتي مسؤول النظام، أريد تنفيذ المتطلب التشغيلي في موديول Epic 11: Time off، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Leave Management Process
فتح سريع للقصة
Actor: HR Administrator
حسب المصدر الأساسي HRM V1.0c — As an HR Administrator, I want to manage the public holidays calendar(s), so that leave and attendance calculations correctly exclude them.
As an HR Administrator, I want to manage the public holidays calendar(s), so that leave and attendance calculations correctly exclude them.
Acceptance Criteria (2)
Holidays are managed per calendar (a company can have multiple calendars for multi-region operations, per Epic 1 US-003); Add/Edit/Delete/List/View follow the standard reference-data CRUD pattern (Epic 5, US-001).
Public Holiday coverage itself is Pattern 4 (Automatic, US-009) and never appears as a requestable leave type - it is a non-working-day marker consumed by leave duration calculation (US-004) and attendance (Epic 9).
HRM-V1-E11-US011
الموارد البشرية والإدارة · موديول Epic 11: Time offHRM V1.0c · المصدر الأساسي
بصفتي مستخدم الأعمال، أريد مراجعة واعتماد أو رفض العملية في موديول Epic 11: Time off حسب الصلاحية، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Leave Management Process
فتح سريع للقصة
Actor: Compliance Officer
حسب المصدر الأساسي HRM V1.0c — As a Compliance Officer, I want the 10 business rules from the Leave Management BRD enforced consistently across every leave type and workflow pattern, so that the system remains legally and operationally sound regardless of leave type or approval pattern.
As a Compliance Officer, I want the 10 business rules from the Leave Management BRD enforced consistently across every leave type and workflow pattern, so that the system remains legally and operationally sound regardless of leave type or approval pattern.
Acceptance Criteria (10)
BR-001: Request numbers (LR-YYYY-NNNNN) are unique, sequential per calendar year, never reused.
BR-002: Balance sufficiency is checked before submission proceeds to any approval layer.
BR-003: Mandatory attachments block submission until provided; Optional attachments are flagged missing to the approver but don't block.
BR-004: Balance is reserved on submission and finally deducted only on final approval; released on rejection/cancellation.
BR-005: Requests against a future accrual period are evaluated using projected balance as of the leave start date.
BR-006: Overlapping requests from the same employee for overlapping dates are detected and blocked with a reference to the conflicting request.
BR-007: Cancellations affecting a payroll cycle already Calculated or Approved (Epic 19) raise a recalculation flag rather than silently altering figures.
BR-008: Every state transition and approval/rejection action writes an immutable audit-log entry with actor, timestamp, and (on rejection) mandatory comment.
BR-009: SLA timeouts on any pending approval layer trigger automatic escalation with a notification, never silent stalling.
BR-010: Statutory-category leave types can never be configured below their Labor Law No. 14/2025 minimum duration or wage ratio (cross-referenced from US-001).
HRM-V1-E12-US001
الموارد البشرية والإدارة · موديول Epic 12: Request Configuration EngineHRM V1.0c · المصدر الأساسي
بصفتي مسؤول النظام، أريد عرض ومتابعة سجلات موديول Epic 12: Request Configuration Engine مع الفلاتر والإجماليات المسموح بها، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة HR Policy & Governance Process
فتح سريع للقصة
Actor: HR Admin
حسب المصدر الأساسي HRM V1.0c — As an HR Admin, I want to create, edit, and view Request Type Groups, so that related request types (e.g. all leave-related types) can be organized, jointly activated/deactivated, and reported on together.
As an HR Admin, I want to create, edit, and view Request Type Groups, so that related request types (e.g. all leave-related types) can be organized, jointly activated/deactivated, and reported on together.
Acceptance Criteria (3)
Group has Name (EN/AR, unique, max 100 chars), Status (Active/Inactive).
Deactivating a group hides its linked Request Types from the employee create-request selector for new requests; existing PENDING requests continue their approval lifecycle unaffected; reactivating restores selectability immediately.
Edit requires a mandatory Change Reason (min 5, max 500 characters), saved to the System Audit Log alongside the updating user's ID and timestamp — this closes the gap the source itself flagged as present in spec but missing from the live UI.
HRM-V1-E12-US002
الموارد البشرية والإدارة · موديول Epic 12: Request Configuration EngineHRM V1.0c · المصدر الأساسي
بصفتي مسؤول النظام، أريد تنفيذ المتطلب التشغيلي في موديول Epic 12: Request Configuration Engine، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة HR Policy & Governance Process
فتح سريع للقصة
Actor: HR Admin
حسب المصدر الأساسي HRM V1.0c — As an HR Admin, I want to define conditional benefit rules (e.g. tenure/age-based entitlement tiers) under a Master Policy, so that complex eligibility logic like Egyptian labor law's age/tenure-based leave entitlements can be modeled without custom code per rule.
As an HR Admin, I want to define conditional benefit rules (e.g. tenure/age-based entitlement tiers) under a Master Policy, so that complex eligibility logic like Egyptian labor law's age/tenure-based leave entitlements can be modeled without custom code per rule.
Acceptance Criteria (3)
Master Policy has Name (EN/AR, unique, max 255), optional Law Reference, optional Description (EN/AR).
Conditional rules define eligibility criteria (tenure, age, disability status, etc.) each mapping to a specific entitlement outcome (e.g. 'Tenure >= 120 months OR Age >= 50' -> Annual Leave increased tier).
Multiple conditional rules can exist per policy, each independently editable.
HRM-V1-E12-US003
الموارد البشرية والإدارة · موديول Epic 12: Request Configuration EngineHRM V1.0c · المصدر الأساسي
بصفتي مسؤول النظام، أريد تنفيذ المتطلب التشغيلي في موديول Epic 12: Request Configuration Engine، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة HR Policy & Governance Process
فتح سريع للقصة
Actor: HR Admin
حسب المصدر الأساسي HRM V1.0c — As an HR Admin, I want to define a sequential benefit rule made of ordered tiers (each with Days, Wage %, optional Label), so that entitlements like sick leave are consumed tier-by-tier with decreasing wage percentages.
As an HR Admin, I want to define a sequential benefit rule made of ordered tiers (each with Days, Wage %, optional Label), so that entitlements like sick leave are consumed tier-by-tier with decreasing wage percentages.
Acceptance Criteria (3)
Exactly one sequential rule per Master Policy; tiers are auto-numbered from 1 with no gaps, drag-to-reorder re-sequences.
Minimum 1 tier, maximum 20; Days required positive numeric; Wage % required 0-100 inclusive.
Tier consumption snapshot is stored per request for payroll/audit traceability; editing/reordering/deleting affects future requests only.
HRM-V1-E12-US004
الموارد البشرية والإدارة · موديول Epic 12: Request Configuration EngineHRM V1.0c · المصدر الأساسي
بصفتي مسؤول النظام، أريد إنشاء سجل جديد في موديول Epic 12: Request Configuration Engine بعد التحقق من البيانات والقواعد، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة HR Policy & Governance Process
فتح سريع للقصة
Actor: HR Admin
حسب المصدر الأساسي HRM V1.0c — As an HR Admin, I want to create a Request Type with its Balance Mode (None/Fixed/Policy) and link it to benefit rules, so that each request type's balance behavior is precisely configured.
As an HR Admin, I want to create a Request Type with its Balance Mode (None/Fixed/Policy) and link it to benefit rules, so that each request type's balance behavior is precisely configured.
Acceptance Criteria (3)
Balance Mode None: no balance tracking, requests always pass. Fixed: static balance/unit/reset-period stored directly. Policy: dynamic entitlement calculated by the rule engine (US-002/003).
Effect Type (No salary effect / Vacation / Permission / WFH / Leave Salary Deduction / Overtime) determines downstream module updates on approval — this is the field that determines whether a request type is payroll-relevant.
Code is a unique, immutable-after-save business identifier, auto-generated as RT-#### and editable before first save.
HRM-V1-E12-US005
الموارد البشرية والإدارة · موديول Epic 12: Request Configuration EngineHRM V1.0c · المصدر الأساسي
بصفتي مسؤول النظام، أريد تعديل بيانات موديول Epic 12: Request Configuration Engine مع حفظ التاريخ وإعادة الاحتساب، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة HR Policy & Governance Process
فتح سريع للقصة
Actor: HR Admin
حسب المصدر الأساسي HRM V1.0c — As an HR Admin, I want to edit a Request Type, with fields affecting balance/rules/payroll/history locked once real requests exist against it, so that editing a live request type can't silently corrupt historical data.
As an HR Admin, I want to edit a Request Type, with fields affecting balance/rules/payroll/history locked once real requests exist against it, so that editing a live request type can't silently corrupt historical data.
Acceptance Criteria (4)
No related requests exist: all fields editable per selected Balance Mode.
Related requests exist: Balance Mode cannot be switched; safe-editable fields limited to Name EN/AR, Responsible Department, Visible For Departments, Status; previously selected Policy rules lock (cannot remove, can add).
Existing submitted requests keep their original configuration snapshot; new requests after the edit date use the latest configuration — this non-retroactive principle appears throughout the source and is confirmed sound.
Mandatory Change Reason field and audit log entry (old/new value, changed by, date/time, reason) — this was the source's own flagged gap (spec required it, live UI didn't show it); now closed.
HRM-V1-E12-US006
الموارد البشرية والإدارة · موديول Epic 12: Request Configuration EngineHRM V1.0c · المصدر الأساسي
بصفتي مسؤول النظام، أريد احتساب ومطابقة القيم والأرصدة في موديول Epic 12: Request Configuration Engine، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة HR Policy & Governance Process
فتح سريع للقصة
Actor: HR Admin
حسب المصدر الأساسي HRM V1.0c — As an HR Admin, I want to maintain a reusable library of business validation rules (required fields, date ranges, balance sufficiency, overlap checks) that can be linked to any Request Type, so that validation logic is defined once and reused rather than duplicated per type.
As an HR Admin, I want to maintain a reusable library of business validation rules (required fields, date ranges, balance sufficiency, overlap checks) that can be linked to any Request Type, so that validation logic is defined once and reused rather than duplicated per type.
Delete blocked if the rule is linked to any request type or used in validation history; deactivation offered instead — same protective pattern used throughout the system.
Rules support EN/AR error messages, configurable trigger points (Create/Modify), and failure behavior (Block / Warn / Allow Exception).
HRM-V1-E13-US001
الموارد البشرية والإدارة · موديول Epic 13: Employee Requests ManagementHRM V1.0c · المصدر الأساسي
بصفتي الموظف، أريد عرض ومتابعة سجلات موديول Epic 13: Employee Requests Management مع الفلاتر والإجماليات المسموح بها، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Employee
حسب المصدر الأساسي HRM V1.0c — As an Employee, I want to submit a new request by selecting a Request Type, with the form dynamically rendering the relevant fields, balance panel, and approval flow preview, so that I understand exactly what I'm submitting and its impact before I do.
As an Employee, I want to submit a new request by selecting a Request Type, with the form dynamically rendering the relevant fields, balance panel, and approval flow preview, so that I understand exactly what I'm submitting and its impact before I do.
Acceptance Criteria (4)
Create Request card: Department, Sub Department, Request Type (searchable, lists only active/visible types), Urgent toggle (off by default).
Request Details fields render dynamically per selected type (e.g. Annual Leave shows Start/End/Back-to-Work/Wanted/Description; Overtime shows Start Date/Wanted/Reason).
Right-hand Balance panel shows live Available/Used/Remaining for the selected type's unit (Days/Hours/currency), updating as the employee adjusts requested duration, before submission — not just after.
Right-hand Approval Flow panel previews the stages the request will pass through (Direct Manager, named Approvers, Completed) based on the employee's Report Line configuration (Epic 4, US-014-017).
HRM-V1-E13-US002
الموارد البشرية والإدارة · موديول Epic 13: Employee Requests ManagementHRM V1.0c · المصدر الأساسي
بصفتي مستخدم الأعمال، أريد مراجعة واعتماد أو رفض العملية في موديول Epic 13: Employee Requests Management حسب الصلاحية، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Authorized HR User
حسب المصدر الأساسي HRM V1.0c — As the System, I want to validate a submitted request against configured field-level and business-level rules (Epic 12, US-006) before accepting it, so that invalid requests never enter the approval pipeline.
As the System, I want to validate a submitted request against configured field-level and business-level rules (Epic 12, US-006) before accepting it, so that invalid requests never enter the approval pipeline.
Acceptance Criteria (2)
Field-level validation (required, type, format) runs first; business-rule validation (balance sufficiency, date-range consistency, overlap, eligibility) runs second — a clear two-stage flow avoiding duplicated logic between the two layers.
Reserve-on-Submit (if enabled for the type) holds the requested balance while pending; rejection/cancellation/expiry releases it; final approval consumes it into Used.
HRM-V1-E13-US003
الموارد البشرية والإدارة · موديول Epic 13: Employee Requests ManagementHRM V1.0c · المصدر الأساسي
بصفتي الموظف، أريد عرض ومتابعة سجلات موديول Epic 13: Employee Requests Management مع الفلاتر والإجماليات المسموح بها، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Employee
حسب المصدر الأساسي HRM V1.0c — As an Employee, I want to view my own submitted requests with status and available actions, so that I can track progress and manage pending items.
As an Employee, I want to view my own submitted requests with status and available actions, so that I can track progress and manage pending items.
Employee sees only their own requests (row-level security on requester = current user), reusing the Record-Level Data Scoping mechanism from Epic 2, US-005 rather than a bespoke filter.
Status values match the live system's canonical set: Opening, Pending, In Progress, Closed, Rejected (adopted per the BA Review Summary resolution of the source's flagged status-set mismatch).
HRM-V1-E13-US004
الموارد البشرية والإدارة · موديول Epic 13: Employee Requests ManagementHRM V1.0c · المصدر الأساسي
بصفتي المعتمد، أريد عرض ومتابعة سجلات موديول Epic 13: Employee Requests Management مع الفلاتر والإجماليات المسموح بها، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Employee or Approver
حسب المصدر الأساسي HRM V1.0c — As an Employee or Approver, I want to view full request details and its action history, so that I understand the current state and everything that led to it.
As an Employee or Approver, I want to view full request details and its action history, so that I understand the current state and everything that led to it.
Acceptance Criteria (3)
Details render dynamically per Request Type, all fields read-only.
Timeline/audit history (creation, approvals, status changes, notifications) is accessed via Actions -> Logs on the admin list — adopted as canonical per the BA Review Summary, resolving the source's flagged inline-vs-Logs placement gap.
Payroll Impact section appears only for payroll-relevant types (per Effect Type, Epic 12 US-004); marked Preview before final approval.
HRM-V1-E13-US005
الموارد البشرية والإدارة · موديول Epic 13: Employee Requests ManagementHRM V1.0c · المصدر الأساسي
بصفتي الموظف، أريد تعديل بيانات موديول Epic 13: Employee Requests Management مع حفظ التاريخ وإعادة الاحتساب، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Employee
حسب المصدر الأساسي HRM V1.0c — As an Employee, I want to cancel or modify my request before it's finally approved, so that I can correct mistakes or withdraw if plans change.
As an Employee, I want to cancel or modify my request before it's finally approved, so that I can correct mistakes or withdraw if plans change.
Acceptance Criteria (2)
Cancel (Pending only): withdraws the request and releases any reserved balance instantly.
Modify (before final approval): re-editing resets the approval cycle to step 1, since a materially changed request needs fresh review from the start — retained from source, sound as specified.
HRM-V1-E13-US006
الموارد البشرية والإدارة · موديول Epic 13: Employee Requests ManagementHRM V1.0c · المصدر الأساسي
بصفتي المدير المسؤول، أريد عرض ومتابعة سجلات موديول Epic 13: Employee Requests Management مع الفلاتر والإجماليات المسموح بها، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Admin, HR Admin, or Manager
حسب المصدر الأساسي HRM V1.0c — As an Admin, HR Admin, or Manager, I want to view and monitor all requests within my scope, so that I can track organizational request volume and status.
As an Admin, HR Admin, or Manager, I want to view and monitor all requests within my scope, so that I can track organizational request volume and status.
Acceptance Criteria (1)
List scoped by Record-Level Data Scoping (Epic 2, US-005) per the viewer's role — e.g. a Department Manager sees only their department's requests, not company-wide, unless their role grants broader scope.
HRM-V1-E13-US007
الموارد البشرية والإدارة · موديول Epic 13: Employee Requests ManagementHRM V1.0c · المصدر الأساسي
بصفتي المعتمد، أريد تعديل بيانات موديول Epic 13: Employee Requests Management مع حفظ التاريخ وإعادة الاحتساب، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Approver
حسب المصدر الأساسي HRM V1.0c — As an Approver, I want to change a request's status through the configured transition menu (Close/Reject/In Progress/Pending), so that approval reflects the live system's actual status-transition model rather than dedicated Approve/Reject buttons that don't exist in the running system.
As an Approver, I want to change a request's status through the configured transition menu (Close/Reject/In Progress/Pending), so that approval reflects the live system's actual status-transition model rather than dedicated Approve/Reject buttons that don't exist in the running system.
Acceptance Criteria (3)
Status control offers Close, Reject, In Progress, Pending per the current status and the approver's permission.
Actions -> New Reason lets an authorized user attach a reason to a status action; this and all transitions are recorded in Logs with performer, role, action, old/new status, timestamp, and reason.
System prevents duplicate status processing under concurrent actions (optimistic locking or equivalent), closing a real race-condition risk in multi-approver scenarios.
HRM-V1-E13-US008
الموارد البشرية والإدارة · موديول Epic 13: Employee Requests ManagementHRM V1.0c · المصدر الأساسي
بصفتي مستخدم الأعمال، أريد مراجعة واعتماد أو رفض العملية في موديول Epic 13: Employee Requests Management حسب الصلاحية، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Authorized HR User
حسب المصدر الأساسي HRM V1.0c — As the System, I want to route each request through its Report Line's ordered approver chain (Epic 4, US-014-017), so that approval routing is consistent and centrally configured rather than hardcoded per request type.
As the System, I want to route each request through its Report Line's ordered approver chain (Epic 4, US-014-017), so that approval routing is consistent and centrally configured rather than hardcoded per request type.
Acceptance Criteria (2)
Approval progresses step-by-step per the configured chain; each step's completion (approval) triggers routing to the next step or final completion if it was the last.
Applies the Direct Manager hierarchy resolution (Epic 5, US-005) when a chain step is configured as 'Direct Manager' rather than a named individual.
HRM-V1-E13-US009
الموارد البشرية والإدارة · موديول Epic 13: Employee Requests ManagementHRM V1.0c · المصدر الأساسي
بصفتي المعتمد، أريد تعديل بيانات موديول Epic 13: Employee Requests Management مع حفظ التاريخ وإعادة الاحتساب، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Employee or Approver
حسب المصدر الأساسي HRM V1.0c — As an Employee or Approver, I want to receive notifications/emails on request creation and status changes, so that I don't need to manually poll for updates.
As an Employee or Approver, I want to receive notifications/emails on request creation and status changes, so that I don't need to manually poll for updates.
Acceptance Criteria (1)
Requester notified on status change to In Progress/Pending/Closed/Rejected/Cancelled; configured recipients notified when action is needed; failed email delivery is logged for retry/diagnosis but never blocks the underlying status update.
HRM-V1-E13-US010
الموارد البشرية والإدارة · موديول Epic 13: Employee Requests ManagementHRM V1.0c · المصدر الأساسي
بصفتي الموظف، أريد تنفيذ المتطلب التشغيلي في موديول Epic 13: Employee Requests Management، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Employee Requests Process
فتح سريع للقصة
Actor: Employee
حسب المصدر الأساسي HRM V1.0c — As an Employee, I want request forms for HR Letters, Training, and Loan requests to capture the fields specific to each, so that HR receives complete information without follow-up.
As an Employee, I want request forms for HR Letters, Training, and Loan requests to capture the fields specific to each, so that HR receives complete information without follow-up.
Acceptance Criteria (3)
HR Letter: Letter Type (e.g. salary certificate, employment verification), Purpose/Destination, Language (EN/AR).
Training: Course Name, Provider, Dates, Estimated Cost (routes to budget-approval step if above a configurable threshold).
Loan: Requested Amount, Repayment Period, Reason — links into the Loans & Repayments epic (Epic 18) upon approval, creating the actual loan account rather than existing only as a request record.
HRM-V1-E14-US001
الموارد البشرية والإدارة · موديول Epic 14: KPI Cycle ManagementHRM V1.0c · المصدر الأساسي
بصفتي مسؤول النظام، أريد عرض ومتابعة سجلات موديول Epic 14: KPI Cycle Management مع الفلاتر والإجماليات المسموح بها، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Performance Management Cycle
فتح سريع للقصة
Actor: HR Administrator
حسب المصدر الأساسي HRM V1.0c — As an HR Administrator, I want to launch a KPI evaluation cycle for a defined employee population, routed through each employee's Report Line, so that evaluations reach the correct reviewer without a separate reviewer-assignment step.
As an HR Administrator, I want to launch a KPI evaluation cycle for a defined employee population, routed through each employee's Report Line, so that evaluations reach the correct reviewer without a separate reviewer-assignment step.
Acceptance Criteria (3)
Cycle defines a Period, target population (by Organizational Unit/Job Position/individual), and Evaluation Form (linked to KPI/KRA config, Epic 15).
If Self-Evaluation is enabled for the cycle, the employee completes their self-assessment first; it becomes visible to the reviewer alongside their own evaluation, not as a replacement for manager review.
Reviewer is resolved via the employee's Report Line (Epic 4), consistent with every other approval-routing use in this system.
HRM-V1-E14-US002
الموارد البشرية والإدارة · موديول Epic 14: KPI Cycle ManagementHRM V1.0c · المصدر الأساسي
بصفتي مستخدم الأعمال، أريد عرض ومتابعة سجلات موديول Epic 14: KPI Cycle Management مع الفلاتر والإجماليات المسموح بها، حتى تكتمل العملية بنتيجة صحيحة وقابلة للتتبع.
دورة العمل: دورة Performance Management Cycle
فتح سريع للقصة
Actor: Reviewer
حسب المصدر الأساسي HRM V1.0c — As a Reviewer, I want to score an employee against configured KPIs/KRAs with weighted scoring, so that the evaluation produces an objective composite score.
As a Reviewer, I want to score an employee against configured KPIs/KRAs with weighted scoring, so that the evaluation produces an objective composite score.
Acceptance Criteria (1)
Form renders KPIs/KRAs from Epic 15's configuration with their defined weights; composite score auto-calculates as the weighted sum, not manually entered.