Skip to content
Gallery
sfry
Navigation
HR's Manual
Services
Business Analysis Document for Adding Cars
Share
Explore

icon picker
Navigation

The system in question facilitates various HR-related requests for employees within an organization. Employees can request financial adjustments, lifecycle changes, work policy alterations, and more, while HR representatives are responsible for processing these requests. The system allows employees to request purchases, allowances, bonuses, and salary improvements, among others, and track the status of these requests. Additionally, employees can request changes to personal information, such as adding or removing family members, and have access to tools for submitting health reports and participating in surveys. HR managers can send company decisions to employees, who, in turn, can acknowledge receipt. The system also supports employee performance evaluations with quarterly assessments. For each process, the system provides user-friendly interfaces for submitting requests, notifications for updates, and options for HR to review and manage the requests efficiently. The system emphasizes ease of use, security, and scalability to meet business growth.
⁠
Classification and Requests Table
Category
English
Arabic
1
Financial Requests
Request Purchases
طلب المشتريات
2
Financial Requests
Request Allowances
طلب البدلات
3
Financial Requests
Request Bonuses
طلب المكافآت
4
Financial Requests
Request Payroll Deductions Cancels
طلب إلغاء الخصومات من الرواتب
5
Financial Requests
Request Commissions
طلب العمولات
6
Financial Requests
Request Advances
طلب السلف
7
Financial Requests
Request Settlements
طلب التسويات المالية
8
Employee Lifecycle
Request Retirement Age Extensions
طلب تمديد سن التقاعد
9
Employee Lifecycle
Request Resignations
طلب الاستقالات
10
Employee Lifecycle
Request Promotions
طلب الترقيات
11
Employee Lifecycle
Request Salary Improvements
طلب تحسين الرواتب
12
Work Policies and Procedures
Request Work Hours Changes
طلب تغيير ساعات العمل
13
Work Policies and Procedures
Request Permissions
طلب الأذونات
14
Work Policies and Procedures
Request Overtime
طلب العمل الإضافي
15
Personnel Requests
Request Vacation
طلب الإجازات
16
Personnel Requests
Request Transfers
طلب نقل
17
Personnel Requests
Request Sponsorship Transfers
طلب نقل الكفالة
18
Delegations Requests
Request External Delegations
طلب الانتدابات الخارجية
19
Delegations Requests
Request Internal Delegations
طلب الانتدابات الداخلية
20
Development Requests
Request Trainer Registrations
طلب تسجيل المدربين
21
Development Requests
Request Training Additions
طلب إضافة الدورات التدريبية
22
Development Requests
Request Training Bonuses
طلب مكافآت التدريب
There are no rows in this table
⁠
User Stories and Acceptance Criteria (Request)
User Story: Employee Goal:
As an employee, I want to be able to create new requests through the application to request actions within the system.
I want to be able to review and modify my requests before submitting them.
I want to be able to track the status of my requests and receive notifications of any changes.
Acceptance Criteria:
Create Request:
The employee should be able to enter all required information, including:
Employee name (view to HR)
Current salary (view to HR)
Request date (view to HR)
Employment period (view to HR)
Request title
Reason for request
Attachments (optional)
The employee should be able to save the request as a draft or submit it.
Manage Requests:
The employee should be able to review and modify their requests before submitting them.
The employee should be able to cancel their requests before submitting them.
Track Requests:
The employee should be able to view the status of all their requests.
The employee should receive notifications of any changes to the status of their request, such as:
The request has been submitted.
The request has been opened by HR.
The request status has been changed (approved, rejected, requested additional information).
User Story: HR Representative Goal:
As an HR representative, I want to be able to review and process employee requests efficiently and effectively.
I want to be able to communicate with employees about their requests if necessary.
I want to be able to view the history of an employee's requests.
Acceptance Criteria:
Review Requests:
The HR representative should be able to view a list of all pending requests.
The HR representative should be able to open each request and view all details.
The HR representative should be able to approve the request, reject it, or request additional information.
The HR representative should be able to update the status of the request.
View Request History:
The HR representative should be able to view the history of an employee's requests.
Additional Notes:
The system should be secure and protect employee data.
The system should be easy to use for both employees and HR representatives.
The system should be scalable to meet the growing needs of the business.
User Stories and Acceptance Criteria for Request History
User Story: HR Representative
Goal:
As an HR representative, I want to be able to access a comprehensive history of all employee requests with the ability to filter requests based on various criteria.
Acceptance Criteria:
There should be a history of all employee requests accessible to the HR representative.
The HR representative should be able to filter requests by type, date, employee name, job title, department, or request status.
The history should be updated automatically when a new request is opened or the status of an existing request changes.
User Story: Employee
Goal:
As an employee, I want to be able to access a comprehensive history of all my requests with the ability to filter requests based on various criteria.
Acceptance Criteria:
There should be a history of all employee requests accessible to the employee.
The employee should be able to filter requests by type, date, or request status.
The history should be updated automatically when a new request is submitted or the status of an existing request changes.
Submitting Leave Request
User Story: Employee - Submit Leave Request
As an employee, I want to submit a leave request by specifying the start and end dates, and the type of leave, so that I can formally notify my employer about my absence.
Acceptance Criteria:
Selecting Dates from Calendar:
The leave request form should display a calendar.
When the employee opens the date picker to select the start date, the calendar should only show dates starting from the next day onwards (excluding the current date).
When selecting the end date, it must be the same as or after the start date.
Selecting Leave Type:
A dropdown list of leave types should be available on the form.
This list should display all registered leave types retrieved from the HR dashboard.
Reason for Leave (Optional):
The employee should have the option to enter a reason for their leave in a dedicated field.
Additional Notes (Optional):
The employee can optionally provide additional notes in a designated field.
Submitting Leave Request:
When the employee clicks the submit button, the system should validate the form.
If all required fields are filled correctly (start date, end date, leave type), the system should send the leave request to HR for review.
Upon successful submission, the employee should receive a notification confirming their request.
User Story: HR Manager - Reviewing Leave Request
As an HR manager, I want to review leave requests submitted by employees, so that I can make informed decisions about approving, rejecting, or requesting additional information.
Acceptance Criteria:
Receiving Notification:
Upon an employee submitting a leave request, the HR manager should receive a notification for a new request.
Reviewing Request:
When the HR manager opens the request, the system should display all relevant details, including dates, leave type, and reason for leave (if provided).
Decision Making:
The HR manager can choose to approve, reject, or request additional information.
Approve:
When the manager approves the request, the system should:
Record the leave in the employee's calendar.
Send a notification to the employee confirming approval.
Reject:
When the manager rejects the request, the system should:
Prompt the employee to enter a reason upon reopening the request.
Send a notification to the employee informing them of the rejection.
Request More Information:
When the manager requests more information, the system should:
Send a notification to the employee requesting the additional information.
Allow the employee to re-submit the request after providing the information.
User Story: Direct Manager - Approving Leave Request
As a direct manager, I want to review and approve leave requests submitted by my team members, so that I can ensure smooth workflow continuity during their absence.
Acceptance Criteria:
Receiving Notification:
Upon an employee within the team submitting a leave request, the direct manager should receive a notification.
Reviewing Request:
When the direct manager opens the request, the system should display all relevant details, including dates, leave type, and reason for leave (if provided).
Decision Making:
The direct manager can choose to approve, reject, or request additional information.
Approve:
When the manager approves the request, the system should:
Record the leave in the employee's calendar.
Send a notification to the employee confirming approval.
Reject:
When the manager rejects the request, the system should send a notification to the employee explaining the reason for rejection.
Request More Information:
When the manager requests more information, the system should:
Send a notification to the employee requesting the additional information.
Allow the employee to re-submit the request after providing the information.
Submit Sponsorship Transfer Request
User Story: Employee
As an employee, I want to submit a sponsorship transfer request by selecting the new sponsor from the system and specifying the reason for the transfer, so that I can formally notify my employer about my request.
Acceptance Criteria:
1. Selecting New Sponsor:
- The sponsorship transfer request form should have a dropdown list for sponsors.
- This list should display all registered sponsors retrieved from the HR system.
2. Reason for Transfer:
- The form should include a dedicated field for the employee to enter the reason for the sponsorship transfer.
3. Submitting Transfer Request:
- When the employee clicks the submit button, the system should validate the form.
- If all required fields are correctly filled (new sponsor, reason for transfer), the system should send the transfer request to HR for review.
- Upon successful submission, the employee should receive a notification confirming their request.
User Story: HR Manager - Reviewing Sponsorship Transfer Request
As an HR manager, I want to review sponsorship transfer requests submitted by employees, so that I can make informed decisions about approving, rejecting, or requesting additional information.
Acceptance Criteria:
1. Receiving Notification:
- Upon an employee submitting a sponsorship transfer request, the HR manager should receive a notification for a new request.
2. Reviewing Request:
- When the HR manager opens the request, the system should display all relevant details, including the new sponsor and reason for transfer.
3. Decision Making:
- The HR manager can choose to approve, reject, or request additional information.
- Approve:
- When the manager approves the request, the system should:
- Update the employee's record with the new sponsor.
- Send a notification to the employee confirming the approval.
- Reject:
- When the manager rejects the request, the system should:
- Prompt the employee to enter a reason upon reopening the request.
- Send a notification to the employee informing them of the rejection.
- Request More Information:
- When the manager requests more information, the system should:
- Send a notification to the employee requesting the additional information.
- Allow the employee to resubmit the request after providing the information.
User Story: Direct Manager - Approving Sponsorship Transfer Request
As a direct manager, I want to review and approve sponsorship transfer requests submitted by my team members, so that I can ensure smooth workflow continuity during the transition.
Acceptance Criteria:
1. Receiving Notification:
- Upon an employee within the team submitting a sponsorship transfer request, the direct manager should receive a notification.
2. Reviewing Request:
- When the direct manager opens the request, the system should display all relevant details, including the new sponsor and reason for transfer.
3. Decision Making:
- The direct manager can choose to approve, reject, or request additional information.
- Approve:
- When the manager approves the request, the system should:
- Update the employee's record with the new sponsor.
- Send a notification to the employee confirming the approval.
- Reject:
- When the manager rejects the request, the system should send a notification to the employee explaining the reason for rejection.
- Request More Information:
- When the manager requests more information, the system should:
- Send a notification to the employee requesting the additional information.
- Allow the employee to resubmit the request after providing the information.
As an employee, I want to submit a loan request by specifying the loan amount, repayment period in months, and optionally the reason for the loan, so that I can formally request a loan from my employer.
Acceptance Criteria:
1. Specify Loan Amount:
- The loan request form should have a field for the employee to enter the loan amount.
2. Specify Repayment Period:
- The form should include a field for the employee to enter the number of months for repayment.
3. Reason for Loan (Optional):
- The form should include an optional field for the employee to enter the reason for the loan.
4. Submit Loan Request:
- When the employee clicks the submit button, the system should validate the form.
- If all required fields are correctly filled (loan amount, repayment period), the system should send the loan request to HR for review.
- Upon successful submission, the employee should receive a notification confirming their request.
As an employee, I want to submit an allowance request by specifying the type and amount of the allowance, and optionally the reason for the request, so that I can formally request allowances from my employer.
Acceptance Criteria:
1. Specify Bonus Amount:
- The bonus request form should have a field for the employee to enter the bonus amount.
2. Reason for Request (Optional):
- The form should include an optional field for the employee to enter the reason for the request.
3. Submit Bonus Request:
- When the employee clicks the submit button, the system should validate the form.
- If all required fields are correctly filled (bonus amount), the system should send the bonus
request to HR for review.
- Upon successful submission, the employee should receive a notification confirming their request.
User Story: HR Manager - Viewing Employee Salary Details
As an HR manager, I want to view the salary details of employees so that I can monitor their salaries individually or collectively, with the ability to print the data or export it as a PDF.
Acceptance Criteria:
1. Individual Details:
- The salary details page for each employee should include the following fields: basic salary, bonuses, commissions, allowances, loans.
- The loan amount should be deducted from the total.
- The net salary should be displayed, which equals basic salary + bonuses + commissions + allowances - monthly loan installment.
2. Collective Details:
- There should be a page displaying salary details for all employees.
3. Print or Save as PDF:
- The HR manager should have the option to print the page or save it as a PDF.
User Story: HR Manager - Manage Employee Salary Components
As an HR manager, I want to manage the salary components for employees so that I can add basic salary, bonuses, commissions, allowances, and loans.
Acceptance Criteria:
1. Add Basic Salary:
- The HR manager should be able to enter and update the basic salary for each employee through the system.
2. Manage Loans:
- The HR manager should be able to add loans or approve loan requests submitted by employees.
3. Manage Allowances:
- The HR manager should be able to add allowances or approve allowance requests submitted by employees.
4. Manage Bonuses:
- The HR manager should be able to add bonuses or approve bonus requests submitted by employees.
5. Update Salary Details:
- The net salary details should be automatically updated when any of the above components are added or modified.
User Story: Employee
Goal:
As an employee, I want to submit a purchase request for specific products through the application.
Acceptance Criteria:
1. The employee should be able to fill out the request with the required information for each product, such as name, quantity, and reason.
2. The employee should be able to submit the request to HR.
3. The employee should receive a notification of any change in the request status, whether it's opened by HR or approved.
User Story: HR Representative
Goal:
As an HR representative, I want to review and process purchase requests submitted by employees efficiently, including dealing with each product individually.
Acceptance Criteria:
1. The HR representative should be able to open the request and change its status to "Under Review" automatically.
2. The HR representative should be able to modify the quantities of the requested products.
3. The HR representative should be able to approve the entire request, reject some products and approve the rest.
4. The HR representative should be able to access the purchase requests history for all employees and filter requests by type, date, and status.
Field Name Mandatory Specifications:
Column 1
Column 2
Column 3
1
Field Name
Mandatory
Specifications
2
Product Name
Yes
A text field displaying the name of the requested product.
3
Quantity
Yes
A numeric field displaying the quantity of the product.
4
Reason
Yes
A text field allowing the employee to input the reason for the purchase.
There are no rows in this table
⁠
User Story: Employee - Request Allowance
Goal:
As an employee, I want to submit a request for a specific allowance through the application.
Acceptance Criteria:
1. The employee should have access to the functionality to request an allowance.
2. When submitting the request, the employee should provide details such as the amount and reason.
3. The system should validate that all required fields are filled before allowing the employee to submit the request.
4. After submitting the request, the employee should receive a confirmation message.
User Story: HR Representative - Manage Allowance Requests
Goal:
As an HR representative, I want to review and manage allowance requests submitted by employees efficiently.
Acceptance Criteria:
1. The HR representative should have access to a list of all allowance requests submitted by employees.
2. The HR representative should be able to view the details of each allowance request, including amount, reason, and status.
3. The HR representative should be able to approve or reject each allowance request.
4. The system should notify the HR representative of any new allowance requests submitted by employees.
5. The HR representative should be able to filter allowance requests by date and status.
Field Name Mandatory Specifications( Request Allowances ):
Column 1
Column 2
Column 3
1
Field Name
Mandatory
Specifications
2
Allowance Type
No
This field will be filled in by HR based on the type of allowance requested.
3
Amount
Yes
A numeric field displaying the amount of the allowance requested.
4
Reason
Yes
A text field allowing the employee to input the reason for the allowance request.
There are no rows in this table
⁠

