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.
DSDP/MTJ/Uninstall Screen
Use-Case Specification: Uninstall custom screen
1. BRIEF DESCRIPTION
This use-case describes how a custom screen can be uninstalled from the Flow designer.
2. FLOW OF EVENTS
2.1 Basic Flow of Events
- B1. The user decides to uninstall a container from the Flow designer.
- B2. The user deletes the plug-in file from Eclipse.
- B3. The user starts Eclipse.
- a) The custom screen component is removed from component palette.
- b) The custom component group is removed if there aren’t any other components.
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 removed screen is in use in a flow diagram
- A3. The user starts Eclipse after plug-in removal.
- A4. The user opens a flow design which uses the removed screen.
- a) The system will inform that the flow diagram contains components that are no longer available.
- b) The system asks 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: The user has installed a screen that can be uninstalled
5.2 Precondition 2: Eclipse is not running
6. POSTCONDITIONS
6.1 Postcondition 1: The selected screen is uninstalled
The screen is no longer available in the screen list.
7. EXTENSION POINTS
8. SPECIAL REQUIREMENTS
9. ADDITIONAL INFORMATION
Comments:
Back to main DSDP-MTJ Use Cases