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/Install Screen
Use-Case Specification: Install custom screen
1. BRIEF DESCRIPTION
This use-case describes how the user can install a custom screen to the Flow designer.
2. FLOW OF EVENTS
2.1 Basic Flow of Events
- B1. The user decides to install a custom screen.
- B2. The user adds the plug-in file to the plug-in’s folder.
- B3. The user starts Eclipse.
- a) The system updates the installed component to the list of available flow designer components. Installed component can also add new component group.
2.2 Alternative Flows
- Alternative flow 1: The screen location is corrupt (e.g. jar file is corrupt)
- A1. The system will show the user an error message that explains what has happened. The installation is aborted.
- Alternative flow 2: The location contains no screen to install
- A2. The system ignores the plug-in.
- Alternative flow 3: The screen already exists
- A3. The system checks if this is an update to an existing screen. If so, the newer version will be used. Otherwise, the plug-in will be ignored.
- Alternative flow 4: The Flow designer is open with the wrong UI toolkit
- A4. The installed custom screen is not displayed in the list of available Flow designer components.
3. SUBFLOWS
4. KEY SCENARIOS
5. PRECONDITIONS
5.1 Precondition 1: The user has a custom screen he wants to add
The user must have created a custom screen as an Eclipse plug-in that can be installed to the Flow designer.
5.2 Precondition 2: The Flow designer is open with the same UI toolkit
6. POSTCONDITIONS
6.1 Postcondition 1: The installed screen is available for use
The added screen is visible in the component list and can be added to the flow.
7. EXTENSION POINTS
8. SPECIAL REQUIREMENTS
9. ADDITIONAL INFORMATION
Comments:
Back to main DSDP-MTJ Use Cases