DSDP/MTJ/Remove Component

Use-Case Specification: Remove Component

1. BRIEF DESCRIPTION

The user removes a UI component from the container.

2. FLOW OF EVENTS 2.1 Basic Flow of Events

B1. The user selects the component he wants to remove. B2. The user removes the component. a) The system removes the component from the UI design. b) The system removes the component’s commands and references to other components. c) The system removes any associated code. The removed code contains the code for the component’s initialisation and the code for the component’s properties. Import statements are not removed. d) The UI designer views are redrawn to match the changes. This includes the actual UI designer area, property views, etc.

2.2 Alternative flows

Alternative flow 1: The user removes the component by editing the code

A1. The user edits the code to remove the component. The UI designer notices that code has been removed and updates the UI designer views accordingly.

Alternative flow 2: Multi selection

A2. The user can select multiple UI components and delete the selected components. After removing the selected components, the UI designer views are redrawn to match the changes. This includes the actual UI designer area, property views, etc.

Alternative flow 1: The code file cannot be deleted

A3. If the code file cannot be removed, the user will be informed of this and component deletion continues. This might happen, e.g. when some other program has locked the code file.

3. SUBFLOWS

4. KEY SCENARIOS

5. PRECONDITIONS

5.1 Precondition 1: The UI designer is open for a container and the container has one or more components

The UI designer is opened for a container, showing the components of that container. The container must have at least one component that can be removed.

6. POSTCONDITIONS

6.1 Postcondition 1: The component is removed from the container and all associated code is removed

The component is no longer visible in the UI designer or in the container.

6.2 Postcondition 2: The undo feature is available

The undo feature is available to undo the deletion of the component.

7. EXTENSION POINTS

8. SPECIAL REQUIREMENTS

9. ADDITIONAL INFORMATION

---

Comments:

Back to main DSDP-MTJ Use Cases