User Story: Employee - Viewing Salary Details

As an employee, I want to view my salary details so that I can understand my basic salary, bonuses, commissions, allowances, loans, and net salary.
Acceptance Criteria:
1. Display Details:
- The salary details page should include the following fields: basic salary, bonuses, commissions, allowances, loans.
- The loan amount should be deducted from the total.
- The net salary should be displayed, which equals basic salary + bonuses + commissions + allowances - monthly loan installment.
2. Print or Save as PDF:
- The employee should have the option to print the page or save it as a PDF.

User Story: Employee - Viewing Basic Salary Details

As an employee, I want to view my basic salary details so that I can know my initial salary, duration of employment, and any salary increments with their dates and details.
Acceptance Criteria:
Display Details:
The basic salary page should include the following fields: initial salary, duration of employment.
Any salary increments should be displayed with their dates and details.
Salary Increment Requests:
The employee should be able to submit a salary increment request through a form with the necessary fields.

User Story: Employee - Viewing Bonuses Details

As an employee, I want to view my bonuses details so that I can know the date, type, and amount of each bonus I have received.
Acceptance Criteria:
Display Details:
The bonuses page should include the following fields: date, type of bonus, amount.
Bonus Requests:
The employee should be able to submit a bonus request through a form with the necessary fields.

