Siebel Business Process Framework: Task UI Guide > Implementing Task UI > Scenario for Iterative Development of a Task UI Implementation >
Designing the Task UI
At this point, User A is ready to start working with User C, who is an expert in human-computer interaction, but also familiar with the Expense Report business object and its underlying data model. Together, they sketch on a whiteboard the layout of the identified views. User C identifies business components that will be (re)used, as well as applets that will be created for the two new tasks (Submit expense report and Review expense report).
One important design decision that must be made at this point is the determination of whether all expense items should be created in the same view, or whether each item should be created in a separate view. After some brainstorming—including considering that most users will use this task quite frequently—User A and User C agree that productivity is more important than UI simplicity, and they conclude that all items should be created in the same view.
As an advantage of this top-down approach, User C realizes the possibility of reuse for a pair of applets in two similar views: the third view in the submission task displays the same data as the only view in the review task.