| 1 | .. _label-uc-service-manage: |
|---|
| 2 | |
|---|
| 3 | Use-Case: Modify a Service |
|---|
| 4 | *********************************************************************** |
|---|
| 5 | |
|---|
| 6 | .. Description of a use case |
|---|
| 7 | .. The description must be formulated as seen from system (not: actors) |
|---|
| 8 | .. Describes those changes an (outside) actor can notice |
|---|
| 9 | .. Short and abstract as possible, as long as necessary. |
|---|
| 10 | .. Each use case must have at least one actor involved |
|---|
| 11 | .. Each use case must have a trigger and a result |
|---|
| 12 | |
|---|
| 13 | |
|---|
| 14 | Short Description |
|---|
| 15 | ----------------------------------------------------------------------- |
|---|
| 16 | |
|---|
| 17 | A service is modified by staff. |
|---|
| 18 | |
|---|
| 19 | Actor(s) |
|---|
| 20 | ----------------------------------------------------------------------- |
|---|
| 21 | |
|---|
| 22 | Staff |
|---|
| 23 | |
|---|
| 24 | |
|---|
| 25 | Trigger(s) |
|---|
| 26 | ----------------------------------------------------------------------- |
|---|
| 27 | |
|---|
| 28 | - Imports (modifying existing data) |
|---|
| 29 | - Web form(s) submitted by authorized user. |
|---|
| 30 | |
|---|
| 31 | |
|---|
| 32 | Result(s) |
|---|
| 33 | ----------------------------------------------------------------------- |
|---|
| 34 | |
|---|
| 35 | - Data (terms, title, description) of the given service is modified. |
|---|
| 36 | |
|---|
| 37 | |
|---|
| 38 | Incoming Data |
|---|
| 39 | ----------------------------------------------------------------------- |
|---|
| 40 | |
|---|
| 41 | - Service ID, names and values of parameters to change. |
|---|
| 42 | |
|---|
| 43 | Outgoing Data |
|---|
| 44 | ----------------------------------------------------------------------- |
|---|
| 45 | |
|---|
| 46 | - Message about service modification. |
|---|
| 47 | - (optional) regarding customers are informed by email or |
|---|
| 48 | SMS. Regarding customers are those having a contract created by |
|---|
| 49 | the modified service. |
|---|
| 50 | - Log message |
|---|
| 51 | |
|---|
| 52 | |
|---|
| 53 | Precondition(s) |
|---|
| 54 | ----------------------------------------------------------------------- |
|---|
| 55 | |
|---|
| 56 | - Service ID must exist. |
|---|
| 57 | - Submitting user must be authorized to perform the operation. |
|---|
| 58 | |
|---|
| 59 | |
|---|
| 60 | Postcondition(s) |
|---|
| 61 | ----------------------------------------------------------------------- |
|---|
| 62 | |
|---|
| 63 | - The new service data were checked for validity. Validation here is |
|---|
| 64 | stricter than when adding a service. For instance it is not allowed |
|---|
| 65 | to change terms for the past if there are already existing |
|---|
| 66 | contracts created by this service. |
|---|
| 67 | |
|---|
| 68 | |
|---|
| 69 | Invariant(s) |
|---|
| 70 | ----------------------------------------------------------------------- |
|---|
| 71 | |
|---|
| 72 | |
|---|
| 73 | Essential Steps |
|---|
| 74 | ----------------------------------------------------------------------- |
|---|
| 75 | |
|---|
| 76 | - System receives service ID and any optional parameters |
|---|
| 77 | specifying the data to change in the service. |
|---|
| 78 | - Data is validated. |
|---|
| 79 | - If passed-in parameters are invalid, user is offered a possibility |
|---|
| 80 | to fix the invalid data. |
|---|
| 81 | - System updates the given service. |
|---|
| 82 | |
|---|
| 83 | |
|---|
| 84 | Open Issues |
|---|
| 85 | ----------------------------------------------------------------------- |
|---|
| 86 | |
|---|
| 87 | |
|---|
| 88 | |
|---|
| 89 | Remarks |
|---|
| 90 | ----------------------------------------------------------------------- |
|---|
| 91 | |
|---|
| 92 | |
|---|
| 93 | .. raw:: latex |
|---|
| 94 | |
|---|
| 95 | \pagebreak[4] |
|---|