User Story: Employee - Viewing Commissions Details

As an employee, I want to view my commissions details so that I can know the date, type, and amount of each commission I have received.
Acceptance Criteria:
Display Details:
The commissions page should include the following fields: date, type of commission, amount.
Commission Requests:
The employee should be able to submit a commission request through a form with the necessary fields.

User Story: Employee - Viewing Allowances Details

As an employee, I want to view my allowances details so that I can know the date, type, and amount of each allowance I have received.
Acceptance Criteria:
Display Details:
The allowances page should include the following fields: date, type of allowance, amount.
Allowance Requests:
The employee should be able to submit an allowance request through a form with the necessary fields.

User Story: Employee - Viewing Loan Details

As an employee, I want to view my loan details so that I can know the initial loan amount, repayment period, months repaid, and the remaining amount.
Acceptance Criteria:
Display Details:
The loans page should include the following fields: initial loan amount, repayment period, months repaid, remaining amount.
Loan Requests:
The employee should be able to submit a loan request through a form with the necessary fields.

User Story: HR Manager - Managing Basic Salary Details

As an HR manager, I want to manage the basic salary details of employees so that I can add or update the basic salary and record any increments with their dates and details.
Acceptance Criteria:
Add and Update Basic Salary:
The HR manager should be able to add or update the basic salary for each employee.
Record Increments:
The HR manager should be able to record any salary increments with their dates and details.

User Story: HR Manager - Managing Bonuses Details

As an HR manager, I want to manage the bonuses details of employees so that I can add or update bonuses with their dates and details.
Acceptance Criteria:
Add and Update Bonuses:
The HR manager should be able to add or update bonuses for each employee.
View Requests:
The HR manager should be able to view and review bonus requests submitted by employees.

User Story: HR Manager - Managing Commissions Details

As an HR manager, I want to manage the commissions details of employees so that I can add or update commissions with their dates and details.
Acceptance Criteria:
Add and Update Commissions:
The HR manager should be able to add or update commissions for each employee.
View Requests:
The HR manager should be able to view and review commission requests submitted by employees.

User Story: HR Manager - Managing Allowances Details

As an HR manager, I want to manage the allowances details of employees so that I can add or update allowances with their dates and details.
Acceptance Criteria:
Add and Update Allowances:
The HR manager should be able to add or update allowances for each employee.
View Requests:
The HR manager should be able to view and review allowance requests submitted by employees.

User Story: HR Manager - Managing Loan Details

As an HR manager, I want to manage the loan details of employees so that I can add or update loans, and track the amounts repaid and remaining for each loan.
Acceptance Criteria:
Add and Update Loans:
The HR manager should be able to add or update loans for each employee.
Track Repayments:
The HR manager should be able to track the amounts repaid and the remaining amounts for each loan.

The Deductions

For Employee:
User Story:
As an employee, I want to be able to view the deductions recorded for my salary by HR in the system.
Acceptance Criteria:
1. The employee should have an easy-to-use interface to display the deductions recorded on their salary.
2. Deductions should be clearly displayed, including the reason for each deduction, its amount if available, or the number of days if specified.
3. The display of deductions should be organized and understandable.
4. There should be an option for the employee to interact with the deductions, such as inquiring about them or requesting corrections if necessary.
For HR:
User Story:
As HR personnel, I want to record a deduction from an employee's salary in the system.
Acceptance Criteria:
1. The deduction should be recorded clearly, including the reason for the deduction and the amount if it's a monetary deduction, or the number of days if specified.
2. If the number of days for the deduction is specified, it should be calculated based on a 30-day month.
3. An notification should be sent to the employee regarding the recorded deduction from their salary.
4. HR should have an easy-to-use interface to record deductions and view previously recorded deductions.
Table of Required Fields and Mandatory Specifications:
Deduction Reason
Yes
HR must specify the reason for the deduction for the employee.
1
Deduction Amount
Optional
The amount of the deduction can be entered if it's a monetary deduction.
2
Deduction Days
Optional
The number of days to be deducted from the employee's salary can be specified.
3
Deduction Date
Yes
The date when the deduction is recorded must be specified.
4
Deduction Status
Yes
The status of the deduction, such as processed, pending, or rejected, must be specified.
There are no rows in this table
⁠

Request Payroll Deductions Cancels

For Employee:
User Story:
As an employee, I want to be able to select a deduction from my previous deductions that I wish to cancel.
Acceptance Criteria:
1. The employee should have access to a user interface allowing them to choose the deduction they want to cancel from their previous deductions.
2. The interface should display a list of previous deductions, enabling the employee to select the deduction they wish to cancel.
3. There should be a field for the employee to specify the reason for canceling the deduction.
4. After submitting the request, the system should update with the cancellation and send a notification to the employee confirming the cancellation request.
For HR:
User Story:
As an HR representative, I want to receive and process cancellation requests for payroll deductions submitted by employees.
Acceptance Criteria:
1. HR should receive notifications about cancellation requests submitted by employees for payroll deductions.
2. HR should have an interface to view and process received cancellation requests from employees.
3. Details of the cancellation request, including employee information, the deduction to be canceled, and the reason for cancellation, should be displayed.
4. HR should be able to approve or reject the cancellation request based on the provided information.
5. Upon approval or rejection of the cancellation request, the system should notify the employee of the outcome of their request.
Required Fields Table with Mandatory Specifications:
Table 18
Column 1
Column 2
Column 3
1
Field Name
Mandatory
Specifications
2
Deduction Selection
Yes
Employee must be able to select the deduction to cancel.
3
Reason for Cancellation
Yes
Employee must provide a reason for canceling the deduction.
There are no rows in this table
⁠

Request Commissions

For the Employee:
User Story:
As an employee, I want to request a commission payout from the system and specify the desired payout method and amount.
Acceptance Criteria:
1. The employee should have access to a feature to request a commission payout.
2. The employee should be able to select their preferred payout method, either with the salary or via bank transfer.
3. The employee should be able to input the desired amount for the commission payout.
For the HR Employee:
User Story:
As an HR employee, I need to review and process commission payout requests submitted by employees.
Acceptance Criteria:
1. The HR employee should have access to view and process commission payout requests submitted by employees.
2. The HR employee should be able to approve or reject commission payout requests based on company policies.
3. The HR employee should be able to see the requested amount for the commission payout.
Mandatory Specifications Table:
Table 30
Field Name
Mandatory
Specifications
1
Payout Method
Yes
The employee must specify the payout method, with options "With Salary" or "Bank Transfer".
2
Amount
Yes
The employee must specify the desired amount for the commission payout.
3
Request Date
Yes
The date when the request is submitted should be recorded.
4
Reason for Request
Optional
The employee may provide a reason for the commission payout request.
There are no rows in this table
⁠

Request Advances

