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/Create New Flow"
m (Create New Flow moved to DSDP/MTJ/Create New Flow) |
|
(No difference)
|
Latest revision as of 13:43, 27 May 2008
Use-Case Specification: Create New Flow
1. BRIEF DESCRIPTION
The user creates a new flow in the flow designer.
2. FLOW OF EVENTS
2.1 Basic Flow of Events
- B1. The user decides to create a new flow.
- B2. The user selects the New Flow –feature.
- a) The system starts the New Flow –wizard.
- B3. The user selects the application model.
- B4. The user selects the UI toolkit.
- B5. The user inputs the class and package name for the application start-up point class (e.g. MIDlet).
- B6. The user closes the wizard.
- a) The system creates the code according to user’s selections.
- b) The system creates a new flow window.
- c) The system adds an application start to the flow.
- d) The system adds an application end to the flow.
2.2 Alternative Flows
- Alternative flow 1: The user uses an existing class as the start-up and ending point
- A1. The user creates a new flow with the wizard.
- A2. The user deselects the choice to create a new application start-up and ending point class from the wizard.
- A3. The user closes the wizard.
- a) The system creates the flow without an application start-up and ending point.
- A4. The user adds an existing class to the wizard that is suitable for the start-up and ending point.
- a) The system recognises that the added class is a start-up and ending class and visualises it accordingly within the flow.
- Alternative Flow 2: The user does not give a package name
- A5. If the user leaves the package name empty, the class is created according to the default package.
- Alternative Flow 3: The user gives an invalid name for the class
- A6. The user enters a name for the application start-up point class.
- a) The system notifies the user and asks for a new name until the user has provided a valid name for the class. The user can cancel the wizard if he wants.
- A6. The user enters a name for the application start-up point class.
- Alternative Flow 4: The user creates a flow during project creation
- A7. The user creates a new project with MTJ’s wizard.
- A8. The user requests the wizard to also create a new Flow Diagram.
- a) The system starts the New Flow Diagram wizard after project is created.
3. SUBFLOWS
4. KEY SCENARIOS
5. PRECONDITIONS
5.1 Precondition 1: The user has an open project
6. POSTCONDITIONS
6.1 Postcondition 1: A new flow with the application’s start-up and ending points is created
The flow created will contain application start-up and end in the flow designer.
6.2 Postcondition 2: The code associated with the flow is created
The code is created for the MIDlet and the commandhandler.
7. EXTENSION POINTS
8. SPECIAL REQUIREMENTS
9. ADDITIONAL INFORMATION
Comments:
Back to main DSDP-MTJ Use Cases