source: main/eko-disco-specs/trunk/use-cases.rst @ 10765

Last change on this file since 10765 was 10755, checked in by Henrik Bettermann, 11 years ago

Adjust use cases index page.

File size: 1.1 KB
Line 
1.. _label-use-cases:
2
3Use Cases
4*********
5
6Here we collect all use-cases identified to occur with regard to the
7Eko Disco Portal. Use-cases are important to check which
8:ref:`label-actors` interact with the system in what way.
9
10In use case titles we distinguish between 'manage' and 'edit'.
11The first verb refer to manager actions and the second to
12customer actions respectively. Actually 'managing' means
13editing 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
29
30Further use cases:
31
32* Import legacy data into new system
33
34  Convert legacy data suitable for new system before.
35
36* Add subcontract
37
38* Manage subcontract
39
40* Remove subcontract
41
42* Add transaction
43
44* Remove transaction
45
46* Add meter
47
48* Manage meter
49
50* Remove meter
51
52* Read meter
53
54* Add user and assign roles
55
56  Depending on the role, different user data entities (Officer, Customer,
57  Accountant) are automatically created.
58
Note: See TracBrowser for help on using the repository browser.