User Stories:
For the Employee:
User Story:
As an employee, I want to request a financial advance from the system, specify the number of monthly installments deducted from my salary, and choose the preferred disbursement method along with the desired disbursement date.
Acceptance Criteria:
1. The employee should have access to a feature to request a financial advance.
2. The employee should be able to specify the desired amount for the advance and the number of monthly installments.
3. The employee should select the preferred disbursement method, either with the salary or via bank transfer.
4. If choosing bank transfer, the employee must select the desired bank account for the transfer.
5. The employee must specify the desired disbursement date for the financial advance.
For the Human Resources (HR) Staff:
User Story:
As an HR staff member, I need to review and process requests for financial advances submitted by employees, including the number of monthly installments, disbursement method, and disbursement date.
Acceptance Criteria:
1. The HR staff member should have access to view and process requests for financial advances submitted by employees.
2. The HR staff member should be able to approve or reject financial advance requests based on company policies.
3. Upon approval, the financial advance should be processed and recorded according to the specified number of monthly installments, disbursement method, and disbursement date.
Mandatory Specifications Table:
Table 31
Field Name
Mandatory
Specifications
1
Amount
Yes
The employee must specify the desired amount for the financial advance.
2
Monthly Installments
Yes
The employee must specify the number of monthly installments.
3
Advance Disbursement Method
Yes
The employee must select the preferred disbursement method, either with the salary or via bank transfer.
4
Bank Account (if bank transfer)
Optional
If choosing bank transfer, the employee must select the desired bank account for the transfer.
5
Disbursement Date
Yes
The employee must specify the desired disbursement date for the financial advance.
6
Reason (Optional)
Optional
The employee may provide a reason or explanation for the financial advance request.
7
Status
Yes
The status of the request, such as: pending, approved, rejected.
There are no rows in this table
⁠

Request Retirement Age Extensions

For the Employee:
User Story:
As an employee, I want to request an extension of my service after reaching retirement age by submitting the required details and documents through the system.
Acceptance Criteria:
1. The employee should have access to a feature to request an extension of their service after retirement age.
2. The employee must be able to view the latest medical report automatically fetched from the system and have the option to add a new medical report.
3. The employee must specify the desired extension period with a "From" and "To" date.
4. The employee must provide a reason for requesting the extension.
5. The employee can optionally attach a PDF file as supporting documentation.
6. The employee must acknowledge and agree to the company's terms and conditions for the request to be submitted.
For the Human Resources (HR) Staff:
User Story:
As an HR staff member, I need to review and process requests for retirement age extensions submitted by employees, ensuring all required information and documents are provided.
Acceptance Criteria:
1. The HR staff member should have access to view and process requests for retirement age extensions submitted by employees.
2. The HR staff member must see the latest medical report or the newly added report by the employee.
3. The HR staff member should verify the specified extension period and ensure it is within allowable limits.
4. The HR staff member must review the reason provided for the extension request.
5. The HR staff member must review any attached PDF files.
6. The HR staff member should ensure the employee has acknowledged the company's terms and conditions before processing the request.
Mandatory Specifications Table:
Table 32
Field Name
Mandatory
Specifications
1
Medical Report
Yes
The latest medical report fetched automatically from the system with an option to add a new report.
2
Extension Period
Yes
The period for the extension specified with "From" and "To" dates.
3
Reason
Yes
A text field for the employee to provide a reason for the extension.
4
Attachment
No
An optional field for the employee to attach a supporting document in PDF format.
5
Terms and Conditions
Yes
Display all company terms and conditions for the approval of this request. The employee must acknowledge them.
There are no rows in this table
⁠

Request Resignations

The Employee:
User Story:
As an employee, I want to submit my resignation from the company through the system, providing the necessary details and attachments.
Acceptance Criteria:
1. The employee should have access to a feature for submitting resignation through the system.
2. The employee should be able to enter the reason for resignation in a text field.
3. The employee should have the option to attach supporting documents in PDF format (optional).
4. The employee should receive a confirmation upon successful submission of the resignation request.
5. The employee should see the date of submission and the expected date of effect for the resignation
For the HR Representative:
User Story:
As an HR representative, I want to review and process employee resignation requests efficiently.
Acceptance Criteria:
1. The HR representative should have access to view all submitted resignation requests.
2. The HR representative should be able to review the reason for resignation and any attached documents.
3. The HR representative should have the option to approve or reject the resignation request.
4. The HR representative should be able to set the official end date of employment based on the company’s policies.
5. The HR representative should ensure the employee is notified of the decision regarding their resignation request.
Field Name Specifications:
Table 33
Field Name
Mandatory
Specifications
1
Reason for Resignation
Yes
Employee must provide the reason for resignation in text.
2
Supporting Documents
No
Option to attach documents in PDF format.
3
Submission Date
Yes
Automatically recorded upon submission.
4
Expected End Date
Yes
Date when the resignation is expected to take effect.
There are no rows in this table
⁠

Request Promotions

For the Employee:
User Story:
As an employee, I want to request a promotion through the system, providing necessary details and justifications for the promotion.
Acceptance Criteria:
1. The employee should have access to a feature for submitting a promotion request through the system.
2. The employee should be able to enter the desired new position and provide a justification for the promotion in a text field.
3. The employee should have the option to attach supporting documents in PDF format (optional).
4. The employee should receive a confirmation upon successful submission of the promotion request.
5. The employee should be able to track the status of their promotion request through the system.
For the HR Representative:
User Story:
As an HR representative, I want to review and process employee promotion requests efficiently.
Acceptance Criteria:
1. The HR representative should have access to view all submitted promotion requests.
2. The HR representative should be able to review the requested new position, justification for the promotion, and any attached documents.
3. The HR representative should have the option to approve or reject the promotion request.
4. The HR representative should be able to update the employee's position in the system upon approval.
5. The HR representative should ensure the employee is notified of the decision regarding their promotion request.
Field Name Specifications:
Table 34
Field Name
Mandatory
Specifications
1
Desired Position
Yes
TEXT
2
Justification
Yes
Employee must provide a justification for the promotion.
3
Supporting Documents
No
Option to attach supporting documents in PDF format.
4
Submission Date
Yes
Automatically recorded upon submission.
5
Request Status
Yes
Status of the request, such as pending, under review, approved, or rejected.
There are no rows in this table
⁠

Request Salary Improvements

For the Employee:
User Story:
As an employee, I want to request a salary improvement through the system, providing necessary details and justifications for the request.
Acceptance Criteria:
1. The employee should have access to a feature for submitting a salary improvement request through the system.
2. The employee should be able to specify the desired new salary and provide a justification for the request in a text field.
3. The employee should have the option to attach supporting documents in PDF format (optional).
4. The employee should receive a confirmation upon successful submission of the salary improvement request.
5. The employee should be able to track the status of their salary improvement request through the system.
For the HR Representative:
User Story:
As an HR representative, I want to review and process employee salary improvement requests efficiently.
Acceptance Criteria:
1. The HR representative should have access to view all submitted salary improvement requests.
2. The HR representative should be able to review the requested new salary, justification for the request, and any attached documents.
3. The HR representative should have the option to approve or reject the salary improvement request.
4. The HR representative should be able to update the employee's salary in the system upon approval.
5. The HR representative should ensure the employee is notified of the decision regarding their salary improvement request.
Field Name Specifications:
Table 35
Field Name
Mandatory
Specifications
1
Desired Salary
Yes
Employee must specify the new salary they are requesting.
2
Justification
Yes
Employee must provide a justification for the salary improvement.
3
Supporting Documents
No
Option to attach supporting documents in PDF format.
4
Submission Date
Yes
Automatically recorded upon submission.
5
Request Status
Yes
Status of the request, such as pending, under review, approved, or rejected.
There are no rows in this table
⁠

Request Work Hours Changes

For the Employee:
User Story:
As an employee, I want to request a change in my work hours through the system, providing necessary details and justifications for the request.
Acceptance Criteria:
1. The employee should have access to a feature for submitting a work hours change request through the system.
2. The employee should be able to choose from predefined work hours options set by HR.
3. The employee should be able to provide a justification for the request in a text field.
4. The employee should have the option to attach supporting documents in PDF format (optional).
5. The employee should receive a confirmation upon successful submission of the work hours change request.
6. The employee should be able to track the status of their work hours change request through the system.
For the HR Representative:
User Story:
As an HR representative, I want to review and process employee work hours change requests efficiently.
Acceptance Criteria:
1. The HR representative should have access to view all submitted work hours change requests.
2. The HR representative should be able to review the requested new work hours, justification for the request, and any attached documents.
3. The HR representative should have the option to approve or reject the work hours change request.
4. The HR representative should be able to update the employee's work hours in the system upon approval.
5. The HR representative should ensure the employee is notified of the decision regarding their work hours change request.
Field Name Specifications:
Table 36
Column 1
Column 2
Column 3
1
Field Name
Mandatory
Specifications
2
Desired Work Hours
Yes
Employee must select from predefined work hours set by HR.
3
Justification
Yes
Employee must provide a justification for the work hours change.
4
Supporting Documents
No
Option to attach supporting documents in PDF format.
There are no rows in this table
⁠

