Siebel Business Process Framework: Task UI Guide > Scenario for Developing a Task UI >

Overview of Scenario for Developing a Task UI

The example in this topic describes how to develop a task UI. The scenario describes work that the following individuals perform:

• Business Analyst. Possesses detailed knowledge of the way the organization does financial planning and reporting. The analyst possesses detailed knowledge of various technologies, from personal computers to wireless personal devices, but possesses no experience using a formal programming language.
• Application Developer. Possesses a computer science degree and a strong technical background, including five years experience creating applications.
• Usability Analyst. Possesses a degree in art history and a technical background, including five years experience designing interfaces. In the last two years the interface developer created user interfaces for various customizations of a predefined Siebel application.
• Information Technology Director. Drives the business process management initiative at the organization that optimizes and automates business processes.

This chapter describes job roles in the context of a fictional organization. Job roles, job titles, and division of labor might vary significantly for your organization.

For more information about:

• General technical procedures, see Roadmap for Developing a Task UI.
• Specific technical procedures, see Examples of Developing a Task UI.

About Iterative Development

To minimize the risk of project failure, your development process can be iterative and incremental. Using an iterative technique means feedback from a phase can cause reiteration of a previous phases. For example, a significant performance issue might require a UI redesign that causes a reiteration of subsequent phases.

Using an incremental technique means that the best way to mitigate the risks of using new technology, such as Siebel Task UI, is to begin with a smaller scope, deliver it to customers, and then use customer feedback to incrementally create functionality. For brevity, this chapter does not fully describe iterations and incremental releases. However, most implementations include iterations and incremental releases, and it is recommended that you plan for them.