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.
Difference between revisions of "DSDP/MTJ/Add Screen Change"
m (Add Screen Change moved to DSDP/MTJ/Add Screen Change) |
|
(No difference)
|
Latest revision as of 13:45, 27 May 2008
Use-Case Specification: Add screen change
1. BRIEF DESCRIPTION
This use-case describes the flow when a screen change is added between two screens in the Flow designer.
2. FLOW OF EVENTS
2.1 Basic Flow of Events
- B1. The user decides to add a screen change between two components.
- B2. The user selects the add screen change feature.
- a) The system displays all possible starting points in the active flow diagram.
- B3. The user selects the starting point.
- B4. The user selects the target component.
- B5. The user accepts the change and saves the file.
- a) The system generates the code.
- b) The system updates the Flow diagram’s code.
- c) The system redraws the Flow diagram.
2.2 Alternative Flows
- Alternative flow 1: The user tries to set an invalid value for the properties
- A1. The user tries to set invalid values for the mandatory properties.
- A2. The user accepts the changes.
- a) The system shows an error message and does not remove the mandatory properties view.
- Alternative flow 2: The user wants to add a screen change to a new starting point
- A3. The user decides to add a screen change between two components.
- A4. The user selects the add screen change feature.
- a) The system displays all possible starting points.
- A5. The user selects the add new command or the add new menu item feature.
- a) The system asks for the mandatory properties of the command/menu item.
- A6. The user sets the mandatory information and saves the changes.
- a) The system generates the code for the command/menu item.
- b) The system updates the flow diagram’s code.
- c) The system redraws the flow.
- d) The system displays the newly created command/menu item as a new starting point.
- A7. The user selects the newly created command/menu item as the starting point.
- A8. The user selects the target component.
- A9. The user accepts the change and saves the file.
- a) The system generates the code.
- b) The system updates the flow diagram’s code.
- c) The system redraws the flow.
3. SUBFLOWS
4. KEY SCENARIOS
5. PRECONDITIONS
5.1 Precondition 1: A flow diagram with two screens must be open
6. POSTCONDITIONS
6.1 Postcondition 1: A screen change is made between the user’s selected screens
7. EXTENSION POINTS
8. SPECIAL REQUIREMENTS
9. ADDITIONAL INFORMATION
Comments:
Back to main DSDP-MTJ Use Cases