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 Application Start
Use-Case Specification: Delete Application Start
1. BRIEF DESCRIPTION
The user can remove the application start component from the flow.
2. FLOW OF EVENTS
2.1 Basic Flow of Events
- B1. The user decides to remove an application start component from the flow.
- B2. The user selects the application start component from within the flow.
- B3. The user removes the selected application start component.
- a) The system removes the code for the application start component.
- b) The system removes the screen changes attached to the application start component.
- c) The system removes the application start component from the flow.
- d) The system updates the other views accordingly.
2.2 Alternative Flows
- Alternative Flow 1: The user removes the application start component from the code.
- A1. If the user removes the application start component from the code, the system notices the removal when the user saves the code. The system updates the flow and other views according to the change.
3. SUBFLOWS
4. KEY SCENARIOS
5. PRECONDITIONS
5.1 Precondition 1: The flow designer is open and has an application start
6. POSTCONDITIONS
6.1 Postcondition 1: The application start component and attached code is removed
The user can no longer run the application because it doesn’t have application starting point.
6.2 Postcondition 2: The undo feature is available
The undo feature is available for undoing the removal of the application start component.
7. EXTENSION POINTS
8. SPECIAL REQUIREMENTS
9. ADDITIONAL INFORMATION
Comments:
Back to main DSDP-MTJ Use Cases