Request Vacation

For the Employee:
User Story:
As an employee, I want to request a vacation through the system, providing necessary details such as start and end dates, vacation type, and any additional information required.
Acceptance Criteria:
1. The employee should have access to a feature for submitting a vacation request through the system.
2. The employee should be able to select the start and end dates for the vacation.
3. The employee should be able to choose the type of vacation (e.g., annual leave, sick leave, etc.).
4. The employee should be able to provide additional information or justification for the vacation request in a text field.
5. The employee should have the option to attach supporting documents in PDF format (optional).
6. The employee should receive a confirmation upon successful submission of the vacation request.
7. The employee should be able to track the status of their vacation request through the system.
For the HR Representative:
User Story:
As an HR representative, I want to review and process employee vacation requests efficiently.
Acceptance Criteria:
1. The HR representative should have access to view all submitted vacation requests.
2. The HR representative should be able to review the vacation dates, type of vacation, justification for the request, and any attached documents.
3. The HR representative should have the option to approve or reject the vacation request.
4. The HR representative should be able to update the employee's vacation balance and record the approved vacation in the system upon approval.
5. The HR representative should ensure the employee is notified of the decision regarding their vacation request.
Field Name Specifications:
Table 37
Field Name
Mandatory
Specifications
1
Vacation Start Date
Yes
The employee must select the start date of the vacation.
2
Vacation End Date
Yes
The employee must select the end date of the vacation.
3
Vacation Type
Yes
The employee must select the type of vacation (e.g., annual leave, sick leave).
4
Justification
No
The employee can provide a justification for the vacation request in a text field.
5
Supporting Documents
No
Option to attach supporting documents in PDF format.
There are no rows in this table
⁠

Request Transfers

User Stories:
For the Employee:
User Story:
As an employee, I want to request a transfer from my current branch to another branch or from one department to another within the same branch.
Acceptance Criteria:
1. The employee should have access to a feature for submitting a transfer request through the system.
2. The employee should be able to select the type of transfer: from branch to branch or from department to department.
3. Based on the transfer type selected, the appropriate fields should be displayed:
- If the transfer type is from branch to branch: fields for current branch and new branch should be shown.
- If the transfer type is from department to department: fields for current department and new department should be shown.
4. The employee should be able to provide a reason for the transfer request in a text field.
5. The employee should have the option to attach supporting documents in PDF format (optional).
6. The employee should receive a confirmation upon successful submission of the transfer request.
7. The employee should be able to track the status of their transfer request through the system.
For the HR Representative:
User Story:
As an HR representative, I want to review and process employee transfer requests efficiently.
Acceptance Criteria:
1. The HR representative should have access to view all submitted transfer requests.
2. The HR representative should be able to review the transfer details, including the type of transfer (from branch to branch or from department to department), the current and new branch or department, the reason, and any attached documents.
3. The HR representative should have the option to approve or reject the transfer request.
4. The HR representative should be able to update the employee's records based on the approved transfer.
5. The HR representative should ensure the employee is notified of the decision regarding their transfer request.
Field Name Specifications:
Table 38
Column 1
Column 2
Column 3
1
Field Name
Mandatory
Specifications
2
Transfer Type
Yes
The employee must select the type of transfer: from branch to branch or from department to department.
3
Current Branch
Yes if transfer type is branch to branch
The employee must select their current branch.
4
New Branch
Yes if transfer type is branch to branch
The employee must select the new branch they wish to transfer to.
5
Current Department
Yes if transfer type is department to department
The employee must select their current department.
6
New Department
Yes if transfer type is department to department
The employee must select the new department they wish to transfer to.
7
Transfer Reason
Yes
The employee must provide a reason for the transfer request in a text field.
8
Supporting Documents
No
Option to attach supporting documents in PDF format.
9
Submission Date
Yes
Automatically recorded upon submission.
10
Request Status
Yes
Status of the request, such as pending, under review, approved, or rejected.
There are no rows in this table
⁠

Request Internal Delegations

Internal Delegations Request
Stakeholder: Employee
User Story:
As an employee, I want to submit an internal Delegations request to perform a specific task within the company at another branch or department, so that I can manage my tasks related to the Delegations outside my primary workplace.
Acceptance Criteria:
1. The form must be user-friendly and accessible through the employee portal.
2. The form should contain all the necessary fields to specify the Delegations details (target branch/department, Delegations period).
3. The employee must receive an acknowledgment upon submission of the request.
4. The employee should be notified of the request status at each stage.
Stakeholder: Direct Manager
User Story:
As a direct manager, I need to review internal Delegations requests submitted by employees under my supervision and evaluate them for approval or rejection based on work requirements.
Acceptance Criteria:
1. The manager must receive a notification immediately after an internal Delegations request is submitted by an employee.
2. The manager should be able to review all details of the Delegations request, including task objectives, target branch/department, and Delegations period.
3. The manager must be able to handle the request with the option to add explanatory comments.
4. The request status should be updated periodically, and the manager should be notified of any changes.
Stakeholder: Human Resources Department
User Story:
As an HR employee, I need to process internal Delegations requests submitted by employees and issue Delegations decisions based on specified policies.
Acceptance Criteria:
1. The HR department should be able to review requests approved by the direct manager and ensure they comply with policies.
2. The department must be able to issue necessary Delegations documents.
3. The department should be able to archive and manage all Delegations requests systematically.
4. The request status should be updated, and all concerned parties should be notified of any changes.
Form Fields and Mandatory Specifications for Internal Delegations
Table 3
Field Name
Mandatory
Specifications
Source
1
Name
Yes
Full name of the employee
Employee's personal data
2
Position
Yes
Current position of the employee
Employee's personal data
3
Organizational Unit
Yes
Department or division to which the employee belongs
Employee's personal data
4
Target Branch/Department
Yes
The branch or department to which the assignment will be made
Employee
5
Assignment Objectives
Yes
Clear description of the task objectives
Employee
6
Assignment Start Date
Yes
Expected start date of the assignment
Employee
7
Assignment End Date
Yes
Expected end date of the assignment
Employee
8
Expected Number of Assignment Days
Yes
Calculated based on the start and end dates
Employee
There are no rows in this table
⁠

Request External Delegations

External Delegations Request
Stakeholder: Employee
User Story:
As an employee, I want to submit an external Delegations request to perform a specific task outside the company in another country or city, so that I can manage my tasks related to the Delegations outside my primary workplace.
Acceptance Criteria:
1. The form must be user-friendly and accessible through the employee portal.
2. The form should contain all the necessary fields to specify the Delegations details (country, city, target entity, Delegations period).
3. The employee must receive an acknowledgment upon submission of the request.
4. The employee should be notified of the request status (under review, approved, rejected) periodically.
5. The request status should be available for the employee to review at any time.
Stakeholder: Direct Manager
User Story:
As a direct manager, I need to review external Delegations requests submitted by employees under my supervision and evaluate them for approval or rejection based on work requirements.
Acceptance Criteria:
1. The manager must receive a notification immediately after an external Delegations request is submitted by an employee.
2. The manager should be able to review all details of the Delegations request, including task objectives, country, city, target entity, and Delegations period.
3. The manager must be able to approve or reject the request with the option to add explanatory comments.
4. The request status should be updated periodically, and the manager should be notified of any changes.
Stakeholder: Human Resources Department
User Story:
As an HR employee, I need to process external Delegations requests submitted by employees and issue Delegations decisions based on specified policies.
Acceptance Criteria:
1. The HR department should be able to review requests approved by the direct manager and ensure they comply with policies.
2. The department must be able to issue necessary Delegations documents such as visas and travel tickets if needed.
3. The department should be able to archive and manage all Delegations requests systematically.
4. The request status should be updated, and all concerned parties should be notified of any changes.
Form Fields and Mandatory Specifications for External Delegations
Table 4
Field Name
Mandatory
Specifications
Source
1
Name
Yes
Full name of the employee
Employee's personal data
2
Position
Yes
Current position of the employee
Employee's personal data
3
Organizational Unit
Yes
Department or division to which the employee belongs
Employee's personal data
4
Country
Yes
The country to which the Delegations will be made
Employee
5
City
Yes
The city to which the Delegations will be made
Employee
6
Target Entity
Yes
The entity to which the Delegations will be made (e.g., company, another branch, institution)
Employee
7
Delegations Objectives
Yes
Clear description of the task objectives
Employee
8
Travel Itinerary
Yes
Details of the planned travel itinerary
Employee
9
Required Visas
Yes
Yes/No (with details of required visas, if any)
Employee
10
Delegations Start Date
Yes
Expected start date of the Delegations
Employee
11
Delegations End Date
Yes
Expected end date of the Delegations
Employee
12
Expected Number of Delegations Days
Yes
Calculated based on the start and end dates
Employee
There are no rows in this table
⁠

