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

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

Some stuff for discussion.

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/meter-reading
19..   use-cases/mg-customer-add
20
21
22Identified use cases:
23
24* Import legacy data into new system
25
26  Convert legacy data suitable for new system before.
27
28* Add Customer by Manager
29
30* Add Customer by Anonymous
31
32  (self-registration)
33
34* Edit Customer Data
35
36  i.e. Contact Data and password
37
38* Remove Customer
39
40* Add Contract
41
42* Manage Contract
43
44* Remove Contract
45
46* Add Subcontract
47
48* Manage Subcontract
49
50* Remove Subcontract
51
52* Add Transaction
53
54* Remove Transaction
55
56* Add Meter
57
58* Manage Meter
59
60* Remove Meter
61
62* Read Meter
63
64* Add User and Assign Roles
65
66  Depending on the role, different user data entities (Officer, Customer,
67  Accountant) are automatically created.
68
69* Add Service
70
71* Manage Service
72
73* Remove Service
74
75
76
Note: See TracBrowser for help on using the repository browser.