DSDP/MTJ/Modify Screen

Use-Case Specification: Modify Screen

1. BRIEF DESCRIPTION

Screen components in the flow have several properties that can be altered by the user. Screen component properties define the behaviour and look and feel of the screen in the application. Single or multiple screens can be selected for modification.

2. FLOW OF EVENTS

2.1 Basic Flow of Events

B1. The user decides to modify a screen.

B2. The user selects the screen component he wants to modify and opens the property editor.

a) The system opens the properties view for the selected screen.

B3. The user modifies the properties.

B4. The user finishes modifying and saves the changes.

a) The system updates the code according to the user’s changes.

b) The system updates the flow design’s code.

c) The system redraws the Flow designers UI.

2.2 Alternative Flows

Alternative Flow 1: Multiple screen modifying

A1. The user performs a multi-selection of several screens.

a) The system marks the screens that have been selected.

b) The system displays a property view with the properties that the selected screens have in common available for selection.

A2. The user modifies the properties.

A3. The user finishes modifying the properties and saves the changes.

a) The system updates the code according to the user’s changes.

b) The system updates the flow design’s code.

c) The system redraws the Flow designers UI.

Alternative Flow 2: Eclipse refactoring while the Flow designer is open

A4. If the user performs Eclipse refactoring when the Flow designer is open, the system will inform the user that refactoring was performed and components in the Flow designer have been updated accordingly.

Alternative Flow 4: Eclipse refactoring while the Flow designer is closed

A5. The user refactors the code using Eclipse’s refactoring tool.

a) The system updates the flow according to the refactoring.

A6. The user opens the Flow designer. The flow is updated according to the refactored code.

Exception 1: The file is locked by another application or editor

A7. The user modifies the properties of a screen of which the file is locked by another application.

A8. The user finishes modifying and saves the file.

a) The system shows an error message explaining why the error has occurred.

b) The modifications are not applied.

3. SUBFLOWS

4. KEY SCENARIOS

5. PRECONDITIONS

5.1 Precondition 1: The Flow designer is open The Flow designer must be open with an active flow present.

5.2 Precondition 2: The user has created a screen and it is within the active flow The active flow in the Flow designer must contain a screen that can be modified.

6. POSTCONDITIONS

6.1 Postcondition 1: The screen is modified according to the user’s actions

7. EXTENSION POINTS

8. SPECIAL REQUIREMENTS

9. ADDITIONAL INFORMATION

---

Comments:

Back to main DSDP-MTJ Use Cases