1. Chapter 8 Work Reengineering and Conceptual Design

2. Work Reengineering Realizing the power and efficiency that automation makes possible Reengineering the work to more effectively support business goals Minimizing retraining

3. “Task Allocation” Creating and Assigning individual actions to the user or the computer  First, the current system is analyzed. And with it the Task Scenario is created.  Using that, a general Use Scenario is made to outline a rough design for the reengineered system.

4. Task Allocation really starts with the creation of the Essential Use Cases… The Essential Use Case does not contain details but does layout the expected necessary tasks. Essential Use Cases focus on showing the interaction between the user tasks and system tasks

5. CONCEPT DESIGN The process of establishing the underlying organization & structure of a UI. Content Diagrams are “low-fidelity” prototypes that represent the designer’s perspective on the organization and structure. (later) A Concrete Use Case can be derived from the Essential Use Case. It is practically the same, but contains likely details to focus the cases. The next step in concept design is to objectify the use cases….

6. Identifying Objects Task Objects AttributesActions  academic  CD-ROM title  research student year email address View Add Print Delete Save

7. Task Object Actions available for Task Object Properties of Task Object Child/Parent Task Objects Each Task Object is connected to others to form the prototype

8. The Content Diagram is a network of containers & links. Content Diagram Example container template:

9. The Main Container

10. A web page that corresponds to a possible content diagram The Final Result Part of the Main container The Enter Search container From the View Updates container A web page that corresponds to a possible content diagram