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

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

Remove pagebreak to save paper.

Add more use cases.

File size: 1.2 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-officer
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/user-add
29   use-cases/user-manage
30   use-cases/user-remove
31
32
33Further use cases:
34
35* Import legacy data into new system
36
37  Convert legacy data suitable for new system before.
38
39* Add supplementary contract
40
41* Manage supplementary contract
42
43* Remove supplementary contract
44
45* Add transaction
46
47* Remove transaction
48
49* Add meter
50
51* Manage meter
52
53* Remove meter
54
55* Read meter
56
57* Request new password
58
59* Customer initializes existing user/customer account
Note: See TracBrowser for help on using the repository browser.