Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
DSDP/MTJ/Modify Application Start
Use-Case Specification: Modify Application Start
1. BRIEF DESCRIPTION
The user can change the properties of the application start component.
2. FLOW OF EVENTS
2.1 Basic Flow of Events
- B1. The user decides to modify the application start component (e.g. MIDlet class) properties.
- B2. The user selects the application start component he wants to modify.
- B3. The user selects the properties list view for the application start component.
- a) The system shows the list of available properties for the application start component.
- B4. The user selects the property he wants to modify.
- a) The system opens the property editor for the selected property.
- B5. The user modifies the property and accepts the change.
- a) The system updates the code according to the changes made.
- b) The system updates the UI of the flow designer component.
2.2 Alternative Flows
- Alternative Flow 1: The user inputs an invalid value for the property
- A1. If the user gives an invalid new value for the property being altered, the system will warn the user about the invalid value and reverts the property back to its original value.
- Alternative Flow 2: The user edits the code for the application start
- A2. If the user edits the code for the application start, the system notices the changed code when the user saves the code. Then system will update the application start component in the flow accordingly.
- Alternative Flow 3: Eclipse refactoring while the Flow designer is open
- A3. 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 designers have been updated accordingly.
- Alternative Flow 4: Eclipse refactoring while the Flow designer is closed
- A4. The user refactors the code using Eclipse’s refactoring tool.
- a) The system updates the flow according to refactoring.
- A5. The user opens the Flow designer. The flow is updated according to the refactored code.
3. SUBFLOWS
4. KEY SCENARIOS
5. PRECONDITIONS
5.1 Precondition 1: The Flow designer is open and has one application start component
6. POSTCONDITIONS
6.1 Postcondition 1: The component is updated according to the changes made
6.2 Postcondition 2: The undo feature is available
The undo feature is available to undo the latest change to properties.
7. EXTENSION POINTS
8. SPECIAL REQUIREMENTS
9. ADDITIONAL INFORMATION
Comments:
Back to main DSDP-MTJ Use Cases