Request Permissions

For the Employee:
User Story:
As an employee, I want to request permission to either arrive late or leave early through the system.
Acceptance Criteria:
1. The employee should have access to a feature for submitting a permission request for arriving late or leaving early through the system.
2. The employee should be able to specify the type of permission requested (arriving late or leaving early).
3. The employee should be able to specify the date and time for the requested permission.
4. The employee should be able to provide a reason for the permission in a text field.
5. The employee should receive a confirmation upon successful submission of the permission request.
6. The employee should be able to track the status of their permission request through the system.
For the HR Representative:
User Story:
As an HR representative, I want to review and process permission requests for arriving late or leaving early submitted by employees efficiently.
Acceptance Criteria:
1. The HR representative should have access to view all submitted permission requests.
2. The HR representative should be able to review the permission details, including the type, date and time, reason, and any attached documents.
3. The HR representative should have the option to approve or reject the permission request.
4. The HR representative should ensure the employee is notified of the decision regarding their permission request.
Field Name Specifications:
Table 40
Field Name
Mandatory
Specifications
1
Permission Type
Yes
The employee must specify the type of permission requested (arriving late or leaving early).
2
Date and Time
Yes
The employee must specify the date and time for the requested permission.
3
Permission Reason
Yes
The employee must provide a reason for the permission request in a text field.
4
Supporting Documents
No
Option to attach supporting documents in PDF format.
There are no rows in this table
⁠

User Stories and Acceptance Criteria for Employee Performance Evaluation

HR Manager
User Story:
As an HR manager, I want to be able to define star values for each question in the quarterly evaluation so that I can determine the overall star rating for each employee.
Acceptance Criteria:
1. The HR manager should be able to define star values for each question in the evaluation.
2. The HR manager should be able to save and manage quarterly evaluations.
3. The system should display the total star rating for each employee based on the direct manager's evaluation.
4. The system should display previous evaluations for each employee and provide a visual comparison of the last 8 evaluations on a bar chart.
User Story:
As an HR manager, I want to receive a notification 10 days before the start of the quarterly evaluation period to remind me to prepare the necessary evaluations so that I do not miss the evaluation deadline.
Acceptance Criteria:
1. The HR manager should receive a notification 10 days before the start of the quarterly evaluation period.
2. The notification should include a reminder to prepare evaluations and define star values for each question.
Direct Manager
User Story:
As a direct manager, I want to be able to evaluate the performance of my employees using a star rating system so that I can provide fair and constructive evaluations.
Acceptance Criteria:
1. The manager should have access to the quarterly evaluations of their subordinates.
2. The evaluation should include a star rating system for each question.
3. The system should automatically calculate the total star rating.
4. The manager should be able to add constructive comments to each evaluation.
User Story:
As a direct manager, I want to receive a notification 10 days before the start of the quarterly evaluation period to remind me to conduct evaluations for my employees so that I do not miss the evaluation deadline.
Acceptance Criteria:
1. The direct manager should receive a notification 10 days before the start of the quarterly evaluation period.
2. The notification should include a reminder to conduct evaluations for their employees.
Employee
User Story:
As an employee, I want to be able to view my quarterly evaluation results and performance comments, as well as a visual comparison of my last 8 evaluations so that I can track my progress.
Acceptance Criteria:
1. The employee should be able to access their quarterly evaluation results after approval.
2. The final report should include the total star rating and manager comments.
3. The system should provide a visual comparison of the last 8 evaluations on a bar chart.
4. The employee should be able to add their own comments to the evaluation.
User Story:
As an employee, I want to receive a notification when my quarterly evaluation is complete so that I can know my results and performance feedback.
Acceptance Criteria:
1. The employee should receive a notification when the evaluation is complete.
2. The notification should include a summary of the evaluation results in star format.
3. The employee should be able to click on the notification to access the detailed evaluation page.
System Notifications
HR Notification:
- Trigger: 10 days before the start of the quarterly evaluation period.
- Recipient: HR manager.
- Content: "Reminder: The quarterly evaluation period is starting soon. Please prepare the evaluations and define star values for each question."
Manager Notification:
- Trigger: 10 days before the start of the quarterly evaluation period.
- Recipient: Direct manager.
- Content: "Reminder: The quarterly evaluation period is starting soon. Please conduct evaluations for your employees."
Employee Notification:
- Trigger: When the evaluation is complete and approved.
- Recipient: Employee.
- Content: "Your evaluation for the current quarter is complete. Click here to view your results and performance feedback."
By using these user stories, acceptance criteria, and defined fields, a comprehensive employee performance evaluation system can be developed, providing star-based ratings, reminder notifications, and detailed evaluation results for stakeholders.

The Health Report

User Stories and Acceptance Criteria
1. Employee
User Story 1:
As an employee, I want to fill out the health report electronically in the company application so that I can provide my health information easily before getting insured.
Acceptance Criteria:
- The employee should be able to access the health report through the company application.
- The report should include all required health-related questions.
- The employee should be able to fill out all mandatory fields and attach any supporting documents if necessary.
- The employee should receive a confirmation upon successful submission of the health report.
2. HR Staff
User Story 1:
As an HR staff member, I want to be able to review and analyze the health reports submitted by employees so that I can make informed insurance decisions based on the provided health information.
Acceptance Criteria:
- The HR staff member should be able to access the health reports submitted by employees.
- The HR staff member should be able to review all the data and attached documents.
- The HR staff member should be able to evaluate the health condition and make appropriate insurance decisions.
System Notifications
Employee Submission Confirmation Notification:
- Trigger: Upon submission of the health report.
- Recipient: Employee.
- Content: "Your health report has been received. Thank you for providing the required information."
This system ensures that employees can easily submit their health information through the company's application, facilitating HR's review and analysis to make informed insurance decisions.

Survey

For Employees:
1. User Story:
- As an employee, I want easy access to the survey so I can express my opinions and feelings about the work environment.
For HR Team:
2. User Story:
- As a HR team, I need detailed and centralized reports on the survey results so I can analyze them and make appropriate decisions to improve the work environment.
Acceptance Criteria:
For Employees:
1. Acceptance Criteria:
Access to the survey should be easy and quick, either via email or the company's internal system.
The survey interface should be user-friendly and allow employees to provide their opinions clearly and directly.
The system should provide employees with a dedicated page displaying their previous survey responses.
Employees should be able to edit their previous survey responses directly from this page.
Changes made to the survey responses should be saved automatically upon submission.
For HR Team:
2. Acceptance Criteria:
- The reports provided to HR should include detailed information about the number of participants in the survey and details about their responses to each question.
- Reports should be customizable and filterable to facilitate analysis and decision-making.

Decisions

