DSDP/MTJ/Install Alert

Use-Case Specification: Install Alert/Dialog

1. BRIEF DESCRIPTION

The user can install a new alert/dialog component.

2. FLOW OF EVENTS

2.1 Basic Flow of Events

B1. The user decides to install a new alert component.

B2. The user copies the new alert/dialog component’s file(s) into Eclipse’s folder.

B3. The user starts Eclipse.

a) The system updates the installed component to the list of available flow designer components. Installed component can also add new component group.

2.2 Alternative flows

Alternative flow 1: Alert/Dialog location is corrupt (e.g. jar file is corrupt)

A1. The system will show the user an error message that explains what has happened. The installation is aborted.

Alternative flow 2: The location contains no alert/dialog to install

A2. The system ignores the plug-in.

Alternative flow 3: The Alert/Dialog already exists

A3. The system checks if this is an update to an existing alert/dialog. If so, the newer version will be being used. Otherwise, the plug-in will be ignored.

Alternative flow 4: The Flow designer is open with the wrong UI toolkit

A4. The installed custom alert/dialog is not displayed in the list of available Flow designer components.

3. SUBFLOWS

4. KEY SCENARIOS

5. PRECONDITIONS

5.1 Precondition 1: The user has the Alert/Dialog he wants to install as a plug-in

6. POSTCONDITIONS

6.1 Postcondition 1: The new Alert/Dialog component is available in the system

7. EXTENSION POINTS

8. SPECIAL REQUIREMENTS

9. ADDITIONAL INFORMATION

---

Comments:

Back to main DSDP-MTJ Use Cases