Use Cases for Update Center UI

Primary user tasks tasks that we expect users will do most often should be very simple to do.

Use Case 1: Grouping

Related activities should be grouped clearly for easy navigation. For example, Available Software, Installed Software, Updates, Preferences.

Use Case 2: Automatic Update Check Interval

User should be able to set how often update center client checks for new updates. For example, daily, weekly, never/manually.

Use Case 3: Connection Settings

User should be able to provide proxy server information to connect to the update center server.

Use Case 4: Update Center URLs

User should be able to change Update Center URL, add new Update Center, remove Update Center and change the query order. Update Center list will initially contain default Update Center URL.

Use Case 5: Save Settings

User should be able to save the preferences.

Use Case 6: New Software Notification

Notify user when a new software is available. The system tray icon should show a tool tip with brief message.

Use Case 7: New Update Notification

Notify user when new updates are available. The system tray icon should show a tool tip with brief message.

Use Case 8: Hide System Tray Icon

Only show system tray icon when there are new updates. This is nice to have.

Use Case 9: Collect Anonymous Usage Stats

Ask the user, if it okay to collect anonymous usage statistics.

Use Case 10: Check for Updates Manually

User should be able to click on a button to check for updates. If there are no updates available, we should show a message. For example, "No Updates are Available Currently". If there is a communication issue, we should let user know. For example, "Update center server could not be contacted" can be shown along with "retry" button. Help button can show that a proxy server may be needed in some cases to contact the update center.

Use Case 11: Installed Software

Use should be able to find out the existing installed components. The installed date, version, size etc. should be shown. If there are lot of components/modules - group them in categories.

Use Case 12: Available Software

User should be able to find out the current available software in the update center that can be installed. We should group the available software in categories so that it is easy to find components. In addition to functional categories (which is the NetBeans way), we should also provide grouping of components into “products” (such as Java EE SDK, Web 2.0 SDK, etc.).

Use Case 13: Details of New Components or Updates

Detailed information about an update or new component should be shown. Example information could be - module name, date, version, description, size, dependencies, etc. We can also show a URL for more details. If a restart is required for an update or new component installation, it should be clearly marked and communicated to the user.

Use Case 14: Express Install

User should be able to choose to install all the available updates or software components. If there is any failure, the details must be shown clearly.

Use Case 15: Selective Install

User can pick only some of the available updates or software components.

Use Case 16: Dependency Resolution

When a new component is selected, we should resolve the dependencies automatically. If necessary components are not selected, we should automatically select the components.

Use Case 17: Uninstall a Software

User should be able to uninstall a previously installed component.

Use Case 18: Update the Update Center Client

User should be able to see new Update Center version in the "Updates" section and should be able to install the update.

Use Case 19: Cancel the download

User should be able to cancel the downlading of the new software or update.

Use Case 20: CLI notification

When Update Center is packaged with Application Server- at the end of start-domain CLI command, check for Updates is done. If there are any updates available - user is prompted if user wants to bring up update center GUI at that point. (This is only done interactive mode).

Use Case 21: GUI notification

When Update Center is packaged with Application Server- when user logs into GUI admin console check for Updates is done. If there are any updates available - is message is displayed to the user that updates are available and user should run Update Center GUI.

Use Case 22: New modules should be graphically distinguishable

User should be able to figure out which modules he/she already looked at and which were not yet looked at. Updates that are available, since the last time GUI was started should be evident.

Use Case 23: Provide Generic Tokenization Support

It should be possible to gather input from user during installation. For example when installing samples into Application Server user name and password etc.

Use Case 24: Show license before installation

When Update Center modules/updates are being installed - license must be shown to the user. Unless user accepts the license - installation should fail.

Use Case 25: Ask permission before deploy

When deploy applications users must be asked for permission.