User Stories:
1. Admin/HR Manager:
- As an Admin/HR manager, I want to send a decision to all employees or specific departments or individuals to ensure that the necessary personnel are informed about important company decisions.
- Acceptance Criteria:
- The system should allow creating a decision with a title and detailed message.
- The system should enable selecting recipients: all employees, specific departments, or specific employees.
- The system should send notifications to the selected recipients.
2. Employee:
- As an employee, I want to receive notifications of decisions from the administration to stay informed about important updates and policies.
- Acceptance Criteria:
- The employee should receive a notification when a decision is sent.
- The employee should be able to view the decision details.
- The employee should be able to acknowledge that they have read the decision by clicking a "Read" button.
3. Admin/HR Manager (for tracking):
- As an Admin/HR manager, I want to track who has read the decision to ensure compliance and awareness among employees.
- Acceptance Criteria:
- The system should display statistics on who has read the decision.
- The system should show a list of employees who have not yet read the decision.
- The system should allow exporting the read/unread status for further analysis.
Table 1
Field Name
Mandatory
Specifications
1
Decision Title
Yes
String, maximum length 150 characters
2
Decision Details
Yes
Text, no maximum length
3
Recipients
Yes
List, allows selection of all employees, specific departments, or specific employees
4
Sent Date
Yes
DateTime, auto-generated when the decision is sent
5
Read Status
Yes
Boolean, default value false, set to true when the employee clicks "Read"
6
Read Date
No
DateTime, auto-generated when the employee clicks "Read"
There are no rows in this table
⁠
Workflow:
1. Creation and Sending of Decision:
- The Admin/HR manager logs into the system.
- The Admin/HR manager navigates to the "Create Decision" section.
- The Admin/HR manager enters the decision title and details.
- The Admin/HR manager selects recipients (all employees, specific departments, or specific employees).
- The Admin/HR manager sends the decision, triggering notifications to the selected recipients.
2. Employee View and Acknowledgment:
- The employee receives a notification about the new decision.
- The employee logs into the system and views the decision details.
- The employee clicks the "Read" button to acknowledge they have read the decision.
3. Tracking and Reporting:
- The Admin/HR manager can view statistics on who has read the decision.
- The system provides a list of employees who have not yet read the decision.
- The Admin/HR manager can export the read/unread status for further analysis.
System Requirements:
- Notification System: To alert employees of new decisions.
- User Interface: For creating decisions, selecting recipients, and viewing decision details.
- Tracking System: To monitor read/unread status of decisions.

HR Letter Request

User Stories:
1. Employee:
- As an employee, I want to request an HR letter containing my salary details for various purposes such as applying for a visa or a loan.
- Acceptance Criteria:
- The employee should be able to request an HR letter through the system.
- The request should include basic employee information and salary details.
- The employee should receive a notification when the letter is issued.
2. HR Manager:
- As an HR manager, I want to be able to process HR letter requests quickly and efficiently to ensure employee satisfaction.
- Acceptance Criteria:
- The request should appear in the HR manager's dashboard with all necessary information.
- The manager should be able to generate the letter in PDF format and print it or send it via email to the employee.
- The manager should be able to track the status of previous requests.
Data Table with Source:
Table 2
Field Name
Mandatory
Source
Specifications (English)
1
Employee Name
Yes
HR Database
Text, maximum length 100 characters
2
Employee ID
Yes
HR Database
Unique identifier, alphanumeric, maximum length 20 characters
3
Department
Yes
HR Database
Text, maximum length 50 characters
4
Basic Salary
Yes
HR Database
Numeric (currency format), minimum value 0
5
Allowances
No
HR Database
Numeric (currency format), default value 0
6
Deductions
No
HR Database
Numeric (currency format), default value 0
7
Net Salary
Yes
HR Database
Numeric (currency format), calculated as (Basic Salary + Allowances) - Deductions
8
Reason for Request
Yes
Employee
Text, maximum length 200 characters
9
Request Date
Yes
System
DateTime, auto-generated when the request is submitted
10
Request Status
Yes
System
Text, values can be "New", "In Progress", "Completed"
11
Processing Date
No
System
DateTime, auto-generated when the request status is changed to "Completed"
There are no rows in this table
⁠
Workflow with Source:
1. Submitting HR Letter Request by Employee:
- The employee logs into the system.
- The employee navigates to the "HR Letter Request" section.
- The employee fills out the form with the required information such as the reason for the request.
- The employee submits the request.
2. Processing the Request by HR Manager:
- The HR manager receives a notification of a new request.
- The HR manager views the request in the dashboard and verifies the information.
- The HR manager retrieves employee information and salary details from the HR database.
- The HR manager prepares the letter in PDF format and prints it or sends it via email to the employee.
- The HR manager updates the request status to "Completed" and records the processing date.
3. Employee Notification:
- The employee receives a notification that the letter is ready.
- The employee can download the letter in PDF format from the system or receive it via email.
System Requirements with Source:
- Request Submission System (Employee):
- To allow employees to submit HR letter requests.
- Manager Dashboard (HR Manager):
- To view and process letter requests.
- HR Database (HR Department):
- To retrieve employee information and salary details.
- Notification System (System):
- To notify employees and managers of the status of requests.

Request Bonuses

Stakeholder: Employee
User Story:
As an employee, I want to submit a request for a bonus to recognize my performance and achievements, so that I can feel motivated and rewarded for my hard work.
Acceptance Criteria:
1. The bonus request form must be user-friendly and accessible through the employee portal.
2. The form should contain all the necessary fields to specify the reason for the bonus request and the desired bonus amount.
3. The employee must receive an acknowledgment upon submission of the request.
4. The employee should be notified of the request status (under review, approved, rejected) periodically.
5. The request status should be available for the employee to review at any time.
Stakeholder: Direct Manager
User Story:
As a direct manager, I need to review bonus requests submitted by employees under my supervision and evaluate them for approval or rejection based on performance metrics and budget constraints.
Acceptance Criteria:
1. The manager must receive a notification immediately after a bonus request is submitted by an employee.
2. The manager should be able to review all details of the bonus request, including the reason for the request and the desired bonus amount.
3. The manager must be able to approve or reject the request with the option to add explanatory comments.
4. The request status should be updated periodically, and the manager should be notified of any changes.
Stakeholder: Human Resources Department
User Story:
As an HR employee, I need to process bonus requests submitted by employees and issue bonus decisions based on specified policies and budget availability.
Acceptance Criteria:
1. The HR department should be able to review requests approved by the direct manager and ensure they comply with policies.
2. The department must be able to issue necessary bonus documentation.
3. The department should be able to archive and manage all bonus requests systematically.
4. The request status should be updated, and all concerned parties should be notified of any changes.
Form Fields and Mandatory Specifications for Bonus Request
Table 5
Field Name
Mandatory
Specifications
Source
1
Name
Yes
Full name of the employee
Employee's personal data
2
Position
Yes
Current position of the employee
Employee's personal data
3
Organizational Unit
Yes
Department or division to which the employee belongs
Employee's personal data
4
Reason for Bonus Request
Yes
Clear description of the reason for the bonus request
Employee
5
Desired Bonus Amount
Yes
The amount of bonus the employee is requesting
Employee
6
Supporting Documents
No
Any supporting documents for the bonus request
Employee
There are no rows in this table
⁠

Request to Add or Remove Family Member

