Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Bugzilla 165566"
Line 23: | Line 23: | ||
<tr align="center" bgcolor="#C0C0C0"><th>Process</th><th bgcolor="#C0C0C0">Sizing</th></tr> | <tr align="center" bgcolor="#C0C0C0"><th>Process</th><th bgcolor="#C0C0C0">Sizing</th></tr> | ||
<tr align="center"><td>Design</td><td>1</td></tr> | <tr align="center"><td>Design</td><td>1</td></tr> | ||
− | <tr align="center"><td>Code</td><td> | + | <tr align="center"><td>Code</td><td>2</td></tr> |
<tr align="center"><td>Test</td><td>1</td></tr> | <tr align="center"><td>Test</td><td>1</td></tr> | ||
− | <tr align="center"><td>Documentation</td><td></td></tr> | + | <tr align="center"><td>Documentation</td><td>1</td></tr> |
<tr align="center"><th><span style="font-size: 10pt; color: red; font-family: Helv;">Total</span></th> | <tr align="center"><th><span style="font-size: 10pt; color: red; font-family: Helv;">Total</span></th> | ||
− | <th><span style="font-size: 10pt; color: red; font-family: Helv;"> | + | <th><span style="font-size: 10pt; color: red; font-family: Helv;">5</span></th></tr> |
</table> | </table> | ||
</span></p> | </span></p> |
Revision as of 10:21, 12 December 2006
Contents
TPTP feature: 165566
Author: | Balan Subramanian |
email: | [1] |
Last updated: | December 12, 2006 |
Rough workload estimate for design/code/test in person weeks:
Process Sizing Design 1 Code 2 Test 1 Documentation 1 Total
5
Rough workload estimate for build and infrastructure in person days: 3.0
Requirement summary
TPTP today has a notification broker for which a WSDM provider is available in the build to manage download. This enables any plugin in the workbench to register with the broker and receive WS-Notifications from WSDM resources. The MAX is today registered as a listener but processes only PropertyChange events. This feature will enable the MAX to use notifications to: 1. Update relationship information by listening on relationship resources 2. Update service group members by subscribing to membership change events on service groups 3. Show different operational state of resources 4. Show visually that a resource's properties have changed and which properties have changed
User interactions
User interface
TBD