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/Add Alert
Use-Case Specification: Add Alert
1. BRIEF DESCRIPTION
The user adds an alert/dialog component to the flow.
2. FLOW OF EVENTS
2.1 Basic Flow of Events
- B1. The user decides to add a new alert to the flow.
- B2. The user selects an alert component from the component list.
- B3. The user adds an alert to the flow designer
- a) The system asks for any mandatory properties applicable to the alert (e.g. the name).
- B4. The user inputs the mandatory properties.
- a) The system adds the new alert to the flow designer.
- b) The system creates the code for the alert.
- c) The system opens the properties view for the alert/dialog
2.2 Alternative Flows
- Alternative flow 1: The user inputs an invalid mandatory property for the alert
- A1. If the user inputs an invalid mandatory property for the alert, he will be warned of the error and asked to provide the property again. The user can also cancel the addition of the alert.
3. SUBFLOWS
4. KEY SCENARIOS
5. PRECONDITIONS
5.1 Precondition 1: The flow designer is open and contains an open flow
Components can only be added to the flow in flow designer.
6. POSTCONDITIONS
6.1 Postcondition 1: A new alert component is added to the flow and its code is created
6.2 Postcondition 2: The new alert is selected and the property list for it is updated
When a new alert is selected, its property list is updated to the mandatory values the user gave when creating the alert.
7. EXTENSION POINTS
8. SPECIAL REQUIREMENTS
9. ADDITIONAL INFORMATION
Comments:
Back to main DSDP-MTJ Use Cases