DSDP/MTJ/Delete Operation Triggering

Use-Case Specification: Delete pre- or post- commands

1. BRIEF DESCRIPTION

This use-case describes how a pre- or post- command can be removed from a command or a menu item to which it is associated.

2. FLOW OF EVENTS

2.1 Basic Flow of Events

B1. The user decides to delete the pre- or post- command.

B2. The user selects the command/menu that contains the pre- or post- command.

B3. The user selects the delete pre- or post- command and deletes it.

a) The system removes the added method calls from 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 removes the pre- or post- command from the code directly

A1. The user removes the pre- or post- command from the code directly.

A2. The user saves his changes.

A3. The user opens the Flow Designer.

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

b) The system redraws the flow diagram.

Exception 1: The file is locked by another application

A4. The user tries to delete the pre- or post- command but the file is locked by another application.

a) The system will show an error message explaining that the operation cannot be performed because it is locked by another application. The pre- or post- command is not removed.

3. SUBFLOWS

4. KEY SCENARIOS

5. PRECONDITIONS

5.1 Precondition 1: The Flow designer is open with a flow diagram present

The Flow designer must be open with a flow diagram present.

5.2 Precondition 2: The active flow diagram must contain a pre- or post- command

The active flow diagram must contain a command or menu item with a pre- or post- command attached to it.

6. POSTCONDITIONS

6.1 Postcondition 1: The pre- or post- command is removed The menu item or command no longer has a pre- or post- command associated with it. The code compiles and undo is available.

7. EXTENSION POINTS

8. SPECIAL REQUIREMENTS

9. ADDITIONAL INFORMATION

---

Comments:

Back to main DSDP-MTJ Use Cases