chapter 8 work reengineering and conceptual design

Chapter 8Chapter 8

Work reengineering andWork reengineering andconceptual designconceptual design

UIDE Chapter 8UIDE Chapter 8

•Introduction to the Digital Introduction to the Digital LibraryLibrary

•Work Reengineering for Work Reengineering for the Digital Librarythe Digital Library

•Task Allocation for the Task Allocation for the Digital LibraryDigital Library


Digital LibraryDigital Library

• Individuals have personal libraries to Individuals have personal libraries to shareshare

• New Digital Library will keep track of New Digital Library will keep track of personal resources.personal resources.


Work ReengineeringWork Reengineering

• Work differently if to work effectivelyWork differently if to work effectively

• Goals:Goals:– Power and efficiency that automation Power and efficiency that automation

makes possiblemakes possible– More effectively support business goalsMore effectively support business goals– Minimize retrainingMinimize retraining


Task ScenariosTask Scenarios

• Use Scenario: description of the Use Scenario: description of the anticipated use of the new UI.anticipated use of the new UI.

• Task Scenario: represents the Task Scenario: represents the present situation.present situation.


Task ScenariosTask Scenarios


Use ScenarioUse Scenario


Task AllocationTask Allocation

• Sharing the different “essential” Sharing the different “essential” tasks between the user and the tasks between the user and the computer.computer.

• Essential use case:Essential use case:


Conceptual DesignConceptual Design• The process of establishing the The process of establishing the

underlying organization and underlying organization and structure of a UIstructure of a UIContent diagramContent diagram – low fidelity prototype – low fidelity prototype

that represents the organization and that represents the organization and structure of the user interface from the structure of the user interface from the designer’s perspective.designer’s perspective.


Content DiagramContent Diagram

• Design needs:Design needs:– Derived concrete use cases Derived concrete use cases – Identify primary task objects, attributes, Identify primary task objects, attributes,

actionsactions– Identify the containers and the task Identify the containers and the task

objects in each oneobjects in each one– Link containers to sLink containers to s– how navigation flow.how navigation flow.


Concrete Use CasesConcrete Use Cases

• Deriving from Essential Use case.Deriving from Essential Use case.


•Conceptual DesignConceptual Design

– Deriving Concrete Use Cases from Deriving Concrete Use Cases from Essential Use CasesEssential Use Cases

– Identifying Task Objects, Identifying Task Objects, Attributes, and ActionsAttributes, and Actions

•Task ObjectsTask Objects

•AttributesAttributes

•ActionsActions


Task Objects, Attributes, Task Objects, Attributes, ActionsActions

• Task Objects: units of information or Task Objects: units of information or data with which the users interact to data with which the users interact to carry out their tasks.carry out their tasks.– Includes Class objects, i.e. media types, Includes Class objects, i.e. media types,

members of the librarymembers of the library



• Attributes: task object componentsAttributes: task object components– Properties and Child ObjectsProperties and Child Objects

•Title and author are properties of bookTitle and author are properties of book

•Owner of CD-ROM is child object of CD-ROM Owner of CD-ROM is child object of CD-ROM because Owner has its own propertiesbecause Owner has its own properties



• Actions: actions performed on task Actions: actions performed on task objectsobjects– Allocating guests to rooms. (Add)Allocating guests to rooms. (Add)– Create, delete, copy , save, edit, etc.Create, delete, copy , save, edit, etc.


Marking up Concrete Use Marking up Concrete Use CasesCases

• Task objects – single underlineTask objects – single underline

• Attributes of objects – double Attributes of objects – double underlineunderline


Compilation of Concrete Use Compilation of Concrete Use CaseCase


– Marking Up the Concrete Use Cases Marking Up the Concrete Use Cases to Identify Task Objects, Their to Identify Task Objects, Their Attributes, and ActionsAttributes, and Actions

– Prototyping Task Objects, Prototyping Task Objects, Attributes, and ActionsAttributes, and Actions


PrototypingPrototyping

Use of “Sticky Notes to prototype task objects, attributes, and actions.



Template for Containers



Double Link



• Main ContainerMain Container


Other ContainersOther Containers


Enter Search CriteriaEnter Search Criteria


LinksLinks

• See SimPACS Flowchart DiagramSee SimPACS Flowchart Diagram


– Creating the Content DiagramCreating the Content Diagram

•Template for ContainersTemplate for Containers

•The Main ContainerThe Main Container

•OtherOther ContainersContainers

•LinksLinks

•Prototyping Containers and LinksPrototyping Containers and Links

•Final Thoughts on Conceptual DesignFinal Thoughts on Conceptual Design

chapter 8 work reengineering and conceptual design

Documents

containersuide chapter

task scenariosuide chapter

propertiesuide chapter

use scenariouide chapter

digital libraryuide

search criteriauide

primary task objects

task allocationsharing