-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time Off Request Sequence Diagram #29
Comments
Also, a few questions on top of my head:
In the future, we can also think about the following:
|
Do we set a carryover cap or do we put a fixed number of timeoff days in a year? |
Let's build in versions, eg version 1, version 2 etc. In the first version we don't have to implement carryover or carry over cap. This would be v1. In v2 we would implement carryover login. You can also make a list of those features and implement the most important in v1, making sure features in v2 will be easily implemented afterwards and that v1 features do not become a barrier for v2 features. |
Ok got it! |
Let me list the things to consider in version 1.
|
The above points are for version 1. The other features like accrual type policies will be considered in version 2. In case of confusion, there is a simple product documentation above each Figma screens. Along with the Figma designs itself, it may help answer some simple questions. And, I'd be glad to answer any further questions, for sure. :) |
Create a timeoff API sequence diagram to show how the timeoff works in the application. The sequence diagram should have the following.
How the different entities communicate
How are requests sent
The reasons for timeoff/ accrual policy
Maximum amount of time off that can be accrued.
Number of days time off is allowed in a year
What are the rules for carrying over unused time off to the next period? (carryover policy)
Track accrued, used and remaining time offs
The text was updated successfully, but these errors were encountered: