Design-Informing Models

Get Started. It's Free
or sign up with your email address
Design-Informing Models by Mind Map: Design-Informing Models

1. Envisioned DIM

1.1. transition from the existing to the envisioned

1.2. when the new work practice and supporting system are quite different from the existing ones

1.3. can just address the differences between both existing and envisioned

2. Types

2.1. Flow

2.1.1. guides

2.1.1.1. to make flows more efficient

2.1.1.2. to avoid

2.1.1.2.1. redundant data entry

2.1.1.2.2. unnecessary physical motions

2.2. Physical

2.3. Artifact

2.4. Sequence = different task models

2.4.1. to reduce and automate steps

2.5. Cultural = Social

2.5.1. diagrammatic description

2.5.1.1. address concerns of people in work roles

2.5.1.2. captures social aspects of the users organizational workplace

2.5.1.3. including the overall flavor, philosophy, ambiance ad environmental factors

2.5.1.4. thought processes, mind-sets, policies, feelings, attitudes, concerns and influences, norms of behavior, attitudes and pressures that affect users

2.5.2. guide

2.5.2.1. find ways to increase communication

2.5.2.2. reinforce positive values

3. Definition

3.1. artifacts that embody, drive, inform and inspire the design

3.2. Design-Oriented Constructs

3.2.1. task descriptions

3.2.2. turn raw data into actionable items

3.2.2.1. as design ideas

3.2.2.2. elements to consider or take into account in the design

3.2.3. personas

3.3. help integrate and summarize the contextual data

3.4. point back to the data, to maintain the " chain of custody"

3.4.1. to ensure that the design is based on real contextual data

3.5. provide shared focus for analysis now and, later, design

3.6. provide intermediate deliverables

3.6.1. important to your working relationship with the customer

3.7. Springboards to

3.7.1. design scenarios

3.7.2. sketches

3.7.3. storyboarding

4. Barriers

4.1. problem that interferes with normal operations of user work practice

4.2. anything that

4.2.1. impedes user activities

4.2.2. interrups work flow or communications

4.2.3. interferes with the performance of work responsibilities

4.3. need to be solved

4.4. identified

4.5. are represented in the DIM

5. Label

5.1. everything in a model

5.2. with an identifier tag

5.2.1. line number

5.2.2. time code

5.2.3. note number

5.2.4. WAAD node ID

5.3. points directly to the original source

5.4. allows team to get back to the raw data

5.4.1. to resolve questions, disagreements or interpretations of the data

6. User Models

6.1. set of models

6.2. define who the users are

6.3. include everything about work roles, sub-roles, user class definitions and personas

6.4. user personas

6.4.1. Contextual data representation

6.4.2. hypothetical but specific " character " in a specific role, with specific user class characteristics

6.4.3. for making users real to designers

6.4.4. story and description of a realistic individual

6.4.4.1. name

6.4.4.2. life

6.4.4.3. peresonality

6.4.5. limit design focus to something specific

6.5. User Class

6.5.1. user population

6.5.1.1. relevant characteristics

6.5.1.1.1. demographics

6.5.1.1.2. skills

6.5.1.1.3. knowledge

6.5.1.1.4. experience

6.5.1.1.5. special needs

6.5.1.2. particular work role

6.5.1.3. physiological characteristics

6.5.1.3.1. accessibility issues

6.5.1.4. experience-based characteristics

6.5.2. description

6.5.3. can include subclass

6.6. Work Roles

6.6.1. Sub-role

6.6.1.1. different subsets of the tasks the work role does

6.6.2. About

6.6.2.1. set of responsibilities

6.6.2.1.1. within an activity

6.6.2.1.2. assumed by a human

6.6.2.1.3. to a focal system

6.6.2.2. duties functions and work activities of a person with a certain job title or responsibility

6.6.2.3. involve

6.6.2.3.1. system usage or not

6.6.2.3.2. internal or external to the organization

6.6.3. Envisioned Work Roles

6.7. Social Models

6.7.1. users organizational workplace

6.7.1.1. overall flavor

6.7.1.2. philosophy

6.7.1.3. ambiance

6.7.1.4. environmental factors

6.7.2. about

6.7.2.1. thought processes

6.7.2.2. mind-sets

6.7.2.3. policies

6.7.2.4. feelings

6.7.2.5. attitdes

6.7.2.6. terminology in the work environment

6.7.2.7. concerns

6.7.2.8. issues

6.7.2.9. how people approach and do their work

6.7.3. social aspects

6.7.3.1. social milieu

6.7.3.2. social ambiance

6.7.3.3. social interaction

6.7.3.3.1. explicit

6.7.3.3.2. implicit

6.7.4. position factors

6.7.4.1. influence

6.7.4.2. political structure of the organization

6.7.4.3. user ogals

6.7.4.4. job-related factors

6.7.4.4.1. job description

6.7.4.4.2. location

6.7.4.4.3. level of responsibility

6.7.4.4.4. motivational factors

6.7.4.4.5. attitudes toward the system

6.7.5. representation

6.7.5.1. nodes

6.7.5.1.1. active roles/entities

6.7.5.1.2. groups and subgroups of roles

6.7.5.1.3. system-related roles

6.7.5.1.4. workplace ambiance

6.7.5.2. arcs

6.7.5.2.1. social relationships

6.7.5.2.2. influence by role on another

6.7.5.2.3. relationships among entities

6.7.5.3. attributes of nodes

6.7.5.3.1. concerns

6.7.5.3.2. perspectives

6.7.5.3.3. label nodes with associated concerns

6.7.6. work environment model

6.7.6.1. defines the milieu in which work gets done

6.7.6.2. induding constraints and artifact and physical models

7. INPUTS

7.1. Extract Imputs

7.1.1. in conjunction w/ requirements extraction

7.1.2. take notes on DIM when traverse the WAAD for extracting requirements

7.1.3. references to

7.1.3.1. task descriptions

7.1.3.2. user types

7.1.3.3. social concerns

7.1.3.4. etc.

7.1.3.5. indirect or implied and sometimes oblique

7.1.4. work activity notes

7.1.4.1. seldom complete descriptions of any component of a DIM

7.1.4.2. hints and clues and pieces of the puzzle

7.2. Bins of notes

7.2.1. from contextual analysis

7.2.1.1. seperate work activity note bins sorted out for each kind of model

7.2.1.2. seperate task related work activity notes into sub-bins

7.2.1.2.1. task sequences

7.2.1.2.2. scenario

7.2.1.2.3. etc

7.2.2. structured and ordered

7.2.3. provide inputs to drive synthesis of models type

7.3. Requirements

7.3.1. Contextual analysis

7.3.1.1. Wheel Lifecycle template

7.3.2. imputs for DIM

7.4. Data

7.4.1. Data Extraction

7.4.1.1. Other contextual data

7.4.1.2. Bins of sorted work activity notes

7.4.1.3. From the Work Activity Affinity Diagram

7.4.2. Labeled

8. Usage Models

8.1. Flow Model

8.1.1. picture of existing work processes

8.1.2. representation

8.1.2.1. like a plan view in architecture

8.1.2.2. workflow graph

8.1.2.2.1. nodes

8.1.2.2.2. arcs

8.1.2.3. barriers to work practice

8.1.2.3.1. problem that interferes with normal operations of user work practice

8.1.2.3.2. anything that impedes user activities

8.1.2.3.3. interrupts work flow or communications

8.1.2.3.4. interferes with the performance of work responsibilities

8.1.3. show territorial boundaries

8.1.3.1. seperation between enterprise and non-enterprise work roles

8.1.4. with whom and with what do the users in each work role interact

8.1.5. whether the system supports inter-role communication or users must do it on their own

8.2. Task Models

8.2.1. what users do or need to do in the work practice and environment

8.2.1.1. using system or not

8.2.2. include

8.2.2.1. task structure models

8.2.2.1.1. Hierarchical Task Inventory

8.2.2.2. task interaction models

8.2.2.2.1. Usage Scenarios

8.2.2.2.2. Step-by-step task interaction models (sequence model)

8.2.2.2.3. Essential Use Case

8.2.3. tasks vs function

8.2.3.1. tasks

8.2.3.1.1. refer to things a user does

8.2.3.2. function

8.2.3.2.1. things the system does

8.2.3.3. if uncertain

8.2.3.3.1. reference to both

8.2.4. Information Object Model

8.2.4.1. about

8.2.4.1.1. work domain objects shared by users and the system

8.2.4.1.2. entities that move through the workflow in the flow model

8.2.4.1.3. analyzing scenarios to identify ontology

8.2.4.2. information objects

8.2.4.2.1. have defining attributes

8.2.4.3. form

8.2.4.3.1. sketch

8.3. Storyboard

8.3.1. Visual scenario

8.3.2. depicting

8.3.2.1. actions

8.3.2.2. states

8.3.2.3. sequences of interaction flow between user and system

8.3.3. cartoon-like frames

8.3.3.1. series of sketches or graphical clips

8.3.3.2. often annotated