Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Business Process Framework: Task UI Guide > Scenario for Developing a Task UI > Overview of Scenario for Developing a Task UIThe example in this topic describes how to develop a task UI. The scenario describes work that the following individuals perform:
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.
About Iterative DevelopmentTo 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. |
![]() ![]() |
Siebel Business Process Framework: Task UI Guide | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |