DSDP/MTJ/Add Component

Use-Case Specification: Add component to UI container

1. BRIEF DESCRIPTION

The user opens the UI designer for the base container component. The UI designer allows the user to add components to the container.

2. FLOW OF EVENTS

2.1 Basic Flow of Events

B1. The user selects the component to add from the list of available components.

B2. The user places the component in the container.

a) The system adds the component to the container in the UI designer.

b) The system asks for any mandatory properties from the user (e.g. component name).

c) The system generates code for the component added.

d) The system updates the component’s properties list.

B3. The user can modify the component’s properties.

2.2 Alternative Flows

Alternative Flow 1: The UI container does not allow a UI component to be added

A1. If the UI container does not support the UI component type that the user is adding, the UI designer will show a visual indication that states the user has tried to add an invalid component. Optionally, there could be an informative message telling the user why the operation was denied/failed.

Alternative Flow 2: The user tries to place a component at an invalid position in the UI container

A2. If the user tries to place the new component 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.

Alternative Flow 3: The user gives an invalid mandatory property value

A3. If the user gives an invalid value for a mandatory property, e.g. name, the user is warned about the error and is asked to enter the property value again.

3. SUBFLOWS

4. KEY SCENARIOS

5. PRECONDITIONS

5.1 Precondition 1: The UI container component has been created

The user must first create a container component, into which the user can add UI components.

5.2 Precondition 2: The UI designer is opened for container components

The UI designer is open for the UI container component. The component list is open.

6. POSTCONDITIONS

6.1 Postcondition 1: The UI component is added to the UI designer

The UI designer shows a new UI component and the component’s properties.

6.2 Postcondition 2: The code for the component has been created

The system has created the code file for the new component. Possible changes that the user has made to the properties are applied to the code.

7. EXTENSION POINTS

8. SPECIAL REQUIREMENTS

9. ADDITIONAL INFORMATION

---

Comments:

Back to main DSDP-MTJ Use Cases