Skip to main content
Jump to: navigation, search

DSDP/MTJ/Delete Alert

< DSDP‎ | MTJ
Revision as of 13:47, 27 May 2008 by Wgp010.motorola.com (Talk | contribs) (Delete Alert moved to DSDP/MTJ/Delete Alert)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Use-Case Specification: Remove Alert/Dialog


1. BRIEF DESCRIPTION

The user removes an alert/dialog from the flow.


2. FLOW OF EVENTS

2.1 Basic Flow of Events

B1. The user decides to remove an alert/dialog from the flow.
B2. The user selects an alert/dialog to remove and then removes it.
a) The system removes all of the code associated with the alert/dialog.
i) The possible screen change code from the deleted alert/dialog.
ii) The possible screen change event’s code to the removed alert/dialog from the other components
b) The system removes the alert/dialog connections in flow designer.
c) The system removes the alert/dialog from the flow designer’s design.

2.2 Alternative Flows

Alternative flow 1: The user deletes multiple alerts/dialogs
A1. The user selects several alerts/dialogs from an active flow.
A2. The user selects the delete alert/dialog feature.
a) The system removes all of the code associated with the deleted alerts/dialogs.
b) The system removes the alerts/dialogs from the active flow and updates the flow’s code.
c) The system redraws the active flow.
Alternative flow 2: The alert/dialog is deleted using a method other than the Flow designer’s delete feature
A3. The user deletes the alert/dialog using another method than that which is provided by the Flow designer.
A4. The user activates flow flow diagram that contains deleted component
a) The system removes all of the code associated with the deleted alert/dialog.
b) The system removes the screen from the active flow and updates the flow’s code.
c) The system redraws the flow.
Alternative flow 3: The file is locked by another application or editor
A5. The user tries to delete an alert/dialog but the file is locked by another application.
a) The system will show an error message explaining that the alert/dialog cannot be removed because it is locked by another application. Delete is aborted.


3. SUBFLOWS


4. KEY SCENARIOS


5. PRECONDITIONS

5.1 Precondition 1: The flow designer is open and contains at least one alert/dialog that can be removed

Alerts can only be removed from the flow when the Flow designer is open.


6. POSTCONDITIONS

6.1 Postcondition 1: The alert/dialog is removed from the flow and the flow is updated

6.2 Postcondition 2: The screen change related code for the alert is removed


7. EXTENSION POINTS


8. SPECIAL REQUIREMENTS


9. ADDITIONAL INFORMATION



Comments:


Back to main DSDP-MTJ Use Cases

Back to the top