Siebel Business Process Framework: Task UI Guide > Building a Task UI >

Roadmap for Developing a Task UI

To develop a task UI, perform the following processes and tasks:

1. Process of Building a Task UI
2. Process of Deploying a Task UI
3. Process of Testing a Task UI
4. Migrating a Task UI
5. Administering a Task UI

Note that these processes do not include analysis and design work. For more information, see:

• Determining Improvement Requirements
• Designing the Task UI

This topic provides a procedural overview for developing a Siebel Task UI. For examples that detail these procedures and the phases of a task UI implementation project, see Examples of Developing a Task UI.

Figure 15 illustrates the planning and development lifecycle of a task UI.

Figure 15. Planning and Development Lifecycle of a Task UI

The following steps are performed to develop a task UI:

1. Analyze. Analyze your business requirements and the job tasks that must be supported.
2. Design. Model the job task to be supported, then define a visual layout for the task UI.
3. Build. Build the task UI by defining objects in Siebel Tools. Example objects include the object definition of the task UI and task steps.
4. Deploy. Deploy your task UI by validating the logic of the task, publishing the object definitions of the task from the repository tables to the run-time tables, then activating the task for use in the Siebel client.
5. Test. Test, verify, and troubleshoot your task UI to make sure the objects and logic you defined meet the business requirements.
6. Migrate. Migrate the deployed task UI to the production environment. You can use a utility, such as ADM, REPIMEXP, or Import/Export.
7. Administer. Administer the migrated task UI in the production environment.

Note that while the lifecycle illustrated is a linear flow, the typical development cycle is iterative.