Stakeholder: Employee
User Story:
As an employee, I want to submit a request to add a new family member or remove an existing one, so that I can accurately update my family information in the system.
Acceptance Criteria:
1. The form for adding/removing a family member must be user-friendly and accessible through the employee portal.
2. The form must contain all necessary fields to specify the new member’s information or the information of the member to be removed.
3. The employee must receive an acknowledgment upon submission of the request.
4. The employee should be notified of the request status (under review, approved, rejected) periodically.
5. The request status should be available for the employee to review at any time.
Stakeholder: Direct Manager
User Story:
As a direct manager, I need to review requests for adding or removing family members submitted by employees under my supervision and evaluate them for approval or rejection based on company policies.
Acceptance Criteria:
1. The manager must receive a notification immediately after a request to add or remove a family member is submitted by an employee.
2. The manager should be able to review all details of the request, including the family member’s information and reason for the request.
3. The manager must be able to approve or reject the request with the option to add explanatory comments.
4. The request status should be updated periodically, and the manager should be notified of any changes.
Stakeholder: Human Resources Department
User Story:
As an HR employee, I need to process requests for adding or removing family members submitted by employees and issue decisions based on specified policies and available documentation.
Acceptance Criteria:
1. The HR department should be able to review requests approved by the direct manager and ensure they comply with policies.
2. The department must be able to issue necessary documentation for updating the family member information.
3. The department should be able to archive and manage all requests systematically.
4. The request status should be updated, and all concerned parties should be notified of any changes.
Form Fields and Mandatory Specifications for Request to Add or Remove Family Member
Table 6
Field Name
Mandatory
Specifications
Source
1
Request Type
Yes
Specify the type of request (Add New Member / Remove Member)
Employee
2
Full Name
Yes
Full name of the family member
Employee
3
Date of Birth
Yes
Date of birth of the family member
Employee
4
Place of Birth
Yes
Place of birth of the family member
Employee
5
Gender
Yes
Gender of the family member
Employee
6
Place of Residence
Yes
Place of residence of the family member
Employee
7
Document Type
Yes
Type of document (Passport, Birth Certificate, etc.)
Employee
8
Document Number
Yes
Document number
Employee
9
Relationship
Yes
Relationship to the employee (Spouse, Child, Relative, etc.)
Employee
10
Evidence Document
No
Any supporting documents that prove the relationship
Employee
There are no rows in this table
⁠
Add or Remove Family Member Form
Add or Remove Family Member Form:
```
Request Type:
- Add New Member [ ]
- Remove Member [ ]
General Information of the Family Member:
- Full Name: [___________]
- Date of Birth: [___________]
- Place of Birth: [___________]
- Gender: [___________]
- Place of Residence: [___________]
- Document Type: [___________]
- Document Number: [___________]
- Relationship: [___________]
- Evidence Document (if any): [___________]
```
Viewing Family Information
Family / Marriages
View Marriage Information:
- View Marriages Button: [View Marriages]
Add Spouse:
- Add Spouse Button: [Add Spouse]
- Spouse’s Name: [Wife’s Name]
- Date of Birth: [Date of Birth]
- Place of Birth: [Place of Birth]
- Place of Residence: [Place of Residence]
- Passport: [Passport]
- Marriage Certificate: [Marriage Certificate]
Family / Children
View Children Information:
- View Children Button: [View Children]
Add Child:
- Add Child Button: [Add Child]
- Child’s Name: [Child’s Name]
- Date of Birth: [Date of Birth]
- Place of Birth: [Place of Birth]
- Gender: [Gender]
- Place of Residence: [Place of Residence]
- Child’s Birth Certificate: [Child’s Birth Certificate]
Family / Relatives
View Relatives Information:
- View Relatives Button: [View Relatives]
Add Relative:
- Add Relative Button: [Add Relative]
- Full Name: [Full Name]
- Date of Birth: [Date of Birth]
- Place of Birth: [Place of Birth]
- Gender: [Gender]
- Relationship: [Relationship]
- Evidence Document: [Evidence Document]

User Story: Show Employee Profile (As a Manager)

User Story:
As a manager, I want to view detailed employee profiles so that I can keep track of their personal information, job details, and performance history.
Acceptance Criteria:
1. The manager can view the employee profile card which includes a photo, full name, job title, email, department, employee ID, and experience (years + months).
2. The profile card also displays the number of requests, proposals, and complaints the employee has made, as well as their last performance review.
3. Additional fields available on the profile include:
- Phone number
- Hiring date
- Address
- Age
- Gender
- Nationality
- Sponsor
- Contract type
- Chronic diseases
- Emergency contact
- Number of marriages
- Number of children
4. There is an "Edit" button that allows the manager to modify these fields as necessary.
5. The profile page is well-organized and loads all relevant details promptly.

User Story: Request More Information (As a Manager or HR)

User Story: As a manager or HR employee, I want to request additional information from the employee regarding their request so that I can make an informed decision.
Acceptance Criteria:
Requesting More Information:
The manager or HR employee can click on the "Request More Information" button on the request page.
Upon clicking the "Request More Information" button, a text field appears where they can enter a message explaining the additional information required (Text & Number).
Sending the Request:
After writing the message, the manager or HR employee can send the request by clicking the "Send" button.
A notification is sent to the employee indicating that additional information is needed for their request.
Receiving Notification:
The employee receives a notification through the system that their request needs additional information.
The notification contains a message detailing the required information.
Employee Response:
The employee can open the request and view the message with the requested information.
The response text field is mandatory, and the employee must enter a response in the text field.
The employee has the option to upload a file containing the required information, but the file upload is optional.
After providing the additional information, the employee can submit their response by clicking the "Submit" button.
Receiving Response and Decision Making:
The manager or HR employee receives a notification that the employee has provided the additional information.
The manager or HR employee can review the response and any attached files.
Based on the new information, the manager or HR employee can make an informed decision.
Confirmation and Notifications:
A confirmation prompt appears before sending the request for additional information to ensure accuracy.
The employee receives a notification confirming the receipt of their response after submission.
The manager or HR employee can track the request status in the system to monitor progress.
Security and Permissions:
Only managers or HR employees with appropriate permissions can request and respond to additional information.
The system logs all requests and responses for audit purposes.
Status Update:
The request status is updated in the system based on the latest interaction between the employee and the manager or HR employee.
The request status (such as "Additional Information Required," "Responded," "Under Review") is displayed to the relevant users.

User Story: Adding a Family Member

User Story: As an employee, I want to add a family member to my profile, so that their information is included in the company's records.
Acceptance Criteria:
Adding a Family Member:
The employee can click on the "Add Family Member" button on their profile page.
Entering Family Member Details:
The employee is presented with a form to enter the family member's details:
Name (Text)
Relation (Dropdown selection)
Date of Birth (Date picker)
File Attachment (Optional file upload, such as proof of relationship)
Submitting the Request:
After filling in the details, the employee can click the "Submit" button to send the request.
A confirmation prompt appears before sending to ensure accuracy.
The request is submitted to the HR department for review.
HR Review:
HR receives a notification about the new family member addition request.
HR reviews the request and the attached file.
HR Decision:
HR can approve, reject, or request more information about the request.
If HR approves the request, the family member is added to the employee's family section in the profile.
If HR rejects the request, a notification is sent to the employee with the reason for rejection.
If HR requests more information, a notification is sent to the employee asking for the additional details.
Employee Notification:
The employee receives a notification about the HR decision:
Approval: The family member appears in the family section of the profile.
Rejection: The reason for rejection is included.
Request for more information: The details of the additional information needed are included.
Status Tracking:
The employee can track the status of their request in the system.
The status options include "Submitted," "Under Review," "Approved," "Rejected," and "More Information Required."
Security and Permissions:
Only the employee can submit the request to add a family member.
Only HR personnel with appropriate permissions can review and process the request.
Example User Interface:
Form for Adding a Family Member:
Name: [Text Field]
Relation: [Dropdown Selection]
Date of Birth: [Date Picker]
File Attachment: [File Upload Button]
Submit: [Submit Button]
HR Review Interface:
View Details of the Request
Approve Button
Reject Button (with Reason Field)
Request More Info Button (with Message Fiel


Classification and Requests Table
User Story: Employee - Viewing Salary Details
User Story: Employee - Viewing Basic Salary Details
User Story: Employee - Viewing Bonuses Details
User Story: Employee - Viewing Commissions Details
User Story: Employee - Viewing Allowances Details
User Story: Employee - Viewing Loan Details
User Story: HR Manager - Managing Basic Salary Details
User Story: HR Manager - Managing Bonuses Details
User Story: HR Manager - Managing Commissions Details
User Story: HR Manager - Managing Allowances Details
User Story: HR Manager - Managing Loan Details
The Deductions
Request Payroll Deductions Cancels
Request Commissions
Request Advances
Request Retirement Age Extensions
Request Resignations
Request Promotions
Request Salary Improvements
Request Work Hours Changes
Request Vacation
Request Transfers
Request Internal Delegations
Request External Delegations
Request Permissions
User Stories and Acceptance Criteria for Employee Performance Evaluation
The Health Report
Survey
Decisions
HR Letter Request
Request Bonuses
Request to Add or Remove Family Member
User Story: Show Employee Profile (As a Manager)
User Story: Request More Information (As a Manager or HR)
User Story: Adding a Family Member
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.