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/Add Event

< DSDP‎ | MTJ

Use-Case Specification: Add Event


1. BRIEF DESCRIPTION

The user can add an event to a component in the UI designer.


2. FLOW OF EVENTS

2.1 Basic Flow of Events

B1. The user decides to add an event to the component.
B2. The user selects the component to which he wants to add a new event.
B3. The user selects the event add –feature.
a) The system shows a list of events available for the selected component.
B4. The user selects the event he wants to add from the list of available events.
a) The system asks for the event listener implementation method from the user.
B5. The user selects the event listener implementation method.
a) The system asks for the mandatory properties for the new event from the user.
b) The system adds the code for the new event.
c) The system adds a new event into the list of events for the selected component.
d) The system adds the new event to other proper event lists in the UI designer.

2.2 Alternative flows

Alternative flow 1: The user adds a new event to the code
A1. If the user adds a new event to the code the system will notice that the code has been changed and re-parses the code for design. This effectively adds the new event to the UI design.
Alternative flow 2: The user gives an invalid mandatory property value
A2. 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.
Alternative flow 3: The code file cannot be created
A3. The user is informed about the error and component addition is cancelled.


3. SUBFLOWS


4. KEY SCENARIOS


5. PRECONDITIONS

5.1 The UI designer is open and has at least one component that allows events
Events are associated with UI components, so events can only be added when the UI designer is open and has components that allow events.


6. POSTCONDITIONS

6.1 Postcondition 1: The code is created for the new event
Code is generated and the file can be opened for editing.

6.2 Postcondition 2: The new event is available in component’s event list
Selecting the component’s event list shows the newly added event included.

6.3 Postcondition 3: The event’s properties are modifiable
The user can select the event and modify its properties.

6.4 Postcondition 4: The undo feature is available
The undo feature allows the user to undo the addition of the event.


7. EXTENSION POINTS


8. SPECIAL REQUIREMENTS


9. ADDITIONAL INFORMATION



Comments:


Back to main DSDP-MTJ Use Cases

Back to the top