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/Delete Screen
< DSDP | MTJ(Redirected from Delete Screen)
Use-Case Specification: Delete screen from flow
1. BRIEF DESCRIPTION
This use-case describes what happens when the user deletes a screen from the active flow.
2. FLOW OF EVENTS
2.1 Basic Flow of Events
- B1. The user decides to delete a screen.
- B2. The user selects the delete screen function.
- a) The system does not delete the screen’s code, but it removes the code associated with the deleted screen.
- i) The possible screenchange code from the deleted screen.
- ii) The possible screenchange events code to the removed screen from other components.
- b) The system removes the screen from the active flow and updates the flow’s code.
- c) The system redraws the active flow.
- a) The system does not delete the screen’s code, but it removes the code associated with the deleted screen.
2.2 Alternative Flows
- Alternative flow 1: The user deletes multiple screens
- A1. The user selects several screens from an active flow.
- A2. The user selects the delete screen function.
- a) The system removes the code associated with the deleted screens.
- b) The system removes the screens from the active flow and updates the flow’s code.
- c) The system redraws the active flow.
- Alternative flow 2: The screen is deleted using something other than the Flow designer’s delete screen function
- A3. The user deletes a screen using another method than those provided by the Flow designer.
- A4. The user activates flow that contains deleted component.
- a) The system removes the code associated with the deleted screen.
- b) The system removes the screen from the active flow and updates the flow’s code.
- c) The system redraws the flow.
- Exception 1: The file is locked by another application or editor
- A5. The user tries to delete a screen but the file is locked by another application.
- a) The system shows an error message explaining that the screen cannot be removed because it is locked by another application. Delete is aborted.
- A5. The user tries to delete a screen but the file is locked by another application.
3. SUBFLOWS
4. KEY SCENARIOS
5. PRECONDITIONS
5.1 Precondition 1: The user has the Flow designer open and the flow contains at least one screen
6. POSTCONDITIONS
6.1 Postcondition 1: The screen is removed from the active Flow Diagram The screen is removed from the active Flow Diagram and also the code linked to the screen. The undo feature is available.
7. EXTENSION POINTS
8. SPECIAL REQUIREMENTS
9. ADDITIONAL INFORMATION
Comments:
Back to main DSDP-MTJ Use Cases