LEAVE

MANAGEMENT SYSTEM

1. REQUIREMENTS
A. Employees can apply for leave (Short, Sick, Casual, Annual)
B. Managers can approve leave
C. Employees and Managers can check the leaves calendars
D. Employees can upload documents while applying for leave
E. Get email alerts in real time when an employee applies for leave and approved or
cancel the leave
F. Leave approval process should through team hierarchy
G. Employees can cancel their leave until leave approved.

2. TASKS AND TIMELINES

A. Documentation and planning
i. Write a proposal for this system – 2 Days
ii. Drowning the mockup for this system – 2 Days
iii. Plan the database schema – 1day

B. Front-end
i. Write the test cases – 4Days
ii. Developments – 5 Days
iii. Manual Testing – 1Days

C. Back-end
i. Write the test cases – 4Days
ii. Developments – 5 Days
iii. Manual Testing – 1Days

3. TECHNICALS DEFINITION
A. You should follow test driven development
B. You should use Laravel for API service
i. You should use Laravel observer for workflow process
C. You should use React for font-end application
D. You should follow PSR standards
E. Test cases should cover more than 90% of the code