DSDP/MTJ/Delete Screen Change

Use-Case Specification: Delete screen change

1. BRIEF DESCRIPTION

This use-case describes how a screen change object is deleted from an active flow diagram.

2. FLOW OF EVENTS

2.1 Basic Flow of Events

B1. The user decides to delete a screen change object.

B2. The user selects the screen change object to delete.

B3. The user selects the delete screen change function.

a) The system removes the code that triggers the screen change in the start-up class (.e.g. the code generated inside the commandAction(Command c,Displayable d) )

b) The system updates the flow diagram’s code.

c) The system redraws the flow diagram.

2.2 Alternative Flows

Exception 1: The file is locked by another application

A1. The user tries to delete a screen change object but the file is locked by another application.

a) The system shows an error message explaining that the screen change object 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 with a flow diagram present which contains at least one screen change object

6. POSTCONDITIONS

6.1 Postcondition 1: The screen change object is removed from the flow

The screen change object is removed from the active flow. The generated code associated with the screen change object is also removed. The undo feature is available.

7. EXTENSION POINTS

8. SPECIAL REQUIREMENTS

9. ADDITIONAL INFORMATION

---

Comments:

Back to main DSDP-MTJ Use Cases