Skip to content
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

payAdventure #13

Open
1 of 6 tasks
madalenassembleia opened this issue Oct 29, 2018 · 0 comments
Open
1 of 6 tasks

payAdventure #13

madalenassembleia opened this issue Oct 29, 2018 · 0 comments
Labels
operation Operation in the system

Comments

@madalenassembleia
Copy link
Collaborator

madalenassembleia commented Oct 29, 2018

Effects: Makes, for client client, the activity reservationactReserv and hotel room reservations roomReserv needed for all participants, calculates tax of the purchase, debits the client’s account fromAccount with the amount amount plus tax, credits the broker’s account toAccount with amount, makes an invoice invoice for the purchase with purchase type Leisure. After this operation, the state of the adventure is
PayedState.

Input: adv, client, num, broker, actReserv, roomReserv, amount, fromAccount, toAccount, invoice

  • It is only possible to pay for adventures added to Adventure Builder. (26)

  • For each adventure in Adventure Builder, the account that is used for
    paying for the adventure belongs to the client that the adventure is created
    for. (27)

  • For each adventure in Adventure Builder, the account that is credited belongs
    to the broker who arranged the adventure. (28)

  • If an adventure is payed for, then it has been created. (31)

  • If an adventure is payed, then the corresponding invoice is created. (35)

  • Tax on purchase depends on the kind of purchase and the price, and the
    tax is always ≥ 0. (37)

@rgcv rgcv added the operation Operation in the system label Oct 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
operation Operation in the system
Development

No branches or pull requests

2 participants