| Line | |
|---|
| 1 | .. _label-use-cases: |
|---|
| 2 | |
|---|
| 3 | Use Cases |
|---|
| 4 | ********* |
|---|
| 5 | |
|---|
| 6 | Here we collect all use-cases identified to occur with regard to the |
|---|
| 7 | Eko Disco Portal. Use-cases are important to check which |
|---|
| 8 | :ref:`label-actors` interact with the system in what way. |
|---|
| 9 | |
|---|
| 10 | In use case titles we distinguish between 'manage' and 'edit'. |
|---|
| 11 | The first verb refer to manager actions and the second to |
|---|
| 12 | customer actions respectively. Actually 'managing' means |
|---|
| 13 | editing by Manager. |
|---|
| 14 | |
|---|
| 15 | .. toctree:: |
|---|
| 16 | :maxdepth: 1 |
|---|
| 17 | |
|---|
| 18 | use-cases/customer-add-by-mg |
|---|
| 19 | use-cases/customer-add-by-anon |
|---|
| 20 | use-cases/customer-edit-basedata |
|---|
| 21 | use-cases/customer-remove |
|---|
| 22 | use-cases/contract-add |
|---|
| 23 | use-cases/contract-manage |
|---|
| 24 | use-cases/contract-remove |
|---|
| 25 | use-cases/service-add |
|---|
| 26 | use-cases/service-manage |
|---|
| 27 | use-cases/service-remove |
|---|
| 28 | .. use-cases/meter-reading |
|---|
| 29 | .. use-cases/mg-customer-add |
|---|
| 30 | |
|---|
| 31 | |
|---|
| 32 | Identified use cases: |
|---|
| 33 | |
|---|
| 34 | * Import legacy data into new system |
|---|
| 35 | |
|---|
| 36 | Convert legacy data suitable for new system before. |
|---|
| 37 | |
|---|
| 38 | * Add customer by manager |
|---|
| 39 | |
|---|
| 40 | * Add customer by anonymous (self-registration) |
|---|
| 41 | |
|---|
| 42 | * Edit customer base data (contact data and password) |
|---|
| 43 | |
|---|
| 44 | * Remove customer |
|---|
| 45 | |
|---|
| 46 | * Add contract |
|---|
| 47 | |
|---|
| 48 | * Manage contract |
|---|
| 49 | |
|---|
| 50 | * Remove contract |
|---|
| 51 | |
|---|
| 52 | * Add service |
|---|
| 53 | |
|---|
| 54 | * Manage service |
|---|
| 55 | |
|---|
| 56 | * Remove service |
|---|
| 57 | |
|---|
| 58 | * Add subcontract |
|---|
| 59 | |
|---|
| 60 | * Manage subcontract |
|---|
| 61 | |
|---|
| 62 | * Remove subcontract |
|---|
| 63 | |
|---|
| 64 | * Add transaction |
|---|
| 65 | |
|---|
| 66 | * Remove transaction |
|---|
| 67 | |
|---|
| 68 | * Add meter |
|---|
| 69 | |
|---|
| 70 | * Manage meter |
|---|
| 71 | |
|---|
| 72 | * Remove meter |
|---|
| 73 | |
|---|
| 74 | * Read meter |
|---|
| 75 | |
|---|
| 76 | * Add user and assign roles |
|---|
| 77 | |
|---|
| 78 | Depending on the role, different user data entities (Officer, Customer, |
|---|
| 79 | Accountant) are automatically created. |
|---|
| 80 | |
|---|
| 81 | * Add service |
|---|
| 82 | |
|---|
| 83 | * Manage service |
|---|
| 84 | |
|---|
| 85 | * Remove service |
|---|
| 86 | |
|---|
| 87 | |
|---|
| 88 | |
|---|
Note: See
TracBrowser for help on using the repository browser.
