Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

DSDP/MTJ/Modify Menu

< DSDP‎ | MTJ

Use-Case Specification: Modify menu in UI Designer


1. BRIEF DESCRIPTION

This use-case describes how the menu can be modified using the UI designer.


2. FLOW OF EVENTS

2.1 Basic Flow of Events

B1. The user decides to modify the menu.

B2. The user selects the menu to modify.

a) The system reveals the properties view for the selected menu.
b) The system activates the in-place editor.
B3. The user modifies the menu’s properties.
i) The user can add menu items.
ii) The user can remove menu items.
iii) The user can rename menu items.
iv) The user can change the order of menu items.
v) The user can change the menu to a sub-menu or remove it from being a sub-menu.
B4. The user saves his changes to the menu.
a) The system generates and modifies the code according the changes.
b) The system redraws the UI design.

2.2 Alternative flows

Alternative flow 1: The user modifies the menu using the in-place editor
A1. The user decides to modify the menu.
A2. The user selects the menu to modify.
a) The system reveals the properties view for the selected menu.
b) The system activates the in-place editor.
A3. The user modifies the menu using the in-place editor.
i) The user can add menu items.
ii) The user can remove menu items.
iii) The user can rename menu items.
A4. The user saves his changes to the menu.
a) The system generates and modifies the code according the changes.
b) The system redraws the UI design.
Alternative flow 2: The user modifies the menu from code
A5. The user modifies the menu directly in the code.
A6. The user compiles and saves the changes.
A7. The user opens the container class in the UI designer.
a) The system redraws the UI design.
Alternative flow 3: The user gives a wrong value for the menu properties
A8. The system will show an error message. After the user has accepted the message, the system restores the original value.
Alternative flow 4: The code file is locked by another editor and the code cannot be updated.
A9. The system shows an error message explaining why the modifications cannot be made. The changes made will not be saved until the file lock is removed and saving is tried again.
Exception 3: The user modifies the menu code so that it does not compile
A10. The user modifies the menu code so that it does not compile in the code editor.
A11. The user tries to open it in UI designer.
a) The system shows an error message explaining that the file cannot be opened in UI designer because it does not compile.


3. SUBFLOWS


4. KEY SCENARIOS


5. PRECONDITIONS

5.1 Precondition 1: The user has created a menu to modify
The user must have created a menu that can be modified

5.2 Precondition 2: The UI designer is open and the UI design with the menu is open and active To modify the menu the UI designer must be open. It must also contain the UI design with the menu to be modified.


6. POSTCONDITIONS

6.1 Postcondition 1: The menu is modified according to the user’s action and the generated/modified code compiles


7. EXTENSION POINTS


8. SPECIAL REQUIREMENTS

9. ADDITIONAL INFORMATION



Comments:


Back to main DSDP-MTJ Use Cases

Back to the top