Update AstronoteSpecification.md
This commit is contained in:
parent
5f12fe2112
commit
98c0d7d12b
@ -39,8 +39,7 @@ Sessions are cookie-based
|
||||
|
||||
[ ] ==**DASHBOARD**==
|
||||
|
||||
Dashboard ensures draft and unvalidated expense reports management, sorted by year and company
|
||||
Within each year sorted in decending order, expense reports are sorted by month in ascending order
|
||||
Dashboard ensures draft and unvalidated expense reports management
|
||||
Every expense report in the dashboard features the following parameters:
|
||||
- Expense status (validated, unvalidated or draft)
|
||||
- Expense data (date, charge incl. and excl. taxes, VAT, distance)
|
||||
@ -57,17 +56,20 @@ Baseline scenario:
|
||||
|
||||
[ ] ==**MANAGE EXPENSE REPORT**==
|
||||
|
||||
Expenses are divided into two sections : costs related to a company (Costs) and the costs related to a customer (Purchases)
|
||||
Expenses include :
|
||||
- date, type, description, charge incl. and excl. taxes, VAT
|
||||
- for mileage expense : date, type, provision, origin, destination, distance
|
||||
|
||||
Only expenses report related to a company will be developed in this step
|
||||
|
||||
Expense report dashboard allows user to keep track of:
|
||||
- Expense report status
|
||||
- Supporting document (or lack thereof)
|
||||
- Saved comments (including writer name, writing date and comment content)
|
||||
- Business expenses
|
||||
|
||||
Expenses are divided into two sections : costs related to a company (Costs) and the costs related to a customer (Purchases)
|
||||
Expenses include :
|
||||
- date, type, description, charge incl. and excl. taxes, VAT
|
||||
- for mileage expense : date, type, provision, origin, destination, distance
|
||||
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and picks specific expence report
|
||||
2. All expense report details are displayed
|
||||
@ -88,7 +90,7 @@ Newly created expense reports are automatically saved as drafts
|
||||
[ ] ==**ADD BUSINESS-RELATED EXPENSE (company)**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to add to. User is redirected to specific expense report HCI, selects "Costs" category and clicks add button
|
||||
1. Active user goes to HCI and selects expense report to add to. User is redirected to specific expense report HCI and clicks add button
|
||||
2. User can complete overhead form with appropriate data
|
||||
3. User can complete line charge form with appropriate data
|
||||
4. User confirms or cancels expense addition
|
||||
@ -106,7 +108,7 @@ Expense can only be added if expense report is already saved as draft
|
||||
[ ] ==**EDIT BUSINESS-RELATED EXPENSE (company)**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to edit from. User is redirected to specific expense report HCI, selects "Costs" category and clicks specific edit button
|
||||
1. Active user goes to HCI and selects expense report to edit from. User is redirected to specific expense report HCI and clicks specific edit button
|
||||
2. User can complete overhead form with appropriate data (fields have current values as default values)
|
||||
3. User can complete line charge form with appropriate data (fields have current values as default values)
|
||||
4. User confirms or cancels expense edition
|
||||
@ -124,7 +126,7 @@ Expense can only be added if expense report is already saved as draft
|
||||
[ ] ==**ADD BUSINESS-RELATED TRAVEL EXPENSE (company)**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to add to. User is redirected to specific expense report HCI, selects "Costs" category and clicks add button
|
||||
1. Active user goes to HCI and selects expense report to add to. User is redirected to specific expense report HCI and clicks add button
|
||||
2. User completes form with appropriate data
|
||||
3. User confirms or cancels expense addition
|
||||
|
||||
@ -138,7 +140,7 @@ Expense can only be added if expense report is already saved as draft.
|
||||
[ ] ==**EDIT BUSINESS-RELATED TRAVEL EXPENSE (company)**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to edit from. User is redirected to specific expense report HCI, selects "Costs" category and clicks specific edit button
|
||||
1. Active user goes to HCI and selects expense report to edit from. User is redirected to specific expense report HCI and clicks specific edit button
|
||||
2. User completes form with appropriate data (fields have current values as default values)
|
||||
3. User confirms or cancels expense addition
|
||||
|
||||
@ -152,7 +154,7 @@ Expense can only be added if expense report is already saved as draft.
|
||||
[ ] ==**DELETE EXPENSE**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to delete expense from. User is redirected to specific expense report HCI, selects "Costs" or "Purchases" category and clicks specific delete button
|
||||
1. Active user goes to HCI and selects expense report to delete expense from. User is redirected to specific expense report HCI and clicks specific delete button
|
||||
2. User is prompted for deletion confirmation as safety measure
|
||||
3. User confirms or cancels deletion
|
||||
|
||||
@ -162,7 +164,7 @@ An expense can only be delete if expense report is already saved as draft.
|
||||
[ ] ==**SAVE EXPENSE REPORT**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to save. User is redirected to specific expense and clicks save button
|
||||
1. Active user goes to HCI and selects expense report to save. User is redirected to specific expense and clicks save button
|
||||
2. User completes form with appropriate data (comments that are optional)
|
||||
3. User confirms or cancels
|
||||
|
||||
@ -173,7 +175,7 @@ Comments will be displayed in dashboard HCI from then on
|
||||
[ ] ==**DELETE EXPENSE REPORT**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to delete. User is redirected to specific expense report HCI and clicks delete button
|
||||
1. Active user goes to HCI and selects expense report to delete. User is redirected to specific expense report HCI and clicks delete button
|
||||
2. User is prompted for deletion confirmation as safety measure
|
||||
3. User confirms or cancels
|
||||
|
||||
@ -184,7 +186,7 @@ If deleted expense report was awaiting validation, it is returned to draft statu
|
||||
[ ] ==**SUBMIT EXPENSE REPORT FOR VALIDATION**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to submit for validation. User is redirected to specific expense report HCI and clicks validate button
|
||||
1. Active user goes to HCI and selects expense report to submit for validation. User is redirected to specific expense report HCI and clicks validate button
|
||||
2. User completes form with appropriate data (comment that is optional)
|
||||
3. User confirms or cancels
|
||||
|
||||
@ -197,7 +199,7 @@ Expense reports might have another status but those are not accessible on the us
|
||||
[ ] ==**ATTACH SUPPORTING DOCUMENT TO EXPENSE**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to attach a document in. User is redirected to specific expense report HCI and clicks attach button
|
||||
1. Active user goes to HCI and selects expense report to attach a document in. User is redirected to specific expense report HCI, browses supporting document files and clicks attach button
|
||||
2. User completes form with appropriate data
|
||||
3. User confirms or cancels attachment
|
||||
|
||||
@ -212,7 +214,7 @@ Supporting documents can be joined regardless of expense report status
|
||||
[ ] ==**DELETE SUPPORTING DOCUMENT FROM EXPENSE**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to delete a document in. User is redirected to specific expense report HCI, browses supporting document files and clicks file link
|
||||
1. Active user goes to HCI and selects expense report to delete a document in. User is redirected to specific expense report HCI, browses supporting document files and clicks file link
|
||||
2. File information is displayed on click (description, file name, file size, upload date, last edit date)
|
||||
3. User clicks delete button
|
||||
4. User is prompted for deletion confirmation as safety measure
|
||||
@ -224,7 +226,7 @@ Supporting documents can be deleted regardless of expense report status
|
||||
[ ] ==**EDIT SUPPORTING DOCUMENT FROM EXPENSE**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to edit a document in. User is redirected to specific expense report HCI, browses supporting document files and clicks file link
|
||||
1. Active user goes to HCI and selects expense report to edit a document in. User is redirected to specific expense report HCI, browses supporting document files and clicks file link
|
||||
2. File information is displayed
|
||||
3. User clicks edit button
|
||||
4. User completes form with appropriate data (fields have current values as default values, including file)
|
||||
@ -241,7 +243,7 @@ Supporting documents can be edited regardless of expense report status
|
||||
[ ] ==**GENERATE EXPENSE WITH OCR**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to generate expense in. User is redirected to specific expense report HCI, selects "Costs" or "Purchases" category and clicks generate button
|
||||
1. Active user goes to HCI and selects expense report to generate expense in. User is redirected to specific expense report HCI and clicks generate button
|
||||
2. User selects snapshot from gallery or takes snapshot on the spot
|
||||
3. OCR system parses data from snapshot and automatically compute rates
|
||||
4. Form loads with parsed data as default value in appropriate fields
|
||||
@ -251,7 +253,7 @@ Baseline scenario:
|
||||
[ ] ==**ADD CUSTOMER INTERACTION-RELATED EXPENSE**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to add to. User is redirected to specific expense report HCI, selects "Purchases" category and clicks add button
|
||||
1. Active user goes to HCI and selects and expense report to add to. User is redirected to specific expense report HCI and clicks add button
|
||||
2. User can complete overhead form with appropriate data
|
||||
3. User can complete line charge form with appropriate data
|
||||
4. User confirms or cancels expense addition
|
||||
@ -269,7 +271,7 @@ Expense can only be added if expense report is already saved as draft
|
||||
[ ] ==**EDIT CUSTOMER INTERACTION-RELATED EXPENSE**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to edit from. User is redirected to specific expense report HCI, selects "Purchases" category and clicks specific edit button
|
||||
1. Active user goes to HCI and selects expense report to edit from. User is redirected to specific expense report HCI and clicks specific edit button
|
||||
2. User can complete overhead form with appropriate data (fields have current values as default values)
|
||||
3. User can complete line charge form with appropriate data (fields have current values as default values)
|
||||
4. User confirms or cancels expense edition
|
||||
@ -287,7 +289,7 @@ Expense can only be added if expense report is already saved as draft
|
||||
[ ] ==**ADD CUSTOMER INTERACTION-RELATED TRAVEL EXPENSE**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to add to. User is redirected to specific expense report HCI, selects "Purchases" category and clicks add button
|
||||
1. Active user goes to HCI and selects expense report to add to. User is redirected to specific expense report HCI and clicks add button
|
||||
2. User completes form with appropriate data
|
||||
3. User confirms or cancels expense addition
|
||||
|
||||
@ -301,7 +303,7 @@ Expense can only be added if expense report is already saved as draft
|
||||
[ ] ==**EDIT CUSTOMER INTERACTION-RELATED TRAVEL EXPENSE**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to edit from. User is redirected to specific expense report HCI, selects "Purchases" category and clicks specific edit button
|
||||
1. Active user goes to HCI and selects expense report to edit from. User is redirected to specific expense report HCI and clicks specific edit button
|
||||
2. User completes form with appropriate data (fields have current values as default values)
|
||||
3. User confirms or cancels expense edition
|
||||
|
||||
@ -315,7 +317,7 @@ Expense can only be added if expense report is already saved as draft
|
||||
[ ] ==**COPY EXPENSE**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to copy expense from. User is redirected to specific expense report HCI, selects "Costs" or "Purchases" category and clicks specific copy button
|
||||
1. Active user goes to HCI and selects expense report to copy expense from. User is redirected to specific expense report HCI and clicks specific copy button
|
||||
2. User specifies to which expense report the expense needs to be copied. Only expense reports already saved as drafts can be selected. Default value is current expense report
|
||||
3. User confirms or cancels copy
|
||||
|
||||
@ -326,7 +328,7 @@ An expense can only be copied if expense report is already saved as draft
|
||||
[ ] ==**COPY EXPENSE REPORT**==
|
||||
|
||||
Baseline scenario:
|
||||
1. Active user goes to HCI and selects year and expense report to copy. User is redirected to specific expense report HCI and clicks copy button
|
||||
1. Active user goes to HCI and selects expense report to copy. User is redirected to specific expense report HCI and clicks copy button
|
||||
2. User specifies month and year
|
||||
3. User confirms or cancels
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user