References
CPS-1434 - Getting issue details... STATUS
CPS-1713 - Getting issue details... STATUS
Requirements
Functional
# | Interface | Requirement | Additional Information | Signoff |
|---|---|---|---|---|
Error Handling
# | Error Scenario | Expected behavior |
|---|---|---|
| 1 | What happens if we receive a Cm Data AVC event for replace , but there is no corresponding record in CPS-Cache ? |
Characteristics
# | Parameter | Expectation | Notes |
|---|---|---|---|
| 1 |
Out-of-scope
- Any operation other than "replace" . eg : create , merge , delete etc.
Assumptions
# | Assumption | Notes |
|---|---|---|
| 1 |
Issues & Decisions
# | Issue | Notes | Decision |
|---|---|---|---|
| 1 | Do we persist the incoming CM Data AVC Event in our database ? | ||
| 2 | Which model to be used for the data in the cache ? | ||
| 3 | Who will upload the model ? will it be done using our model-loader way ? | ||
| 4 | How will the data be uploaded which will later be updated ? | ||
| 5 | What happens once the data is updated ? Is cps-core responsible to send out the updated events ? | ||
| 6 | Frequency of VES message , which determines the frequency of Data AVC events. |