Meetings2012-03-01 » History » Version 3
J. Moringen, 03/01/2012 04:30 PM
extended requirements
| 1 | 1 | J. Moringen | h1. Meetings 2012-03-01 |
|---|---|---|---|
| 2 | 1 | J. Moringen | |
| 3 | 1 | J. Moringen | h2. Scope of the Configuration Service |
| 4 | 1 | J. Moringen | |
| 5 | 2 | J. Moringen | * Supply parameter values for components running in a system |
| 6 | 2 | J. Moringen | * Components expose parameters |
| 7 | 3 | J. Moringen | ** Parameters consist of |
| 8 | 3 | J. Moringen | *** Name |
| 9 | 3 | J. Moringen | *** Type |
| 10 | 3 | J. Moringen | **** Complex values have to be possible: e.g. arbitratry Protocol buffer types, array of joint velocities) |
| 11 | 3 | J. Moringen | *** Current value |
| 12 | 3 | J. Moringen | *** Default value (supplied by component?) |
| 13 | 3 | J. Moringen | ** Provided functionality |
| 14 | 3 | J. Moringen | *** Parameter values and default values can be queried |
| 15 | 3 | J. Moringen | *** Parameter values can be reset to default values |
| 16 | 3 | J. Moringen | *** Parameters can be updated from outside |
| 17 | 2 | J. Moringen | |
| 18 | 1 | J. Moringen | h2. Requirements |
| 19 | 1 | J. Moringen | |
| 20 | 1 | J. Moringen | * Has to be suitable for component layer (e.g. CCA) |
| 21 | 1 | J. Moringen | * Component developers should not have to handle parameter updates explicitly |
| 22 | 2 | J. Moringen | ** However, parameter updates should be interceptable via callbacks |
| 23 | 3 | J. Moringen | * Partial updates of complex/structured values |
| 24 | 3 | J. Moringen | (e.g. only transfer, notify sub-elements of composite values in case of partial change) |