DSDP/MTJ/Add Menu

Use-Case Specification: Add menu to UI container

1. BRIEF DESCRIPTION

This use-case describes how a menu is added to a UI container in the UI Designer. Typically in LCDUI applications the menu contains commands and in eSWT applications the menu contains menu items or commands

2. FLOW OF EVENTS

2.1 Basic Flow of Events

B1. The user decides to add a menu to the UI container in the UI designer.

B2. The user selects the menu component from the component list and adds it to the UI container.

a) The system adds the menu to the UI container and visualises it.

b) The system generates the required code for menu creation.

c) The system lists the menu component’s properties for the user.

B3. The user can modify the menu’s properties with editors.

2.2 Alternative Flows

Alternative flow 1: The user creates a sub-menu

A1. The user decides to add a submenu of an existing menu.

A2. The user selects the add menu feature.

A3. The user adds the menu to an existing menu in the UI container.

a) The system creates the code for the menu and sets it as a submenu of the existing menu.

b) The system adds the menu to the UI container as a submenu of the existing menu.

c) The system redraws the UI container.

d) The system lists the menu component’s properties for the user.

A4. The user can modify the menu’s properties with editors.

Alternative flow 2: The user creates a sub-menu with the properties editor

A5. The user decides to add a sub-menu to an existing menu.

A6. The user selects the add menu feature.

A7. The user places the menu in the UI container but not upon an existing menu.

a) The system adds the menu to the UI container and visualises it.

b) The system generates the required code for menu creation.

a) The system lists the menu component’s properties for the user.

A8. The user selects the parent menu from the menu component’s properties.

a) The system modifies the menu’s code so that it is set as a sub-menu of another menu.

b) The system adds the menu as a sub-menu of an existing menu.

c) The system redraws the UI container.

Alternative flow 3: Sub-menu creation is not allowed

A9. The user decides to add a submenu to an existing menu.

A10. The user selects the add menu feature and tries to place it upon an existing menu in the UI container.

a) The system shows a visual indication that the menu cannot be added as a sub-menu of the existing menu.

Alternative flow 4: The UI container does not allow a menu to be added

A11. If the UI container does not support the menu the user is adding, the UI designer will show a visual indication that states the user may not perform this task. Optionally, there could be an informative message telling the user why the operation was denied/failed.

Alternative flow 5: The user tries to place a menu at an invalid position in the UI container

A12. If the user tries to place a menu at a position where it cannot be added, there will be a visual indication about invalid placement. Optionally, there could be an informative message telling the user why the operation was denied/failed.

3. SUBFLOWS

4. KEY SCENARIOS

5. PRECONDITIONS

5.1 Precondition 1: The UI designer is open and contains a UI container
The UI designer must be open and include an active UI container.

6. POSTCONDITIONS

6.1 Postcondition 1: A menu component is added to the UI container
A menu component is added to the UI container.

6.2 Postcondition 2: The code for the menu is created
The code required for menu creation is created.

7. EXTENSION POINTS

8. SPECIAL REQUIREMENTS

9. ADDITIONAL INFORMATION

---

Comments:

Back to main DSDP-MTJ Use Cases