DSDP/MTJ/GENERIC SDK DEFINITION
Short description: Provide a method to allow the user to manually define an SDK when the definition does not exist. This will create the EMF data to recognize an SDK.
Owner: Kevin Horowitz
Community Review: Begin Review Feb. 21, 2007
1. Use Case Description This mechanism is intended to provide a simple way for the user to define a SDK when one is not found by the IDE when a device is created.
2. Basic Flow
- B1: The user is creating either a "Runtime Target" or a "Device Platform."
- B2: They see that the one they want is not defined already.
- B3: They go to add a new platform, and defines the root directory for the platform.
- B4: The system does not match any predefined rules for runtimes, and prompts the user to enter all of the required data for their platform:
- Platform Data (name, ...)
- Profile Data (name, library, ...)
- Configuration Data (name, library, ...) [ This is optional since not all systems separate out the configuration library
- Device Data (name, ...)
- Optional API Data (name, ...)
- B5: The user completes the addition by selecting the device for the runtime, and completing the configuration.
- B6: User uses the SDK in a project.
3. Alternate Flows
Alternate Flow : Device is not defined, but is already a know type of device. (Default example is a UEI device.)
- A1: The user goes to configure a device that is not defined already.
- A2: The user adds a new platform, and defines the root directory for the platform.
- A3: The platform matches one of the defined definitions, and the user is prompted to select the device for the runtime, and complete the configuration.
- The user has installed all the needed vendor SDKs in known locations.
- The user creates a project using the SDK definition.
6. Extension Points
7. Special Requirements
8. Additional Information