Introducing 

Prezi AI.

Your new presentation assistant.

Refine, enhance, and tailor your content, source relevant images, and edit visuals quicker than ever before.

Loading…
Transcript

case studies

new media, interactive installations, software artworks

Trifonova and Jaccheri

• requirements are difficult as they may be vague and changeable,

• risk analysis is crucial to these types of projects,

• interaction is very important but it is difficult

to gauge ahead of time how an audience will react with a result that early prototyping is needed,

• artists and software developers have different

process and tools but both groups can benefit from the other.

25 works, software

engineering problems

Biswas and Singh

• Requirement challenges

• system analysis and design challenges

• development and coding challenges

• test and validation challenges

Marchese

the processes assisted in managing risk, time, people and budgets

Steinheider and Legrady

psychological perspective

• co-located inclusive team building to improve collaboration,

• a single kick-off meeting with all team members present,

• regular reviews of prototypes,

• communication of team interdependencies to

remind everybody of their roll,

• team members should accept the stress of

initial uncertainty,

• team leaders should trust team members and

their expertise.

creativity as

process

software development

process

good for projects where the requirements change

Agile

Bunt: "cycles are shorter and the software does not develop in a linear hierarchical fashion"

Cognitive psychological

approach

individuals and interactions are valued over processes and tools

(a) preparation

(b) incubation

(c) illumination

(d) verification

Four stage model

simultaneous stages

cycling

stages not as defined

focus on sub-processes

More dynamic model

short iterative cycles

Geneplore

Finke, Ward and Smith 1992

oscillates between the two sets of processes

generative and exploratory

emergent - processes determined during project

Goal oreinted vs exploratory

iteration

Candy and Edmonds 2002

digital artwork collaborations

both approaches can be useful

process which supports planned

and exploratory approach

frequent demos

communication

with community

re-usable re-mixable

artist

coder

in progress

can cope with unknown requirements that change at the last minute

tries not to

predict outcome

tries to deliver

what is wanted

qualitative

Research

artist experience

play

plan

email discussion

questionnaire

explore

minimise risks

forum discussion

good for capturing view and experiences

literature

google docs

requirements from customer

values

unpredictable

results

well known international digital artists

openframeworks forum

organised from process point of view

c++ library collection for artists

code as medium

Hayles: "computer ... is a mind amplification tool"

explore

manifests when it runs not when it is written

can remix existing code

repeats easily

with different

results

Galloway, Hayles

Tribe

Davis

Investigating the Software artwork creation process from an Agile perspective.

linguistic

Maia Grotepass

Bunt, Lee

Digital Arts Division

Wits School of Arts

University of the Witwatersrand

ambiguity, all options need to be coded in case of a narrative

maiatoday@gmail.com

Hayles

supervisors:

Tegan Bristow

Stephen Levitt

Learn more about creating dynamic, engaging presentations with Prezi