Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
DSDP/MTJ/Modify Screen Change
Use-Case Specification: Modify screen change
1. BRIEF DESCRIPTION
This use-case describes the flow when the screen change object is modified in the Flow designer.
2. FLOW OF EVENTS
2.1 Basic Flow of Events
- B1. The user decides to modify the screen change.
- B2. The user selects the screen change object to modify.
- B3. The user selects the modify screen change feature.
- a) The system reveals the properties view of the screen change object.
- B4. The user modifies the properties.
- i) The user can change the starting point.
- ii) The user can change the target component.
- B5. The user accepts the changes made.
- a) The system generates the required code.
- b) The system modifies the flow diagram’s code.
- c) The system redraws the flow diagram.
2.2 Alternative Flows
3. SUBFLOWS
4. KEY SCENARIOS
5. PRECONDITIONS
5.1 Precondition 1: The Flow designer is open with an active flow diagram which contains a screen change object
The Flow designer must be open with a flow diagram which must contain at least one screen change object
6. POSTCONDITIONS
6.1 Postcondition 1: The screen change object is modified
The screen change object is modified according to the changes made by the user.
7. EXTENSION POINTS
8. SPECIAL REQUIREMENTS
9. ADDITIONAL INFORMATION
Comments:
Back to main DSDP-MTJ Use Cases