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.
Difference between revisions of "DSDP/MTJ/Add Application Start"
m (Add Application Start moved to DSDP/MTJ/Add Application Start) |
|
(No difference)
|
Latest revision as of 13:43, 27 May 2008
Use-Case Specification: Add Application Start
1. BRIEF DESCRIPTION
The user can add an application start to the flow as the initial state of the application.
2. FLOW OF EVENTS
2.1 Basic Flow of Events
- B1. The user decides to add an application start.
- a) The system shows the application start types available for the flow’s current UI toolkit.
- B2. The user selects the application start component from the component list.
- B3. The user places the application start within the flow.
- a) The system queries mandatory properties (e.g. name) for the application start component.
- B4. The user inputs and accepts the mandatory properties for the application start component.
- a) The system creates the base class for the application model (e.g. MIDlet) and the required methods for it.
- b) The system adds the application start component to the flow.
2.2 Alternative Flows
- Alternative flow 1: The flow already contains an application start component
- A1. If the flow already contains an application start component, the user will be warned about the situation and adding a new application start component is cancelled.
3. SUBFLOWS
4. KEY SCENARIOS
5. PRECONDITIONS
5.1 Precondition 1: The flow without an application start is open
An application start can only be added to an existing and open flow that doesn’t have an application start.
6. POSTCONDITIONS
6.1 Postcondition 1: The code is created for the application start
6.2 Postcondition 2: The application start component is included in the flow
The component in the flow is accessible; it can be moved, etc.
7. EXTENSION POINTS
8. SPECIAL REQUIREMENTS
9. ADDITIONAL INFORMATION
Comments:
Back to main DSDP-MTJ Use Cases