Skip to main content

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.

Jump to: navigation, search

DSDP/MTJ/Uninstall Alert

< DSDP‎ | MTJ

Use-Case Specification: Uninstall Alert/Dialog


1. BRIEF DESCRIPTION

The user can uninstall the alert/dialog component from the system.


2. FLOW OF EVENTS

2.1 Basic Flow of Events

B1. The user decides to uninstall an alert component from the system.
B2. The user removes the alert component files from the system’s folder.

2.2 Alternative Flows

Alternative flow 1: The user doesn’t delete all of the plug-in files.
A1. The user deletes some of the plug-in files.
A2. The user starts Eclipse.
a) The system behaves as if all plug-in files have been deleted.
Alternative flow 2: The uninstalled alert/dialog is in use within a flow diagram
A3. The user starts Eclipse after the plug-in has been removed.
A4. The user opens a flow design which uses the removed alert/dialog.
a) The system will inform that the flow diagram contains components that are no longer available.
b) The system will ask if the components can be removed from the flow diagram.
A5. If user confirms that the components can be removed, the flow diagram is updated according to the basic flow of events in the delete use case. If the components cannot be removed, the flow diagram cannot be opened and the user will be informed about this.


3. SUBFLOWS


4. KEY SCENARIOS


5. PRECONDITIONS

5.1 Precondition 1: Eclipse is not running

Components cannot be removed while the system is running.

5.2 Precondition 2: The user has installed an alert that can be uninstalled


6. POSTCONDITIONS

6.1 Postcondition 1: The alert/dialog component is not available in the system


7. EXTENSION POINTS


8. SPECIAL REQUIREMENTS


9. ADDITIONAL INFORMATION



Comments:


Back to main DSDP-MTJ Use Cases

Back to the top