| 1 | Use Case: Reading a Meter |
|---|
| 2 | *********************************************************************** |
|---|
| 3 | |
|---|
| 4 | .. Description of a use case |
|---|
| 5 | .. The description must be formulated as seen from system (not: actors) |
|---|
| 6 | .. Describes those changes an (outside) actor can notice |
|---|
| 7 | .. Short and abstract as possible, as long as necessary. |
|---|
| 8 | .. Each use case must have at least one actor involved |
|---|
| 9 | .. Each use case must have a trigger and a result |
|---|
| 10 | |
|---|
| 11 | |
|---|
| 12 | Short Description |
|---|
| 13 | ----------------------------------------------------------------------- |
|---|
| 14 | |
|---|
| 15 | A meter is read and the read values are stored in system. |
|---|
| 16 | |
|---|
| 17 | |
|---|
| 18 | Actor(s) |
|---|
| 19 | ----------------------------------------------------------------------- |
|---|
| 20 | |
|---|
| 21 | Meter Reader |
|---|
| 22 | |
|---|
| 23 | |
|---|
| 24 | Trigger(s) |
|---|
| 25 | ----------------------------------------------------------------------- |
|---|
| 26 | |
|---|
| 27 | A read-meter form is requested from portal. |
|---|
| 28 | |
|---|
| 29 | |
|---|
| 30 | Result(s) |
|---|
| 31 | ----------------------------------------------------------------------- |
|---|
| 32 | |
|---|
| 33 | The new meter values are stored in database. |
|---|
| 34 | |
|---|
| 35 | |
|---|
| 36 | Incoming Data |
|---|
| 37 | ----------------------------------------------------------------------- |
|---|
| 38 | |
|---|
| 39 | Meter ID, meter value, date and time of reading |
|---|
| 40 | |
|---|
| 41 | |
|---|
| 42 | Outgoing Data |
|---|
| 43 | ----------------------------------------------------------------------- |
|---|
| 44 | |
|---|
| 45 | - Message about successful reading |
|---|
| 46 | - Log message |
|---|
| 47 | |
|---|
| 48 | |
|---|
| 49 | Precondition(s) |
|---|
| 50 | ----------------------------------------------------------------------- |
|---|
| 51 | |
|---|
| 52 | |
|---|
| 53 | |
|---|
| 54 | Postcondition(s) |
|---|
| 55 | ----------------------------------------------------------------------- |
|---|
| 56 | |
|---|
| 57 | |
|---|
| 58 | |
|---|
| 59 | Invariant(s) |
|---|
| 60 | ----------------------------------------------------------------------- |
|---|
| 61 | |
|---|
| 62 | |
|---|
| 63 | |
|---|
| 64 | Essential Steps |
|---|
| 65 | ----------------------------------------------------------------------- |
|---|
| 66 | |
|---|
| 67 | * Authenticate meter reader |
|---|
| 68 | * Get meter id, meter value, datetime |
|---|
| 69 | * Check input values: |
|---|
| 70 | |
|---|
| 71 | * Does the meter id exist? |
|---|
| 72 | * If not, ask and add a new one. |
|---|
| 73 | * value >= old value? |
|---|
| 74 | |
|---|
| 75 | * Add new reading in database |
|---|
| 76 | * Output success message |
|---|
| 77 | |
|---|
| 78 | |
|---|
| 79 | Open Issues |
|---|
| 80 | ----------------------------------------------------------------------- |
|---|
| 81 | |
|---|
| 82 | Meter data input can also be performed by some automatic system: |
|---|
| 83 | |
|---|
| 84 | - automatic meters send their data automatically (how does these |
|---|
| 85 | data look like and where is it stored?) |
|---|
| 86 | |
|---|
| 87 | - a smartphone/tablet app might deliver the data by photograph/OCR |
|---|
| 88 | |
|---|
| 89 | These input devices need an API to deliver data or they require some |
|---|
| 90 | API to be able to input data into the system. |
|---|
| 91 | |
|---|
| 92 | |
|---|
| 93 | Remarks |
|---|
| 94 | ----------------------------------------------------------------------- |
|---|
| 95 | |
|---|
| 96 | |
|---|
| 97 | .. raw:: latex |
|---|
| 98 | |
|---|
| 99 | \pagebreak[2] |
|---|
