source: main/eko-disco-specs/trunk/use-cases/service-remove.rst @ 10750

Last change on this file since 10750 was 10749, checked in by uli, 11 years ago

Some use-cases, etc.

File size: 2.2 KB
Line 
1.. _label-uc-service-remove:
2
3Use-Case: Remove 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
14Short Description
15-----------------------------------------------------------------------
16
17A service is removed from system.
18
19Actor(s)
20-----------------------------------------------------------------------
21
22Staff
23
24
25Trigger(s)
26-----------------------------------------------------------------------
27
28- Imports (removing existing data)
29- Web form(s) submitted by authorized user.
30
31
32Result(s)
33-----------------------------------------------------------------------
34
35- The given service and all connected data (contracts, etc.) were
36  removed from the system.
37- All removed data is archived.
38
39
40Incoming Data
41-----------------------------------------------------------------------
42
43- Service ID
44
45Outgoing Data
46-----------------------------------------------------------------------
47
48- Message about service removal.
49- Log message
50- Archive entry.
51
52
53Precondition(s)
54-----------------------------------------------------------------------
55
56- Service ID must exist.
57- Submitting user must be authorized to perform the operation.
58
59
60Postcondition(s)
61-----------------------------------------------------------------------
62
63
64Invariant(s)
65-----------------------------------------------------------------------
66
67A service cannot be removed from the system while still contracts
68connected to it exist in the system.
69
70
71Essential Steps
72-----------------------------------------------------------------------
73
74- System checks service ID validity.
75- System checks whether any contracts created by the requested service
76  are still in use in the system and cancels operation if so.
77- Removed data is archived.
78- System removes the given service.
79
80
81Open Issues
82-----------------------------------------------------------------------
83
84
85
86Remarks
87-----------------------------------------------------------------------
88
89
90
91.. raw:: latex
92
93      \pagebreak[4]
Note: See TracBrowser for help on using the repository browser.