Lecture 6 representation techniques

DesignSustainability

Representation Techniques

Nicola Morelli

Nicola Morelli Design & Sustainability 2

A blueprint is the definitive drawing of an object/architecture, containing all the indications for producers to reproduce the object according to the designers’ intentions

Blueprinting PSS


Codification

Codification

Decodification


Technical codification


• If the customer is co-creating the value, s/he has to be supported by an adequate communication system

• We cannot suppose the customer to be familiar with the most common technical language used in blueprints

Customer’s involvement


codification


Different levels of codification

Representations communicate contents with different levels of

abstraction and codification


• While there are standard techniques for technical representation of objects in different levels of detail, there are no standard representation techniques for blueprinting PSS

• Blueprints for PSS should reach different kinds of people, from “hard” technicians (e.g. engineers) to final users

• Blueprints should communicate different things (conditions, instructions, components) according to the “receiver”– Traditional “hard” technician will understand

highly codified representations– Final users are not supposed to be familiar with

any form of communications, although their role in a PSS may be fundamental

Blueprinting PSS


• Time• Logical links/interactions• Sequence of events• Spaces and their qualities• Movements between spaces• Actors performing an action• Visible and invisible processes• Front office/back office• Objects/components• Interaction of objects/components in

the system

Blueprinting = representing


• What?– Entity/system– Objective/subjective

• What for?– Analysis/design– Sketch/define

• Whom for?– Technical/user

Representing what? Why? Who for?


Different views


The front view


System maps (colloquial)


System maps


Generating system maps


Functions and capabilities


Interaction and time


Blueprinting: existing methods

Source Shostack 1982



Source Shostack 1982

TimeLogical links/interactionsSequence of eventsSpaces and their qualitiesMovements between spacesActors performing an actionVisible and invisible processesFront office/back officeObjects/componentsInteraction of objects/components in the system



Source Ramaswami 1996


Use case graphic representation

Space and facilities maintenance

Billing system

John enters

The recep.ist welcomes John

The recep.ist informs John

The rec.ist introduces John to the room assistant

John logs in

John Works on his CV

The billing person processes the bill

John goes to pay the bill

John’s membership card is updated

John walks away

Entrance/reception

Working environment

John pays the bill

Processes implying physical movement

Processes performed by the user

The system verifies John’s identity and

gives him access to the software

John saves hi work

John logs out

The system saves John’s work in his directory

The system saves John’s settings

Human and/or automated operations

The accounting system registers the payment

The room assistant runs the software to clean up the computer

System back up

The system gets ready for the next user

Technical Maintenance and upgrade

Automated operation

Front office

Back office

Processes performed by the service operator

John is guided to the workstation

Vir

tual en

vir

on

men

t


Use case graphic representation



Existing methods: pert chart

A japanese restaurant (Nicola Morelli)


Example: a Japanese take-away

(Nicola Morelli)


Colloquial language


Use Cases/storyboards


Video Sketching


Scenario building and sketching


• Scenarios facilitate convergences of different views by stimulating strategic conversation between actors with different views

Representation as a tool


http://servicedesign.wikispaces.com/Video%20Prototypes

Lecture 6 representation techniques

Technology

Transcript of Lecture 6 representation techniques