source: main/eko-disco-specs/trunk/use-cases/service-manage.rst

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

Shorten use case titles.

Link data entities to use cases only if necessary/interesting.

File size: 2.2 KB
Line 
1.. _label-uc-service-manage:
2
3Modify a Service
4***********************************************************************
5
6Short Description
7-----------------------------------------------------------------------
8
9A service is modified by staff.
10
11Actor(s)
12-----------------------------------------------------------------------
13
14Officer
15
16
17Trigger(s)
18-----------------------------------------------------------------------
19
20- Imports (modifying existing data)
21- Web form(s) submitted by authorized user
22
23
24Result(s)
25-----------------------------------------------------------------------
26
27- Data (terms, title, description) of the given service is modified.
28
29
30Incoming Data
31-----------------------------------------------------------------------
32
33- Service ID, names and values of parameters to change
34
35Outgoing Data
36-----------------------------------------------------------------------
37
38- Message about service modification.
39- Regarding customers are informed by email or
40  SMS. Regarding customers are those having a contract created by
41  the modified service.
42- Log message
43
44
45Precondition(s)
46-----------------------------------------------------------------------
47
48- Service ID must exist.
49- Submitting user must be authorized to perform the operation.
50
51
52Postcondition(s)
53-----------------------------------------------------------------------
54
55- The new service data were checked for validity. Validation here is
56  stricter than when adding a service. For instance it is not allowed
57  to change terms for the past if there are already existing
58  contracts created by this service.
59
60
61Invariant(s)
62-----------------------------------------------------------------------
63
64
65Essential Steps
66-----------------------------------------------------------------------
67
68- System receives service ID and any optional parameters
69  specifying the data to change in the service.
70- Data is validated.
71- If passed-in parameters are invalid, user is offered a possibility
72  to fix the invalid data.
73- System updates the given service.
74
75
76Open Issues
77-----------------------------------------------------------------------
78
79
80
81Remarks
82-----------------------------------------------------------------------
83
84
85.. raw:: latex
86
87      \
Note: See TracBrowser for help on using the repository browser.