The file's text, extracted by GovTribe without its formatting.
GSA SOLICITATION QMAD-JM-100001-N
August 23, 2010
GSA SOLICITATION QMAD-JM-100001-N
Attachment 7 – Notional ETS2 Use Cases and User Roles August 23, 2010
Attachment 7 Notional ETS2 Use Cases and User Roles
| No. |
| Use Case Description |
| Actors |
| 1 |
| Create, modify, delete, and print traveler profile. |
| FT, FTA, FATA |
| 2 |
| Create, modify, cancel, route, and print a travel request before authorization for all travel scenarios before approval. |
| FT, FTA, FATA |
| 3 |
| Authorize, reject, cancel, route, and print a travel request for all travel scenarios with attendant comments and accounting functionality (commitment or obligation). |
| FSTA, FFTA, FATA |
| 4 |
| Create, modify, and cancel airline and rail reservations prior to ticket issuance (subject to vendor cancellation provisions). |
| FT, FTA, FATA |
| 5 |
| Create, modify, and cancel car rental and hotel reservations online at any point in the travel process (subject to vendor cancellation provisions). |
| FT, FTA, FATA |
| 6 |
| View, print, and route travel itinerary. |
| FT, FTA, FSTA, FFTA, FATA, FA, FVE |
| 7 |
| Create, modify (before approval), and route a voucher for all travel scenarios. |
| FT, FTA |
| 8 |
| Create, modify (before approval), and route a voucher amendment for all travel scenarios. |
| FT, FTA |
| 9 |
| Modify (before approval), and route a voucher for all travel scenarios. |
| FSTA, FFTA, FATA |
| 10 |
| Modify (before approval), and route a voucher amendment for all travel scenarios. |
| FSTA, FFTA, FATA |
| 11 |
| Authorize, reject, cancel, modify as appropriate and route a voucher or voucher amendment with attendant comments and accounting functionality (expenditure). |
| FSTA, FFTA, FATA |
| 12 |
| Create and document reports as appropriate by user role. |
| FT, FTA, FTSA,FFTA, FATA, FA, FVE |
| 13 |
| Agency/Department-level system administration: create, delete, and manage user accounts; create, delete, and manage all subsequent level administrator accounts; create, modify, and delete system policies and system features at the component/sub-component level (with the capability to override component/sub-component level system administrative functions). |
| FATA |
| 14 |
| Bureau/Component-level system administration: create and delete user accounts; create, modify, and manage user rights; create, modify, and manage policies; manage systems features. |
| FATA |
| 15 |
| Sub-component level system administration: create, delete and manage sub-component level administrator accounts; these administrator accounts are created with limited administrator access privileges |
| FATA |
| 16 |
| Review travel authorizations and vouchers for the purpose of auditing with the ability to subsequently route the document in accordance with agency auditing rules |
| FVE |
| 17 |
| Ability to configure access rights at the agency/ component/ sub-component level; able to provide different levels of access (e.g. ability to configure only certain administrators to create new profiles) |
| FATA |
| 18 |
| Review travel document without having to visit the pending approval queue. The ability to modify and disapprove a document should be done via the pending documents queue by the approver. |
| FSTA, FFTA, FA |
| FT | = Federal Traveler |
| FTA | = Federal Travel Arranger |
| FSTA | = Federal Supervisory Travel Approver |
| FFTA | = Federal Financial Travel Approver |
| FATA | = Federal Agency Travel Administrator |
| FA | = Federal Auditor |
| FVE | = Federal Voucher Examiner |