DSDP/MTJ/Modify Container

Use-Case Specification: Modify Container

1. BRIEF DESCRIPTION

The user modifies the container in the UI designer to change the outfit of the UI designer.

2. FLOW OF EVENTS

2.1 Basic Flow of Events

B1. The user decides to modify the container.

B2. The user selects the container that he wants to modify.

B3. The user opens the property list for the container.

B4. The user selects the property to modify.

a) The property editor is enabled, allowing the user to alter the property value.

B5. The user modifies the property value and accepts the change.

a) The system modifies the code according to the changes.

b) The system validates the new property value.

c) The system updates the property for the container.

d) The system redraws the container and components included within it when needed.

2.2 Alternative flows

Alternative flow 1: In-place editing

A1. The user can activate in-place editing for certain properties (e.g. text) when a single container is selected. When in-place editing is activated, the editor for a property opens in the UI designer and the user can edit the property directly in the UI editor.

Alternative flow 2: Multi selection

A2. The user can select multiple containers and modify their common properties. When multiple containers are selected, only the properties that are common for those containers are selectable and editable. After editing the property, the new property value is updated for all of the selected container elements.

Alternative flow 3: The user gives an invalid new value for the property

A3. If the user gives an invalid new value for the property being altered, the system will warn the user about the invalid value and reverts the property back to its original value.

Alternative flow 4: The code file cannot be modified

A4. If the system cannot open the code file to modify it, the user is warned about the error and the modification is cancelled.

Alternative flow 5: Eclipse refactoring

A5. If the user performs Eclipse refactoring while the UI designer is open, the system will inform the user that refactoring was performed and components in the designers have been updated accordingly.

3. SUBFLOWS

4. KEY SCENARIOS

5. PRECONDITIONS

5.1 The UI designer is running and has one or more containers
Container properties can only be altered when the UI designer is running.

6. POSTCONDITIONS

6.1 The property of the selected component is changed
The modified property value is visible in the property list. If the property affects a component UI, then the component will be redrawn according to the new property values.

6.2 The undo feature is available
The undo feature allows the user to undo the changes made.

7. Extension Points

8. Special Requirements

9. Additional Information

---

Comments:

Back to main DSDP-MTJ Use Cases