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 Operation Triggering

< DSDP‎ | MTJ(Redirected from Modify Operation Triggering)

Use-Case Specification: Modify pre- and post- command handling


1. BRIEF DESCRIPTION

This use-case describes how pre- and post- command handling functionality can be modified.


2. FLOW OF EVENTS

2.1 Basic Flow of Events

B1. The user decides to modify pre- and post- command handling.
B2. The user selects the command/menu item that contains pre- and post- command handling.
a) The system opens the properties view for the command/menu.
B3. The user selects the existing pre- or post- command handling feature.
a) The system shows a list of classes with suitable methods for pre- and post- command handling.
B4. The user selects the class to use for pre- or post- command handling.
a) The system shows a list of suitable methods for pre- or post- command handling within the selected class.
B5. The user selects the method.
a) The system updates the code according to the user’s selections.
b) The system updates the flow’s code.
c) The system redraws the flow.

2.2 Alternative Flows

Alternative flow 1: The user changes the method to call from code directly
A1. The user changes the method that is called upon pre- or post- command handling.
A2. The user saves the changes.
A3. The user opens the Flow designer.
a) The system shows an information message that the method is no longer available in the pre- or post- command handling function.
Alternative flow 2: The user changes/removes the method name directly from the code
A4. The user changes/removes the method that is called upon pre- or post- command handling.
A5. The user saves the changes.
A6. The user opens the Flow designer.
a) The system shows an information message that the method is no longer available in the pre- or post- command handling function.


3. SUBFLOWS


4. KEY SCENARIOS


5. PRECONDITIONS

5.1 Precondition 1: The Flow designer is open with a flow diagram present

The Flow designer should be open with an active flow diagram present.

5.2 Precondition 2: The active flow must contain a pre- or post- command handling function

The active flow diagram must contain a pre- or post- command handling function.


6. POSTCONDITIONS

6.1 Postcondition 1: The pre- or post- command handling is modified according to the user’s changes

The pre- or post- command handling is modified according to the user’s actions. The code can be compiled and the undo feature is available.


7. EXTENSION POINTS


8. SPECIAL REQUIREMENTS


9. ADDITIONAL INFORMATION



Comments:


Back to main DSDP-MTJ Use Cases

Back to the top